Refer to the exhibit. Why is neighbor 10.1.5.5 stuck in "2WAY" state?

Question

Exhibit

Options

• ARouter ID 10.1.5.5 is not reachable from R2
• BOSPF authentication has failed between R2 and 10.1.5.5
• CIt is an expected behavior when OSPF network type is broadcast
• DOSPF parameters (Area ID or hello interval) are mismatched between R2 and 10.1.5.5

• A
  6% (2)
• B
  3% (1)
• C
  89% (31)
• D
  3% (1)

Explanation

On an OSPF broadcast network type (e.g., multi-access Ethernet), only the Designated Router (DR) and Backup Designated Router (BDR) form a full FULL adjacency with all other routers. Routers that are neither DR nor BDR are called DROthers. DROther routers only exchange Hello packets with each other, which means they remain in the 2WAY state - this is completely expected and correct behavior. Only DR and BDR relationships progress to FULL. Option A is wrong because Router ID reachability is not the cause. Option B is wrong because authentication failure would manifest differently (e.g., the neighbor would not appear or would be stuck in EXSTART). Option D is wrong because parameter mismatches would prevent even the 2WAY state from being reached.

No community discussion yet for this question.