Question

On a multi-access Ethernet segment, R1 forms OSPF adjacencies with the DR and BDR but shows R2 stuck in the 2WAY/DROTHER state in the output of 'show ip ospf neighbor'. Both routers are in the correct area, timers match, and they can ping each other. What is the most likely explanation for the 2WAY state between R1 and R2?

Accepted Answer

R1 and R2 are both DROTHER routers, so they intentionally remain in the 2WAY state and do not become fully adjacent

Answer

There is an OSPF area ID mismatch preventing the adjacency from advancing

Answer

The OSPF hello and dead timers between R1 and R2 do not match

Answer

R1 and R2 have duplicate OSPF router IDs, causing the neighbor process to halt