nerdexam
Juniper

JN0-351 · Question #52

Referring to the exhibit, why is this OSPF adjacency remaining in this state?

The correct answer is B. An MTU mismatch exists between the OSPF neighbors. OSPF stuck in ExStart is mainly related to mismatched MTU. It could also be caused by a firewall filter on the loopback interface, but this is not an alternative.

OSPF

Question

Referring to the exhibit, why is this OSPF adjacency remaining in this state?

Exhibit

JN0-351 question #52 exhibit

Options

  • AA subnet mask mismatch exists between the OSPF neighbors.
  • BAn MTU mismatch exists between the OSPF neighbors.
  • CA hello interval mismatch exists between the OSPF neighbors.
  • DAn area ID mismatch exists between the OSPF neighbors

How the community answered

(30 responses)
  • A
    10% (3)
  • B
    73% (22)
  • C
    3% (1)
  • D
    13% (4)

Explanation

OSPF stuck in ExStart is mainly related to mismatched MTU. It could also be caused by a firewall filter on the loopback interface, but this is not an alternative.

Topics

#OSPF adjacency#MTU mismatch#ExStart state#OSPF troubleshooting

Community Discussion

No community discussion yet for this question.

Full JN0-351 Practice