Concepts / Troubleshooting and ICMP

Troubleshooting and ICMP

Troubleshooting method

Also called network troubleshooting, troubleshooting steps, divide and conquer, theory of probable cause

Finding a fault in order: see it fail, guess a cause, test it, fix one thing, check everything, write it down.

A theory gets tested before anything gets fixed
A theory gets tested before anything gets fixed

A test either proves the theory or sends you back for a new one, and only a proved cause gets a fix. The steps after the fix, checking the whole system, preventing a repeat and writing it down, are the ones people skip.

Identify the problem: make it fail in front of you, find how far it reaches (one machine or all of them) and ask what changed. Form a theory of probable cause and test it: climb the layers from the top or the bottom, or start in the middle with a ping by address and throw away half the suspects with each test (divide and conquer); compare with a machine that works. If the test disagrees, form a new theory or escalate. Plan the fix and what else it touches, change one thing at a time, then check the whole system, prevent a repeat, and document the symptom, the cause, the fix and how you checked it.

See it on real machines

Read next

Learn it on real machines.

Every lab is a small network of real Linux machines in your browser. Sign in with Google or email to start.

Start this lab