OSPF Neighbor Troubleshooting: A Layered Checklist
Diagnose common OSPF adjacency problems by checking interface state, area, timers, authentication, MTU, and network type.
Understand what an adjacency proves
OSPF routers use Hello packets to discover neighbors and confirm that key settings are compatible. On broadcast networks, a Designated Router and Backup Designated Router are elected; not every neighbor relationship becomes a full adjacency. Point-to-point links have different adjacency behavior.
A neighbor stuck in a state is a clue about which phase is failing, not a complete diagnosis. Check the interface and the exact neighbor state together. Use read-only show commands first and avoid resetting a production adjacency until the impact is understood.
Check link and interface prerequisites
Confirm both interfaces are up/up, use the expected subnet, and can exchange IP packets. OSPF commonly uses IP protocol number 89 rather than a TCP or UDP port, so an ACL that permits only common transport ports may still block it. Verify the interface is not configured as passive when a neighbor is expected.
Confirm the OSPF process includes the interface and that the intended area is configured. The process ID is locally significant and does not need to match between routers; the area and network parameters do need to be compatible.
Useful Cisco IOS checks:
show ip ospf neighbor
show ip ospf interface brief
show ip protocols
show ip route ospfCompare the Hello parameters
For neighbors to exchange Hellos successfully, compare the area ID, subnet, Hello and Dead intervals, authentication configuration, and network type. A mismatch in one of these settings can prevent neighbor formation or keep routers from progressing beyond an early state.
If neighbors reach ExStart or Exchange and then fail, inspect the interface MTU and logs. An MTU mismatch can prevent database description packets from completing. Do not disable MTU checks as a first response; verify the path MTU and correct the inconsistent configuration where possible.
Use evidence to narrow the cause
Work from the closest layer outward: physical/link state, IP reachability, OSPF interface participation, Hello compatibility, then database exchange. Compare both routers’ outputs side by side and capture a short Hello exchange only when you are authorized to inspect that link.
After correcting a mismatch, verify the neighbor reaches the expected state and that learned routes appear in the routing table. Check route attributes and reachability to a known test destination; adjacency alone does not prove end-to-end forwarding is correct.
- Interface up/up and correct subnet.
- OSPF enabled on the intended interface; not passive.
- Area, timers, authentication, and network type agree.
- MTU and database exchange are healthy.
- Expected routes are installed and a permitted test path works.
References and further reading
Use primary standards and vendor documentation to verify details and explore the subject further.
Practise this in a safe environment
Reading a guide changes your understanding; practising changes your reflex. The ByteBreach practice labs run in an isolated sandbox inside the browser, so you can apply the same reasoning without touching infrastructure that belongs to somebody else. The learning paths that surround each topic give you the theory in the order it is needed, and the resource vault holds the command syntax so you do not have to reconstruct it from memory in the middle of an exercise.
If you are applying any of this to a live system, confirm first that you are authorised to do so. The educational disclaimer explains the difference between an authorised engagement and an intrusion, and the terms and conditions describe the limits we place on how the material may be used.
Related ByteBreach material
This guide is one part of a larger body of published work. The field guides index lists every guide in the library, the learning paths catalogue shows how the underlying theory is sequenced, and the frequently asked questions cover the platform mechanics such as XP, rank tiers, and how flags are validated. If you want to report an error in this guide, the contact page reaches a maintainer directly.
ByteBreach guides are independently written educational material and are not official certification-provider documentation. Always verify configurations against the documentation for your software and equipment.