Network & Infrastructure / OSPF & Underlay Convergence
Why an OSPF neighbor at 2-Way is sometimes correct
On a broadcast segment, two non-designated routers remain at 2-Way. An automated check reports failure even though both have complete adjacency with the designated and backup routers.
Environment and inputs: OSPFv2 IPv4 underlays, with OSPFv3 explicitly identified where used; timers and diagnostics vary by platform. Diagnostic/design example; not tested on production equipment.
Collect the evidence
Map interface network type, router priority, designated-router roles and all neighbor states on the segment. Check which router pairs are actually required to exchange databases fully.
Explain the result
OSPF broadcast networks intentionally avoid a full mesh of adjacencies between all non-designated routers. Interpreting every 2-Way state as a fault creates unnecessary resets and role churn.
Plan the fix
Adjust monitoring to the expected adjacency topology. Investigate missing Full state to a designated router separately, including network type, multicast delivery and election history.
Check the result and rollback
Verify database consistency and forwarding without forcing a new election. Roll back monitoring changes if they suppress a real missing adjacency or conceal an unexpected network-type mismatch.