Juniper Exam JN0-363 Topic 3 Question 29 Discussion

Actual exam question for Juniper's JN0-363 exam

Question #: 29
Topic #: 3

[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?

Amismatched OSPF hello intervals on the OSPF interfaces

Bmismatched authentication settings on the OSPF interfaces

Cmismatched MTU settings on the OSPF interfaces

Dmismatched subnet settings on the OSPF interfaces

Show Suggested 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.

by Vincent at Apr 10, 2024, 01:24 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Ryann

5 months ago

It's possible, but I think the most likely culprit is the OSPF hello intervals.

upvoted 0 times

...

Devorah

5 months ago

What about mismatched MTU settings? Could that be a possible reason?

upvoted 0 times

...

Melissa

5 months ago

True, that could also be a potential cause for the problem.

upvoted 0 times

...

Frankie

6 months ago

It could also be due to mismatched authentication settings.

upvoted 0 times

...

Roselle

6 months ago

I agree, that could definitely cause the adjacency to stay in ExStart state.

upvoted 0 times

...

Lajuana

7 months ago

I think the issue might be due to mismatched OSPF hello intervals.

upvoted 0 times

...

Arminda

7 months ago

But wouldn't mismatched authentication settings also cause a problem like this?

upvoted 0 times

...

Tayna

7 months ago

I think the issue could be due to mismatched subnet settings on the OSPF interfaces.

upvoted 0 times

...

Elenora

7 months ago

I disagree, I think it's more likely due to mismatched OSPF hello intervals.

upvoted 0 times

...

Colby

7 months ago

I agree with MTU settings could definitely cause this issue.

upvoted 0 times

...

Arminda

7 months ago

I think it could be because of mismatched MTU settings on the OSPF interfaces.

upvoted 0 times

Reena

6 months ago

Let's verify the MTU settings on both routers.

upvoted 0 times

...

Breana

7 months ago

Maybe we should check for that.

upvoted 0 times

...

Providencia

7 months ago

Could be due to mismatched MTU settings.

upvoted 0 times

...

Angelyn

8 months ago

Haha, good point! It's like the classic 'did you try turning it off and on again' of OSPF troubleshooting. Gotta check the basics!

upvoted 0 times

...

Robt

8 months ago

Wait, wait, what if it's actually a mismatched subnet setting? That could also prevent the adjacency from forming properly, right?

upvoted 0 times

...

Daren

8 months ago

Yeah, those are good guesses. I'm leaning more towards the MTU settings being the culprit. I've had issues with that before when troubleshooting OSPF.

upvoted 0 times

...

Grover

8 months ago

I agree, the ExStart state is crucial for establishing the OSPF adjacency. My money's on either mismatched authentication settings or MTU settings causing the problem.

upvoted 0 times

...

Jade

8 months ago

Hmm, the ExStart state is where the routers negotiate the OSPF parameters, so it could be a few different things causing the issue. Let's think this through.

upvoted 0 times

...

Veronique

8 months ago

This question is a classic OSPF troubleshooting scenario. I've seen similar questions in previous exams, so I'm familiar with the topic.

upvoted 0 times

...