Skip to content
7LayerX

Routing / Field note

Troubleshooting OSPF neighbor adjacencies

A practical sequence for finding why two OSPF routers are not forming the expected neighbor relationship.

7LayerX Editorialupdated 3 min readCisco IOSOSPFv2

OSPF adjacency problems are easier to solve when you compare the two ends of a link in the same order. Start with reachability and interface state, then compare the OSPF settings that must agree.

This guide uses OSPFv2 on IPv4 links. Command syntax and output vary by software release, so treat the examples as a checklist and confirm platform-specific details in the vendor documentation.

Check that the interface is up, has the expected address, and can reach the address on the other end of the link.

show ip interface brief
show interfaces GigabitEthernet0/0
ping 192.0.2.2 source 192.0.2.1

If the link is down, resolve the physical, VLAN, or encapsulation issue before investigating OSPF. If the addresses do not share the expected subnet, compare the mask and intended topology on both routers.

Read the neighbor state

Use the neighbor table and interface-specific OSPF view to see how far the exchange has progressed.

show ip ospf neighbor
show ip ospf interface GigabitEthernet0/0

On broadcast networks, a neighbor may remain in 2-WAY with a router that is not selected as a designated router or backup designated router. That can be normal. A pair expected to form a full adjacency should progress beyond that state.

Compare settings that must agree

Check both ends for compatible area, subnet, hello/dead timers, authentication, and network type. A mismatch can prevent adjacency even when basic IP reachability works.

show running-config interface GigabitEthernet0/0
show ip ospf interface GigabitEthernet0/0

Also confirm that the interface is not passive and that both routers use the same OSPF version and address family. For an area mismatch, compare the interface's configured area on each side rather than relying only on the process-level configuration.

Check MTU and database exchange

If neighbors reach EXSTART or EXCHANGE and then stop, compare interface MTU and review logs for database description exchange errors. Do not disable MTU checks as a first response; confirm the end-to-end MTU requirement and platform behavior first.

Use a repeatable comparison

Capture the same outputs from both routers and compare them side by side:

CheckRouter ARouter B
Interface and subnetExpected valueExpected value
OSPF area and network typeMatchingMatching
Hello and dead intervalMatchingMatching
AuthenticationMatchingMatching
Neighbor stateExpected progressionExpected progression

Change one confirmed mismatch at a time, then verify the neighbor state and route table. Keep the original output so the effect of each change is clear.

Key takeaway

Begin with the link, read the neighbor state, compare settings that must agree, and investigate MTU only when the exchange state points there. This keeps troubleshooting tied to evidence and reduces unnecessary configuration changes.

Pass it along

Found this useful? Share it.

Choose a platform or copy the direct link.

LinkedInXFacebook

Continue reading

Reader signal

Was this useful?

Your feedback helps shape the next field note and lab.

… views

Views count when this page opens. You can change or remove your vote during this tab session.