Feature Requirements |
Series |
Models |
|---|---|---|
P2MP TE tunnel outbound interfaces do not support channelized sub-interfaces. mLDP tunnel outbound interfaces do not support channelized sub-interfaces. When a P2MP TE or MPLD tunnel outbound interface is a channelized sub-interface, the bandwidth is not limited by the bandwidth reserved for the channelized sub-interface. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The "mpls te multi-protect fast-switch enable" command and its undo form are added for TE HSB+FRR dual-point fault triggered fast switching. 1, Packets may be lost for a short time after the command function is enabled or disabled. 2, The command applies to L3VPN over RSVP-TE, VLL over RSVP-TE, and VPLS over RSVP-TE scenarios. 3, TE FRR must be deployed on the entire network. HSB must be deployed on the ingress, BFD for TE LSP detection must be enabled, and the delayed interface Down function must be enabled on the outbound interface of the P node. Otherwise, a dual-point fault cannot trigger fast switching. 4, If both the primary LSP and HSB LSP are faulty, the system checks whether the primary LSP's directly connected interface is faulty. If a non-directly connected interface is faulty, the system continues to use the primary LSP to forward traffic. Otherwise, if FRR protection is configured, the FRR protection tunnel is used to forward traffic. If FRR is not configured, traffic is discarded. 5, The command is not applicable to LDP over RSVP-TE and BGP over RSVP-TE scenarios. In these scenarios, using the command cannot ensure fast switching if a TE LSP dual-point fault occurs, but basic forwarding functions are not affected. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
After re-marking is performed in MF traffic classification, packets with the same priority are added to the same TE group. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In a TE tunnel group scenario, if TE tunnels work with physical interfaces or LDP LSPs to balance traffic, although the bandwidth or weight is configured for tunnels of each priority, unequal load balancing based on the bandwidth or weight is not supported. Equal cost load balancing is performed among tunnels of each priority. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If a TE tunnel group and dynamic load balancing ("load-balance dynamic-adjust enable") are configured, and dynamic load-balancing does not take effect. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
VPN QoS is not supported when VLL/VPLS traffic recurses to DS-TE tunnels. When VLL/VPLS traffic recurses to DS-TE tunnels and VPN QoS is configured, traffic is balanced among common TE tunnels. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When VPN traffic recurses to DS-TE tunnels, TE fault cannot be associated with fast VPN FRR switching. You are advised to configure VPN-based BFD to directly trigger VPN FRR fast switching. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
LSP APS fails when penultimate hop popping is configured on devices. Do not configure penultimate hop popping and LSP APS at the same time. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Deleting OAM (TPOAM or MPLS OAM) prior to APS causes APS to falsely determine that OAM detection fails. This affects the protection switching status. Configure TP-OAM or MPLS OAM together with APS. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When the standard DS-TE mode is configured, if the "mpls te service-class default" command is not run, a TE tunnel without a priority is selected for the service that is not associated with a priority. If no such TE tunnel exists, the service is forwarded through the TE tunnel with the lowest priority. As a result, the bandwidth of the services with the lowest priority is preempted. The "mpls te service-class default" command is recommended in standard DS-TE mode. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
PCEP is used only to connect to a Huawei controller. PCEP and NETCONF cannot be used together to modify a stitching label. If both PCEP and NETCONF are used to modify a stitching label due to mal-operation, on the forwarder, run the undo mpls te pce delegate command to cancel tunnel delegation and the mpls te pce delegate command to delegate the tunnel to the controller again. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Entropy label feature: RSVP P2P LSPs and LDP P2P LSPs support entropy label negotiation. Other types of LSPs do not support this function. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When a Huawei forwarder runs PCEP to communicate with a Huawei controller, the Huawei controller may deliver an initiated LSP name carrying special characters, such as a question mark (?), a colon (;), or %, to the forwarder. The forwarder, however, does not support such characters. Do not specify an initiated LSP name carrying the special characters. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When you configure a split tunnel, not that: A split tunnel cannot be used as an outbound interface of a route. The mpls te igp mpls te igp shortcut and mpls te reserved-for-binding commands cannot be run simultaneously for a split tunnel. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
A neighbor node supports GR. If a local node functions as the GR Helper, the mpls rsvp-te hello command must be run on an RSVP-TE tunnel after the mpls rsvp-te hello support-peer-gr command is run in the MPLS view. If the RSVP-TE Hello capability is not configured on the RSVP-TE tunnel, the mpls rsvp-te hello support-peer-gr command functioNonelity fails. When the RSVP node performs a master/slave main control board swithocver, the RSVP adjacency between the local ndoe and its neighbor node is torn down because of the sigNoneling protocol timeout. As a result, a CR-LSP is torn down, and services transmitted over teh CR-LSP are interrupted. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If a TE tunnel passes through multiple IGP areas, an explicit path with inter-node IP addresses included needs to be configured for the tunnel, and CSPF must be configured on the ingress and inter-area nodes. You are advised to plan TE tunnels in the same IGP area. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In an LDP over TE scenario, after the mpls te igp advertise or mpls te igp advertise shortcut command is run in the view of a TE tunnel interface, a remote LDP session must be established based on the tunnel destination address after the route advertisement function is enabled. If no remote LDP session is established, no LDP LSP is established, which interrupts services. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When multiple MPLS TE-enabled IGP processes are deployed on a device, CSPF cannot compute an optimal path among these IGP processes. An optimal path computed within a single process may be different than the expected one. As a result, services are congested or interrupted on a TE tunnel. Solution: An explicit path is configured in the system view and used in the TE tunnel interface view. AlterNonetive solution: The mpls te cspf preferred-igp command is run in the MPLS view to eNoneble CSPF to compute a path within a selected IGP process. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The bypass attribute is mutually exclusive with the detour LSP function. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The reverse LSP function is mutually exclusive with the detour LSP function. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
A label and an IP address cannot be configured in a mixed way for an explicit path. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The include and exclude attributes cannot be simultaneously configured for an affinity on a tunnel. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Hot standby is mutually exclusive with ordinary backup. The latest configuration overrides the previous one. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When a GMPLS tunnel is bound to a GMPLS-UNI interface and the switch-type is EVPL, the process-pst parameter cannot be configured. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Fast reroute is mutually exclusive with the offload function. Fast reroute is mutually exclusive with a bypass tunnel. Fast reroute is mutually exclusive with a protected interface. Fast reroute is mutually exclusive with FF style. Fast reroute is mutually exclusive with reverse LSPs. Fast reroute is mutually exclusive with the reroute disable command. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When BFD monitors a GMPLS-UNI, the process-pst parameter is configured, and the GMPLS tunnel is bound to the GMPLS-UNI, the switch-type parameter cannot be set to EVPL. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Hot standby is mutually exclusive with the offload function. Hot standby is mutually exclusive with the bypass tunnel function. Hot standby is mutually exclusive with a protected interface. Hot standby is mutually exclusive with the FF style. Hot standby is mutually exclusive with the reroute disable command. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The best-effort path function is mutually exclusive with a bypass tunnel. The best-effort path function is mutually exclusive with a protected interface. The best-effort path function is mutually exclusive with the FF style. The best-effort path function is mutually exclusive with the offload function. The best-effort path function is mutually exclusive with ordinary backup. The best-effort path function is mutually exclusive with the reroute disable command. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The FF style is mutually exclusive with FRR. The FF style is mutually exclusive with backup. The FF style is mutually exclusive with automatic bandwidth adjustment. The FF style is mutually exclusive with soft preemption. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The detour LSP function is mutually exclusive with the offload function. The detour LSP function is mutually exclusive with a bypass tunnel. The detour LSP function is mutually exclusive with a protected interface. The detour LSP function is mutually exclusive with the FF style. The detour LSP function is mutually exclusive with the bypass attribute. The detour LSP function is mutually exclusive with reverse LSPs.The detour LSP function is mutually exclusive with the bypass attribute.The detour LSP function is mutually exclusive with the reroute disable command.The detour LSP function is mutually exclusive with PCE delegation. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
A bypass tunnel is mutually exclusive with FRR. A bypass tunnel is mutually exclusive with the detour LSP function. A bypass tunnel is mutually exclusive with backup. A bypass tunnel is mutually exclusive with the reroute disable command. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Ordinary backup is mutually exclusive with the off-load function. Ordinary backup is mutually exclusive with the best-effort path function. Ordinary backup is mutually exclusive with the FF style. Ordinary backup is mutually exclusive with the reroute disable command. Ordinary backup is mutually exclusive with reverse LSPs. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When the reverse LSP function is used, the global label allocation mode must be set to the non-null mode. Otherwise, the reverse LSP feature does not take effect. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Soft preemption is mutually exclusive with the FF style. Soft preemption is mutually exclusive with the reroute disable command. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
A primary tunnel cannot be configured as a protection tunnel. A primary tunnel cannot configure itself as a protection tunnel. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If the mpls te timer auto-bandwidth command must be run in the MPLS view when automatic bandwidth adjustment is configured on a tunnel. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Bit error-triggered switching is mutually exclusive with the protection group function. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
PCE delegation is mutually exclusive with the detour LSP function. PCE delegation is mutually exclusive with the reroute disable command. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The bidirectional co-routed attribute is mutually exclusive with the dynamic reverse LSP attribute. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The reroute disable command is mutually exclusive with PCE delegation. The reroute disable command is mutually exclusive with tunnel re-optimization. The reroute disable command is mutually exclusive with soft preemption. The reroute disable command is mutually exclusive with the detour LSP function. The reroute disable command is mutually exclusive with ordinary backup. The reroute disable command is mutually exclusive with the best-effort path. The reroute disable command is mutually exclusive with FRR. The reroute disable command is mutually exclusive with backup. The reroute disable command is mutually exclusive with a bypass tunnel. The reroute disable command is mutually exclusive with automatic bandwidth adjustment. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The include-all and include-any attributes cannot be simultaneously configured for an affinity. The latest configuration overrides the previous one. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The bandwidth configured in the bypass-attribute command must be lower than or equal to the bandwidth of the primary tunnel. The priority configured in this command cannot be greater than the priority of the primary tunnel. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The reverse LSP function is mutually exclusive with backup. The reverse LSP function is mutually exclusive with FRR. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If bidirectional is enabled for a tunnel, the tunnel cannot be bound to a static bidirectional co-routed CR-LSP on the egress. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The FF style is mutually exclusive with PCE delegation. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
A protected interface is mutually exclusive with FRR. A protected interface is mutually exclusive with the detour LSP function. A protected interface is mutually exclusive with backup. A protected interface is mutually exclusive with ordinary backup and best-effort functions. [~HUAWEI-Tunnel3]display this # interface Tunnel3 tunnel-protocol mpls te destination 3.3.3.3 mpls te record-route label mpls te tunnel-id 3 mpls te protected-interface Ethernet3/0/0 # return [~HUAWEI-Tunnel3]mpls te fast-reroute Error: Fast-reroute can not be configured, because protected-interface is configured. [~HUAWEI-Tunnel3]mpls te detour Error: Detour can not be configured, because protected-interface is configured. [~HUAWEI-Tunnel3]mpls te backup hot-standby Error: Hot-standby can not be configured, because protected-interface is configured.
[~HUAWEI-Tunnel3]mpls te backup ordinary Error: Ordinary/Best-effort can not be configured, because protected-interface is configured. [~HUAWEI-Tunnel3] |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If static and dynamic BFD for TE LSP is simultaneously configured, the static BFD session takes effect. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
BFD and MPLS OAM cannot be configured simultaneously for a tunnel. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
A static tunnel or a static CR tunnel cannot be bound to a reverse RSVP-TE LSP. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
A dynamic tunnel cannot be bound to a reverse LSP of a static protocol. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Diabling the automatic configuration of global physical interface bandwidth is supported only in the transport mode. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
An inter-IGP area P2MP TE tunnel is no supported. An S2L cannot be created on a leaf node that is in a different IGP area than the ingress of a P2MP TE tunnel. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If an LSP is established across IGP areas, the LSP cannot be re-optimized. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
An SR-MPLS TE tunnel established over a labeled explicit path does not respond to messages of the other label stacks or to the make-before-break mechanism. Path re-optimization is not performed, and the origiNonel LSP and traffic are not affected. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
An inter-area detour LSP is not supported. Do not use Detour FRR in an inter-area scenarios. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
An SR-MPLS TE tunnel must be used together with detection function. SR-MPLS TE tunnels do not use signaling protocols. BFD for TE LSP must be configured to monitor the connectivity of the primary and backup LSPs before HSB protection is performed. Without a detection protocol enabled, SR-MPLS TE LSPs cannot detect link faults or switch traffic, resulting in traffic loss. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The bandwidth of the primary tunnel cannot be greater than that of a backup tunnel. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The hard pipe is mutually exclusive with bandwidth attributes. The hard pipe attribute is mutually exclusive with the diffserv-mode command. An inbound interface must be configured for a hard pipe LSP. An outbound interface must be configured for a hard pipe LSP. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
After the reverse LSP in a working tunnel must be different from that in a protection tunnel. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The name of a reverse LSP in a static bidirectional co-routed tunnel must be the same as that of a forward LSP. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
LSP loopback is supported only on a transit node of a static bidirectional co-routed LSP. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
A loopback interface address must be used in the MPLS LSR-ID command. If an LSR ID is not set to a loopback address, an IGP floods the LSR ID and a path is successfully computed. After a TE tunnel is established, application nor protocol packets that depend on the loopback address cannot be handled. For example, in VPN iteration, the peer BGP address is used as a next-hop IP address (which should have been a loopback interface address), and the local end is iterated to the tunnel destined for the peer BGP address. Since the loopback interface address is not used, the iteration fails. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
An inter-area auto bypass tunnel is not supported because LSP cannot be bound to an FRR path in an inter-area scenario. Do not use Auto FRR in an inter-area scenarios. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
An SR-MPLS TE tunnel must be used together with detection function. SR-MPLS TE tunnels do not use signaling protocols. BFD for tunnel must be configured to associate the BFD status with the tunnel status. Without a detection protocol enabled, SR-MPLS TE LSPs cannot detect link faults or notify an App of the tunnel fault. As a result, services iterated to an SR-MPLS TE LSP cannot be switched to a protection LSP, resulting in traffic loss. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When graceful shutdown is performed on the device through which a TE tunnel passes and the path computation of the TE tunnel is not affected by the bandwidth and TE metric value of the device, do not perform the graceful shutdown to upgrade or restart the local board or device. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Only IS-IS responds to graceful shutdown and floods TE attributes of an interface. When OSPF routes are used on an interface, do not perform the graceful shutdown before upgrading or restarting the board or device. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Automatic bandwidth adjustment can be performed only after CSPF is enabled globally. If CSPF is not enabled, pre-computation cannot be performed, and automatic bandwidth adjustment does not take effect. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The destination IP address of the tunnel must be set to the MPLS LSR ID configured on the destination router. If an LSR ID is not set to a loopback address, a path is successfully computed. After a TE tunnel is established, application nor protocol packets that depend on the loopback address cannot be handled. For example, in VPN iteration, the peer BGP address is used as a next-hop IP address (which should have been a loopback interface address), and the local end is iterated to the tunnel destined for the peer BGP address. Since the loopback interface address is not used, the iteration fails. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If the TP OAM lock function is enabled on an interface, the interface cannot be used as the outbound or inbound interface of a static tunnel. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Re-optimization can be performed only after CSPF is enabled globally. If CSPF is not enabled, pre-computation cannot be performed, and re-optimization does not take effect. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
An FRR switchover is incorrectly triggered due to BFD for RSVP detection. Return BFD packets are transmitted through routes. The return path may differ from the GRE tunnel path. If the link over which BFD return packets are transmitted fails, traffic may be incorrectly switched to the TE protection path. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When the version of the ingress does not support the rsvp graceful-shutdown command, interworking is not supported. This is because that after graceful shutdown is performed on a transit node, a PathErr message with a rerouting request is sent. When the ingress of the RSVP-TE tunnel does not support the rsvp graceful-shutdown command, the ingress cannot process PathErr messages and deletes the RSVP-TE LSP. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When configuring bandwidth for an RSVP-TE tunnel, ensure that the same DS-TE mode and TE-class-mapping are configured on each node through which the tunnel passes. If a DS-TE mode or TE-class-mapping configuration inconsistency occurs, a tunnel with a bandwidth value specified may fail to be established. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If static BFD for SR-MPLS TE service is configured, the BFD status is up only when both forward service forwarding and reverse service forwarding are normal. For static BFD for tunnel, services can recurse to tunnels only when the BFD status is up. For static BFD for LSP, services can recurse to a tunnel if an LSP of the tunnel is not configured with BFD or if an LSP of the tunnel is configured with BFD and the BFD status is up. For example, two links are deployed between devices A and B. The SR-MPLS TE tunnel from device A to device B traverses link 1, and the SR-MPLS TE tunnel from device B to device A traverses link 2. If link 1 goes down, the SR-MPLS TE tunnel from device A to device B fails to forward traffic. Due to the forwarding failure of the tunnel from device A to device B, the BFD status of the tunnel from device B to device A also goes down. As a result, services cannot recurse to the tunnel from device B to device A. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Uses NSO run command: show devices device R22 live-status mpls:mpls mplsTe rsvpTeTunnels rsvpTeTunnel tunnelPaths tunnelPath OR show devices device R22 live-status mpls:mpls mplsTe rsvpTeTunnels rsvpTeTunnel tunnelPaths doesn't show tunnel path information. 1. Show with rsvpTeTunnel's key(tunnelName) (eg:show devices device R22 live-status mpls:mpls mplsTe rsvpTeTunnels rsvpTeTunnel Tunnel1 tunnelPaths tunnelPath). 2. Config one of affinityName. 3. Show tunnelPath at website of NSO. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Uses NSO run command: show devices device R22 live-status mpls:mpls mplsTe rsvpTeTunnels rsvpTeTunnel tunnelPaths tunnelPath OR show devices device R22 live-status mpls:mpls mplsTe rsvpTeTunnels rsvpTeTunnel tunnelPaths doesn't show tunnel path information. 1. Show with rsvpTeTunnel's key(tunnelName) (eg:show devices device R22 live-status mpls:mpls mplsTe rsvpTeTunnels rsvpTeTunnel Tunnel1 tunnelPaths tunnelPath). 2. Configure one of affinityName. 3. Show tunnelPath at website of NSO. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The RSVP-TE entropy label is encapsulated into the MPLS label. The entropy label can be used to guide traffic forwarding only after the MPLS label is popped out. Forwarding along an RSVP-TE over GRE tunnel is performed based on IP packets. The RSVP entropy label does not take effect, and load balancing is performed based on the GRE tunnel specification. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
By default, when a BFD session or neighbor is Admin Down, the TE CR-LSP status is not affected. After the system restarts, the BFD session needs to be renegotiated. If the BFD session does not go Up, the TE CR-LSP goes Down. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
By default, P2MP TE is not affected when a BFD session or neighbor is in Admin Down state. After the system restarts, the BFD session needs to be re-negotiated. If the BFD session does not go Up, P2MP TE goes Down. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
To deploy both RSVP-TE and GRE tunnels, certain requirements must be met. If an RSVP-TE tunnel is deployed over a GRE tunnel which is then deployed over the RSVP-TE tunnel, the GRE and RSVP-TE tunnels have the same source and destination. After routes are advertised, the outbound interface of the GRE tunnel changes to the RSVP-TE tunnel. As such, traffic fails to be forwarded. If a loop is formed, an infinite loop occurs during forwarding. You need to perform configurations to prevent this problem. If an RSVP-TE tunnel is deployed over a GRE tunnel which is deployed over another RSVP-TE tunnel and this RSVP-TE tunnel is then deployed over another GRE tunnel, the number of required encapsulations continuously increases, reducing forwarding efficiency. Therefore, you need to perform configurations to avoid this scenario. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
For a topology of Device A<->Device B<->C, there are two links between Device A and Device B (Link 1 and Link 2). There is only one link between Device B and Device C. Device A functions as the ingress of a P2MP tunnel, and Device B and Device C function as leaf nodes of the P2MP tunnel. Link 1 is configured as an explicit path on Device B, and no explicit path is configured on Device C. In this scenario, if RSVP-TE is not enabled on Link 1, the P2MP tunnel cannot be established. Because Link 1 is configured as an explicit path on Device B, this abnormal link cannot be excluded during P2MP path calculation. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When a tunnel is not configured with the hot-standby, ordinary, or best-effort function but is configured with the attributes (such as hop-limit, affinity, and explicit path) associated with the secondary or best-effort function, the configurations of such attributes cannot be synchronized during incremental or full synchronization. The secondary or best-effort related attributes take effect only when hot-standby, ordinary, or best-effort is configured, so the corresponding configuration can be added. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
By default, when a BFD session or neighbor is Admin Down, the TE tunnel status is not affected. When the system restarts, the BFD session needs to be renegotiated. If the BFD session does not go Up, the TE tunnel goes Down. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In a multi-VS scenario, an SR-MPLS TE tunnel is configured. In this situation, the controller cannot deliver stitching label, whereas a forwarder can be used to allocate stitching labels. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
By default, the RSVP status is not affected when a BFD session or neighbor is in Admin Down state. When the system restarts, the BFD session needs to be re-negotiated. If the BFD session does not go Up, RSVP goes Down. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |