Skip to main content

Understanding OSPF Area Types: Stub, NSSA, Totally Stubby, and Totally NSSA

When designing an OSPF network, understanding the various area types plays a crucial role in optimizing routing efficiency and controlling the size of the routing table. OSPF areas such as Stub, NSSA (Not-So-Stubby Area), and their Cisco proprietary counterparts, Totally Stubby and Totally NSSA, each serve specific purposes in different network scenarios. These area types help reduce the amount of routing information shared within an area while controlling the advertisement of external and inter-area routes. In this post, we will explore the characteristics, use cases, and default route advertisement behavior of these OSPF areas, providing insight into how they can improve network performance and scalability.

OSPF Area Type

Allowed LSAs

Disallowed LSAs

Use Cases

Key Characteristics

Default Route Injection

Stub Area

Type 1 (Router),
Type 2 (Network),
Type 3 (Summary)

Type 4 (ASBR Summary),

Type 5 (External)

Small areas where external routes aren’t needed.

Provides a default route to reach external destinations.
Reduces routing table size.
No external routes allowed (Type 5 LSAs).

Automatically injected by the ABR.

Totally Stubby Area

Type 1 (Router),
Type 2 (Network)

Type 3 (Summary except default),
Type 4,
Type 5

Ideal for branch offices or remote sites.

More restricted than Stub Areas.
Only a default route is propagated from the ABR.
Prevents external and inter-area routes.

Automatically injected by the ABR.

NSSA (Not-So-Stubby Area)

Type 1 (Router),
Type 2 (Network),
Type 3 (Summary),
Type 7 (NSSA External)

Type 4,
Type 5

Areas that need to inject external routes from an ASBR (Type 7 LSAs).

Allows redistribution via Type 7 LSAs.
Type 7 LSAs are converted to Type 5 at the ABR.
Blocks Type 5 LSAs.

Requires manual injection using default-information originate.

Totally NSSA

Type 1 (Router),
Type 2 (Network),
Type 7 (NSSA External)

Type 3 (Summary except default),
Type 4,
Type 5

Used where external routes are needed but fewer routes are required.

ike Totally Stub, but allows Type 7 LSAs.
Only default route and Type 7 external routes allowed.
Blocks Type 3 summary LSAs (except default).

Requires manual injection using default-information originate.

Key Differences:

  • Cisco Proprietary Extensions:
    • Totally Stubby Area and Totally NSSA are Cisco proprietary and further reduce the routing information exchanged within the area compared to standard OSPF Stub and NSSA areas.
  • Default Route Advertisement:
    • Stub, Totally Stubby Area, and Totally NSSA automatically receive a default route (0.0.0.0) from the ABR.
    • NSSA requires manual configuration of a default route using default-information-originate.

Summary:

  • Stub Area: Blocks external routes but allows inter-area routes. Default route injected automatically.
  • Totally Stubby Area: Blocks both external and inter-area routes, allows only a default route.
  • NSSA: Blocks external routes but allows redistribution of local external routes as Type 7 LSAs.
  • Totally NSSA: Blocks both external and inter-area routes but allows local external redistribution as Type 7 LSAs and receives a default route from ABR.

These OSPF areas help optimize routing and reduce the size of the OSPF database depending on the network design.

 


Labels:

Comments

Post a Comment

Popular posts from this blog

Basic MPLS BGP and L3VPN Lab Setup

In this lab, we’ve set up a basic MPLS, BGP, and L3VPN environment, which is a great foundation for understanding how service providers build scalable networks. The lab uses the EVE-NG simulator along with Router IOS C7200-ADVENTERPRISEK9-M, Version 15.2(4)M8 to emulate a realistic MPLS environment. Below is a summary of the key components and roles of each router in the lab. MPLS Core Routers : The MPLS core consists of the routers responsible for label switching and forwarding customer traffic through the network: PE1 (Provider Edge 1) : Connects customer networks to the MPLS core and handles both MPLS and BGP routing. It also hosts VRF (Virtual Routing and Forwarding) instances for customers. PE2 (Provider Edge 2) : Functions similarly to PE1, connecting another customer network to the MPLS core. P1 (Core Router 1) and P2 (Core Router 2) : These routers serve as MPLS core routers and handle label switching but do not store or process customer routes directly. They simply f
Post a Comment
Read more

OSPF Adjacency Stuck in EXSTART on Cisco IOS XR – Issue and Solution

In a recent lab setup using Cisco IOS XR on EVE-NG, I faced a common but frustrating issue with OSPF adjacencies getting stuck in the EXSTART state. After spending considerable time troubleshooting interface MTUs and configurations, I discovered that the root cause was related to the virtual network interface type being used. This post outlines the issue, troubleshooting steps, and the eventual solution that got everything working. Issue: While configuring OSPF between two routers running Cisco IOS XR in my lab, OSPF adjacencies were getting stuck in the EXSTART state. I verified that interface configurations, MTU settings, and OSPF parameters were correct, but the problem persisted. I tried adjusting the MTU size, using the mtu-ignore command, and even checked for ACLs, but nothing seemed to resolve the issue. Troubleshooting Steps: MTU Settings: I started by verifying that both sides of the OSPF adjacency had matching MTUs. I used the default MTU and even tried different values wit
Post a Comment
Read more

How to Properly Clone an EVE-NG Lab with Configurations

Cloning labs in EVE-NG is a great way to duplicate setups and expand or experiment on a new copy without affecting the original lab. However, if not done correctly, the cloned lab may only copy the topology without configurations. In this guide, I’ll show you how to properly clone a lab in EVE-NG with all configurations using the EVE-NG GUI . Follow these steps to ensure that both the topology and router configurations are retained when cloning your lab. Steps to Clone an EVE-NG Lab with Configurations Save Running Configuration on All Devices In your original lab, make sure all devices have their configurations saved to NVRAM. Go into the CLI of each router and run the command: copy running-config startup-config Export All Configurations (CFGs) On the left sidebar in the EVE-NG Web UI , click on the "More Actions" option. Then select "Export all CFGs" . This step exports the configurations of all devices in the lab. Shutdown All Devices After exporting the confi
Post a Comment
Read more