Scribd
Upload
63 views1 page

Mtu Between Ios and XR

The document discusses MTU sizes for interfaces on IOS-XE and IOS-XR routers. IOS-XR interfaces account for layer 2 overhead and have an MTU that is typically 14 bytes larger than equivalent IOS-XE interfaces. To allow VLAN tagging and a 1500 byte layer 3 payload, the MTUs need adjusting so the IOS-XR interface is set to 1514 and the IOS-XE interface is set to 1504.

Uploaded by

Mustafa Hussien
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
63 views1 page

Mtu Between Ios and XR

The document discusses MTU sizes for interfaces on IOS-XE and IOS-XR routers. IOS-XR interfaces account for layer 2 overhead and have an MTU that is typically 14 bytes larger than equivalent IOS-XE interfaces. To allow VLAN tagging and a 1500 byte layer 3 payload, the MTUs need adjusting so the IOS-XR interface is set to 1514 and the IOS-XE interface is set to 1504.

Uploaded by

Mustafa Hussien
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

MTU between IOS and XR

When calculating the MTU, you should


subtract the overhead. In the case of Both IOS-XE and IOS-XR
An MTU or Maximum ethernet this is the layer 2 header account for the FCS
Transmission Unit defines the information and FCS. automatically so don’t need to
size of the largest packet be considered when calculating
(Protocol Date Unit) that the In Ethernet the maximum Frame size is MTU. Only IOS-XE accounts for
layer is allowed to transmit over 1518. If you subtract the overhead you get the remaining layer 2 overhead.
an interface 1500. The breakdown is as follows:

1518 - Source MAC Address (6) - Cisco IOS-XR MTU commands will include
Destination MAC address (6) - EtherType (2) the following:
Cisco IOS-XE MTU commands will > The Layer2 overhead excluding the FCS
include the following: - FCS (4) = 1500
(4 bytes) and Frame Delimiter for ethernet
> Tag (VLAN) headers frames
> The L3 payload (including its This results in equivalent IOS MTUs being > Tag (VLAN) headers
headers) 14 bytes smaller than IOS-XR MTUs. > The L3 payload (including its headers)

interface Gi1 interface Gi0/0/0/0


mtu 1500 mtu 1514
No tagging
IOS-XE IOS-XR

If this link was PPP or HDCP the Layer 2 overhead excluding FCS and
IOS-XR side would be 1504 preamble = Source MAC Address (6)
(which included the PPP or HDLC + Destination MAC address (6) +
overhead) and the IOS-XE side EtherType (2) = 14. As a result of
would be 1500. this the default Ethernet (L2) MTU
in Cisco IOS-XR is 1514 bytes.

To enable the above link to carry one VLAN tag Note that this adjustment to allow a VLAN tag enables the
(802.1q, which is 4 bytes) and a packet of size Layer 3 payload to remain at 1500 bytes. Without this
1500, change the MTUs to the following: adjustment, only Layer 3 frames up to a maximum size of
1496 could be sent - however hosts typically send packets
IOS: 1500 + 4 = 1504 with 1500 bytes of data so this is not recommended if you
XR = 1514 + 4 = 1518 want to avoid fragmentation

R1#show interface gigabitEthernet 1


GigabitEthernet1 is up, line protocol is up
Hardware is CSR vNIC, address is 5000.0007.0000 (bia 5000.0007.0000)
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation 802.1Q Virtual LAN, Vlan ID 1., loopback not set
Keepalive set (10 sec)
Full Duplex, 1000Mbps, link type is auto, media type is RJ45
output flow-control is unsupported, input flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
RP/0/0/CPU0:XR1#show im database interface GigabitEthernet0/0/0/0
Last input 00:07:01, output 00:07:01, output hang never
Mon Apr 13 19:51:48.071 UTC
Last clearing of "show interface" counters never
Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0
View: OWN - Owner, L3P - Local 3rd Party, G3P - Global 3rd Party, LDP - Local
Queueing strategy: fifo
Data Plane
Output queue: 0/40 (size/max)
GDP - Global Data Plane, RED - Redundancy, UL - UL
5 minute input rate 3000 bits/sec, 4 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
Node 0/0/CPU0 (0x0)
3548717 packets input, 361003522 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
Interface GigabitEthernet0/0/0/0, ifh 0x00000040 (up, 1514)
0 runts, 0 giants, 0 throttles
Interface flags: 0x000000000150059f (ROOT_IS_HW|PHYS_ON_RP
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
|IFCONNECTOR|IFINDEX|SUP_NAMED_SUB|BROADCAST
0 watchdog, 0 multicast, 0 pause input
|CONFIG|HW|VIS|DATA|CONTROL)
961504 packets output, 84863980 bytes, 0 underruns
Encapsulation: ether
396 output errors, 0 collisions, 0 interface resets
Interface type: IFT_GETHERNET
0 unknown protocol drops
Control parent: None
0 babbles, 0 late collision, 0 deferred
Data parent: None
0 lost carrier, 0 no carrier, 0 pause output
Views: UL|GDP|LDP|G3P|L3P|OWN
0 output buffer failures, 0 output buffers swapped out
R1#
Protocol Caps (state, mtu)
-------- -----------------
None ether (up, 1514) IOS-XR offers the im database
ether_sock ether_sock (up, 1500) command to easiily show the
vlan vlan_target (up, 1500) various sizes that can be used.

RP/0/0/CPU0:XR1#

by Steven Crutchley www.netquirks.co.uk

You might also like