We like to joke about first-world problems, and lacking Internet access is not really a hardship. But for those of us who are the last line of defense for infrastructures that can and do develop emergent problems in an instant, it's more of a concern. Not to mention it's hardly OK for an IT professional to have multiple circuit outages, no matter what the cause. Our nature dictates that we feel a sense of unease and discomfort until all the pieces to the puzzle are back in place and the bits flow again as they should.
However, I decided to dispense with that concern, if only for a day. I would silence the internal alarms that ring throughout an outage or unscheduled downtime. I would at least try to stop the background processing that rolls through unabated, mulling over the various data points of the problem, looking for correlations or clues that would fix the problem -- all of the normal trappings of an IT ninja in a crisis. After all, it was New Year's Eve, and I had my phone and tablet if something horrible happened at a remote facility.
I was moderately successful. I had a good time at a few parties that evening, and I found myself drifting back to the problem only occasionally, during lulls in conversation and other natural pauses. A good troubleshooter never rests, I suppose.
The problem was eventually resolved. The first sign was the phone ringing on New Year's Day with a call from Fairpoint telling us that our connections had been restored. Both analog lines happened to be controlled by a switching card that failed on New Year's Eve.
All Internet circuits were still down, however. I grabbed a beer and watched a few bowl games, and within a few hours, the DSL circuit came back up of its own accord. The next day, a nice fellow from Time Warner Cable showed up to check the circuit and quickly figured out they'd somehow managed to disable my modem remotely. Only a higher-tier tech could determine that and fix it, he said. He was out the door in less than 10 minutes, and all was back to normal.
If there's a lesson here, it's that even when the odds are seemingly stacked against a particular root cause, you still can't count it out. The other lesson, perhaps, is that I need to learn how to take time off -- but those instructions will have to wait for another day.
This story, "In IT, downtime chooses you," was originally published at InfoWorld.com. Read more of Paul Venezia's The Deep End blog at InfoWorld.com. For the latest business technology news, follow InfoWorld.com on Twitter.