Kimberly Adams wrote:
I remember another call I received from one of my field engineers from a site and the conversation went like this:
Field Engineer: "We suspect the router may have some water damage."
Me: I thought, why is there water residue on it? But insted asked him, "Why do you suspect there is water damage on the router?"
Field Engineer: "Because there is water dripping into and out of the router."
Me: "Right now?"
Field Engineer: "Yes, because there is a big hole in the roof."
Me: "Well, ok then."
We had to ship a replacement router to the site to bring them back on line once the roof was fixed.
Cheers!
Kimberly
Well, I laughed. :-)
Water, water everywhere, and nary a drop to drink.
I worked in a place once where the roof drains were *very* badly designed. Our office was in the top floor of a 10 (or so) floor tower - and the roof drains ran straight down into the false ceiling before taking a 90-degree turn to run to the downpipes through the service cavity.
Oh, and did I mentione that the roof drains were all 6 inch pipe - and at the 90-degree turn it dropped to a 4 inch pipe?
Oh - and the 90-degree joint was *PVC*.
I got this trouble call one day saying they were experiencing a flood - being in the days of coax 10Base2 networking, I thought packet-flood - wondered if someone had somehow managed to sandwich an extra workstation into a segment I didn't know about which was causing excessive collissions.
What they meant was a *real* flood. There had been a serious storm - something like 4 inches of rain in 30 minutes - and the downpipe *shattered* at the 90-degree joint under the load of water trying to get off the roof.
The floor was under 6 inches of water and rising.
I told 'em to throw the breaker on the server room and leave the rest to figure out once the legal case against the building owner was over and done with. :-)
Yes, it took at least 6 weeks to put the office back online.
