MENU
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?
Suggested Answer: A
Get Premium D-SNC-DY-00 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
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
39 comments · newest first
RO
Royal
10 months ago
I doubt it's an IPv6 address type issue, seems unlikely.
LI
Linn
11 months ago
Wait, are we sure the cable is even plugged in?
OW
Owen
11 months ago
Could be an IPv6 issue too, like option C.
JU
Justine
11 months ago
I think it's more likely a spanning-tree problem, option B.
JO
Josphine
11 months ago
Sounds like a cable issue, maybe option D?
MA
Mabel
12 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.
RO
Rosann
12 months ago
I feel like we covered something about needing to enable IPv6 on both interfaces. Is that what this question is hinting at?
TE
Teri
12 months ago
I'm not entirely sure, but I think we practiced a question where an incorrect IPv6 address caused connectivity issues.
LA
Lai
1 year ago
I remember we discussed how spanning-tree can block links if there's a loop. Could that be the issue here?
BL
Blondell
1 year 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.
TR
Tracie
1 year 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.
PI
Pilar
1 year 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.
DE
Dean
1 year ago
Hmm, this looks like a tricky one. I'll need to carefully review the information provided and think through the possible causes.
DO
Dong
1 year 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.
LA
Laticia
1 year ago
This looks like a tricky migration scenario. I'll need to carefully consider the requirements to avoid any downtime or data loss.
VI
Viki
2 years ago
A missing cable, eh? That's like trying to play Tetris without any blocks - good luck with that one!
LE
Leslee
2 years 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!
SO
Sonia
2 years 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.
JE
Jesusita
2 years ago
User 4: Yeah, better safe than sorry.
BE
Ben
2 years ago
User 3: Check the STP configs just to be sure.
CO
Colton
2 years ago
User 2: Could be, but it could also be an unplugged cable.
KA
Kathrine
2 years ago
User 1: Maybe it's a spanning-tree issue.
AL
Alonzo
2 years ago
Hmm, looks like a connection issue. I bet it's the cable - who unplugged it? Probably the intern trying to 'optimize' the network.
VI
Virgina
2 years ago
User 3: We should check the physical connection first.
ST
Stephane
2 years ago
User 2: Yeah, that could be the cause of the failure.
CL
Clarinda
2 years ago
Maybe the cable between SONiC-1 and SONiC-2 is unplugged.
CA
Carrol
2 years ago
But if the cable is unplugged, there won't be any traffic passing between the switches.
EZ
Ezekiel
2 years ago
I disagree, I believe it's option B, a spanning-tree blocking the link.
CA
Carrol
2 years ago
I think the cause of the failure is option D, a cable that is unplugged.
AR
Ariel
2 years ago
Ah, the classic spanning-tree dance. I'll go with option B, just to keep things interesting.
JO
Joseph
2 years ago
Maybe IPv6 is not enabled on SONiC-1's interface.
DA
Dalene
2 years ago
I believe a spanning-tree is blocking the link.
MI
Mindy
2 years ago
I think the issue is with the IPv6 address type on SONiC-2.
TA
Tatum
2 years ago
C'mon, guys, let's not be IPv6 deniers. I bet it's option C - no IPv6 on that interface.
RO
Royal
2 years ago
Hmm, I think it's option D. That cable must be as elusive as the Loch Ness Monster!
JA
Jamal
2 years ago
I agree with User1, it's probably the unplugged cable, option D.
BR
Brendan
2 years ago
I think IPv6 might not be enabled on Eth 1/1 of SONiC-1, option C.
CL
Clorinda
2 years ago
Maybe there's a spanning-tree blocking the link, option B.
JA
Jaime
2 years ago
It could be option D, the cable might be unplugged.