Troubleshooting
Structured Troubleshooting Methodology
Covers a layered, methodical approach to diagnosing network problems, moving through the OSI model to isolate faults efficiently rather than guessing.
What you need to know
- Bottom-up troubleshooting starts at Layer 1 (cabling, power, interface status) and moves up; useful when the problem is likely physical.
- Top-down troubleshooting starts at Layer 7/application and moves down; useful when many users report an application-specific issue.
- Divide-and-conquer starts in the middle (commonly Layer 3) and moves up or down based on results; efficient when the fault layer is unclear.
- Always verify Layer 1 status first: interface up/up state, cabling, and duplex/speed mismatches, before assuming a Layer 3 problem.
- Use show interfaces to check errors, drops, and CRC counters that indicate physical or duplex problems.
- Use ping and traceroute to isolate where in the path connectivity fails, then check routing tables and ACLs at the identified hop.
- Document the problem, gather information, establish a theory, test it, and verify full functionality; this mirrors the standard troubleshooting process taught for CCNA.
Configuration commands
| Command | Mode | Purpose |
|---|---|---|
| show interfaces <intf> | exec | Check interface status, errors, drops, and duplex/speed for Layer 1/2 issues. |
| show ip interface brief | exec | Quickly view interface up/down and line protocol status across the device. |
| show cdp neighbors detail | exec | Confirm physical topology and neighboring device details. |
| ping <ip> | exec | Test basic Layer 3 reachability to a destination. |
| traceroute <ip> | exec | Identify the hop-by-hop path and where connectivity fails. |
| show ip route | exec | Verify the routing table contains the expected route to the destination. |
| show access-lists | exec | Check for ACL entries that might be blocking traffic. |
| debug ip icmp | exec | Observe real-time ICMP packet processing to troubleshoot ping failures. |
| show vlan brief | exec | Confirm VLAN assignments and port membership when troubleshooting switching issues. |
Verify it
- show interfaces
- show ip interface brief
- show ip route
- show mac address-table
- show cdp neighbors
- ping
- traceroute
Common mistakes
- Jumping to Layer 3/4 troubleshooting without first confirming the physical interface is up/up.
- Not checking both ends of a link for duplex or speed mismatch when errors appear in show interfaces.
- Ignoring ACLs as a cause of failed connectivity when routing and interfaces look correct.
- Failing to document each test result, leading to repeated or contradictory troubleshooting steps.
- Assuming a single root cause when multiple independent issues (e.g. VLAN misconfig plus ACL) are present.
Practise Structured Troubleshooting Methodology in a real CLI
Generated labs, graded against the simulated network state.