Forming a Thought Process for Troubleshooting
Periodically, I get a message from someone asking for troubleshooting help. The most recent of these went something like the following (paraphrasing)–
I have the following routers, R1 through R5, and I cannot ping R5 from R1. Please tell me what the problem is.
In these cases, I could review the configuration or import them into my lab. Inevitably, that might solve the problem for the individual. However, it doesn’t really help the individual solve problems in the future. I prefer to try to help others think through the problem and reach the solution on their own.
Given the symptom of R1 not being able to ping R5, what could that mean? My initial thoughts are–
- R1 isn’t producing packets destined to R5
- R5 isn’t producing packets destined to R1
- One of the routers between R1 and R5 doesn’t know how to reach R5
- One of the routers between R5 and R1 doesn’t know how to reach R1
- Traffic is being filtered somewhere along the way
The first step in troubleshooting this is to understand that there should be two flows being produced. The first flow is a series of echo requests from R1 to R5 and the other flow is a Continue reading


