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

How to import Putty Saved Connections to mRemoteNG

Just started using mRemoteNG and its being very cool to connect to different remote connection with different protocols e.g Window Remote Desktop, VNC to Linux, SSH, HTTP connection etc. from a single application. As new user I configured some remote desktop connection which was quite easy to figure out. But when I wanted to add SSH connections, it came in my mind to import all of the saved connections in the putty. But I couldn't figure it out how can it be done, though it was quite easy and here are the steps. Open your mRemoteNG Create a folder if you want segregation of multiple networks Create a new connection Enter the IP address of remote server under connection in Config pane Under the config pane, select protocol " SSH version 2 ".  Once you select protocol to SSH version 2 you are given option to import putty sessions, as shown in the snap below. In the above snap, I have imported CSR-AWS session from my saved sessions in Putty.
1 comment
Read more

Authoritative DNS Servers Delegation and Internal DNS Explained

DNS (Domain Name System) plays a critical role in how users and systems find resources on the internet or within internal networks. Whether it's managing an internal domain in an enterprise or delegating parts of a domain for traffic distribution, DNS setups vary widely depending on needs. In this blog post, we’ll break down the different types of DNS setups, including authoritative DNS servers, DNS delegation, and how internal DNS functions within organizations. 1. Authoritative DNS Server An Authoritative DNS server is the final source of truth for a specific domain. When someone queries a domain (e.g., example.com ), the authoritative DNS server for that domain holds the DNS records (A records, CNAME, MX, etc.) and responds with the corresponding IP address. Key Points: Who can host it? Authoritative DNS servers are often hosted by domain registrars (e.g., GoDaddy, Namecheap) or cloud DNS providers (e.g., AWS Route 53, Cloudflare). However, organizations can also host their ...
Post a Comment
Read more

BGP MED: Managing Inbound Traffic with Multi-Exit Discriminator

The Multi-Exit Discriminator (MED) is used in BGP to control inbound traffic into your AS. It tells a neighboring AS which entry point into your network it should prefer when there are multiple links between your AS and the neighboring AS. The lower the MED value , the more preferred the path. MED is only honored between the same neighboring AS . Example Scenario : You are connected to ISP1 via two routers, CE1 and CE2 , and want to control which router ISP1 uses to send traffic into your AS. Network Topology : CE1 (connected to ISP1): 10.0.1.1/30 CE2 (connected to ISP1): 10.0.2.1/30 iBGP Router (Internal) connected to both CE1 (10.0.1.2/30) and CE2 (10.0.2.2/30). Configuration on CE1 (Lower MED, More Preferred) : Create a route map to set the MED to 50 for CE1: route-map SET_MED permit 10 set metric 50 Apply this route map to the neighbor in the BGP configuration for CE1: router bgp 65001 neighbor 10.0.1.1 remote-as 65000 neighbor 10.0.1.1 route-map SET_MED out Configuratio...
Post a Comment
Read more