Difference between revisions of "Manual:Maximum Transmission Unit on RouterBoards"

From MikroTik Wiki
Jump to navigation Jump to search
Line 20: Line 20:
Mikrotik RouterOS recognizes several types of MTU:
Mikrotik RouterOS recognizes several types of MTU:

Full frame MTU:
*Full frame MTU

=L2MTU on RouterBoards=
=L2MTU on RouterBoards=

Revision as of 10:18, 8 June 2009


It is sole responsibility of administrator to configure MTUs such that intended services and applications can be successfully implemented in network. In other words - administrator must make sure that MTUs are configured in a way that packet sizes does not exceed the capabilities of network equipment.

Originally MTU was introduced because of the high error rates and low speed of communications. Fragmentation of the data stream gives ability to correct corruption errors only by resending corrupted fragment, not the whole stream. Also on low speed connections such as modems it can take too much time to send a big fragment, so in this case communication is possible only with smaller fragments.

But in present days we have much lower error rates and higher speed of communication, this opens a possibility to increase the value of MTU. By increasing value of MTU we will result in less protocol overhead and reduce CPU utilization mostly due to interrupt reduction.

This way some non-standard frames started to emerge:

  • Giant or Jumbo frames - frames that are bigger than standard (IEEE) Ethernet MTU
  • Baby Giant or Baby Jumbo frames - frames that are just slightly bigger that standard (IEEE) Ethernet MTU

It is common now for Ethernet interfaces to support physical MTU above standard, but this can not be taken for granted. Abilities of other network equipment must be taken into account as well - for example, if 2 routers with Ethernet interfaces supporting physical MTU 1526 are connected through Ethernet switch, in order to successfully implement some application that will produce this big Ethernet frames, switch must also support forwarding such frames.

MTU on RouterOS

Mikrotik RouterOS recognizes several types of MTU:

  • Full frame MTU
  • MAC/L2 MTU
  • MPLS/L2.5 MTU
  • IP/L3 MTU

L2MTU on RouterBoards

This table shows how many additional bytes is supported by Mikrotik RouterBoards outside of standard (IEEE) Ethernet MTU:

RouterBoard ether1 ether2 ether3 ether4 ether5 ether6 ether7 ether8 ether9
RB493, RB493AH +22 +18 +18 +18 +18 +18 +18 +18 +18
RB450 +22 +18 +18 +18 +18
RB433, RB433AH +22 +18 +18
RB411, RB411A, RB411AH +22
CrossRoads +100
RB1000 +8000 +8000 +8000 +8000
RB600, RB600A +8000 +8000 +7500

So if table indicate "+22" - interface has Layer 2 MTU 14+22+1500=1534 bytes, and can handle 22 bytes (over standard Ethernet MTU of 1500) that can be utilized for VLAN tags, MPLS tags, Increase of layer-3 MTU

All wireless interfaces in RouterOS (including Nstreme2) Layer-2 1600 byte Physical MTU, so you have spare +86 bytes for VLAN tags, MPLS tags, Increase of layer-3 MTU

MTU in RouterOS

IP/Layer-3 MTU

Configured as interface mtu setting (/interface <type> <name> set mtu=X). Specifies how big IP packets router is allowed to send out the particular interface.

If router receives IP packet of size 1500, but MTU for outgoing interface is set to 1400, router will either fragment the packet (if "Don't Fragment" bit is not set in IP header) or drop the packet and send ICMP "Need Fragmentation" error back to originator (this is essential for Path MTU Discovery to work).

Sometimes it can be bad idea to change IP MTU from its default 1500 bytes on router interfaces if complete path end-to-end is not in administrators control. Although IP fragmentation and end-to-end Path MTU Discovery is intended to handle this situation, if ICMP Need Fragmentation errors are filtered somewhere along the path, Path MTU Discovery will not work.

There are several features in MikroTik RouterOS that is can benefit from possibility to exceed standard MTU


Configured in "/mpls interface" menu, specifies how big packets, including MPLS labels, router is allowed to send out the particular interface (default is 1508).

Note that when actually sending packet out the interface, link layer header is going to get attached, so it is only safe to configure MPLS MTU up to the value of physical MTU minus size of any link layer header(s) that is going to get applied (e.g. 14 in regular ethernet case, or 18 in case of one VLAN tag).

MPLS MTU affects packets depending on what action MPLS router is performing. It is strongly recommended that MPLS MTU is configured to the same value on all routers forming MPLS cloud because of effects MPLS MTU has on MPLS switched packets. This requirement means that all interfaces participating in MPLS cloud must be configured to the smallest MPLS MTU values among participating interfaces, therefore care must be taken to properly select hardware to be used.

MPLS Switching

If packet with labels included is bigger than MPLS MTU, MPLS tries to guess protocol that is carried inside MPLS frame.

If this is IP packet, MPLS produces ICMP Need Fragment error. This behaviour mimics IP protocol behaviour. Note that this ICMP error is not routed back to originator of packet but is switched towards end of LSP, so that egress router can route it back.

If this is not IP packet, MPLS simply drops it, because it does not know how to interpret the contents of packet. This feature is very important in situations where MPLS applications such as VPLS are used (where frames that are MPLS tagged are not IP packets, but e.g. encapsulated ethernet frames as in case of VPLS) - if somewhere along the LSP MPLS MTU will be less than packet size prepared by ingress router, frames will simply get dropped.

IP ingress

When router first introduces label (or labels) on IP packet, and resulting packet size including MPLS labels exceeds MPLS MTU, router behaves as if interface MTU was exceeded - either fragments packet in fragments that does not exceed MPLS MTU when labels are attached (if IP Dont Fragment is not set), or generates ICMP Need Fragmentation error that is sent back to originator.

VPLS ingress

When router encapsulates ethernet frame for forwarding over VPLS pseudowire, it checks if packet size with VPLS Control Word (4 bytes) and any necessary labels (usually 2 labels - 8 bytes), exceeds MPLS MTU of outgoing interface. If it does, VPLS fragments packet so that it honours MPLS MTU of outgoing interface. Packet is defragmented at egress point of VPLS pseudowire.

MTU examples for common technologies

Examples on how different technologies and their combinations relate to MTUs are given below. All examples are given assuming common standard 1500 byte IP packet size and that outgoing interface is ethernet. The total size of packet after all encapsulations must not exceed the physical MTU of outgoing interface.

Simple Routing

The image shows the packet MTU size for simple routing, packets size is not modified,


Routing with VLAN Encap

Each VLAN tag is 4 bytes long, VLAN tag is added by router. L2-MTU is increased by 4 bytes.


Simple MPLS with tags

When MPLS is used as plain replacement for IP routing, only one label is attached to every packet, therefore packet size increases by 4 bytes, we have the situation with two MPLS labels. In order to be able to forward standard size (1500 bytes) IP packet without fragmentation, MPLS MTU must be set to at least 1508 for two MPLS labels.


Simple MPLS over VLAN

If simple MPLS packets (with 1 label) are forwarded across ethernet additionally encapsulated in Vlan:


Note that MPLS MTU of VLAN interface matters in this case and it should be at least 1504.

VPLS Tunnel

Two MPLS labels are present, when remote endpoint is not directly attached. One MPLS label is used to get to remote endpoint, second label is used to identify VPLS tunnel.


Q-in-Q over VPLS tunnel