New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Juniper JN0-363 Exam - Topic 4 Question 22 Discussion

Actual exam question for Juniper's JN0-363 exam
Question #: 22
Topic #: 4
[All JN0-363 Questions]

You are troubleshooting two OSPF routers that have an adjacency that remains in the ExStart state.

What would cause this problem?

Show Suggested Answer Hide Answer
Suggested Answer: C

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

Neighbors Stuck in Exstart/Exchange State The problem occurs most frequently when you attempt to run OSPF between a Cisco router and another vendor router. The problem occurs when the maximum transmission unit (MTU) settings for neighboring router interfaces do not match. If the router with the higher MTU sends a packet larger that the MTU set on the neighboring router, the neighbor router ignores the packet. When this problem occurs, the output of the show ip ospf neighbor command displays output similar to what is shown in this figure.


Contribute your Thoughts:

0/2000 characters
Raylene
3 months ago
ExStart state? I thought that was rare!
upvoted 0 times
...
Deonna
3 months ago
Wait, are we sure it's not the subnet settings?
upvoted 0 times
...
Nohemi
3 months ago
Mismatched authentication can cause issues too!
upvoted 0 times
...
Catherin
4 months ago
I think it's more likely the hello intervals.
upvoted 0 times
...
Marjory
4 months ago
Definitely a mismatch in MTU settings.
upvoted 0 times
...
Felix
4 months ago
Mismatched subnet settings seem less likely to cause an ExStart state, but I guess it could be a possibility if the networks aren't aligned.
upvoted 0 times
...
Zana
4 months ago
I practiced a question similar to this, and I feel like authentication settings could definitely play a role in OSPF adjacency problems.
upvoted 0 times
...
Remona
4 months ago
I think mismatched hello intervals might be a factor too, but I can't recall if they specifically affect the ExStart state.
upvoted 0 times
...
Junita
5 months ago
I remember reading that mismatched MTU settings can cause issues with OSPF adjacency, but I'm not entirely sure if that's the only reason.
upvoted 0 times
...
Beckie
5 months ago
I'm a bit confused on this one. The OSPF adjacency process is still a bit fuzzy for me. I'll need to review my notes on the different adjacency states to have a better chance at solving this.
upvoted 0 times
...
Desiree
5 months ago
Okay, let's see. The ExStart state is where the routers exchange their database descriptions, so it's likely something preventing them from reaching that stage. Mismatched hello intervals or authentication settings would make sense.
upvoted 0 times
...
Galen
5 months ago
Hmm, this seems like a tricky one. I'll need to think through the OSPF adjacency process carefully to figure out what could be causing the issue.
upvoted 0 times
...
Vincenza
5 months ago
Ah, I've seen this problem before. It's usually due to a mismatch in the MTU or subnet settings on the OSPF interfaces. I'll double-check those configurations first before looking at anything else.
upvoted 0 times
...
Janet
5 months ago
A culture, a set of technical practices, and a mindset - those seem like the core elements to me. I'll select those three and move on.
upvoted 0 times
...
Margarita
5 months ago
I feel pretty good about this question. The ACID principles are a core part of transaction management, so I should be able to recall which one refers to the data being preserved long-term. I'll go with durability.
upvoted 0 times
...
Vilma
5 months ago
This is a tricky one. I think option A with the workflow is the cleanest solution, but I'm not sure how difficult it would be to set up. Option B might be a bit more straightforward, but I'm not sure if it's the best long-term approach.
upvoted 0 times
...

Save Cancel