Troubleshooting an OSPF adjacency

Check absent neighbors and adjacencies stuck in INIT, 2-WAY, EXSTART or EXCHANGE.

Start with the neighbor state. It narrows down whether the routers can exchange hellos, whether they should form an adjacency and where the exchange is failing.

No neighbor appears

  • Check whether ACLs or firewalls permit OSPF protocol 89 and the expected multicast traffic.
  • Verify addressing on the link and verify that both sides use the intended area.
  • Make sure the interface is not passive when it is expected to form neighbors.

INIT or 2-WAY

  • Check hello and dead timers on both ends.
  • Compare authentication type and key.
  • Check the interface network type.
  • On a broadcast segment, two DROTHER routers normally remain in 2-WAY.

EXSTART or EXCHANGE

Compare the interface MTUs. OSPF database description packets carry the sender's MTU. A mismatch can keep the exchange from finishing, particularly on VLAN subinterfaces or where only one side uses jumbo frames.

# FRR
show ip ospf neighbor
show ip ospf interface eth0   # check MTU, timers and network type
debug ospf packet hello
Fix the mismatch

Align the MTUs. Ignoring the check may bring up the adjacency while larger updates still fail.

FULL with no routes

  • Verify that the prefix is advertised through the intended OSPF interface.
  • Check area type and policy on the originating router.
  • If the prefix is in show ip ospf database but missing from the routing table, inspect local installation filters.