OSPF can run as one large area, but larger designs may divide the routing domain into multiple areas. The engineering purpose is not to create complexity for its own sake. Areas create boundaries for link-state information, and an Area Border Router (ABR) connects a non-backbone area to the OSPF backbone. This lesson builds directly on OSNEC.001: OSPF Fundamentals, OSNEC.002: Route Summarization Fundamentals, and OSNEC.003: OSPF Default Routes.
Learning Objectives
- Explain why OSPF uses areas and why Area 0 is the backbone.
- Identify internal routers, backbone routers, and Area Border Routers.
- Distinguish intra-area routes from inter-area routes.
- Configure a simple two-area OSPF lab.
- Verify neighbors, area membership, LSDB information, and inter-area routes.
- Recognize when multi-area OSPF adds useful scale and when it adds unnecessary complexity.
Why OSPF Has Areas
Every router inside an OSPF area maintains link-state information for that area and runs the SPF calculation against that topology. Dividing a large routing domain into areas can limit how widely detailed topology changes must be processed. It also creates boundaries where engineers can summarize internal routes when the addressing plan supports it.
A small or moderate network does not automatically need multiple areas. Modern routers can handle substantial single-area OSPF deployments, and a simple design is usually easier to operate. Engineers should introduce additional areas to solve a defined scale, failure-domain, or summarization problem—not merely because the protocol supports them.
Area 0 Is the Backbone
In a normal multi-area OSPF design, Area 0 is the backbone area. Other areas exchange inter-area routing information through the backbone. An interface belongs to one OSPF area, while a router can participate in more than one area because different interfaces may be assigned to different areas.
What an ABR Does
An Area Border Router participates in the backbone and at least one additional OSPF area. It maintains separate link-state information for its attached areas and provides the routing boundary between them. In OSPFv2, ABRs can originate Type 3 summary LSAs that describe inter-area destinations. This is also the boundary where internal route summarization can be performed in designs that support it.
An ABR is not the same thing as an Autonomous System Boundary Router (ASBR). An ASBR injects routes from outside the OSPF routing domain through redistribution. A router can technically perform both roles, but the functions are different and should be understood separately.
How Inter-Area Routes Appear
On Cisco IOS-style output, a route learned from another OSPF area commonly appears with the code O IA. The O identifies OSPF, while IA means inter-area. A route learned inside the router’s own area appears as an intra-area OSPF route without the IA marker. The exact display varies by platform, so engineers should verify both the route table and the OSPF database instead of relying on one command.
Two-Area Lab Topology
Build a controlled three-router lab. R1 and the R1–R2 link belong to Area 0. R2 is the ABR. The R2–R3 link and R3 belong to Area 10. Add a loopback on R1 to represent a backbone network and a loopback on R3 to represent a network inside Area 10.
- R1–R2: 10.0.12.0/30, Area 0
- R1 loopback: 10.0.1.1/32, Area 0
- R2–R3: 10.0.23.0/30, Area 10
- R3 loopback: 10.10.3.3/32, Area 10
Cisco IOS-Style Configuration
On R1, enter router ospf 1, then advertise the R1–R2 network into Area 0 with network 10.0.12.0 0.0.0.3 area 0. Advertise the R1 loopback with network 10.0.1.1 0.0.0.0 area 0.
On R2, enter router ospf 1. Place the R1-facing network into Area 0 with network 10.0.12.0 0.0.0.3 area 0. Place the R3-facing network into Area 10 with network 10.0.23.0 0.0.0.3 area 10. Because R2 has OSPF interfaces in Area 0 and Area 10, it becomes the ABR in this lab.
On R3, enter router ospf 1, then use network 10.0.23.0 0.0.0.3 area 10 and network 10.10.3.3 0.0.0.0 area 10. These commands are examples for an isolated lab; interface-based OSPF configuration may be preferred on other platforms or designs.
Verify Before You Trust the Design
On every router, start with show ip ospf neighbor. R1 should form a neighbor relationship with R2, and R3 should form one with R2. On R2, use show ip ospf interface brief to confirm that one routed interface belongs to Area 0 and the other belongs to Area 10.
Next, inspect show ip route ospf. R1 should learn the Area 10 loopback as an inter-area route, while R3 should learn the Area 0 loopback as an inter-area route. On Cisco IOS-style output, these should normally appear as O IA. Then inspect show ip ospf database summary to study the summary LSAs that represent inter-area reachability.
Real-World Design Debate
Multi-area OSPF is technically important, but engineers do not agree that every enterprise network should use it. In modern networks, a single well-designed Area 0 can often remain simpler and perfectly adequate. The decision should be driven by the size of the LSDB, route summarization requirements, topology-change scope, platform limits, and operational skill—not by a rule that every site deserves its own area.
Failure Test
After the lab is stable, shut the R2–R3 interface or otherwise disable that link in the simulator. Confirm that the R1 route to 10.10.3.3/32 disappears after OSPF converges. Restore the link and verify that the neighbor adjacency returns and the inter-area route is relearned. This exercise proves that the route is dependent on the expected area boundary rather than simply appearing in the table by accident.
Engineering Exercise
- Build the R1–R2–R3 topology in a simulator or approved lab.
- Record the OSPF neighbor table on all three routers.
- Record the area membership of each routed interface.
- Verify the R3 loopback on R1 and the R1 loopback on R3.
- Identify which routes are intra-area and which are inter-area.
- Capture the summary-LSA output on R1 or R3.
- Fail the Area 10 link, observe convergence, then restore it.
- Explain whether this three-router design actually needs multiple areas in production and justify your answer.
Knowledge Check
1. What is the purpose of Area 0? 2. What makes a router an ABR? 3. What does O IA mean in Cisco-style routing output? 4. Why can multiple OSPF areas reduce the scope of topology information? 5. Why should engineers avoid creating extra areas without a clear design reason? 6. Which command verifies OSPF neighbor relationships?
Answer Guide
1. Area 0 is the OSPF backbone that carries inter-area routing information between normal OSPF areas. 2. An ABR participates in Area 0 and at least one additional OSPF area. 3. It identifies an OSPF inter-area route. 4. Routers maintain detailed link-state topology for their own area, while ABRs exchange summarized inter-area reachability between areas. 5. Extra areas add configuration, troubleshooting, and design complexity. 6. show ip ospf neighbor.
References
Primary technical references: RFC 2328 — OSPF Version 2 and Cisco’s OSPF areas and router roles guide. The next canonical certification track after Network Engineering is Python.
Leave a Reply