OSPF does not make every router in a large network maintain one undifferentiated topology. It divides the routing domain into areas, each with its own link-state database for that area. Routers within an area use local link-state advertisements (LSAs) to calculate shortest paths; area border routers (ABRs) exchange selected reachability information between areas. Understanding which LSA crosses which boundary is what makes an OSPF design predictable.
OSPFv2 areas and LSA types only make sense once neighboring routers exchange routes correctly. Establish the OSPF adjacency and routing foundation first; then assess when area-design trade-offs justify changing LSA flooding boundaries.
What changes when a network is divided into areas?
In a single area, routers participating in that area’s OSPF topology share the relevant router and network LSAs. Their shortest-path calculation has the area’s topology information available. With multiple areas, the area border router connects separate link-state databases and advertises inter-area network reachability where area policy permits. A router in a non-backbone area does not need the entire topology graph of every other area to install an inter-area route.
That is a scalability mechanism, not an automatic performance guarantee. Poor boundary placement, unstable links, incorrect summaries or a heavily interconnected service topology can make a multi-area design harder to troubleshoot than one well-sized area. A second area is justified by routing scale, operational boundaries and change behavior—not merely by the number of VLANs.
Area 0 and the roles of internal routers, ABRs and ASBRs
Area 0 is the OSPF backbone. In a normal multi-area OSPFv2 design, non-backbone areas exchange inter-area reachability through the backbone. An internal router has all of its OSPF-enabled interfaces in one area. An ABR participates in more than one area and has the database and advertisement responsibilities that connect them. An ASBR injects external routes into OSPF from another routing domain, static routes or another source.
An ABR and an ASBR are different roles; one device may perform both. For example, a branch-edge router participating in area 10 and area 0 is an ABR. A core router redistributing selected external prefixes into OSPF is an ASBR. How the resulting LSAs spread depends on area type and redistribution policy.
A route appearing in the routing table is not proof that every router has the same complete topology. Inter-area routes summarize reachability, while intra-area routes derive from the local area’s detailed topology. When troubleshooting, identify the area membership and whether the destination is intra-area, inter-area or external before interpreting the LSA database.
| LSA type | Originator and meaning | Typical flooding scope |
|---|---|---|
| Type 1 — Router | Each router describes its links and costs within its area. | Inside one area. |
| Type 2 — Network | A designated router describes a multiaccess network and attached routers. | Inside one area. |
| Type 3 — Summary | An ABR advertises inter-area network reachability. | Into the receiving area according to area policy. |
| Type 4 — ASBR summary | An ABR advertises reachability to an ASBR, as needed. | Into applicable areas. |
| Type 5 — AS-external | An ASBR advertises external routes. | Across Type-5-capable OSPF areas, not normal stub areas or NSSAs. |
| Type 7 — NSSA external | An ASBR in a Not-So-Stubby Area advertises external reachability locally. | Inside the originating NSSA; selected LSAs may be translated at an ABR. |
The table covers the familiar OSPFv2 types relevant to basic enterprise area design. OSPFv3 uses a different LSA numbering and addressing model. Do not apply a Type 3/4/5 OSPFv2 diagram uncritically to every OSPFv3 implementation.
Type 1 and Type 2: why local topology stays local
Every router participating in an area originates Type 1 router LSAs reflecting its local links, neighbors and costs as appropriate. On broadcast or nonbroadcast multiaccess networks, a designated router (DR) may originate a Type 2 network LSA describing the attached router set. Those LSAs let the routers in that area calculate the local shortest-path tree without importing every internal link of every other area.
A misleading troubleshooting shortcut is to expect the same Type 1 LSA on two routers that belong to different areas. The LSDB is area-scoped. Instead, compare databases between routers inside the same area and confirm that the ABR advertises the intended inter-area reachability to the other area.
A neighbor stuck in an intermediate adjacency state or a missing Type 2 entry may have a local area, network type, DR election or interface issue. That is different from a missing inter-area summary LSA and should be investigated before changing ABR summarization policy.
Type 3 and Type 4: moving reachability between areas
An ABR originates Type 3 summary LSAs for networks reachable outside the receiving area. Despite the name, a Type 3 is not always an aggregated prefix; it can describe an individual inter-area network. Aggregation is a separate administrative choice made at appropriate area boundaries.
Type 4 advertises the location of an ASBR to routers that need to reach it. A router installing certain external routes may need both the external route description and a valid route to the ASBR or forwarding address. If external traffic fails while the external prefix is visible, check this reachability chain rather than assuming that seeing a Type 5 means the route is usable.
For example, an ABR between area 10 and area 0 might advertise area 10’s 10.20.0.0/16 network information into the backbone. Routers elsewhere receive a reachability summary, not the complete internal link graph of area 10. Whether they install a matching route still depends on the routing calculation and competing route preferences.
Type 5 and Type 7: importing external routes
Type 5 LSAs carry external prefixes originated by an ASBR. They can be E1 or E2 external routes with different cost interpretation; choosing between them is a policy and traffic-engineering decision. External route propagation is not the same as distributing all intra-area topology. Filtering external routes at area boundaries may be part of a stub-area design.
An NSSA allows selected external routes to originate inside an otherwise stub-like area using Type 7 LSAs. Type 7 advertisements remain inside that NSSA. An NSSA border router may translate eligible Type 7 LSAs into Type 5 so other Type-5-capable areas can use the external routes. The translation is not unconditional: configuration, translator election, propagation flags and route properties matter.
RFC 3101 describes this NSSA behavior. A useful failure scenario is an external network reachable within the NSSA but missing from area 0. Check whether the Type 7 exists, whether it is eligible for propagation and whether a border router is translating it. Adding a global default route is not a substitute for diagnosing a missing external advertisement.
Standard, stub, totally stubby and NSSA areas compared
| Area type | External routes | Inter-area visibility | Operational consequence |
|---|---|---|---|
| Normal area | Type 5 permitted. | ABR Type 3 summaries may be received. | Flexible, but potentially larger route and advertisement sets. |
| Stub area | Type 5 blocked. | Type 3 inter-area information generally available, often including default routing supplied by ABR. | Suitable when internal routers do not need each external detail. |
| Totally stubby area | Type 5 blocked. | Most specific Type 3 information suppressed in favor of a default. This is a common vendor-specific extension. | Simpler internal table at the cost of reduced route detail. |
| NSSA | Type 7 external routes may originate inside; Type 5 is blocked inside. | Type 3 behavior depends on NSSA options. | Useful for a stub-like site that must redistribute local external routes. |
Do not assume a totally stubby configuration is interchangeable across platforms. Verify vendor syntax and capabilities. A stub area also cannot contain an ordinary ASBR that floods Type 5 external LSAs; use an NSSA when controlled local external redistribution is required.
Area-type and hello-option mismatches can prevent neighbor adjacency. Converting an area from normal to stub or NSSA is therefore not a cosmetic routing-table change; all relevant routers must agree, and external-reachability behavior needs a migration test.
A diagnostic example: a route disappears after an area change
A branch in area 20 originally learns a redistributed vendor network as an external route. An administrator changes area 20 to a stub area to reduce the routing table and suddenly the vendor network disappears. The likely cause is not a failed interface: Type 5 external LSAs are no longer permitted inside the stub. If an ABR provides an appropriate default, the branch may still reach the network through that default, but only if next-hop and security routing agree.
The correct investigation is to inspect the exact destination and route classification, confirm area type on each router, inspect Type 3/default behavior and determine whether the branch needs explicit external prefix visibility. A design that requires local redistribution into the branch might warrant an NSSA rather than a normal stub, subject to policy.
When the issue concerns area 0 reachability or Type 7 translation, inspect the ABR’s databases and translation behavior instead. The key is to locate the point where the expected advertisement changes scope.
What the LSDB can and cannot prove
Useful verification includes interface area assignments, adjacency state, the router’s area-specific LSDB, ABR summaries and the installed routing table. On Cisco platforms, commands such as show ip ospf neighbor, show ip ospf database and show ip route ospf expose different parts of that process. Their exact availability and syntax depend on software family and release.
A healthy neighbor session does not guarantee that a route will be installed. The advertised prefix may be filtered, overridden by a more preferred route, lack valid reachability to its forwarding address, or be disallowed by the receiving area type. Treat OSPF path calculation and actual packet forwarding as separate checks.
Good multi-area design starts with a traceable path through those checks: local topology belongs to an area, ABRs advertise inter-area reachability, ASBRs introduce external information, and area policy determines which LSA classes may be seen. When something fails, that model is far more useful than memorizing a list of LSA numbers without their flooding scopes.