The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2003-Mar> msg00070



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

Fwd: MTU problems in EoMpls domain..

  • From: Roger Clark Williams <rogerw@nordlink.com>
  • Date: Thu, 20 Mar 2003 22:47:32 -0800
  • Resent-Date: Fri, 21 Mar 2003 03:20:22 -0500
  • To: MPLS-ops Mailing List <mpls-ops@mplsrc.com>
  • X-Sender: rogerw@together.net@pop.mindspring.com

Tarun, your issue is one of the classic trip-wire situations for MPLS. Since an MPLS/Ethernet frame is bigger than a normal Ethernet frame without labels, that bigger frame can be seen by some systems as an error, and the frame either dropped or fragmented, just as you say.

You may have to specifically set the MTU size for both the routers and switches. Though the routers may be MPLS-aware, the LAN interfaces, ie. Ethernet, don't automatically deal with jumbo frames. An MPLS frame would be the 1500 bytes of Ethernet plus the label(s) at 4 bytes each. You have to tell the routers what to do. Router WAN interfaces work differently. It is my understanding that the new MPLS Ethertypes carried in WAN headers inform the interfaces that a jumbo packet may be following, and the WAN interfaces on MPLS-aware routers will then accept it. Many non-MPLS-aware switches will discard these jumbo frames unless you tell them explicitly to allow them.

Look over this set of router commands....
interface fastethernet 0/0
mpls ip
mpls mtu 1512

and this switch command....
set port 1/3 jumbo enable

as possible candidates that may help.

Roger Williams




Resent-Date: Fri, 21 Mar 2003 00:31:26 -0500
X-Authentication-Warning: host.secure4-hosting.net: mplsrc12 set sender to mpls-ops-request@mplsrc.com using -f
From: "Tarun Bhalla" <tarun.bhalla@wipro.com>
To: <mpls-ops@mplsrc.com>
Date: Fri, 21 Mar 2003 10:11:49 -0800
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-OriginalArrivalTime: 21 Mar 2003 04:49:11.0877 (UTC) FILETIME=[3753CF50:01C2EF65]
Subject: [MPLS-OPS]: MTU problems in EoMpls domain..
Resent-From: mpls-ops@mplsrc.com
X-Mailing-List: <mpls-ops@mplsrc.com> archive/latest/5465
X-Loop: mpls-ops@mplsrc.com
Resent-Sender: mpls-ops-request@mplsrc.com

hi all,
 
I am new to this mailing list. so hi to all.. now my problems :((
Actually, I am trying to handle the problem of fragmentation in
Ethernet over MPLS network.
 
This is the existing network topology...
 
LAN A -------> MPLS Domain ----------> LAN B
 
To implement EoMPLS, I am capturing the packet in Ingress of the MPLS domain
and trying to send this as a payload over the MPLS domain.. When I
am doing this the problem is that the frames which are 1500 bytes (normal
ethernet frames) can not be sent across this MPLS domain as the payld
of this domain can only be 1496 bytes... (4 bytes label gets added and leave
the matter when multiple labels are added).. So, I am stuck as i am not
able to send 1500 bytes frames..
 
These all things are being carried on test setups. So, I can not
have the liberty or leisure to use SONET interfaces as my core n/w
interfaces.. also am not sure what to do in order to make use of jumbo
ethernet frames... So, the only option left is to fragment the frames when i
capture the ethernet frames.. but for that i need ur advice..
 
I mean is there any standard methodology that says how to handle
fragmentation in ethernet layer cos I will have to anyway go to this
final resort.. or is there any other way arnd. ??
 
Thanks & Regards
Tarun B
_________________________________________________
Tarun Bhalla
Wipro Technologies
26 Hosur Main Road,
Bommanahalli,
Bangalore- 560 068. India
Tel +91-80-5732293, Extn 3139 <http://www.wipro.com/>

 
 
------- The MPLS-OPS Mailing List Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml Archive: http://www.mplsrc.com/mpls-ops_archive.shtml