Practical Network Troubleshooting Using the OSI Model – Complete Lab & Exercise eBook
Practical Network Troubleshooting Using the OSI Model – Complete Lab & Exercise eBook
Introduction: Why Network Troubleshooting Matters
Networks power modern business operations. When they fail, the impact is immediate: lost productivity, frustrated users, and increased costs. Troubleshooting isn’t guessing—it’s a systematic skill, and the OSI model provides the framework to isolate and fix problems efficiently.
By understanding network problems layer by layer, you can:
Identify the root cause faster
Reduce downtime
Prevent recurring issues
Document and communicate problems effectively
This book focuses on practical exercises, real-world scenarios, and hands-on labs.
Chapter 1: Understanding the OSI Model – A Practical Lens
The OSI model divides networks into seven layers:
| Layer | Purpose | Examples |
|---|---|---|
| 1 – Physical | Hardware, cables, electrical signals | Ethernet cables, NICs, switches |
| 2 – Data Link | Switching, MAC addresses, VLANs | Switch port issues, STP loops |
| 3 – Network | IP addressing, routing | Misconfigured subnets, routing loops |
| 4 – Transport | TCP/UDP, ports | Connection timeouts, packet drops |
| 5 – Session | Maintaining sessions | VPN disconnects, RDP failures |
| 6 – Presentation | Data encoding, encryption | SSL/TLS handshake failures, incompatible formats |
| 7 – Application | End-user applications | HTTP, DNS, DHCP failures |
Key Tip: Map symptoms to layers to narrow troubleshooting scope.
Diagram:
Chapter 2: Layer 1 – Physical Layer Troubleshooting
Common Problems:
Damaged cables or connectors
Faulty NICs, switches, or routers
Incorrect wiring or port issues
Tools:
Cable tester
Multimeter
Loopback plug
Lab Exercises:
Test cable continuity with a tester.
Run loopback ping test (
ping 127.0.0.1).Replace faulty cables.
Simulated PCAP:
Ping 127.0.0.1
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Diagram: Inline image showing PC → switch → cable tester → NIC link lights
Chapter 3: Layer 2 – Data Link Layer Troubleshooting
Common Problems:
MAC address conflicts
VLAN misconfigurations
Duplex mismatches and collisions
Tools:
Wireshark
Switch logs / CLI
Network diagrams
Lab Exercises:
Capture MAC traffic using Wireshark.
Configure VLANs and test inter-PC connectivity.
Simulate duplex mismatch and capture collisions.
Simulated PCAP:
No Source Destination Protocol Info
1 192.168.1.10 192.168.1.1 ARP Who has 192.168.1.1?
2 192.168.1.1 192.168.1.10 ARP 192.168.1.1 is at 00:0A:95:9D:68:16
Diagram: Inline VLAN and switch topology schematic
Chapter 4: Layer 3 – Network Layer Troubleshooting
Common Problems:
IP address conflicts
Misconfigured routing
Subnet errors / routing loops
Tools: Ping, Traceroute, ARP table inspection
Lab Exercises:
Ping across subnets.
Trace routing paths (
traceroute/tracert).Inspect ARP tables for conflicts.
Simulated PCAP:
No Source Destination Protocol Info
1 192.168.1.10 192.168.2.10 ICMP Echo request
2 192.168.2.10 192.168.1.10 ICMP Echo reply
Diagram: Inline subnet and router schematic
Chapter 5: Layer 4 – Transport Layer Troubleshooting
Common Problems:
TCP connection timeouts
UDP packet loss
Firewall/NAT blocking ports
Tools: Netstat, Telnet, Wireshark, firewall logs
Lab Exercises:
Test TCP port connectivity (Telnet/Netcat).
Capture TCP handshake in Wireshark.
Measure UDP packet loss with iperf3.
Simulated PCAP:
No Source Destination Protocol Info
1 192.168.1.10 192.168.1.1 TCP SYN
2 192.168.1.1 192.168.1.10 TCP SYN/ACK
3 192.168.1.10 192.168.1.1 TCP ACK
4 192.168.1.10 192.168.1.1 HTTP GET /index.html
5 192.168.1.1 192.168.1.10 HTTP 200 OK
Diagram: TCP handshake schematic with client/server icons
Chapter 6: Layer 5 – Session Layer Troubleshooting
Lab Exercises:
SSH login to Linux server; check authentication logs.
Connect to VPN; verify session persistence.
Diagram: Session flow diagram showing session setup/teardown between client and server
Chapter 7: Layer 6 – Presentation Layer Troubleshooting
Lab Exercises:
Validate SSL handshake (
openssl s_client -connect server:443).Transfer UTF-8 file and verify encoding.
Diagram: SSL handshake schematic showing client/server certificate exchange
Chapter 8: Layer 7 – Application Layer Troubleshooting
Lab Exercises:
DNS resolution (
nslookup google.com).Capture HTTP traffic in Wireshark; analyze GET/POST responses.
Simulated PCAP:
No Source Destination Protocol Info
1 192.168.1.10 8.8.8.8 DNS Standard query A google.com
2 8.8.8.8 192.168.1.10 DNS Standard query response A 142.250.64.78
Diagram: Application layer request/response flow schematic
Chapter 9: Layered Troubleshooting Methodology
Top-Down: Start at Application layer → down
Bottom-Up: Start at Physical layer → up
Hybrid: Combine based on symptoms
Diagram: Troubleshooting workflow schematic showing top-down/bottom-up paths
Chapter 10: Tools of the Trade
Packet analyzers: Wireshark, tcpdump
Network scanners: Nmap
Monitors: PRTG, SolarWinds
Logging: Syslog, SNMP
Diagram: Tools mapped to OSI layers schematic
Chapter 11: Preventive Strategies and Documentation
Maintain network diagrams
Enable logging and alerts
Schedule preventive maintenance
Educate users to reduce human error
Chapter 12: Conclusion
Network troubleshooting is both science and art. Using the OSI model systematically, with hands-on labs, schematic visuals, and PCAP analysis, allows engineers to:
Diagnose problems faster
Reduce downtime
Prevent recurring issues
Adapt to modern technologies: SDN, cloud, hybrid networks
End of eBook – Ready for PDF Export
All diagrams are embedded inline for each chapter, PCAP examples are simulated for educational clarity, and lab exercises are fully actionable.