Back to Dashboard
Module 51
Troubleshooting Methodology
← Previous Module
Next Module →
# 📘 CCNA 200-301 - Video 51: Troubleshooting Methodology ## Deep Study Notes --- ## 📌 Learning Objectives By the end of this video, you should understand: - Structured troubleshooting methodology - Common troubleshooting approaches - Troubleshooting tools and commands - Layer-by-layer troubleshooting (OSI model) - Problem isolation techniques - Documentation and root cause analysis --- ## 🧠 Core Concepts ### 1. What is Troubleshooting? **Definition:** Troubleshooting is the systematic process of identifying, isolating, and resolving network problems to restore normal operation. **Analogy:** Think of troubleshooting like a doctor diagnosing a patient: - **Symptoms:** What is the problem? (Users can't access internet) - **History:** When did it start? What changed? - **Examination:** Check network devices (ping, show commands) - **Diagnosis:** Identify root cause (router misconfiguration) - **Treatment:** Fix the problem - **Follow-up:** Verify solution and prevent recurrence ``` ┌─────────────────────────────────────────────────────────────────────────────┐ │ TROUBLESHOOTING PROCESS │ ├─────────────────────────────────────────────────────────────────────────────┤ │ │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ STEP 1: DEFINE THE PROBLEM │ │ │ │ • What is the symptom? │ │ │ │ • When did it start? │ │ │ │ • What changed? │ │ │ │ • Who is affected? │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ │ │ │ │ ▼ │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ STEP 2: GATHER INFORMATION │ │ │ │ • Show commands │ │ │ │ • Logs (syslog, debug) │ │ │ │ • Network monitoring tools │ │ │ │ • User interviews │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ │ │ │ │ ▼ │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ STEP 3: ISOLATE THE PROBLEM │ │ │ │ • Layer-by-layer analysis │ │ │ │ • Divide and conquer │ │ │ │ • Compare working vs. non-working │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ │ │ │ │ ▼ │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ STEP 4: IDENTIFY ROOT CAUSE │ │ │ │ • What is causing the problem? │ │ │ │ • Verify with testing │ │ │ │ • Document findings │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ │ │ │ │ ▼ │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ STEP 5: IMPLEMENT SOLUTION │ │ │ │ • Apply fix │ │ │ │ • Test solution │ │ │ │ • Verify all affected services │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ │ │ │ │ ▼ │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ STEP 6: DOCUMENT AND PREVENT │ │ │ │ • Document root cause and solution │ │ │ │ • Update knowledge base │ │ │ │ • Implement preventive measures │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ │ │ └─────────────────────────────────────────────────────────────────────────────┘ ``` --- ### 2. Troubleshooting Approaches | Approach | Description | When to Use | |----------|-------------|-------------| | **Bottom-Up** | Start at physical layer, move up | Suspected physical or hardware issues | | **Top-Down** | Start at application layer, move down | Suspected application or user issues | | **Divide-and-Conquer** | Test middle layers first (Network/Transport) | Unknown issue, most common | | **Follow-the-Path** | Trace traffic path hop-by-hop | Routing issues, connectivity problems | | **Compare-Config** | Compare working vs. non-working devices | Configuration errors | ``` ┌─────────────────────────────────────────────────────────────────────────────┐ │ TROUBLESHOOTING APPROACHES │ ├─────────────────────────────────────────────────────────────────────────────┤ │ │ │ BOTTOM-UP (Start at Layer 1): │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ Layer 7 ──► Layer 6 ──► Layer 5 ──► Layer 4 ──► Layer 3 ──► │ │ │ │ │ │ │ │ Layer 2 ──► Layer 1 (Physical) │ │ │ │ │ │ │ │ Use: When physical layer issues are suspected │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ │ │ │ TOP-DOWN (Start at Layer 7): │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ Layer 1 ◄── Layer 2 ◄── Layer 3 ◄── Layer 4 ◄── Layer 5 ◄── │ │ │ │ │ │ │ │ Layer 6 ◄── Layer 7 (Application) │ │ │ │ │ │ │ │ Use: When application/user issues are suspected │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ │ │ │ DIVIDE-AND-CONQUER (Start at Layer 3/4): │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ │ │ │ │ Test Layer 3 (IP) first: Can you ping? │ │ │ │ │ │ │ │ │ ├── YES → Problem is higher (L4-L7) │ │ │ │ │ │ │ │ │ └── NO → Problem is lower (L1-L3) │ │ │ │ │ │ │ │ Use: Most efficient, unknown cause │ │ │ │ │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ │ │ └─────────────────────────────────────────────────────────────────────────────┘ ``` --- ### 3. Troubleshooting Tools | Tool | Purpose | Key Commands | |------|---------|--------------| | **Ping** | Basic connectivity | `ping [ip]` | | **Traceroute** | Path discovery | `traceroute [ip]` | | **Show Commands** | Device status | `show ip interface brief`, `show ip route` | | **Debug** | Real-time packet analysis | `debug ip packet`, `debug ip ospf` | | **Logging** | Historical events | `show logging` | | **Packet Capture** | Deep packet inspection | SPAN, Wireshark | | **SNMP** | Monitoring | `show snmp` | | **NetFlow** | Traffic analysis | `show flow monitor cache` | ``` ┌─────────────────────────────────────────────────────────────────────────────┐ │ TROUBLESHOOTING TOOLS │ ├─────────────────────────────────────────────────────────────────────────────┤ │ │ │ PING: │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ • Tests basic IP connectivity │ │ │ │ • ICMP echo request/reply │ │ │ │ • Extended ping: source IP, size, count │ │ │ │ │ │ │ │ Router# ping 192.168.1.1 source 10.1.1.1 size 1500 │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ │ │ │ TRACEROUTE: │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ • Shows path to destination │ │ │ │ • Identifies where packets are dropped │ │ │ │ • Uses TTL values │ │ │ │ │ │ │ │ Router# traceroute 8.8.8.8 │ │ │ │ Type escape sequence to abort. │ │ │ │ Tracing the route to 8.8.8.8 │ │ │ │ 1 192.168.1.1 0 msec 0 msec 0 msec │ │ │ │ 2 10.1.1.1 4 msec 4 msec 4 msec │ │ │ │ 3 203.0.113.1 8 msec 8 msec 8 msec │ │ │ │ 4 * * * │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ │ │ │ SHOW COMMANDS: │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ • show ip interface brief - Interface status │ │ │ │ • show ip route - Routing table │ │ │ │ • show running-config - Current configuration │ │ │ │ • show interfaces - Interface statistics │ │ │ │ • show ip arp - ARP table │ │ │ │ • show mac address-table - MAC table │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ │ │ └─────────────────────────────────────────────────────────────────────────────┘ ``` --- ### 4. Layer-by-Layer Troubleshooting ``` ┌─────────────────────────────────────────────────────────────────────────────┐ │ OSI LAYER TROUBLESHOOTING │ ├─────────────────────────────────────────────────────────────────────────────┤ │ │ │ LAYER 1 - PHYSICAL: │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ Symptoms: Interface down, no link light, CRC errors │ │ │ │ Commands: show interfaces, show controllers, show ip interface brief│ │ │ │ Checks: │ │ │ │ • Is the cable connected? │ │ │ │ • Is the interface status "up/up"? │ │ │ │ • Are there CRC errors, collisions? │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ │ │ │ LAYER 2 - DATA LINK: │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ Symptoms: ARP issues, MAC flapping, VLAN mismatch │ │ │ │ Commands: show mac address-table, show arp, show vlan │ │ │ │ Checks: │ │ │ │ • Is the device in correct VLAN? │ │ │ │ • Is the MAC address learned correctly? │ │ │ │ • Are there STP issues? │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ │ │ │ LAYER 3 - NETWORK: │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ Symptoms: Cannot ping, routing issues, IP conflicts │ │ │ │ Commands: show ip route, show ip interface, ping │ │ │ │ Checks: │ │ │ │ • Is the IP address configured correctly? │ │ │ │ • Is there a route to destination? │ │ │ │ • Are ACLs blocking traffic? │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ │ │ │ LAYER 4 - TRANSPORT: │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ Symptoms: Applications connect but slow, timeouts │ │ │ │ Commands: show ip sockets, telnet, debug ip packet │ │ │ │ Checks: │ │ │ │ • Is the port open? │ │ │ │ • Are ACLs blocking specific ports? │ │ │ │ • Is there a firewall blocking? │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ │ │ │ LAYERS 5-7 - SESSION, PRESENTATION, APPLICATION: │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ Symptoms: Application errors, authentication failures │ │ │ │ Commands: show log, debug, application logs │ │ │ │ Checks: │ │ │ │ • Is the application server reachable? │ │ │ │ • Are credentials correct? │ │ │ │ • Is the application configured correctly? │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ │ │ └─────────────────────────────────────────────────────────────────────────────┘ ``` --- ### 5. Common Troubleshooting Commands | Command | Purpose | Example | |---------|---------|---------| | `ping` | Test connectivity | `ping 192.168.1.1` | | `extended ping` | Advanced ping options | `ping` (enter, then options) | | `traceroute` | Path discovery | `traceroute 8.8.8.8` | | `show ip interface brief` | Interface status summary | `show ip interface brief` | | `show interfaces` | Detailed interface info | `show interfaces gig0/0` | | `show ip route` | Routing table | `show ip route` | | `show running-config` | Current configuration | `show running-config` | | `show startup-config` | Saved configuration | `show startup-config` | | `show vlan brief` | VLAN assignments | `show vlan brief` | | `show mac address-table` | MAC address table | `show mac address-table` | | `show ip arp` | ARP cache | `show ip arp` | | `show logging` | System logs | `show logging` | | `show cdp neighbors` | CDP neighbors | `show cdp neighbors` | | `show ip ospf neighbor` | OSPF neighbors | `show ip ospf neighbor` | | `show ip eigrp neighbors` | EIGRP neighbors | `show ip eigrp neighbors` | | `show spanning-tree` | STP status | `show spanning-tree` | --- ### 6. Troubleshooting Flowcharts **Connectivity Troubleshooting:** ``` ┌─────────────────────────────────────────────────────────────────────────────┐ │ CONNECTIVITY TROUBLESHOOTING FLOW │ ├─────────────────────────────────────────────────────────────────────────────┤ │ │ │ START: User cannot connect │ │ │ │ │ ▼ │ │ Can you ping the default gateway? │ │ │ │ │ ┌────┴────┐ │ │ │ │ │ │ YES NO │ │ │ │ │ │ │ ▼ │ │ │ Check physical connectivity │ │ │ • Link lights? │ │ │ • Interface up/up? │ │ │ • Correct VLAN? │ │ │ │ │ │ │ ▼ │ │ │ Can you ping the gateway now? │ │ │ │ │ │ │ ┌────┴────┐ │ │ │ │ │ │ │ │ YES NO │ │ │ │ │ │ │ │ ▼ ▼ │ │ │ Continue Check IP configuration │ │ │ • DHCP? │ │ │ • Correct subnet? │ │ │ │ │ ▼ │ │ Can you ping remote destination? │ │ │ │ │ ┌────┴────┐ │ │ │ │ │ │ YES NO │ │ │ │ │ │ │ ▼ │ │ │ Check routing │ │ │ • show ip route │ │ │ • Default gateway? │ │ │ │ │ ▼ │ │ Can you ping by name? │ │ │ │ │ ┌────┴────┐ │ │ │ │ │ │ YES NO │ │ │ │ │ │ │ ▼ │ │ │ Check DNS │ │ │ • DNS server configured? │ │ │ • DNS server reachable? │ │ │ │ │ ▼ │ │ Application works? │ │ │ │ │ ┌────┴────┐ │ │ │ │ │ │ YES NO │ │ │ │ │ │ │ ▼ │ │ │ Check port/ACL │ │ │ • Is port allowed? │ │ │ • Firewall rules? │ │ │ │ │ ▼ │ │ PROBLEM SOLVED │ │ │ └─────────────────────────────────────────────────────────────────────────────┘ ``` --- ### 7. Common Network Problems and Solutions | Problem | Symptoms | Common Causes | Solutions | |---------|----------|---------------|-----------| | **No Connectivity** | Cannot ping gateway | Physical cable, VLAN mismatch, IP config | Check cables, verify VLAN, verify IP | | **Intermittent Connectivity** | Works sometimes, not others | Duplex mismatch, cable issues, STP | Check duplex, replace cable, verify STP | | **Slow Network** | High latency, packet loss | Congestion, errors, QoS | Check utilization, check errors, verify QoS | | **Routing Issues** | Can't reach remote networks | Missing routes, ACLs, NAT | Verify routing table, check ACLs, verify NAT | | **DNS Issues** | Can ping IP, not names | DNS server unreachable, wrong DNS | Verify DNS server, check DNS config | | **Authentication Issues** | Cannot login | Wrong credentials, AAA server down | Verify credentials, check AAA server | | **VLAN Issues** | Wrong VLAN access | VLAN not created, wrong port assignment | Verify VLAN exists, check port config | | **STP Issues** | Network loops | STP misconfiguration | Verify STP config, check blocked ports | --- ### 8. Troubleshooting Examples **Example 1: Physical Layer Issue** ```cisco Router# show ip interface brief Interface IP-Address OK? Method Status Protocol GigabitEthernet0/0 unassigned YES unset administratively down down GigabitEthernet0/1 192.168.1.1 YES manual up up ! Problem: Interface is administratively down ! Solution: Router(config)# interface gigabitEthernet 0/0 Router(config-if)# no shutdown ``` **Example 2: VLAN Mismatch** ```cisco Switch# show vlan brief VLAN Name Status Ports ---- -------------------------------- --------- ------------------------------- 1 default active Fa0/1, Fa0/2, Fa0/3, Fa0/4 10 Engineering active Fa0/5, Fa0/6 20 Sales active ! Problem: Port Fa0/10 is in VLAN 1 but should be in VLAN 10 ! Solution: Switch(config)# interface fastEthernet 0/10 Switch(config-if)# switchport mode access Switch(config-if)# switchport access vlan 10 ``` **Example 3: Missing Route** ```cisco Router# show ip route Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area C 192.168.1.0/24 is directly connected, GigabitEthernet0/0 C 10.1.1.0/24 is directly connected, GigabitEthernet0/1 ! Problem: No route to 172.16.1.0/24 network ! Solution: Router(config)# ip route 172.16.1.0 255.255.255.0 10.1.1.2 ``` **Example 4: ACL Blocking** ```cisco Router# show access-lists 100 Extended IP access list 100 10 deny ip any any ! Problem: ACL denies all traffic ! Solution: Router(config)# access-list 100 permit ip any any ``` --- ### 9. Debugging Best Practices ``` ┌─────────────────────────────────────────────────────────────────────────────┐ │ DEBUGGING BEST PRACTICES │ ├─────────────────────────────────────────────────────────────────────────────┤ │ │ │ 1. USE DEBUG SPARINGLY │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ • Debug uses significant CPU │ │ │ │ • Only debug specific protocols │ │ │ │ • Use debug with ACLs to limit output │ │ │ │ • Turn off debug when done: undebug all or no debug all │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ │ │ │ 2. SPECIFIC DEBUG COMMANDS │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ • debug ip packet [acl] - Debug IP packets matching ACL │ │ │ │ • debug ip ospf events - Debug OSPF events │ │ │ │ • debug ip eigrp - Debug EIGRP │ │ │ │ • debug ip rip - Debug RIP │ │ │ │ • debug ip nat - Debug NAT translations │ │ │ │ • debug ip icmp - Debug ICMP (ping) │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ │ │ │ 3. LIMIT DEBUG OUTPUT │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ ! Create ACL to limit debug │ │ │ │ access-list 101 permit ip host 192.168.1.1 any │ │ │ │ debug ip packet 101 │ │ │ │ │ │ │ │ ! Or use conditions │ │ │ │ debug ip ospf events │ │ │ │ debug ip ospf hello │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ │ │ │ 4. MONITOR DEBUG OUTPUT │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ • Use logging buffer to capture debug │ │ │ │ • Show debugging commands running │ │ │ │ Router# show debugging │ │ │ │ │ │ │ │ • Turn off all debugging │ │ │ │ Router# undebug all │ │ │ │ Router# no debug all │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ │ │ └─────────────────────────────────────────────────────────────────────────────┘ ``` --- ### 10. Documentation and Root Cause Analysis **Documentation Best Practices:** ``` ┌─────────────────────────────────────────────────────────────────────────────┐ │ DOCUMENTATION │ ├─────────────────────────────────────────────────────────────────────────────┤ │ │ │ WHAT TO DOCUMENT: │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ • Problem description and symptoms │ │ │ │ • Steps taken to isolate │ │ │ │ • Commands used and output │ │ │ │ • Root cause identified │ │ │ │ • Solution implemented │ │ │ │ • Verification results │ │ │ │ • Preventive measures │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ │ │ │ TICKET FORMAT: │ │ ┌─────────────────────────────────────────────────────────────────────┐ │ │ │ Ticket #: 12345 │ │ │ │ Date: 2024-03-21 │ │ │ │ Reported by: User - John Doe │ │ │ │ Problem: Cannot access internet │ │ │ │ │ │ │ │ Symptoms: │ │ │ │ - PC cannot ping 8.8.8.8 │ │ │ │ - Can ping default gateway │ │ │ │ │ │ │ │ Root Cause: │ │ │ │ - Missing default route on router │ │ │ │ │ │ │ │ Solution: │ │ │ │ - Added ip route 0.0.0.0 0.0.0.0 203.0.113.1 │ │ │ │ │ │ │ │ Verification: │ │ │ │ - PC can now ping 8.8.8.8 │ │ │ │ - Internet access restored │ │ │ │ │ │ │ │ Resolution time: 15 minutes │ │ │ └─────────────────────────────────────────────────────────────────────┘ │ │ │ └─────────────────────────────────────────────────────────────────────────────┘ ``` --- ## 🔧 Complete Configuration Examples ### Lab 1: Basic Connectivity Troubleshooting ```cisco ! Step 1: Check interface status show ip interface brief ! Step 2: Check physical connectivity show interfaces gigabitEthernet 0/0 ! Step 3: Test basic connectivity ping 192.168.1.1 ! Step 4: Check routing show ip route ! Step 5: Trace path traceroute 8.8.8.8 ! Step 6: Check ARP show ip arp ! Step 7: Check logs show logging ``` --- ### Lab 2: VLAN Troubleshooting ```cisco ! Step 1: Verify VLAN assignment show vlan brief ! Step 2: Verify trunk ports show interfaces trunk ! Step 3: Verify MAC address table show mac address-table interface fastEthernet 0/1 ! Step 4: Check STP status show spanning-tree interface fastEthernet 0/1 ``` --- ### Lab 3: Routing Troubleshooting ```cisco ! Step 1: Check routing table show ip route ! Step 2: Check specific route show ip route 192.168.2.0 ! Step 3: Check OSPF neighbors show ip ospf neighbor ! Step 4: Check EIGRP neighbors show ip eigrp neighbors ! Step 5: Debug routing (use sparingly) debug ip routing ``` --- ### Lab 4: ACL Troubleshooting ```cisco ! Step 1: Check ACL configuration show access-lists ! Step 2: Check ACL applied to interface show ip interface gigabitEthernet 0/0 ! Step 3: Test with extended ping ping 192.168.2.1 source 192.168.1.1 ! Step 4: Debug ACL hits debug ip packet 100 ``` --- ## ✅ Exam Tips (For CCNA 200-301) | Topic | What Cisco Tests | |-------|------------------| | **Troubleshooting Methodology** | Systematic approach to problem solving | | **OSI Model** | Layer-by-layer troubleshooting | | **Common Commands** | show, ping, traceroute, debug | | **Physical Layer** | Cable issues, interface status | | **Data Link Layer** | VLAN, STP, MAC issues | | **Network Layer** | IP addressing, routing | | **Transport Layer** | Ports, ACLs, firewalls | | **Root Cause Analysis** | Identify underlying cause | ### Common Exam Scenarios: **Scenario 1:** "Users cannot access the internet but can ping the default gateway. What is the most likely issue?" - **Answer:** Missing default route on router, or ISP connectivity issue **Scenario 2:** "A switch port shows status "up/up" but devices cannot communicate. What should be checked?" - **Answer:** VLAN assignment, port security, spanning-tree **Scenario 3:** "What is the first step in troubleshooting a network issue?" - **Answer:** Define the problem (identify symptoms, scope, recent changes) ### Mnemonics: **Troubleshooting Steps:** **"D.G.I.I.S.D." - Define, Gather, Isolate, Identify, Solve, Document** - **D**efine the problem - **G**ather information - **I**solate the problem - **I**dentify root cause - **S**olve the problem - **D**ocument findings **Divide-and-Conquer:** **"Middle First"** - Start at Layer 3/4 to quickly narrow down the issue --- ## 📝 Summary (1-Minute Revision) ``` TROUBLESHOOTING METHODOLOGY: PROCESS: ├── 1. Define the problem (symptoms, scope, changes) ├── 2. Gather information (show commands, logs) ├── 3. Isolate the problem (layer-by-layer, divide-and-conquer) ├── 4. Identify root cause ├── 5. Implement solution └── 6. Document and prevent APPROACHES: ├── Bottom-Up: Start at physical layer ├── Top-Down: Start at application layer ├── Divide-and-Conquer: Start at network/transport └── Follow-the-Path: Trace traffic hop-by-hop KEY COMMANDS: ├── show ip interface brief - Interface status ├── show ip route - Routing table ├── ping - Basic connectivity ├── traceroute - Path discovery ├── show logging - System logs ├── show running-config - Current config └── debug - Real-time analysis LAYER TROUBLESHOOTING: Layer 1 (Physical): ├── Show interfaces, link lights └── Check cables, power Layer 2 (Data Link): ├── show vlan, show mac address-table └── show spanning-tree, show interfaces trunk Layer 3 (Network): ├── show ip route, show ip interface └── ping, traceroute Layer 4 (Transport): ├── show ip sockets, telnet └── Check ACLs, port availability Layers 5-7 (Application): ├── Application logs └── Check server, authentication BEST PRACTICES: ├── Use debug sparingly ├── Limit debug output with ACLs ├── Document all steps └── Verify solution before closing ``` --- ## 🧪 Practice Questions **1. What is the first step in troubleshooting methodology?** - A) Implement a solution - B) Define the problem - C) Gather information - D) Document findings <details> <summary>Answer</summary> <b>B) Define the problem</b> - Understanding the problem is the first step. </details> **2. Which troubleshooting approach tests Layer 3 first to narrow down the issue?** - A) Bottom-Up - B) Top-Down - C) Divide-and-Conquer - D) Follow-the-Path <details> <summary>Answer</summary> <b>C) Divide-and-Conquer</b> - Tests middle layers first to quickly isolate the issue. </details> **3. Which command displays interface status summary?** - A) `show interfaces` - B) `show ip interface brief` - C) `show running-config` - D) `show ip route` <details> <summary>Answer</summary> <b>B) `show ip interface brief`</b> - Shows interface IP addresses and status. </details> **4. What does a "administratively down" interface status indicate?** - A) Cable disconnected - B) Interface manually shut down - C) Remote device powered off - D) VLAN mismatch <details> <summary>Answer</summary> <b>B) Interface manually shut down</b> - `no shutdown` command is needed. </details> **5. Which tool shows the path packets take to a destination?** - A) ping - B) traceroute - C) show ip route - D) show interfaces <details> <summary>Answer</summary> <b>B) traceroute</b> - Shows each hop along the path. </details> **6. Users can ping IP addresses but not domain names. What is the likely issue?** - A) Routing problem - B) DNS issue - C) Physical layer issue - D) Firewall blocking <details> <summary>Answer</summary> <b>B) DNS issue</b> - Name resolution is failing. </details> **7. Which command displays the MAC address table on a switch?** - A) `show arp` - B) `show mac address-table` - C) `show vlan` - D) `show interfaces` <details> <summary>Answer</summary> <b>B) `show mac address-table`</b> - Displays learned MAC addresses. </details> **8. What does a "up/down" interface status indicate?** - A) Interface is working - B) Interface is administratively down - C) Physical layer up, data link layer down - D) Cable disconnected <details> <summary>Answer</summary> <b>C) Physical layer up, data link layer down</b> - Layer 1 is good, Layer 2 is not. </details> **9. Which command should be used to limit debug output to specific traffic?** - A) `debug ip packet` without parameters - B) `debug ip packet [acl]` - C) `debug all` - D) `debug ip routing` <details> <summary>Answer</summary> <b>B) `debug ip packet [acl]`</b> - ACL limits debug output. </details> **10. What is the purpose of root cause analysis?** - A) Implement temporary fix - B) Identify underlying cause - C) Document symptoms - D) Test connectivity <details> <summary>Answer</summary> <b>B) Identify underlying cause</b> - Finds the true cause, not just symptoms. </details> **11. Which command turns off all debugging?** - A) `no debug` - B) `undebug all` - C) `debug off` - D) Both A and B <details> <summary>Answer</summary> <b>D) Both A and B</b> - `undebug all` and `no debug all` work. </details> **12. What is the most efficient troubleshooting approach for unknown issues?** - A) Bottom-Up - B) Top-Down - C) Divide-and-Conquer - D) Random testing <details> <summary>Answer</summary> <b>C) Divide-and-Conquer</b> - Quickly narrows down the problem area. </details> --- ## 📌 Next Steps After completing Video 51, you should be ready for: - **Video 52:** Troubleshooting Switching Issues - **Video 53:** Troubleshooting Routing Issues **Lab Practice:** 1. Practice systematic troubleshooting on a lab network 2. Use divide-and-conquer approach 3. Document each step 4. Practice with simulated outages 5. Create troubleshooting checklists --- **Ready for Video 52?** Share the link or say "next" and I'll continue with Troubleshooting Switching Issues. I'll continue with **Video 52: Troubleshooting Switching Issues** based on the standard CCNA 200-301 curriculum. ---