A network engineer is troubleshooting OSPF adjacency issues between two routers connected via a Gigabit Ethernet link. The engineer notices that the routers are stuck in the EXSTART state. Both routers have the same MTU of 1500 bytes. What is the most likely cause of this issue?
Trap 1: The OSPF network type is point-to-point on one router and broadcast…
Incorrect because OSPF network type mismatch typically causes issues in the 2WAY or FULL state, not EXSTART. The EXSTART state is specifically for DBD exchange.
Trap 2: The OSPF hello and dead intervals are mismatched.
Incorrect because mismatched timers prevent the adjacency from forming at all, typically leaving the routers in the INIT state.
Trap 3: The OSPF router IDs are the same.
Incorrect because duplicate router IDs prevent adjacency formation entirely, typically resulting in a state of DOWN or INIT, not EXSTART.
- A
The OSPF network type is point-to-point on one router and broadcast on the other.
Why wrong: Incorrect because OSPF network type mismatch typically causes issues in the 2WAY or FULL state, not EXSTART. The EXSTART state is specifically for DBD exchange.
- B
The OSPF hello and dead intervals are mismatched.
Why wrong: Incorrect because mismatched timers prevent the adjacency from forming at all, typically leaving the routers in the INIT state.
- C
One router has a lower IP MTU configured on the interface, causing the DBD packet to be dropped.
Correct because OSPF routers exchange DBD packets in the EXSTART state. If the DBD packet size exceeds the IP MTU, the packet is dropped, and the routers remain stuck in EXSTART.
- D
The OSPF router IDs are the same.
Why wrong: Incorrect because duplicate router IDs prevent adjacency formation entirely, typically resulting in a state of DOWN or INIT, not EXSTART.