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

Ericsson Exam ECP-206 Topic 4 Question 25 Discussion

Actual exam question for Ericsson's ECP-206 exam
Question #: 25
Topic #: 4
[All ECP-206 Questions]

Which mismatched field would cause an IS-IS adjacency between two routers to fail?

Show Suggested Answer Hide Answer
Suggested Answer: A

MTU mismatch would cause an IS-IS adjacency between two routers to fail. MTU stands for maximum transmission unit, which is the maximum size of a packet that can be transmitted on a link. IS-IS hellos are padded to the full MTU size, partly to allow a router to implicitly communicate its MTU to its neighbors.If two routers have different MTUs on their interfaces, they will not be able to exchange hellos properly, and their adjacency will not form or will be dropped34. To solve this problem, the MTUs on both interfaces must be configured to match.

SEL, context, and SysID are not fields that would cause an IS-IS adjacency failure. SEL stands for selector, which is a one-octet field that identifies the network layer service to which a packet should be sent.For IS-IS routers, the SEL must always be 005.Context is not a field in IS-IS packets, but rather a term used to describe the scope of routing information in different levels or areas6. SysID stands for system identifier, which is a six-octet field that uniquely identifies a router within an area.SysID does not have to match between two routers for them to form an adjacency7.


by Tarra at Aug 28, 2024, 04:09 AM

Limited Time Offer

25%

Off

Get Premium ECP-206 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Stephen
3 months ago
I think SysID is also important for identifying the router, so that could be a potential mismatch causing the adjacency to fail.
upvoted 0 times
...
Benedict
3 months ago
MTU all the way! I once had a colleague who thought changing the MTU would make the network 'go faster'. Needless to say, we had to roll back that change pretty quickly.
upvoted 0 times
Mose
2 months ago
B) SEL
upvoted 0 times
...
Emogene
3 months ago
Oh no, changing the MTU can definitely cause issues with IS-IS adjacencies.
upvoted 0 times
...
Casie
3 months ago
A) MTU
upvoted 0 times
...
...
Laurene
3 months ago
Gotta be the Context field. I mean, who even uses that anyway? Sounds like something straight out of a networking trivia game.
upvoted 0 times
Flo
2 months ago
Definitely, it's not a common field to come across in networking.
upvoted 0 times
...
Nana
2 months ago
Yeah, I agree. Context seems like the odd one out here.
upvoted 0 times
...
Wendell
2 months ago
D) SysID
upvoted 0 times
...
Ernie
2 months ago
C) Context
upvoted 0 times
...
Blair
3 months ago
B) SEL
upvoted 0 times
...
Annmarie
3 months ago
A) MTU
upvoted 0 times
...
...
Lenna
3 months ago
But MTU affects the maximum size of packets that can be transmitted, so it seems like a critical field to match.
upvoted 0 times
...
Lorrine
3 months ago
SysID, for sure. Can't have two routers with the same system ID, that's just asking for trouble. Although, I did once work with a team that thought changing the SysID was a good way to 'optimize' the network. Needless to say, that didn't end well.
upvoted 0 times
...
Hannah
3 months ago
I disagree, I believe it's Context that would cause the adjacency to fail.
upvoted 0 times
...
Florinda
4 months ago
Definitely the MTU! I learned that one the hard way during a network troubleshooting session. Reminds me of the time I accidentally set the MTU to 1400 on a link - instant connectivity loss!
upvoted 0 times
Wilda
3 months ago
B) SEL
upvoted 0 times
...
Elfrieda
3 months ago
Oh no, that must have been frustrating!
upvoted 0 times
...
Leatha
3 months ago
A) MTU
upvoted 0 times
...
...
Lenna
4 months ago
I think the mismatched field that would cause an IS-IS adjacency to fail is MTU.
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