Two Cisco routers, R1 and R2, are directly connected via an Ethernet link and configured for OSPFv2 single-area routing. An administrator notices that the OSPF neighbor state between R1 and R2 remains continuously stuck in the EXSTART state. Which configuration mismatch is the most likely cause of this issue?
- An IP Maximum Transmission Unit (MTU) mismatch on the interconnecting interfacesCevap
- BMismatched OSPF Hello or Dead timer intervals on the interface
- CDifferent OSPF Area IDs assigned to the connecting interfaces
- DSetting the OSPF interface priority to 0 on both routers
Cevap
An IP Maximum Transmission Unit (MTU) mismatch on the interconnecting interfaces causes OSPF neighbors to become stuck in the ExStart or Exchange state.
During the ExStart state of OSPFv2 neighbor formation, routers elect a Master and Slave to sequence Database Description (DBD) packets. Cisco routers validate the IP MTU header field in incoming DBD packets against their local interface MTU. If an MTU mismatch exists, the larger-MTU router drops the smaller-MTU router's DBD packets (or vice versa), keeping the neighbor process continuously stuck in ExStart/Exchange.
Adım Adım Çözüm
Anahtar Kavram
OSPF Neighbor States and MTU Mismatch Troubleshooting