Feature Requirements |
Series |
Models |
|---|---|---|
OSPF checks whether a neighbor in the full state exists in the backbone area before advertising a default route to the stub area. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When a device in an NSSA generates an NSSA LSA based on an imported external route, the device preferentially uses the IP address of a loopback interface in the NSSA as the forwarding address (FA). If no loopback interfaces exist in the NSSA, the device selects the IP address of a non-loopback interface. As a result, the downstream device may fail to implement load balancing using routes even when links with the same cost exist. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
OSPF advertises default routes to an NSSA only when neighbor relationships in the Full state exist in the backbone area or default routes of another protocol or of another OSPF process exist in the same VPN instance on the device, and the nssa default-route-advertise command is run. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
1. The mapping SID priority is not supported. All mapping SIDs are processed based on the default priority. 2. On a TI-LFA protection path, the devices from the source node to the Q node must support segment routing and the LDP path from the Q node to the destination node must be available. 3. The SR route mapped to a mapping SID does not support anycast FRR. Anycast FRR protection is not formed between the SR routes mapped to the mapping SIDs and between the SR route mapped to mapping SID and the common SR route. 4. The SR route mapped to the mapping SID does not support remote anti-micro-loop. 5. in cross-process and cross-protocol scenarios, when ASBRs function as interworking stitching nodes, the mapping-SID mapping needs to be configured on the process to be imported. Properly plan the network. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In SR and LDP interworking scenarios, PHP is not supported. 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. Properly plan the network. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
In an SR and LDP interworking scenario, FRR does not take effect in some scenarios, for exmaple: In the SR to LDP direction, the Q node and all NEs on the path before the Q node are required to support SR. In the LDP to SR interworking FRR scenario, the PQ and all NEs on the path before the PQ are required support LDP. Properly plan configurations. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When the maximum cost is advertised after a routing loop is detected, the apply cost configuration in a route-policy does not take effect. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
OSPF multi-area neighbors and OSPFv3 multi-instance neighbors cannot be distinguished on the forwarding plane. Therefore, both share the same session-CAR entries. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The OSPF NM component supports association between BFD and the costs of broadcast links. (1) If only one OSPF neighbor relationship is established over a broadcast link and the BFD session is down, the OSPF neighbor relationship is not deleted. Instead, the OSPF LSDB component is notified that association between BFD and the cost has taken effect for the neighbor relationship. (2) If multiple OSPF neighbor relationships are established over a broadcast link, this function is not supported. When more than one OSPF neighbor relationship is established over a broadcast link, the OSPF neighbor relationships are deleted when the associated BFD sessions are down, and the OSPF LSDB component is notified of the deletion. Ensure that only one OSPF neighbor relationship is established over a broadcast link. |
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 a routing loop is removed, the device cannot automatically exit the routing loop state. To allow the device to exit the routing loop state and clear the alarm, you need to configure a routing policy or route tag and then run the clear route loop-detect ospf alarm-state command. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Only the loops that occur during inter-process route import between two devices can be detected. If more than two devices are involved during inter-process route import, loops cannot be detected. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Summary and NSSA routes do not support loop detection. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Router ID conflicts, including intra-AS and inter-AS router ID conflicts, are not supported because a router ID conflict may trigger a false detection. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When the device advertises a large cost during the routing loop period, the apply cost command does not take effect in the routing policy. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
A single process supports loop detection for a maximum of 100,000 routes. If more than 100,000 routes are imported, routing loops cannot be detected for the excess routes. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
After the device enters the loop breaking state, it cannot automatically exit the routing loop state and the alarm cannot be automatically cleared. In this case, manual intervention is required. For example, after a routing policy or route tag is correctly configured, run the clear route loop-detect ospf alarm-state command to exit the routing loop state and clear the alarm. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The default route advertised using the default-route-advertise command supports only loop detection and does not support self-healing. |
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 OSPF 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 OSPF neighbor is set to Down. In other cases, the OSPF status is not affected. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |