It happens all the time: equipment in a Telecoms network stops reporting traffic statistics. It’s often a problem, though not always the one you think.
The problem can be caused by a failing component somewhere along the data delivery path. You might think that’s the problem.
More likely, the device is under excessive load, and it stopped reporting stats to dedicate all its processing power to providing service.
Of course, it is up to you to figure out which it is. Fault Management systems might help by alerting you to the failing component. But if the issue is excessive load, the solution lies on a different path.
Many telecoms components are designed to provide service as their number one priority over all others. When that priority is threatened, low-priority tasks are discontinued. From the perspective of the equipment, we say it’s designed to shed low-priority load when under stress.
Stress is often caused by an anomalously high load, or by a capacity shortfall. An anomalous load could be triggered by a natural disaster, weather, a civil disturbance, or anything where large numbers of people begin using the network at the same time.
A capacity shortfall means you best start preparing a Capital budget request to fund a capacity augment.
But those aren’t the problems I wanted to discuss. I want to discuss how you can design your Excel Dashboards and recurring reports to handle errors and data dropouts. The types of data dropouts I described above happen all the time. Having an Error Correction strategy built-in will save you tons of time and avoid long explanations. Continue reading “Excel Telecom Tricks – Error Correction”