Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location PL
Mob_nav_barsMENU

Juniper Exam JN0-351 Topic 6 Question 12 Discussion

Actual exam question for Juniper's JN0-351 exam
Question #: 12
Topic #: 6
[All JN0-351 Questions]

Exhibit.

Why is this OSPF adjacency remaining in this state?

Show Suggested Answer Hide Answer
Suggested Answer: B

The exhibit shows the output of the commandshow ospf neighbor, which displays information about the OSPF neighbors on a router1.

The output shows that the OSPF neighbor with the address 172.26.1.1 and the interface ge-0/0/3.0 is in the Exstart state1.

The Exstart state is the fourth state in the OSPF neighbor formation process, after Down, Init, and 2-Way states2.In this state, the OSPF neighbors establish a master-slave relationship and exchange database description (DBD) packets, which contain summaries of their link-state databases2.

The most common reason for OSPF neighbors to be stuck in the Exstart state is an MTU mismatch between the interfaces3.MTU stands for maximum transmission unit, which is the largest size of a packet that can be transmitted on a network segment4.If the MTU values of two OSPF neighbors are different, they may not be able to exchange DBD packets successfully, as some packets may be dropped or fragmented due to their size exceeding the MTU limit3.

To solve this problem, you need to ensure that the MTU values of both OSPF neighbors are the same or compatible.You can use the commandshow interfacesto display the MTU value of an interface5. You can also use the commandpingwith thedo-not-fragmentoption to test the MTU size between two routers.You can change the MTU value of an interface by using the commandset interfaces interface-name mtu mtu-valuein configuration mode5.


by Yolando at Feb 10, 2024, 06:02 AM

Limited Time Offer

25%

Off

Get Premium JN0-351 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Weldon
6 months ago
I see your point, Lashawn. A hello interval mismatch could definitely be the issue here.
upvoted 0 times
...
Lashawn
6 months ago
I think it might be a hello interval mismatch that is causing the OSPF adjacency to remain in this state.
upvoted 0 times
...
Mireya
6 months ago
Yes, that's a good point Dylan. An MTU mismatch could also be the cause.
upvoted 0 times
...
Dylan
6 months ago
I beliMireya it could also be due to an MTU mismatch between the OSPF neighbors.
upvoted 0 times
...
Weldon
6 months ago
I agree with Mireya, a subnet mask mismatch can definitely cause this issue.
upvoted 0 times
...
Mireya
6 months ago
I think the OSPF adjacency is remaining in this state because of a subnet mask mismatch.
upvoted 0 times
...
Bev
6 months ago
I don't think so, I believe a hello interval mismatch is more likely to cause this problem.
upvoted 0 times
...
Rachael
7 months ago
What about an MTU mismatch? Could that be the reason?
upvoted 0 times
...
Marisha
7 months ago
I agree with Lazaro, a subnet mask mismatch can definitely cause this issue.
upvoted 0 times
...
Lazaro
7 months ago
I think the OSPF adjacency is remaining in this state because of a subnet mask mismatch.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77