Networking: %OSPF-5-ADJCHG: Nbr 10.0.0.2 from EXSTART to DOWN — OSPF neighbor stuck in EXSTART/EXCHANGE (MTU mismatch)
Two OSPF routers see each other but never finish exchanging databases, cycling between EXSTART and DOWN.
OSPF neighbor stuck in EXSTARTOSPF stuck in EXCHANGE%OSPF-5-ADJCHG: Process 1, Nbr from EXSTART to DOWNOSPF MTU mismatchNbr 10.0.0.2 Adjacency stuck in EXSTART Meaning
The classic cause is different interface MTU on the two ends, because OSPF includes the MTU in Database Description packets. Make the MTU equal (or use ip ospf mtu-ignore as a workaround) and also check duplicate router IDs, unicast reachability and ACLs blocking IP protocol 89.
Common causes
- Different interface MTU on the two routers
- Duplicate OSPF router ID
- ACL or firewall blocking protocol 89
- Unicast connectivity problem (only multicast works)
- Authentication or area mismatch
⚡ Quick fix
- Compare
show ip ospf interfaceMTU on both ends - Make MTUs identical (or temporarily
ip ospf mtu-ignore) - Check router IDs are unique
Detailed fix by platform
Cisco
- text
show ip ospf neighbor show interfaces Gi0/1 | include MTU interface Gi0/1 ip mtu 1500
How to diagnose
- State — EXSTART/EXCHANGE?
- MTU — Equal?
- Router ID — Unique?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Networking
- Rogue DHCP server hands out wrong gateway/DNS Networking: Clients receive the wrong default gateway or DNS server — a rogue DHCP server (often a home router) answers first
- Idle connections silently dropped by firewall/NAT Networking: Connection works, then fails after being idle — firewall/NAT idle timeout dropped the TCP session (use keepalive)
- DHCPDISCOVER: no free leases Networking: dhcpd: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via eth0: network 192.168.1.0/24: no free leases
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 5 Nov 2026