Troubleshooting OSPF NSSA: Configuration, Compatibility & Error Resolving

Overview & Thematic Scope

This FAQ provides targeted troubleshooting and configuration guidance for network engineers deploying OSPF Not-So-Stubby Areas (NSSA) on edge routers. NSSA allows external route redistribution into a stub-like area via Type 7 LSAs, which are translated to Type 5 LSAs by the Area Border Router (ABR) . This article addresses common technical issues, from P-bit handling and default route advertisement to translator state elections and high-availability failures.

Frequently Asked Questions

Q1: What is the primary troubleshooting step when OSPF does not convert an area to NSSA after configuration?

Verify that the command correctly sets the area type to NSSA; however, on some platforms, the area may not generate Type 7 LSAs until a reboot or process restart occurs. If the configuration does not take effect immediately, save the configuration and reboot the router, as this forces the router to re-evaluate its area role and generate the correct LSA types . This is a known behavior on certain software versions.

Q2: How do I prevent specific external routes learned in an NSSA from being advertised to the rest of the OSPF domain?

Control the P-bit (Propagate bit) in the Type 7 LSA generated by the NSSA ASBR. If the P-bit is set to 0, the NSSA ABR will not translate the Type 7 LSA into a Type 5 LSA, preventing the route from being flooded to the backbone and other areas. Use the summary-address command with the not-advertise keyword on the ASBR to set the P-bit to 0 for specific routes .

Q3: Why does my aggregation switch lose its OSPF default route for up to 20 minutes after a stack split, and how can I fix it?

This occurs because the standby core switch (ASBR) sends a route-withdrawal LSA when its default route becomes invalid upon split, and the active core does not re-advertise its default route immediately. The default route is refreshed every 1800 seconds, leading to a long outage .
Solution: Configure the nssa default-route-advertise backbone-peer-ignore command on the core switches. This prevents the ABR from checking the neighbor status and ensures a default Type 7 LSA is generated as long as there is an Up interface in the backbone area .

Q4: What triggers the NSSA translator state to change on an ABR, and how do I verify the elected translator?

The translator state changes due to topology changes, such as the configuration or deletion of the translator-always command, a new router ID taking effect, or the addition/removal of a device from the NSSA . To verify the current translator state, use the display ospf brief or display ospfv3 area command to check if the local device is in the ELECTED or ALWAYS state .

Q5: Why isn’t OSPF forming equal-cost multipath (ECMP) routes for the default route in an NSSA?

This can happen when the default route is generated by the ABR using the nssa default-route-advertise command. The Type 7 LSA generated by the ABR is populated with a forwarding address (FA) that is set to one of its own interface addresses in the NSSA. When calculating the route, the router will only install the path to that specific IP address (the FA) as the next hop, rather than installing multiple equal-cost paths to the ABR itself .

Q6: Which router performs the translation of Type 7 LSAs to Type 5 LSAs in an NSSA, and how is it selected?

The NSSA ABR performs the translation. If there are multiple ABRs in the NSSA, only the one with the highest router ID is elected to perform the translation. This is the default behavior, unless the translator-always command is configured on a specific ABR, forcing it to take on the translation role .

Q7: What are the key configuration steps and considerations for setting up OSPF NSSA on an edge router?

First, ensure basic OSPF connectivity is established. Enter router configuration mode and specify the area type as NSSA . For redistribution, configure the redistribute command, optionally using the nssa-only keyword to ensure routes remain Type 7 LSAs. To generate a default route into the NSSA, use the nssa default-route-advertise command . Finally, verify the configuration using the show ip ospf area command .