Operations Week Finale: The Troubleshooting “Final Boss”

The Ticket: “Help! The Computer Lab in Building B is completely offline, None of the 20 students can log in, and the teacher says “internet is broken’ since the storm last night.”

Step 1: Identify the Problem (Gathering Info)

You arrive at the lab. You don’t just start swapping cables.

• Observation: You look at the workstations. All of them show the “Global/No internet” Icon.
• Scope: It’s not just one student; it’s the entire room. This tells you the problem is likely centralized (A switch or a router) rather than individual PCs.

Step 2: Establish a Theory (Probably Cause)

Since there was a storm, your mind should go to two places:

1. Power: Did a surge fry the switch in the closet?
2. Layer 1: Did a leak or a physical break happen on the “Trunk” line connecting Building B to the Main Office?

Step 3: Test the Theory

You open your terminal on a lab PC and run ipconfig.

• Result: The IP is 169.254.x.x.
• Diagnosis: This is an APIPA Address. The computer can’t find the DHCP server.
• Test: You try to ping the default gateway. Request Timed out.
• The Theory: The lab switch is either dead or disconnected from the core.

Step 4: Plan of Action & Implementation

You head to the wiring closet. You see the switch is powered on (the fans are spinning), but the Uplink Port (The fiber line back to the core) has no light.

• Action: You pull out your Loopback Plug. You plug it into the switch’s uplink port. The light stays off.
• The Real Fix: the SFP Transceiver (The little module the fiber plugs into) was fried by the surge. You swap it with a spare from your tech bag.

Step 5: Verify Functionality

The link light turns green! you head back to the lab.

• You run ipconfig /renew.
• The computer grabs a proper 10.x.x.x address.
• You have the teacher try to open the grading portal. Success.

Step 6: Document Findings (The “Piller” of the Post)

You updated the tiicket. “Storm casued surge; fried SFP module in Buildin B closet. Swapped SFP, verified DHCP and connectivity. Recommend adding a higher-grade surge protector to that rack.”

🛠️ The “Tech Bag” Essentials Checklist

To end the week, here is the “Cyber Ledger: list of what should be in your bag every single day:

1. Console Cable: Talk to switches when the network is down.
2. Known-Good Patch Cables: Cat6 and a Fiber jumper
3. RJ-45 Loopback Plug: To test NICs instantly
4. Tone & Probe: For the “unlabeled cable” nightmare.
5. Basic Cable Tester: To check for crossed pairs.
6. USB to Ethernet Adapter: For those modern laptops that don’t have a port.

The Week in Review

We have moved from being “reactive” to being “methodical.”

• Monday: We learned to See with CLI.
• Tuesday: We learned to Listen with SNMP
• Wednesday: We learned to Think with the 7-step Method.
• Thursday: We learned to Touch with hardware Tools.
• Today: We Solved the problem

What’s Next?

We have conquered the “Grind” of Operations! we are officially thinking like a Network Engineer.

Next week, we move into the final pillar: Network Security & Hardening. We’ll talk about how to stop the “bad actors” before they even get to the firewall. We’ll coer 802.1X, Port Security, and Wireless Encryption.