A. It identified network loops.
> NO, we can all agree that network loop isn't a good situation but it is not caused by a bad cable
B. It identified port flapping.
> Yes, if the port is flapping, that could be the result of a bad cable
C. It identified interface errors.
> YES, when you have a bad cable you have CRC errors and stuff like that
D. It identified a missing VLAN.
> NO ! how could a bad cable cause missing VLAN ??
Hard one, but I would also say B and C.
A loop occurs when multiple links exist between devices, so that's not a bad cable.
Missing VLAN is not bad cable, it's misconfigured.
https://blogs.juniper.net/en-us/enterprise-cloud-and-transformation/juniper-mist-ai-powered-troubleshooting-for-wired-networks
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
maartjeclaartje
Highly Voted 1 year, 8 months agoredgi0
Most Recent 1 year, 2 months agokujup
1 year, 2 months agoVarshadas
1 year, 5 months ago