Skip to content
FALCON CORETECHNOLOGIES

// Troubleshooting guide

OSPF neighbours will not reach FULL

Diagnose OSPFv2 adjacency problems by state — what each stuck state means and which parameter mismatch causes it.
2 min read#ccna#ospf#troubleshooting

Symptoms

  • show ip ospf neighbor is empty on a link that should have a neighbour
  • A neighbour is stuck in INIT, EXSTART or EXCHANGE
  • Neighbours keep going up and down
  • OSPF routes are missing even though neighbours are FULL

Start from the state

show ip ospf neighbor tells you how far the routers got. Use the state to narrow the cause.

What you see Most likely causes
No neighbour at all Interface not in OSPF, passive interface, hellos blocked by an ACL, different subnet, mismatched area, hello/dead timers, authentication, interface down
Stuck in INIT Hellos only work in one direction (ACL or filtering on one side)
Stuck in 2-WAY on Ethernet Normal between two DROTHERs — they only go FULL with the DR and BDR
Stuck in EXSTART / EXCHANGE MTU mismatch, or duplicate router IDs
Flapping Dead timer too short, unstable link, CPU overload
FULL but routes missing Network not advertised, passive/area design, a filter, a lower-AD route preferred
  • Area ID
  • Subnet and mask (on multi-access and point-to-point Ethernet)
  • Hello and dead intervals
  • Authentication type and key
  • Area type (stub flags)
  • MTU (otherwise stuck in EXSTART/EXCHANGE)
  • Network type should match — mixing broadcast and point-to-point forms an adjacency but leaves the routes missing

Router IDs must be unique.

Commands to compare both sides

show ip ospf interface GigabitEthernet0/0/0
show ip ospf interface brief
show ip protocols
show running-config | section router ospf

show ip ospf interface shows on one screen the area, network type, cost, timers, DR/BDR and neighbour count. Run it on both routers and compare line by line.

Common causes

Interface not in OSPF. The network statement wildcard does not cover the interface address. show ip ospf interface brief does not list the interface. Fix the network statement or use ip ospf 1 area 0 on the interface.

Passive interface. show ip protocols lists it under "Passive Interface(s)". Passive interfaces are advertised but send no hellos, so they form no neighbours. Use no passive-interface on links to other routers.

Area mismatch. The log may show "mismatched area ID". Make both ends the same area.

Timer mismatch. One side has ip ospf hello-interval 5. Remove it, or set the same value on both ends.

MTU mismatch. One side has a smaller IP MTU; the neighbour sticks in EXSTART. Match ip mtu on both ends (ip ospf mtu-ignore is a workaround, not a fix).

Duplicate router ID. The log shows a duplicate router-id message. Set unique IDs with router-id, then clear ip ospf process.

ACL dropping OSPF. OSPF is IP protocol 89 sent to 224.0.0.5/224.0.0.6. An inbound ACL that does not permit it drops the hellos: add permit ospf any any above the deny.

Debug carefully

debug ip ospf adj shows the reason an adjacency fails, but use it only in a lab or a maintenance window, and turn it off with undebug all.