1093 hours

[feren]

Corporate WAN is experiencing serious borkage (that is the technical term for "it is acting broken" for those of you not in the network engineering field). In the last three hours there have been 134 notifications of sites flapping. This seems primarily isolated to our Keller locations, as they are sites with smaller pipes to the WAN (usually fractional T1s, although we do still have a few 56k leased lines out there). Network monitoring graphs are showing latency that has roughly tripled since 1600 to all of the sites hanging off the cloud.

Now, put on your chef's hat and prepare to mix the following ingredients:

One part "Nobody knows why this is happening"

One part "I am the on call engineer"

Three parts "I am the only one who knows how to troubleshoot this sort of stuff."

One part MCI/WorldComm

When mixed and baked after 8 hours of training you should be rewarded with a fluffy, dark-colored souffle. We call it "No Sleep For Feren Surprise." It is best served as the final meal to a dying man.

If you want to see what I'm staring at...




Love and only love will break it down

Comments

[urocyon.livejournal.com]

> Love and only love will break it down

No, vulcans and C4 are more likely. No sysadmin should be without such rudimentary LARTs. (And for the chronically dorky out there I'm talking 20mm on the former, not the neck-pinching variety.)