Feature Requirements |
Series |
Models |
|---|---|---|
When using Binding SID for inter-AS E2E SR-MPLS TE tunnels, the following limitations exist: 1. When the number of label stack layers exceeds 3, the tunnel does not go Up. 2. When a layer of label stack is configured and the label type is Binding SID, the tunnel's packet priority mapping, statistics, MTU and TTL functions are not supported. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
For an SR-MPLS TE tunnel with the BGP-EPE label as the first label, when the BGP-EPE label corresponds to multiple outbound interfaces, TE bandwidth limit is not supported. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Anycast protection cannot be deployed on segment routing MPLS ingress and egress nodes. Anycast protection means that the same prefix SID is configured for multiple devices. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Traffic over Segment Routing tunnels can be sampled by NetStream on the ingress (user-to-network) and by NetStream on the egress. NetStream sampling on the ingress (network-to-user) or transit node is not supported. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
SR-MPLS TE Policies do not support inter-tunnel recursion. 1. SR-MPLS TE Policies cannot be recursed to other types of tunnels, including SR-MPLS TE Policy tunnels. 2. Other types of tunnels cannot be recursed to SR-MPLS TE Policy tunnels. If relevant configurations are incorrect, traffic is interrupted. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The bandwidth limit function is not supported on Segment Routing tunnels using node SIDs. The controller guarantees the bandwidth of the delivered Segment Routing tunnels established using node SIDs. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
SR-MPLS TE tunnels consisting of adjacency SIDs do not support SR-MPLS TE anycast protection. Deploy anycast protection for SR-MPLS TE tunnels consisting of node SIDs. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The function of detecting BGP EPE outbound interface faults and triggering service switching through SBFD for SR-MPLS TE tunnel can be used only when the following conditions are met: 1. The destination of an SR-MPLS TE tunnel is the local ASBR of BGP EPE. 2. The innermost label in an SR-MPLS TE label stack is a BGP EPE label. 3. SBFD for SR-MPLS TE tunnel has been deployed. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The function of detecting BGP EPE outbound interface faults and triggering service switching through SBFD for SR-MPLS TE tunnel can be used only when the BGP EPE outbound interface is an Ethernet main interface, Ethernet sub-interface, Eth-Trunk main interface, or Eth-Trunk sub-interface. If the type of the BGP EPE outbound interface is not supported, traffic cannot rapidly recover in the case of a BGP EPE outbound interface fault. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The function of detecting BGP EPE outbound interface faults and triggering service switching through SBFD for SR-MPLS TE tunnel poses the following risks if seven or more BGP EPE links fail at the same time in BGP EPE load balancing scenarios: 1. Although traffic can continue to be forwarded, SR-MPLS TE SBFD goes down, triggering traffic convergence or switching on the ingress of an SR-MPLS TE tunnel. 2. Data packets are discarded, but SBFD is still up. As a result, traffic recovers until BGP EPE convergence is complete. Do not deploy seven or more BGP EPE links for load balancing. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The function of detecting BGP EPE outbound interface faults and triggering service switching through SBFD for SR-MPLS TE tunnel applies only to scenarios where inter-AS public IP unicast packets are transmitted over SR-MPLS TE tunnels. Suggestions: 1. Disable the MPLS TE IGP shortcut function on SR-MPLS TE tunnel interfaces to prevent unexpected public IP traffic from recursing to inter-AS SR-MPLS TE tunnels. 2. Configure redirection to steer inter-AS traffic to inter-AS SR-MPLS TE tunnels. 3. Run the mpls te reserved-for-binding command on SR-MPLS TE tunnel interfaces to prevent VPN traffic from recursing to inter-AS SR-MPLS TE tunnels. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
A maximum of 64 BGP EPE links can be configured for load balancing. If more than 64 BGP EPE links exist, the first 64 links are selected based on the OutIfIndex values of outbound interfaces in descending order. If the sixty-fourth and sixty-fifth links have the same OutIfIndex value, the one with the largest NextHop value is selected. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The function of enabling BGP EPE outbound interface faults to trigger routing table lookups due to the rollback of public IP unicast traffic can be used when the outbound interface of a BGP EPE link is an Ethernet or ETH-Trunk. Other types of interfaces do not support fast switching. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In a scenario where UCMP is implemented for SR-MPLS TE Policy candidate paths according to segment list weights, relevant restrictions are as follows: 1, The load balancing precision is 1/128. 2, The segment list whose weight proportion is less than 1/128 does not forward traffic. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In a scenario where UCMP is implemented for SR-MPLS TE Policy candidate paths according to segment list weights, if the segment list weight is adjusted, relevant restrictions are as follows: 1, If SBFD for segment list is not configured and the segment list weight is adjusted from a non-zero value to zero, packet loss may occur. 2, If SBFD for segment list is not configured and the segment list weight is adjusted from zero to a non-zero value, packet loss may occur. 3, If SBFD for segment list is configured, the segment list weight is adjusted from a non-zero value to zero, and delayed deletion is performed (the default delay is 20s and can be configured), configure a proper deletion delay to prevent packet loss. 4, If SBFD for segment list is configured and the segment list weight is adjusted from zero to a non-zero value, packet loss may occur. You are advised to configure SBFD for segment list and run the "sr-te-policy delete-delay" command as needed to adjust the delay in deleting segment lists when SBFD goes down. This helps reduce or prevent packet loss when the segment list weight is adjusted from a non-zero value to zero. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Path verification cannot be enabled on the ingress of an inter-AS SR-MPLS TE tunnel. If path verification is enabled, LSPs cannot be created due to path verification failures. Ensure that the mpls te path verification enable command is not run. By default, the function is disabled. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In FRR and load balancing scenarios, if routes carry different colors, secondary optimal routes all search for the corresponding slice ID based on the color ID of the optimal route. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If an SR-MPLS TE Policy is configured and then SBFD is enabled, the segment lists and paths of the SR-MPLS TE Policy remain Up. If SBFD is not configured on the reflector, the segment list status is set to Down after BFD negotiation times out (5 minutes). As a result, traffic on the forwarding plane is interrupted. You are advised to configure SBFD before configuring an SR-MPLS TE Policy. In addition, you need to configure the reflector. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If you enable SBFD after configuring an SR-MPLS TE Policy under which candidate paths and the segment lists of the candidate paths are up, the candidate paths and segment lists keep up, and traffic can be properly steered into the SR-MPLS TE Policy. If you enable SBFD and then configure an SR-MPLS TE Policy whose initial state is down, traffic can be steered into the SR-MPLS TE Policy only when SBFD detects that the SR-MPLS TE Policy is up. You are advised to enable SBFD and then configure an SR-MPLS TE Policy. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If the first hop of an explicit path is assigned a BSID (indicating that the tunnel that references the explicit path needs to be forwarded through a tunnel assigned the BSID), the first hop of the explicit path used by the tunnel assigned the BSID cannot be assigned a BSID. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If BFD is configured on the ingress and the reverse BFD path is over a BSID tunnel but the tunnel mapped to the BSID on the egress does not exist, the BFD session goes Down. Configure a tunnel mapped to the BSID on the egress to ensure that the reverse BFD path can go Up. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When the outer label in the label stack of an SR-MPLS TE explicit path is a BSID, the maximum SID depth (MSD) cannot exceed three. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Local CSPF path computation for SR-MPLS TE tunnels supports node labels. The prefix SID of a node must be unique in an IGP domain. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
SR-MPLS Flex-Algo does not support multi-source TI-LFA or multi-source microloop avoidance. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When a BSID label is configured for an explicit path, the system does not check whether the tunnel mapped to the BSID exists or is Up. If the tunnel does not exist or is not Up, a tunnel established over the explicit path can go Up but fails to forward traffic. Therefore, ensure that the configuration is correct. You are advised to configure BFD. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
After a BSID is configured for a tunnel and is referenced by an explicit path, the BSID of the tunnel cannot be modified or deleted. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
After the device is restarted, the BFD session status reported by the device is Up. If the Flex-Algo LSP is not in the Up state, the Flex-Algo LSP is set to Down. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If CSPF is used to compute SR-MPLS TE LSP paths, ensure that node labels are configured for all processes or no node label is configured for the node if the node has SR capabilities and IGP multi-processes. Node labels cannot be configured for some processes but not for other processes. Ensure that the node label is configured for all processes or is not configured for the node. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If a BSID is configured for a tunnel and is referenced by an explicit path, the tunnel cannot be deleted. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
After the device is restarted, the BFD session status reported by the device is Up. If the tunnel is not in Up state, the tunnel is set to Down. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
After the device is restarted, the SR-MPLS TE Policy status is not affected when the BFD session or neighbor is in Admin Down state. After the BFD session is renegotiated, if the BFD session goes Down, the SR-MPLS TE Policy goes Down. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
An SR-MPLS BE Prefix/Node SID must be unique on an entire network. The SID value must be within the SRGB range. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
A single binding sid (BSID) is configured for each tunnel. Each BSID can be referenced by only a single tunnel. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The SID forwarding entry corresponding to an IP route prefix is generated only when the IP route of the involved process is active. When multiple processes or protocols are deployed, the following restrictions exist. Otherwise, SR-MPLS BE and SR-MPLS TE traffic may fail to be forwarded. 1. Do not advertise the IP route prefix used for SID advertisement in multiple processes or protocols at the same time. 2. If the route must be advertised through multiple processes or protocols at the same time, ensure that the IP route advertised by the protocol or process used for SID advertisement has the highest priority on the device within the SID advertisement range. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |