Troubleshooting steps
Introduction
Troubleshooting network issues is one of the common skills of every network engineer. And usually, we don’t think about it. We don’t study and train this skill especially. I tell about troubleshooting as a formal process. We just get experience from our daily routine or follow company workflow. I will try to formalize some basic notions. Hope it will be helpful.
Of course, it depends on the situation and business constraints but when we try to resolve some issue we should follow the next steps:
Preparing -> Information-gathering -> Isolating -> Resolving -> Escalating
Let's look at every step.
Preparing
Every network has infrastructure tools (monitoring, inventory, etc), but we should continuously improve and keep up to date them. Try to develop and integrate a new one. This stack of tools is our source of truth. If we have it, we can easily fetch a full amount of information before, during, and after problems. It’s an enormous topic but without these tools, we can’t successfully troubleshoot our network.
Mandatory tools:
- Syslog (at least simple Syslog server. And good to have e.g. Elastic stack)
- Alarm management system (e.g. Zabbix)
- Statistics collector (e. Continue reading








