Mist has detected a bad cable.
What are two ways that Marvis determined this result? (Choose two.)
Mist has detected a bad cable.
What are two ways that Marvis determined this result? (Choose two.)
Marvis detected a bad cable through port flapping and interface errors. Port flapping occurs when a port goes up and down repeatedly, which can be caused by a faulty cable. Interface errors, such as CRC errors, are indicative of transmission faults often due to bad cables. Identifying network loops or missing VLANs, however, would not be directly associated with a bad cable.
I would say, B&C because those are Layer 1 issues, the other ones are layer 2 issues
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
I think B & D