Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Dell EMC D-SNC-DY-00 Exam - Topic 3 Question 11 Discussion

Actual exam question for Dell EMC's D-SNC-DY-00 exam
Question #: 11
Topic #: 3
[All D-SNC-DY-00 Questions]

Refer to the exhibit.

Eth 1/1 of SONiC-1 and Eth1/56 of SONiC-2 should be a routed link connecting the two Enterprise SONiC switches. No traffic is passing between them.

What is the cause of the failure?

Show Suggested Answer Hide Answer
Suggested Answer: A

From the exhibit, it is evident that Eth1/56 on SONiC-2 is assigned a link-local IPv6 address (fe80::e7d:8aff:fecb

/64). Link-local addresses are not routable beyond the local network segment, which means they cannot be used to route traffic between SONiC-1 and SONiC-2. For routed links, global unicast addresses must be used.


Dell Technologies SONiC documentation

IPv6 Addressing Guide

Contribute your Thoughts:

0/2000 characters
Royal
4 months ago
I doubt it's an IPv6 address type issue, seems unlikely.
upvoted 0 times
...
Linn
4 months ago
Wait, are we sure the cable is even plugged in?
upvoted 0 times
...
Owen
4 months ago
Could be an IPv6 issue too, like option C.
upvoted 0 times
...
Justine
4 months ago
I think it's more likely a spanning-tree problem, option B.
upvoted 0 times
...
Josphine
5 months ago
Sounds like a cable issue, maybe option D?
upvoted 0 times
...
Mabel
5 months ago
What if the cable is just unplugged? I think that could be a simple fix, but I can't recall if we had a question like that before.
upvoted 0 times
...
Rosann
5 months ago
I feel like we covered something about needing to enable IPv6 on both interfaces. Is that what this question is hinting at?
upvoted 0 times
...
Teri
5 months ago
I'm not entirely sure, but I think we practiced a question where an incorrect IPv6 address caused connectivity issues.
upvoted 0 times
...
Lai
5 months ago
I remember we discussed how spanning-tree can block links if there's a loop. Could that be the issue here?
upvoted 0 times
...
Blondell
5 months ago
I think I've got it! The issue is likely that IPv6 is not enabled on the interface of SONiC-1. That would explain why the routed link is not working. I'll select option C and move on to the next question.
upvoted 0 times
...
Tracie
5 months ago
Hmm, I'm a bit confused. The question mentions that it's a routed link, so I don't think a spanning-tree issue would be the cause. But I'll make sure to read through the details carefully before answering.
upvoted 0 times
...
Pilar
5 months ago
Alright, let's go through the options. Option A seems plausible - an incorrect IPv6 address type could definitely cause the link to fail. But I'll need to double-check the other options as well.
upvoted 0 times
...
Dean
5 months ago
Hmm, this looks like a tricky one. I'll need to carefully review the information provided and think through the possible causes.
upvoted 0 times
...
Dong
5 months ago
Okay, let's see. The question says the interfaces should be a routed link, but no traffic is passing between them. That suggests a configuration issue, but I'm not sure which one.
upvoted 0 times
...
Laticia
6 months ago
This looks like a tricky migration scenario. I'll need to carefully consider the requirements to avoid any downtime or data loss.
upvoted 0 times
...
Viki
1 year ago
A missing cable, eh? That's like trying to play Tetris without any blocks - good luck with that one!
upvoted 0 times
...
Leslee
1 year ago
IPv6, huh? That's like the elusive Loch Ness monster of networking - you never know when it's gonna pop up and cause problems. Better check those settings!
upvoted 0 times
...
Sonia
1 year ago
Hold up, what if it's a spanning-tree issue? I've seen that trip up even the best network engineers. Gotta check those STP configs.
upvoted 0 times
Jesusita
1 year ago
User 4: Yeah, better safe than sorry.
upvoted 0 times
...
Ben
1 year ago
User 3: Check the STP configs just to be sure.
upvoted 0 times
...
Colton
1 year ago
User 2: Could be, but it could also be an unplugged cable.
upvoted 0 times
...
Kathrine
1 year ago
User 1: Maybe it's a spanning-tree issue.
upvoted 0 times
...
...
Alonzo
1 year ago
Hmm, looks like a connection issue. I bet it's the cable - who unplugged it? Probably the intern trying to 'optimize' the network.
upvoted 0 times
Virgina
1 year ago
User 3: We should check the physical connection first.
upvoted 0 times
...
Stephane
1 year ago
User 2: Yeah, that could be the cause of the failure.
upvoted 0 times
...
Clarinda
1 year ago
Maybe the cable between SONiC-1 and SONiC-2 is unplugged.
upvoted 0 times
...
...
Carrol
1 year ago
But if the cable is unplugged, there won't be any traffic passing between the switches.
upvoted 0 times
...
Ezekiel
1 year ago
I disagree, I believe it's option B, a spanning-tree blocking the link.
upvoted 0 times
...
Carrol
1 year ago
I think the cause of the failure is option D, a cable that is unplugged.
upvoted 0 times
...
Ariel
1 year ago
Ah, the classic spanning-tree dance. I'll go with option B, just to keep things interesting.
upvoted 0 times
Joseph
1 year ago
Maybe IPv6 is not enabled on SONiC-1's interface.
upvoted 0 times
...
Dalene
1 year ago
I believe a spanning-tree is blocking the link.
upvoted 0 times
...
Mindy
1 year ago
I think the issue is with the IPv6 address type on SONiC-2.
upvoted 0 times
...
...
Tatum
2 years ago
C'mon, guys, let's not be IPv6 deniers. I bet it's option C - no IPv6 on that interface.
upvoted 0 times
...
Royal
2 years ago
Hmm, I think it's option D. That cable must be as elusive as the Loch Ness Monster!
upvoted 0 times
Jamal
1 year ago
I agree with User1, it's probably the unplugged cable, option D.
upvoted 0 times
...
Brendan
1 year ago
I think IPv6 might not be enabled on Eth 1/1 of SONiC-1, option C.
upvoted 0 times
...
Clorinda
1 year ago
Maybe there's a spanning-tree blocking the link, option B.
upvoted 0 times
...
Jaime
1 year ago
It could be option D, the cable might be unplugged.
upvoted 0 times
...
...

Save Cancel