Skip to content
CCNA 200-301 v1.1 reference — IP Connectivity

OSPF adjacency troubleshooting

Evidence-led OSPF diagnosis: neighbor states, mismatched parameters and passive interfaces, separating symptoms from confirmed causes.

Objective 3.4v1.1 exam target

Neighbor states and what they mean

StateMeaningIf stuck here, suspect
DOWNNo hellos receivedLink down, OSPF not enabled, passive, ACL blocking protocol 89
INITHello received, own RID not yet seenOne-way reachability, multicast filtering
2-WAYBidirectional — DR election pointNormal on broadcast between DROTHERs; if stuck FULL needed, check network types
EXSTARTMaster/slave DBD negotiationMTU mismatch is the classic cause
EXCHANGEDBD packets flowingMTU or duplicate RID
LOADINGRequesting LSAsLSA corruption/flood issues
FULLDatabases synchronizedThe goal — adjacency complete

Mismatch → where to look

RequirementVerification command
Same areashow ip ospf interface brief — the area column
Same subnetshow ip interface on both ends
Hello/dead matchshow ip ospf interface — timer line
MTU matchshow interfaces — MTU field both ends
Auth matchshow ip ospf interface — auth type line
Unique RIDshow ip ospf — the router ID field
Not passiveshow ip protocols — passive interface list
Protocol 89 allowedInterface ACLs + debug ip ospf hello

Verification toolbox

  • show ip ospf neighbor — state and role per neighbor.
  • show ip ospf interface — network type, timers, cost, passive.
  • show ip ospf database — the LSDB itself.
  • show ip route ospf — what OSPF actually installed.
  • debug ip ospf adj/hello — the mismatch in the device's own words (lab only).
On this page

Related resources

Sources

Targets CCNA 200-301 v1.1 objectives. Supplemental blocks are labeled beyond exam scope.

Search guided lessons, transcript chapters, flashcards, CLI drills and cheat sheets

OSPF adjacency troubleshooting | CCNA Study