Feature Requirements |
Series |
Models |
|---|---|---|
On an IS-IS broadcast network, P2P two-way handshake, IS-IS multi-instance, or IS-IS multi-topology network, BFD session establishment check does not take effect even if the bfd session-up check command is run. The association between BFD and IS-IS neighbor Up does not support broadcast interfaces or the advanced MT. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If an IS-IS Level-1-2 router imports a route with a priority lower than IS-IS and the route is learned by another level of the current device after route leaking, route flapping occurs. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When services without private network labels enter a Policy, the last SID of the Policy must carry the USD attribute, and this SID must be the SID of the egress. Otherwise, traffic cannot be forwarded. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In Encap mode, when the last SID of a Policy is a BSID, traffic fails to be forwarded. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The NSO has its own configuration database and saves delivered configurations. When a configuration with a must condition, it is checked based on the configuration database saved by the NSO. The configuration can be delivered only when it meets the must condition. 1. When a configuration with the must condition is configured, the matching condition is delivered by the NSO command and can be delivered without repeated delivery or synchronization. 2. When a configuration with the must condition is configured, the matching condition is delivered by the CLI or other tools. The new configuration can be delivered only after synchronization. If synchronization is not performed, the must check may fail. Plan the configuration properly. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If an IS-IS Level-1-2 router imports a route with a priority lower than IS-IS, ensure that the route is not learned by another level of the current router after route leaking. Otherwise, route flapping occurs. Properly plan the network. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When multiple import points exist and different devices are configured with the same system ID, a false loop alarm may be reported. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When load balancing is used: 1. The TI-LFA backup next hop cannot be calculated. 2. Multi-source load balancing routes do not support FRR. 3. FRR is not supported in SR-MPLS BE load balancing scenarios. Properly plan the network. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
1. The mapping SID does not support priority comparison. 2. The mapping SID cannot be used in anycast FRR. 3. The mapping SID cannot be used in the SR anti-micro-loop function. 4. in cross-process and cross-protocol scenarios, when ASBRs function as interworking stitching nodes, mapping-SID mapping needs to be configured on the processes to be imported. Properly plan the network. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In SR and LDP interworking scenarios, only the mapping SID with the 32-bit mask IP prefix is supported. The SR interworking function does not take effect for the mapping SID mapped to an IP prefix with a non-32-bit mask. Properly plan the network. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In SR and LDP interworking scenarios, FRR does not take effect in the following situations: In the SR-to-LDP direction, one of the Q node and NEs on the path before the Q node does not support SR. In the LDP-to-SR direction, one of the PQ node and NEs on the path before the PQ node does not support LDP. Properly plan the network. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
SBFD is not supported in SR and LDP interworking scenarios because LDP does not support SBFD. Properly plan the network. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
After the device is restarted, if the BFD session of the local device or its neighbor is in Admin Down state, the IS-IS status is not affected. When the BFD session is renegotiated, if the BFD detection status reported by BFD is Down (used to be Up), the IS-IS neighbor is set to Down. In other cases, the IS-IS status is not affected. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Association between BFD and IS-IS neighbor status does not support broadcast interfaces or advanced MT interfaces. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |