Documente Academic
Documente Profesional
Documente Cultură
MTU on RouterOS
Mikrotik RouterOS recognizes several types of MTU: IP/Layer-3/L3 MTU MPLS/Layer-2.5/L2.5 MTU MAC/Layer-2/L2 MTU Full frame MTU
MAC/Layer-2/L2 MTU
L2MTU indicates the maximum size of the frame without MAC header that can be sent by this interface. Starting from the RouterOS v3.25 L2MTU values can be seen in "/interface" menu. L2MTU support is added for all Routerboard related Ethernet interfaces, VLANs, Bridge, VPLS and wireless interfaces. Some of them support configuration of L2MTU value. All other Ethernet interfaces might indicate L2MTU only if the chip set is the same as Routerboard Ethernets. This will allow users to check if desired setup is possible. Users will be able to utilize additional bytes for VLAN and MPLS tags, or simple increase of interface MTU to get rid of the some unnecessary fragmentation. This table shows max-l2mtu supported by Mikrotik RouterBoards (Starting from the RouterOS v5.3 also available in "/interface print" menu as value of read-only "max-l2mtu" option): Integrated Solutions
RouterBoard Groove A-5Hn, Groove 5Hn, SXT 5HnD ether1 ether2 ether3 ether4 ether5 ether6 ether7 ether8 ether9 ether10 ether11 ether12-13 2028
RB750, RB750UP, RB751U-2HnD, 4076 OmniTik U-5HnD, OmniTik UPA-5HnD RB750GL, RB751G-2HnD RB1200 RB1100AH RB1100AHx2 4074 4078 9498 9498
2028
2028
2028
2028
4074 4078 9498 9498 4080 9498 9498 4080 9498 9498 4080 9498 9498 9116 9498 9498 9116 9498 9498 9116 9500 9116 9116
RouterBOARD
RouterBoard RB411, RB411U, RB411AR, RB411AH, RB411UAHR RB433, RB433AH, RB433UAH, RB433L, RB450, RB493, RB493AH RB411GL, RB433GL RB435G, RB450G, RB493G RB711 series RB711G series RB800 RB2011 series ether1 ether2 ether3 ether4 ether5 ether6 ether7 ether8 ether9 ether10 1526 ether11 ether12-13
1526
1522
1522
1522
1522
1522
1522
1522
1522
1524 1520
9500 4074
9116 4074 4074 4074 2028 2028 2028 2028 2028 [sfp1] 4047
Old Products
RouterBoard
ether1 ether2 ether3 ether4 ether5 ether6 ether7 ether8 ether9 ether10 ether11 ether12-13 9500 9498 1524 1632 1518 1600 7200 9000 9500 9498 1524 1632 1518 1600 7200 9000 7200 9000 1518 1518 1514 1514 1514 1514 9500 9498 1524 9498 1524 9498 9498 9498 9498 9498 9116 9116
RB600, RB600A, RB1000 9500 RB1100 RB750G RB333 RB1xx RB532, CrossRoads RB44G RB44GV 9498 1524 1632 1518 1600 7200 9000
MPLS/Layer-2.5/L2.5 MTU
Configured in "/mpls interface" menu, specifies maximal size of packet, including MPLS labels, that is allowed to send out by the particular interface (default is 1508). Make sure that MPLS MTU is smaller or equal to L2MTU 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 behavior mimics IP protocol behavior. 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.
IP/Layer-3/L3 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 can benefit from possibility to exceed standard MTU
Simple Examples
In these examples we will take a look at frames entering and leaving router via Ethernet interfaces.
Simple Routing
The image shows the packet MTU size for simple routing, packets size is not modified.
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.