He was really nervous showing the new install off to us, and he was just talking through the positions of the switch; but he actually moved the switch to each of them as he did it.
Back in the days the conslops ran the asylum. :)
Any old school UF types looking at this, The Dog list lives on, and is again meeting from time to time. :) But at quieter venues. Our ears have unaccountably gotten old.
We were student employees, who were nonetheless in charge of all the systems. It was an absolutely awesome experience.
Sorry, couldn't hold myself :)
Cisco had a virtual router. N1000 perhaps, the hardware was a C220 and it had some sort of appliance running on it. Which depended on some sort of LUN from NetApp for its storage. But you couldn’t stand the LUN up until the vCenter was up because UCS provisioned the LUN, it didn’t work if you did it manually, and that ran on vCenter, and the vCenter depended on the router so that it could reach the LUN. It was pure circular logic hell.
There was a path to make this work, but it literally took half a dozen very ~~clever~~ expensive Cisco and NetApp engineers a couple of days in a room with a whiteboard to figure it out. It was absurd.
Second story, around 2005---I, along with a friend and my father, were in Las Vegas eating lunch at one of the major casinos when the power went out completely. It was eerily silent and dark! (and then slowly, we started hearing the groans of slotzombies rising among us) I'm sure someone lost their job for a UPS cut-over failure.
For some reason, he decides to demo the UPS cut-over switch. I have no idea why. But he manages to toggle it the wrong way and instead of switching the entire room full of servers to the UPS, he manages to cut power to _all of them_.
My recollection is that the cooling went out too and the room was suddenly very silent. But in retrospect that doesn't make sense.
What I do remember is that it was non-trivial to bring all our Unix servers back up because over the years they had been setup with NFS mounts in a loop such that for A to boot, it needed B to be up, which needed C to be up, which needed A to be up.
Oops.
So it took a lot of manual intervention to bring everything back up.
During that time, none of the CS professors could use their workstations since they were all dumb terminals. Same for many of the CS lab machines. Email was down for cis.ufl.edu. So was NNTP.
It took most of the day (as I recall), but eventually we got everything back up.
I say "we" because besides getting my CS degree, I was also working for the CS department as a lab assistant/sys op.