OSPF Configured, but No OSPF Routes Appear

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.

Symptom

router ospf 100 exists on both routers, yet show ip route ospf is empty.

Layered workflow

R1# show ip interface brief
R1# ping <direct-neighbour-IP>

No direct IP reachability means OSPF is not the first problem.

2 — Is OSPF enabled on the intended interface?

R1# show ip ospf interface brief

3 — Did a neighbour form?

R1# show ip ospf neighbor

No neighbour: compare area, subnet, timers, network type and authentication where configured.

4 — Only now inspect learned routes

R1# show ip route ospf
R1# show ip ospf database

Key lesson

A missing route can be the final symptom of an earlier adjacency failure. Troubleshoot the dependency chain, not the last symptom only.