Labs · Episode 16 · 4:14

Diagnose and repair a broken network

Learn a repeatable troubleshooting sequence: establish a working baseline, reproduce an interface fault, check a successful control, inspect CLI, Info and Events evidence, then repair and verify connectivity and saved configuration.

English narration and on-screen explanations. Read the narration transcript.

Chapters
Open MP4

Narration transcript

The English narration in this video. Select a time to watch that moment.

  1. Establish a working baseline

  2. Start with two routers and a working route between their loopbacks.

  3. On this fresh path, the first echo may fail while ARP learns the next hop.

  4. Repeat the ping and check for 100 percent success before saving the baseline.

  5. Save the device configurations, then save a named baseline version.

  6. A baseline gives you evidence to compare with a later fault.

  7. Reproduce one fault

  8. Shut down R2’s uplink to introduce one deliberate fault.

  9. The remote loopback is now unreachable from R1.

  10. Ping R1’s own loopback as a control. That local test still succeeds.

  11. Keep the failed test and the successful control together when diagnosing.

  12. Inspect the evidence

  13. Read the interface status and routing table to locate the broken path.

  14. Open Info to confirm R2’s uplink is administratively down.

  15. Search Events for shutdown and check which device issued the command.

  16. Save a separate fault version, then compare the baseline with the current lab.

  17. The comparison identifies the interface shutdown without a topology change.

  18. Repair and recheck

  19. Use no shutdown on the same interface to repair this fault.

  20. Save the configuration and repeat the original connectivity test.

  21. A successful ping and restored route confirm the path works again.

  22. Compare with the baseline again to verify the saved configuration is restored.

Back to all Labs videos