OSNEC.010: OSPF Stub and NSSA Areas Explained

Original cinematic anime illustration of a Latina network engineer examining routing diagnostics at a laptop beside high-speed network switches

OSNEC.010 explains why two healthy OSPF adjacencies can carry different sets of link-state advertisements. A stub area reduces external routing detail, while a not-so-stubby area (NSSA) makes a controlled exception for redistributed routes. The difference matters when a branch can reach internal subnets but not an advertised external service. Start with OSNEC.004 on areas and area border routers and OSNEC.005 on LSAs and the LSDB.

Cisco OSPF Lab 3, published 2024: Stub, Totally Stubby, NSSA and route redistribution. Publicly identified independent lab; actual player playback remains untested.

Stub areas reduce external advertisements

A normal OSPF area can receive Type 3 inter-area summary LSAs, Type 4 ASBR summaries, and Type 5 external LSAs when appropriate. A standard stub area blocks the external Type 4 and Type 5 information while retaining ordinary Type 3 summaries. An area border router (ABR) supplies a default route for other destinations. The result is a smaller routing database, not a disconnected branch.

A totally stubby area also suppresses non-default Type 3 summaries from other areas and relies on a default summary originated by the ABR. The totally stubby option is a common vendor extension, so operators must confirm platform syntax and behavior. Cisco’s OSPF area documentation describes the variation. A stub option mismatch between OSPF neighbors can prevent adjacency formation.

NSSA uses Type 7 LSAs

An ordinary stub area does not permit a local autonomous system boundary router (ASBR) to inject newly redistributed external routes. An NSSA permits local redistribution through Type 7 external LSAs. A selected NSSA ABR can translate eligible Type 7 information into Type 5 LSAs for other OSPF areas. Translation depends on the propagation bit and translator behavior; not every observed Type 7 must become Type 5. Consult Cisco’s NSSA guide and RFC 3101.

Standard NSSAs generally accept Type 3 inter-area summaries. A totally NSSA additionally suppresses non-default Type 3 summaries while retaining the local Type 7 mechanism. A crucial operational distinction concerns the default: do not assume a regular NSSA automatically receives a default route. The ABR’s default generation depends on configured options and vendor behavior. Juniper’s OSPF area guide details the relevant choices.

Tech With Ravish, “NSSA and Totally NSSA in OSPF Explained with Configuration Steps,” published 2025. Source video verified; reference documentation controls exact platform differences.

What each area should carry

AreaInter-area Type 3External Type 5Local Type 7
NormalAllowedAllowedNo
StubAllowed; ABR defaultBlockedNo
Totally stubbyDefault onlyBlockedNo
NSSAGenerally allowedBlockedAllowed
Totally NSSADefault onlyBlockedAllowed
OSPFv2 overview. “Totally” variants and default origination are platform-dependent. A regular NSSA does not universally inject a default automatically. Sources: Cisco and RFC 3101.

A default is useful only when its next hop can actually reach the destination. The presence of a 0.0.0.0/0 route is not proof of end-to-end service health. See OSNEC.003 on default routes. If the OSPF adjacency never reaches Full, resolve neighbor conditions before interpreting LSAs; OSNEC.006 addresses adjacency states and MTU mismatches.

Read-only lab: the missing external route

Consider a fictional Area 20 branch with a local ASBR and an ABR connecting to Area 0. The branch reaches an internal prefix but an external route does not appear in another area. Record the current area mode and compare LSAs on the ASBR, ABR and receiving router. On supported Cisco IOS devices, read-only inspection may use:

show ip ospf neighbor
show ip ospf
show ip ospf database summary
show ip ospf database nssa-external
show ip ospf database external
show ip route ospf

First, establish whether Area 20 is a stub or NSSA. A stub should not carry locally originated Type 7 information. In an NSSA, verify that an ASBR originated the required Type 7, then inspect eligible translation and filtering at the ABR. If the failure instead concerns missing internet reachability, investigate default-route origination and forwarding rather than guessing that all NSSAs contain a default. Juniper provides different commands such as show ospf route. Actual output depends on platform and software version.

Avoid changing a production area to NSSA during diagnosis. Area-option changes, redistribution policies and ABR settings can reset adjacencies or alter reachability. Run configuration experiments only in a lab or an approved maintenance window.

Pedro Lino Cáceres, “OSPF Stub Areas & Totally Stubby Areas,” May 2024. Verified public instructional video. Playback within the published iframe requires separate testing.

Exercises and conclusion

For a normal, stub, NSSA and totally NSSA area, predict whether Type 3, Type 5 and Type 7 LSAs should appear. Explain one reason a Type 7 may remain untranslated, and identify the specific ABR and policy evidence you would collect. Finally, explain why an OSPF Full adjacency and an installed default route are insufficient to prove external application reachability.

Takeaway: Stub areas reduce external routing detail, whereas NSSAs enable a limited local external-route exception. Effective troubleshooting checks the actual area type, permitted LSAs, ABR translation, default-route policy and forwarding state instead of trusting a green adjacency indicator.

Editor’s Note: Cisco documentation, RFC 3101 and Juniper guidance were used to verify the technical distinctions. Area 20 is an illustrative case, not a production incident. Three source-identified YouTube videos are included, but independent player playback and mobile viewport testing were not available. The original 1200 × 630 cinematic-anime featured image does not depict actual operational equipment, and no router commands were executed.

We volunteer daily to ensure the credibility of the information on this platform is Verifiably True. If you would like to support to help further secure the integrity of our research initiative, please scan the QR code below

Original BitcoinVersus.Tech QR for an optional 5,000-satoshi donation

The voluntary suggested donation is 5,000 satoshis. Verify recipient 3C9o19EH5HSiwEPyCTmEKzxhNCbo2X6TTb and amount before sending. Bitcoin transfers generally cannot be reversed. The lesson is educational and is not permission to modify production networks, professional engineering advice, or financial or investment advice.

Leave a Reply