nerdexam
Cisco

200-101 · Question #216

What can cause two OSPF neighbors to be stuck in the EXSTART state?

The correct answer is B. The neighbors have different MTU settings.. OSPF neighbors become stuck in EXSTART when they cannot successfully negotiate the master-slave relationship during Database Description (DBD) exchange, which occurs when an MTU mismatch causes one side to reject DBD packets.

Implement a Scalable OSPF Based Solution

Question

What can cause two OSPF neighbors to be stuck in the EXSTART state?

Options

  • AThere is a low bandwidth connection between neighbors.
  • BThe neighbors have different MTU settings.
  • CThe OSPF interfaces are in a passive state.
  • DThere is only layer one connectivity between neighbors.

How the community answered

(49 responses)
  • A
    2% (1)
  • B
    82% (40)
  • C
    10% (5)
  • D
    6% (3)

Why each option

OSPF neighbors become stuck in EXSTART when they cannot successfully negotiate the master-slave relationship during Database Description (DBD) exchange, which occurs when an MTU mismatch causes one side to reject DBD packets.

AThere is a low bandwidth connection between neighbors.

Low bandwidth slows OSPF convergence and may cause retransmissions, but it does not prevent the EXSTART state from progressing to EXCHANGE - the adjacency will eventually complete just slowly.

BThe neighbors have different MTU settings.Correct

During the EXSTART and EXCHANGE states, OSPF routers exchange DBD packets. If the MTU values differ between neighbors, the router with the smaller MTU will receive DBD packets that exceed its MTU and silently drop them, causing the higher-MTU router to keep retransmitting and the adjacency to remain permanently stuck in EXSTART or EXCHANGE state.

CThe OSPF interfaces are in a passive state.

Passive interfaces stop OSPF from sending Hello packets on that interface, so neighbors would never even reach INIT state, let alone get stuck in EXSTART.

DThere is only layer one connectivity between neighbors.

Layer 1 connectivity alone (no Layer 2 or Layer 3) means OSPF Hellos cannot be exchanged at all, so the neighbor relationship would not form any OSPF state, not specifically EXSTART.

Concept tested: OSPF EXSTART state failure due to MTU mismatch

Source: https://www.cisco.com/c/en/us/support/docs/ip/open-shortest-path-first-ospf/13684-12.html

Topics

#OSPF EXSTART state#MTU mismatch#neighbor adjacency#OSPF troubleshooting

Community Discussion

No community discussion yet for this question.

Full 200-101 Practice