No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

NE20E-S2 V800R010C10SPC500 Configuration Guide - IP Services 01

This is NE20E-S2 V800R010C10SPC500 Configuration Guide - IP Services
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Interface MTU Setting

Interface MTU Setting

When nodes are properly communicating, use the default MTU value. Two nodes on both ends of a link must use the same MTU value so that they can properly operate protocols, such as OSPF and IS-IS, and successfully forward packets.

To change an interface MTU, run the mtu mtu-value command in the interface view. For information about MTU settings' impact on packet transmission is up to traffic type, interface type and board type.

Each interface on NE20E has a default interface MTU value. The Table 8-1 lists interface default MTUs on NE20E.

Table 8-1 Interface default MTUs
Interface Type

Default MTU Value

(Bytes)

Value Range

(Bytes)

Description

Ethernet interface

Ethernet sub-interface

1500 46 to 1500 When physical interface is added to Eth-Trunk, MTU can only be configured in Eth-Trunk and physical interface will take the MTU configured in Eth-Trunk.
NOTE:

The effective MTU of physical member interface is the same as Eth-Trunk, not the MTU value shown in the output of the display interface command.

Eth-Trunk interface

Eth-Trunk sub-interface

1500 46 to 9600
  • Interface MTUs take effect only on Layer 3 traffic.

    NOTE:
    An Eth-Trunk interface and its sub-interfaces work at Layer 3 by default and send only Layer 3 traffic. After the portswitch command is run in the Eth-Trunk interface view, the Eth-Trunk interface and its sub-interfaces work at Layer 2 and send only Layer 2 traffic.
  • The interface MTU must be changed in the Eth-Trunk interface view or sub-interface view, not the member interface view. After a member interface is added to an Eth-Trunk interface, the Eth-Trunk interface MTU automatically takes effect on the member interface. When the Eth-Trunk interface MTU changes, member interfaces automatically synchronize their MTU values with the Eth-Trunk interface MTU.
  • The MTU values on both ends of an Eth-Trunk link must be the same. An MTU inconsistency may cause a service interruption.

GE interface

GE sub-interface

1500

46 to 9600

Both control traffic and forwarding traffic will be affected by MTU setting.
NOTE:
A GE interface and its sub-interfaces work at Layer 3 by default and send only Layer 3 traffic. After the portswitch command is run in the GE interface view, the GE interface and its sub-interfaces work at Layer 2 and send only Layer 2 traffic.
Tunnel interface 1500 46 to 9600
  • For LDP over TE scenario, MTU on the tunnel interface impacts MPLS packet fragmentation, because the LDP LSP is over TE tunnel and the tunnel interface is an outbound interface of the LDP LSP. (Note: the physical interface of TE-tunnel does not impact MPLS packet fragmentation in LDP over TE.)
  • MTU in tunnel interface does not impact data plane fragmentation, only impacts control plane fragmentation. For example: the MTU set in tunnel interface of PE impacts the VPN-Ping from PE to PE, since the VPN-Ping packets pass through both the control plane and data plane of PE. But the MTU set in tunnel interface does not impact the VPN-Ping from CE to CE. For another example, if the VPN-Ping is from PE to remote PE, the effected MTU is the Tunnel interface MTU, and has nothing with the TE Path MTU. Note: for the ping lsp -te tunnel command, the effected MTU is the smaller one between the Tunnel interface MTU and the TE Path MTU.
  • The MTU modification of a TE tunnel interface takes effect immediately and no need to reset tunnel interface and LSP.
VLANIF interface 1500 46 to 9600
  • MTUs on VLANIF interfaces take effect only on Layer 3 IP traffic.
Virtual-Ethernet interface 1500 960 to 1518 -
Virtual-Template interface 1500 328 to 9600 Interface MTUs configured on VT interfaces are used in the Link Control Protocol (LCP) phase. Two Point-to-Point Protocol (PPP) nodes exchange packets to negotiate and select the smaller one between two configured MTUs as the effective MTU.
Translation
Download
Updated: 2019-01-02

Document ID: EDOC1100055376

Views: 18069

Downloads: 35

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next