The scene: a NOC operations room, early evening on a Friday. A heretofore unknown bug crops up in a core network device. Catastrophe follows, with network administrators pulling their hair out trying to make sense of a nonsensical situation. There's chaos, mayhem, and blood in the data center aisles. Gravely assessing the situation, the head network guru states, "We must have hit an undocumented bug. We need to try a new firmware version, and fast!"
With the main Internet connections down, it's a good thing there's a laptop with a mobile data card at the ready. An admin sits down and pulls up the networking vendor's support site.
[ Find out how to block the viruses, worms, and other malware that threaten your business, with hands-on advice from InfoWorld's expert contributors in InfoWorld's "Malware Deep Dive" PDF guide. ]
Sweat pours from his face as he waits for the cutesy Flash-based splash page to load. He grimaces waiting for the neato server-side dynamic droplist element population. He slogs his way through page after page of nonsense surrounding the few actual pieces of information he needs. Minutes tick by. A storage admin vomits in terror in the hallway. The CEO is reportedly "on his way from his daughter's wedding."
But the admin is almost there, only a few more slow-loading pages to go. But what's this? The new firmware image can't be downloaded without the use of a proprietary Java-based "download assistant"? And it's 45MB? "Dear God," mutters the admin.
The room goes as quiet as a morgue while everyone fervently watches the download progress bar creep across the screen. Someone calls 911 on behalf of the storage admin, who is laid out on a desk in the corner, whimpering softly, his eyes rolling aimlessly in his head. The progress bar moves ahead another percent. An interminable gulf of time now exists, and all in the room know that this is just the first part -- the actual firmware isn't even being downloaded yet. But finally the Java download assistant has been downloaded. Thank God the CEO hasn't arrived yet.
The network admin starts the installer. It launches, but disaster strikes yet again -- it requires JRE 1.6.11, the admin's laptop only has JRE 1.6.5. The storage admin's whimpering ceases as he quietly expires. Nobody notices.
The only one with his wits about him, the head networking guru leaps toward the table and snatches the laptop. He runs at breakneck speed to the elevators, but veers in the direction of the stairs. He jumps down the steps two, three at a time, the laptop swinging from his hand like a frisbee ready to fly.