Nexnet AcademyV1 · alpha
← CourseTroubleshooting methodology~5 min read

A method for finding the fault

Isolate the layer

Work bottom-up or divide-and-conquer. Ping by IP to test connectivity; if that works but names fail, it's DNS. If local works but the internet doesn't, look at the gateway or a route. Prove where the packet stops before changing anything.

Use scope

Who is affected and who isn't? If one department is down but its neighbour on the same router is fine, the fault is something only that group has - a per-PC gateway, a VLAN, a duplicate IP. Scope points you straight at the difference.

Not down - just slow

Sometimes nothing is broken; a link is saturated. Monitoring shows utilization per link. A cable carrying more traffic than its capacity queues and drops packets, so everything feels slow. Find the hot link and give it more bandwidth.

Concept cards

Scope isolation

Using who-is-affected vs who-isn't to localize a fault.

If only one floor lost power, check that floor's breaker.

Root cause

The underlying reason a symptom occurs, not just the symptom.

Treating the leak, not just mopping the floor.

Link utilization

Offered load ÷ link capacity; ≥100% means saturation and loss.

A highway at rush hour - more cars than lanes.

Now try it
M8-02Is It DNS?
Start the mission →