There are times when working in large companies that the fear of making any change can mean that a simple outage can become a major problem. For example, I have had Core Switch upgrades delayed for nine months because of refusal to accept that the network would be offline for for 12 hours. Of course, when the Core melted down (as predicted) it took two hours to fix since we just went ahead and railroaded the upgrades into place. Bit unlucky that it was the middle of the day though.
Or the time that we spent preparing to cutover the NetScaler load balancers from the F5 but no one would agree until an unplanned outage happened and then we just switched over at that point.
For moments like those, when you are sitting in front of the core switches and about to reboot, knowing that your butt is on the line, and your work colleagues are going to tease you mercilessly if you flub it, and the boss is going to blame it all on you, here is a little thought to help you through.
Etherealmind’s Action Motto : If I can’t fix it I’ll break it, in which case it needs fixing, anyway.
From time to time I get resistance to making changes to an existing network. This always strikes me as odd. No system can remain static, you will end up with something that is doesn’t change as the business changes. In no way am I abrogating change management and control. This is a vitally important function. But fear of making any change can mean that a simple outage can become a major problem because you don’t know how to troubleshoot.
Corollary : I won’t make it any more broken than it is now.
Remember, you learn the most from your mistakes. You don’t learn from doing things you already know.
If you don’t fix it, you’ll break it and that’s OK, it needed fixing anyway.