A layered checklist for BGP neighbor troubleshooting
Separate BGP transport, session, policy, and route-advertisement problems with a repeatable peer checklist.
Routing / Field note
A practical sequence for finding why two OSPF routers are not forming the expected neighbor relationship.
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.1If 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.
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/0On 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.
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/0Also 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.
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.
Capture the same outputs from both routers and compare them side by side:
| Check | Router A | Router B |
|---|---|---|
| Interface and subnet | Expected value | Expected value |
| OSPF area and network type | Matching | Matching |
| Hello and dead interval | Matching | Matching |
| Authentication | Matching | Matching |
| Neighbor state | Expected progression | Expected 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.
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.
Continue reading
Separate BGP transport, session, policy, and route-advertisement problems with a repeatable peer checklist.
Reader signal
Your feedback helps shape the next field note and lab.
Views count when this page opens. You can change or remove your vote during this tab session.