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-S V800R010C10SPC500 Configuration Guide - MPLS 01

This is NE20E-S V800R010C10SPC500 Configuration Guide - MPLS
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).
Licensing Requirements and Limitations for MPLS LDP

Licensing Requirements and Limitations for MPLS LDP

Restrictions and Guidelines

Restrictions

Guidelines

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.

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.

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

After the lsp-trigger { all | ip-prefix } or label distribution control-mode independent command is run, LDP may create a proxy egress. If an LDP LSP functioning as a public network tunnel to carry VPN traffic, VPN traffic fails to be forwarded.

A policy configured using the proxy-egress disable command limit the creation of the proxy egress. If the label distribution control-mode independent command is used, no workaround is available.

Public network traffic is transmitted properly, but private network traffic fails to be forwarded.

After the VLANIF interface is bound to a VSI, it is used as a Layer 2 interface and does not allow the Layer 3 service configuration. Such a VLANIF interface allows the MPLS service configuration.

Do not configure MPLS on a VLANIF interface bound to a VSI.

Although MPLS is configured on the interface, no MPLS services use the interface.

When MBB traffic detection is enabled, if only a little MBB LSP traffic is received within a short period of time (in seconds) during MBB convergence, an MBB switchover is triggered in advance and packet loss occurs.

  • The NG MVPN ingress uses the non-aggregation forwarding mode by default. You can run the ng-mvpn forwarding-mode aggregation command to set the aggregation mode.
  • There is no workaround for other scenarios.

Packet loss occurs during the mLDP MBB switchover.

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055103

Views: 20128

Downloads: 35

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