Cyber Services / All lessons / Diploma in Network Technology / Real-World Case Studies

Real-World Case Studies

Module 36 of 36 · 5 min read · Free to read

MODULES ↓ Command blocks have a COPY button

Your Gateway to a Career in Network Engineering

Module 8: Analyzing Real-World Case Studies

This is the final step in your journey from student to professional. Technical knowledge is essential, but what employers truly value is your ability to apply that knowledge to solve real-world problems. This section will walk you through common network scenarios, demonstrating the thought process of a skilled technician.

A Universal Troubleshooting Framework

For any problem, from the simple to the complex, a structured approach will always serve you best. Before looking at the cases, internalize this five-step process:

  1. Define the Problem: What is the exact issue, and who is affected?
  2. Gather Information: Ask questions and use diagnostic commands (ping, tracert, show commands).
  3. Form a Hypothesis: Based on the information and your knowledge of the OSI model, what is the most likely cause?
  4. Test the Hypothesis: Perform a test or make a single change to prove or disprove your theory.
  5. Propose a Solution: Once the cause is confirmed, outline the steps to fix it.

Case Studies in Network Troubleshooting

Case Study #1: The Connectivity Outage

The Scenario:

A user in the Sales department calls the help desk. "I can't get on the internet. I can't even access the company portal. The whole network is down!"

Analyst's Thought Process:
  1. The user says "the whole network is down," but that's unlikely. I need to define the scope. My first suspect is always the physical layer. This calls for a **Bottom-Up** or **Divide-and-Conquer** approach.
  2. I'll start at my desk and use the Divide-and-Conquer method. Can I ping the user's default gateway? If yes, the core network is fine. In this case, I can't reach the user's gateway. The problem is on their local segment.
  3. I ask the user to check their physical connection. "Is the cable plugged in firmly? Do you see a green light on your computer's network port and on the wall jack?" The user confirms the lights are off.
  4. This confirms a **Layer 1 (Physical)** issue. Before I dispatch a technician, I'll check the switch. I log in to the switch and run show ip interface brief. I see the user's interface, GigabitEthernet0/5, is in an "administratively down" state.
Likely Cause:

The switch port was accidentally shut down, likely during a previous maintenance window or due to a configuration error.

Proposed Solution:

Enter interface configuration mode for GigabitEthernet0/5 and use the no shutdown command to re-enable the port.

Key Takeaway: Always verify the foundational layers (1-3) before looking for complex problems. A systematic approach quickly turned a vague "network is down" report into a simple fix.

Case Study #2: The Performance Problem

The Scenario:

The entire Marketing department complains that "the network is very slow," especially when accessing large files from the main server. The issue seems to get worse in the afternoon.

Analyst's Thought Process:
  1. "Slow" is subjective. I need data. This is a perfect case for comparing current performance against our established **network baseline**.
  2. I check our network monitoring system. I see that bandwidth utilization on the link to the Marketing department's switch is high but not maxed out. However, I see a very high number of errors and collisions on several user-facing ports, including the port connected to the file server.
  3. High error counts are often a symptom of a **Layer 1 or Layer 2** issue. My primary hypothesis is a **duplex mismatch**. This can happen if one side of a link is hard-coded to "full-duplex" and the other is set to "auto-negotiate." The auto side will often fall back to half-duplex, causing massive collisions and slow performance.
  4. I log into the switch and run show interface GigabitEthernet0/10 (a user port). I see a high number of CRC errors and collisions. I then check the network card settings on the user's PC and see it has been manually set to full-duplex.
Likely Cause:

A duplex mismatch between the switch ports (set to auto) and the NICs on several Marketing PCs (hard-coded to full).

Proposed Solution:

Set both the switch ports and the client PC network cards to `auto-negotiate` for both speed and duplex. This is the industry best practice.

Key Takeaway: Performance issues are often invisible. Network monitoring and baselines are essential for spotting problems like error rates that indicate underlying physical or data-link layer faults.

Case Study #3: The Access Problem

The Scenario:

A new web server (192.168.20.50) has been deployed in the Server VLAN (VLAN 20). Users in the Marketing VLAN (VLAN 30) can access it, but users in the Sales VLAN (VLAN 10) cannot. All users can access the internet and other internal resources.

Analyst's Thought Process:
  1. This is not a simple connectivity issue, as some users can access the server. This points to a rule-based problem, likely at **Layer 3 or 4**. My primary hypothesis is an **Access Control List (ACL)** or firewall rule.
  2. I'll use a **Top-Down** approach. From a Sales PC, I try to ping 192.168.20.50. It fails. Then, I run tracert 192.168.20.50. The trace reaches the default gateway (the router) and then times out. This confirms the router is receiving the traffic but is actively dropping it.
  3. I log in to the router, which handles the Inter-VLAN routing. I run show access-lists.
  4. I find an existing ACL applied to the interface for the Server VLAN. The ACL has a rule permitting traffic from the Marketing subnet (192.168.30.0/24) but has no rule for the Sales subnet (192.168.10.0/24).
Likely Cause:

The ACL was configured to only permit the Marketing VLAN. Due to the **implicit deny all** at the end of every ACL, traffic from the Sales VLAN is being blocked as intended by the old rules, but the rules were never updated for the new server.

Proposed Solution:

Modify the existing access list to add a new `permit` statement allowing the Sales subnet to access the new web server on TCP ports 80 and 443.

Key Takeaway: Security policies like ACLs are a common cause of "selective" connectivity issues. Understanding top-down processing and the implicit deny is critical for troubleshooting them.

Modules (36) ← Diploma in Network Technology