(no subject)

[plonq]

There is an alarm ringing in the next room.

BEEP BEEP BEEP BEEP BEEP

My office is located next to our main server room. 

BEEP BEEP BEEP BEEP BEEP

Some piece of critical equipment has gone into meltdown.

BEEP BEEP BEEP BEEP BEEP

Even through the wall it's annoying as hell.

BEEP BEEP BEEP BEEP BEEP

As long as the network keeps working then I will assume that it doesn't affect me, aside from driving me insane.

BEEP BEEP BEEP BEEP BEEP

Maybe some music will drown it out...

Comments

[feren.livejournal.com]

Our operators are cheerfully oblivious. Something can be beeping, flashing or otherwise on fire in the data center and they won't do a thing about it. Case in point: one day I came out to the NOC to look at a patch cable and noticed several amber and red LEDs lit on our FLM-150 (which is responsible for breaking our OC3 line down into two T-3 and 28 T-1 circuits for voice and data services). The dialog was thus:

Feren, with concern: Umm, how long have those lights been lit?
Operator, casually indifferent: Oh, a few days.
Feren, mortified: And you didn't notify anybody that there were red lights on a critical piece of WAN equipment WHY?
Operator, annoyed: It's not our problem.
Feren: Ah, I see now. You're not there to monitor the equipment (hence the title OPERATOR), you're there to keep the floor where it is. Glad we cleared that up.

[plonq.livejournal.com]

This reminds me a bit of something that happened back in my more active RPG days, in a Paranoia campaign.

My memory is a bit hazy (been a few years), but I think the scenario is in one of the computer's power plants. There is a red light flashing and a loud klaxon sounding.

Player: Citizen, what does that alarm and flashing light mean?
Citizen: It means that the reactor core is going critical and could melt down at any time.
Player: (pause) Shouldn't you be doing something about it?
Citizen: (shrug) It goes off all the time.

[furahi.livejournal.com]

Maybe they finally got, and are just testing this?