Feature Requirements |
Series |
Models |
|---|---|---|
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. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When the LDP LSP outbound interface is a sub-interface, the sub-interface BFD association with LDP FRR / TI-LFA fast switching is supported only under the following conditions: 1. The interface type is an Ethernet sub-interface and an eth-trunk sub-interface 2. Meet the conditions of BFD binding the IP of the sub-interface |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When penultimate hop popping is configured, the egress node does not support pipes. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
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. You are advised to take the following preventive measures: 1, 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. 2, There is no workaround for other scenarios. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If SR-MPLS BE TI-LFA is used for an LDP FRR backup path, LDP ECMP and LDP FRR cannot be both enabled. If SR-MPLS BE TI-LFA is used for an LDP FRR backup path and LDP ECMP and LDP FRR are both enabled, LDP ECMP takes effect preferentially. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
On an inter-AS node in an NG MVPN scenario, mLDP needs to obtain the next hop address of a BGP route. This address must be an IPv4 address that is reachable to an IGP. When the next hop address of a BGP route is an IPv6 address, an mLDP tunnel cannot be established. Examples of scenarios that are not supported: 1. Public network BGP route recursion to SRv6 TE Policies. 2. Public network BGP route recursion to SRv6 BE. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
On an inter-AS node in an NG MVPN scenario, mLDP needs to obtain the next hop address of a BGP route. This address must be an IPv4 address that is reachable to an IGP. When the next hop address of a BGP route is an IPv6 address, an mLDP tunnel cannot be established. Examples of scenarios that are not supported: 1. Public network BGP route recursion to SRv6 TE Policies. 2. Public network BGP route recursion to SRv6 BE. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
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. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
After the device is restarted, if the BFD session or neighbor is in Admin Down state, the LDP LSP and LDP tunnel status are not affected. When the BFD session is re-negotiated, if the BFD report goes Down, BFD on the forwarding plane triggers fast LDP service traffic switching, and LDP on the control plane determines the master/backup status based on the route convergence result. If BFD has not been Up, BFD is not associated with LDP services on the forwarding plane. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
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. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |