Mastering OSPF Stub Areas: When and Why to Use Them

March 2015   |   Reading Time: 10 min read

Introduction

Open Shortest Path First (OSPF) is a link-state routing protocol widely used in enterprise and service provider networks. As OSPF networks scale, it becomes critical to manage the size of routing tables and the number of LSAs (Link-State Advertisements) flooded throughout the topology. OSPF stub areas are one method to reduce this overhead without sacrificing network reachability.

What Are OSPF Stub Areas?

Stub areas are special types of OSPF areas where external routes (Type 5 LSAs) are restricted. Instead of learning each external route individually, routers in stub areas receive a default route (0.0.0.0/0) pointing toward the ABR (Area Border Router).

Types of Stub Areas

• Stub Area – Blocks Type 5 LSAs, injects a default route.
• Totally Stubby Area – Blocks Type 3 and Type 5 LSAs, only default route is allowed.
• Not-So-Stubby Area (NSSA) – Allows Type 7 LSAs from redistribution inside the area and converts them to Type 5 at the ABR.
• Totally NSSA – Like NSSA, but blocks inter-area routes (Type 3 LSAs).

When to Use Stub Areas

Stub areas are ideal for edge segments or branches that need connectivity but don't require visibility into external destinations. Using stub areas can reduce router CPU, memory usage, and LSA flooding, which improves convergence time.

Design Considerations

• All routers in the area must agree on stub configuration.
• You cannot have an ASBR inside a stub area (except for NSSA).
• Mixing stub and non-stub routers causes adjacency failure.
• Stub areas work best for leaf segments with a single path to the core.

Sample Configuration

    ! Configure Area 1 as a stub on the ABR
    router ospf 1
     area 1 stub
    !
    ! Configure on internal routers
    router ospf 1
     area 1 stub
    !
    ! To make Area 1 a totally stubby area
    router ospf 1
     area 1 stub no-summary

NSSA Configuration Example

    router ospf 1
     area 2 nssa
    !
    ! NSSA with no-summary (Totally NSSA)
    router ospf 1
     area 2 nssa no-summary
    !
    ! Redistributing into NSSA
    router ospf 1
     redistribute static subnets
     area 2 nssa

Benefits of Stub Areas

• Reduced routing table size
• Lower LSA flooding and faster convergence
• Minimized complexity for edge routers
• More predictable routing behavior

Limitations and Pitfalls

• Cannot have multiple exit points without breaking stub logic
• Default routes may mask suboptimal paths
• Cannot host an ASBR (except in NSSA)
• Must manually configure all routers consistently

Verification and Troubleshooting

• Use show ip ospf and show ip ospf database to inspect LSA types
• Check for neighbor issues using show ip ospf neighbor
• Confirm stub configuration with show ip protocols
• Debug with debug ip ospf adj for adjacency problems

Conclusion

Stub areas are a simple yet powerful way to optimize OSPF networks. By strategically applying stub area configurations, network engineers can ensure scalability, improve stability, and maintain control over routing behavior. Understanding the differences between stub types and applying them correctly is key to successful OSPF design.

Eduardo Wnorowski is a network infrastructure consultant and technologist.
With over 20 years of experience in IT and consulting, he brings deep expertise in networking, security, infrastructure, and transformation.
Connect on Linkedin

Optimizing OSPF Design in Multi-Area Environments

October 2013   |   Reading Time: 10 minutes

Open Shortest Path First (OSPF) remains one of the most deployed interior gateway protocols (IGPs) in enterprise networks. When networks scale, OSPF's support for hierarchical design using areas becomes invaluable. However, poorly structured multi-area OSPF designs can create instability, introduce suboptimal routing, and complicate troubleshooting.

Why Use Multi-Area OSPF?

OSPF scales better when the link-state database (LSDB) is segmented. Area 0 serves as the backbone, and additional areas (1, 2, etc.) connect to it via Area Border Routers (ABRs). This segmentation improves convergence and limits flooding scope for LSAs.

Key Design Principles

• Always connect non-backbone areas to Area 0: Virtual links should only be temporary workarounds.
• Minimize ABRs: Too many ABRs can result in inconsistent LSDBs and route flapping.
• Summarize: Use area range statements on ABRs to reduce routing table size and provide stability.
• Plan LSAs: Understand which LSAs are injected where. Type 3 LSAs (summary) are most common between areas.

Common Pitfalls

Misunderstanding LSA propagation often causes routing loops or instability. For example, injecting Type 5 LSAs (external routes) into stub or totally stubby areas causes configuration issues. Misplacing ABRs or neglecting area summarization results in excessive LSA flooding and convergence delays.

ABR Behavior in IOS and IOS-XE

In IOS-based routers, ABR behavior is based on active interfaces belonging to multiple areas. In OSPFv2 (IPv4), at least one interface must be in Area 0. In newer platforms, ABRs behave differently when using passive interfaces — a key consideration when virtualizing edge routers.

Optimizing with Stub, Totally Stubby, and NSSA Areas

Using stub area types reduces Type 5 LSA propagation and can simplify routing decisions. NSSA areas allow redistribution of external routes without exposing the entire external LSA set to the backbone. Remember that NSSA Type 7 LSAs are converted to Type 5 by the ABR.

Design Example

Consider a WAN with 3 branch offices and a central hub. Each branch connects to Area 1, Area 2, and Area 3, respectively, while the core remains in Area 0. Using summarization on ABRs prevents detailed branch prefixes from polluting the backbone. Virtual links are avoided entirely, and NSSA is deployed on Area 3 to support Internet redistribution.

Tuning OSPF Timers

In high-performance environments, adjusting hello and dead timers can improve convergence. Fast hello intervals (e.g., 1 second hello, 3 second dead) may be acceptable on Ethernet segments but can increase CPU usage. Apply carefully in LANs, not across WANs.

Best Practices

• Design with hierarchy in mind and limit areas to fewer than 50 routers.
• Use summarization aggressively at ABRs.
• Deploy NSSA or stub areas where appropriate.
• Visualize LSDB and SPF calculations using tools like IOS commands: show ip ospf database and show ip ospf border-routers.

With careful planning and proper LSA scoping, multi-area OSPF can scale efficiently even in complex enterprise topologies. Avoid overengineering and focus on simplicity, summarization, and proper ABR placement.

Eduardo Wnorowski is a network infrastructure consultant and technologist.
With over 18 years of experience in IT and consulting, he brings deep expertise in networking, security, infrastructure, and transformation.
Connect on Linkedin