OSPF Routes Missing After Configuration

advanced
LAB TOPOLOGY

Multi-Area OSPF Lab

Area 0 backbone with four attached areas

AREA 1AREA 0 · BACKBONEAREA 2AREA 3AREA 4192.168.70.0/24NICG0/0172.16.29.0/30G0/1G0/0172.16.29.4/30G0/1G0/0172.16.29.8/30G0/2G0/0172.16.29.12/30G0/3G0/0192.168.71.0/24G0/1NIC192.168.73.0/24G0/1NIC192.168.72.0/24G0/1NICPC1192.168.70.0/24192.168.70.10R1ABR192.168.70.1R2BACKBONER3ABR192.168.71.1R4ABR192.168.73.1R5ABR192.168.72.1PC2AREA 2192.168.71.10PC3AREA 3192.168.73.10PC4AREA 4192.168.72.10
Topology note:Area IDs and network ranges follow the supplied OSPF lab. Interface names are presentation labels and may differ by IOS image.

Situation

R2 and R3 are directly connected on 172.16.29.4/30. R2 advertises the link in Area 0. R3 accidentally advertises the same link in Area 2. Remote routes never appear.

R2(config-router)# network 172.16.29.4 0.0.0.3 area 0
R3(config-router)# network 172.16.29.4 0.0.0.3 area 2

Your task

What should you verify first: routing table or neighbour state? What configuration mismatch prevents a healthy adjacency?

Reasoning

OSPF routers on the same link must agree on important adjacency parameters, including area. If the neighbour relationship is not healthy, expecting learned OSPF routes is premature.

Commands

R2# show ip ospf neighbor
R2# show ip ospf interface
R3# show ip ospf interface

Fix

Place the R3 backbone-facing network in Area 0, then verify the neighbour reaches FULL and only then check show ip route ospf.