Network storms are one of those problems that cry out to be fixed right now. They impact user access to online systems, inter-system communication, and even the network paths that vendors use to identify and repair the very issues that cause the storms. They’re a huge mess to deal with. The worse the storm, the more you want to just reboot the entire network and put an end to it. In fact, if there were a single giant power button for the entire infrastructure, you’d be quite tempted to push it.
There’s a reason you want to fix the problem so badly and immediately. It is impacting the business, alarms are going off, people are being called in from home, company executives you’ve never met before are stopping by your desk for “a quick update”, etc.
Addressing the storm quickly is critical. There are two questions you should be asking yourself before you take any steps:
Most of us address the first without thinking about the second until the next day. But that doesn’t have to be the case. Root cause analysis and future event prevention can be a low-impact component of your response. You just need to know how to track down the cause of a network storm. This article gives you the information you need to do just that – in a cost-effective and low-impact way.