PacketLab
OSPF · Multi-area design

Backbone and ABRs

Identify the area boundary and preserve a connected backbone.

Understand

R1 and R2 connect through area 0. R1 also attaches area 1/R3; R2 attaches area 2/R4. R1 and R2 are ABRs, maintaining separate area databases. Interfaces belong to areas; a router can participate in several. R3 and R4 are internal routers in their own areas.

Inter-area routing uses a backbone-centered hierarchy. Non-backbone areas connect to area 0 through ABRs; keep area 0 contiguous. An area number on an isolated interface is not a substitute for actual backbone connectivity. Virtual links can logically extend the backbone through a transit area, but have constraints and are a repair/design exception rather than the default solution. Stub areas cannot be virtual-link transit areas.

Lab setup

Use a fresh lab for this lesson; changes from other lessons are not cumulative. All outputs are illustrative excerpts, not recorded router tests. Transit cost is explicitly 10 and Loopback0 cost is 1. Interface names may vary by image.

Lab topologyIllustrative topology
192.0.2.0/30area 0192.0.2.4/30area 2192.0.2.8/30area 1R3Lo0 · 10.255.0.3/32R1Lo0 · 10.255.0.1/32R2Lo0 · 10.255.0.2/32R4Lo0 · 10.255.0.4/32
Solid lines are physical links, configured as point-to-point. Interfaces and areas are listed below. Router symbol: GNS3, GPL-2.0. Original layout.
RouterInterfaceIPv4 addressArea
R1Gi1192.0.2.1/300
R2Gi1192.0.2.2/300
R2Gi2192.0.2.5/302
R4Gi1192.0.2.6/302
R1Gi2192.0.2.9/301
R3Gi1192.0.2.10/301

Loopback0 is 10.255.0.<router number>/32; area assignments: R1: area 0, R2: area 0, R3: area 1, R4: area 2.

Complete baseline configurations

R1

Configuration
configure terminal
hostname R1
router ospf 1
 router-id 10.255.0.1
 passive-interface Loopback0
 exit
interface Loopback0
 ip address 10.255.0.1 255.255.255.255
 ip ospf 1 area 0
 ip ospf cost 1
 exit
interface GigabitEthernet1
 ip address 192.0.2.1 255.255.255.252
 ip ospf network point-to-point
 ip ospf cost 10
 ip ospf 1 area 0
 no shutdown
 exit
interface GigabitEthernet2
 ip address 192.0.2.9 255.255.255.252
 ip ospf network point-to-point
 ip ospf cost 10
 ip ospf 1 area 1
 no shutdown
 exit
end

R2

Configuration
configure terminal
hostname R2
router ospf 1
 router-id 10.255.0.2
 passive-interface Loopback0
 exit
interface Loopback0
 ip address 10.255.0.2 255.255.255.255
 ip ospf 1 area 0
 ip ospf cost 1
 exit
interface GigabitEthernet1
 ip address 192.0.2.2 255.255.255.252
 ip ospf network point-to-point
 ip ospf cost 10
 ip ospf 1 area 0
 no shutdown
 exit
interface GigabitEthernet2
 ip address 192.0.2.5 255.255.255.252
 ip ospf network point-to-point
 ip ospf cost 10
 ip ospf 1 area 2
 no shutdown
 exit
end

R3

Configuration
configure terminal
hostname R3
router ospf 1
 router-id 10.255.0.3
 passive-interface Loopback0
 exit
interface Loopback0
 ip address 10.255.0.3 255.255.255.255
 ip ospf 1 area 1
 ip ospf cost 1
 exit
interface GigabitEthernet1
 ip address 192.0.2.10 255.255.255.252
 ip ospf network point-to-point
 ip ospf cost 10
 ip ospf 1 area 1
 no shutdown
 exit
end

R4

Configuration
configure terminal
hostname R4
router ospf 1
 router-id 10.255.0.4
 passive-interface Loopback0
 exit
interface Loopback0
 ip address 10.255.0.4 255.255.255.255
 ip ospf 1 area 2
 ip ospf cost 1
 exit
interface GigabitEthernet1
 ip address 192.0.2.6 255.255.255.252
 ip ospf network point-to-point
 ip ospf cost 10
 ip ospf 1 area 2
 no shutdown
 exit
end

Apply

Apply the complete multi-area baseline. First verify R1–R2 in area 0, then the R1–R3 and R2–R4 links. Do not merge all interfaces into area 0 merely because a remote route is absent. Area IDs must match across each link, not across every interface on the router.

Verify and interpret

Illustrative output · excerpt
R1# show ip ospf
 Routing Process "ospf 1" with ID 10.255.0.1
 It is an area border router
 Number of areas in this router is 2
R1# show ip ospf interface brief
Interface PID Area IP Address/Mask Cost State Nbrs F/C
Gi1       1   0    192.0.2.1/30    10   P2P   1/1
Gi2       1   1    192.0.2.9/30    10   P2P   1/1

R1 participates in two areas. Omitted Loopback0 belongs to area 0; its router identity does not determine all interface areas.

Illustrative output · excerpt
R3# show ip route ospf | include 10.255.0.4
O IA 10.255.0.4/32 [110/31] via 192.0.2.9, GigabitEthernet1

R3 crosses its ABR, the backbone, and the other ABR. The total is three transit costs plus R4’s loopback cost.

As a controlled fault, shut R1 Gi1. Area 1 loses its only working backbone attachment and remote area-2 reachability after convergence. Restore no shutdown and verify R3’s inter-area route and a sourced ping to R4. There is no redundant backbone path in this lab.

Technical references

OSPFv2 standard · Router configuration guide

Key Takeaways

  • Areas are assigned per interface.
  • ABRs maintain distinct databases for their attached areas.
  • Non-backbone areas use a connected area-0 hierarchy.
  • An area ID alone does not establish backbone connectivity.
  • Verify each area link before diagnosing inter-area routes.

Backbone and ABRs Quiz

Six questions · four options each · select one answer per question. Submit all answers to see your score and explanations.

1. Which routers are ABRs here?
2. What area is R1–R2?
3. Where is R3 internal?
4. Can adjacent interfaces use different area IDs?
5. What cost reaches R4 Lo0 from R3?
6. What does shutting R1 Gi1 remove?