Limitations for OSPF-NE05E
Restrictions |
Guidelines |
Impact |
|---|---|---|
OSPF checks whether a neighbor in the full state exists in the backbone area before advertising a default route to the stub area. |
Plan configurations properly. |
Default routes fail to be delivered. |
OSPF advertises default routes to an NSSA only when at least neighbor in the full state exists in the backbone area or default routes of another protocol or of another OSPF process exists in the same VPN instance, and the nssa default-route-advertise command is run. |
Plan configurations properly. |
Default routes fail to be delivered. |
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. |
Plan configurations properly and determine whether to enable OSPF on the loopback interface. |
Load balancing fails to be implemented, which may cause link congestion. |
Before running the undo ospf process-id command to delete an OSPF process, you need to check whether segment routing is enabled. If segment routing is enabled, you need to disable it before deleting the OSPF process. Otherwise, Opaque LSAs may remain unexpectedly due to the Opaque capability change if the process is reconfigured. |
Before running the undo ospf process-id command to delete an OSPF process, you need to check whether segment routing is enabled. If segment routing is enabled, you need to disable it before deleting the OSPF process. Otherwise, Opaque LSAs may remain unexpectedly due to the Opaque capability change if the process is reconfigured. |
The residual Opaque LSAs are used for calculation. As a result, a calculation error occurs and may last for a maximum of 3600s. |
Previous
