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

NE40E V800R010C00 Configuration Guide - MPLS 01

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).
MPLS LDP Precautions

MPLS LDP Precautions

Precautions

Preventive Measures

Impact

When penultimate hop popping is configured, the egress node does not support pipes.

None

When penultimate hop popping is configured, the egress node does not support pipes.

mLDP does not support the following outbound interfaces:serial interfaces, serial sub-interfaces, VLANIF interfaces, ATM main interfaces, ATM sub-interfaces, POS sub-interfaces, low-speed E1/T1/E3/T3 interface, MFR interfaces, MP-group interfaces, Eth-Trunk dot1q sub-interface for VLAN tag termination, Eth-Trunk QinQ sub-interface for VLAN tag termination, Global-MP-Group interface, ATM-Trunk main interface, ATM-Trunk sub-interfaces, and POS-Trunk interface.

Run the mpls te p2mp-te disable command on the interface to prevent MPLS traffic from traveling through it.

Traffic over a tunnel fails to be forwarded through the outbound interface.

mLDP over TE is not supported.

Do not enable MPLS TE for interfaces on mLDP paths, preventing such interfaces from functioning as TE outbound interfaces.

mLDP LSPs cannot be set up.

If the outbound interface of an LDP LSP is an Ethernet sub-interface or Eth-Trunk sub-interface and a BFD session is bound to the IP address of the sub-interface, the BFD session can be associated with LDP FRR/TI-LFA fast switching.

None.

If a BFD session is bound to IP addresses of an Ethernet sub-interface or Eth-Trunk sub-interface and another sub-interface, the BFD session cannot be associated with LDP FRR/TI-LFA fast switching.

mLDP FRR:

1. Link protection is only supported.

2. The FRR paths selected before and after a traffic switchover may be different.

3. If the P2P and P2MP primary tunnels fail simultaneously, protection fails, and traffic is interrupted. The backup P2P tunnel cannot be established over the FRR path of its own.

4. If a backup path is over TE or GRE, link protection works in best-effort mode and may fail. If the backup path is the same as the primary path, link protection takes effect. If the backup path and the primary path do not share the same path, link protection also takes effect.

Properly plan the network and configuration.

None

FRR does not take effect after a multi-link mLDP FRR path is established and the primary LSP fails.

Plan a new backup LSP that at least passes through another device that does not reside on the primary LSP.

FRR does not take effect after the primary LSP fails.

Download
Updated: 2018-07-12

Document ID: EDOC1100028530

Views: 103005

Downloads: 336

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