smd@clock.ORG writes:
You would think that a person working at UUNET might be able to find a counterpart at Abovenet and ask directly, rather than floating a "ha ha look - Abovenet crashed!" message on the NANOG mailing list.
Could be a few different reasons. a) Curiousity b) Concern it may have a root cause shared by other providers c) Lack of notification via formal channels d) Spite e) All of the above What's the only thing worse for a network engineer than having his network crash? No one noticing it crashed. I'm really surprised more providers haven't figured out one way to keep people from posting about their outages is by setting up peering agreements with NDA's and then keeping the other providers informed about problems. Of course if there isn't an NDA or they learn about the outage from other sources, they are free to inform the world about the outage. Oh well, another Sprint exec Gerry Degruiter is going to stop by next week. I hope he can tell me why our Sprint line failed last November, no one else has been willing too. I'll keep you posted :-) -- Sean Donelan, Data Research Associates, Inc, St. Louis, MO Affiliation given for identification not representation
Personally, I'm glad it was posted. I have a friend who has two servers at abovenet and they were not told, and definatly not 3 times, what the cause of the downtime was. I realise it is one of the hazards of co-location of your servers, not to be able to run to it, but still would be nice to know it wasn't your machines that were down. On Tue, 27 Apr 1999, Sean Donelan wrote:
smd@clock.ORG writes:
You would think that a person working at UUNET might be able to find a counterpart at Abovenet and ask directly, rather than floating a "ha ha look - Abovenet crashed!" message on the NANOG mailing list.
On Tue, 27 Apr 1999, Becki Kain wrote:
Personally, I'm glad it was posted. I have a friend who has two servers at abovenet and they were not told, and definatly not 3 times, what the cause of the downtime was. I realise it is one of the hazards of co-location of your servers, not to be able to run to it, but still would be nice to know it wasn't your machines that were down.
Hmmm - you may want to check with Avi or their noc@above.net address and make sure that your friend is actually on their notification list - but I in fact was notified the 3 times that Avi does speak about - of course I had already called the NOC re: same moments after it happenend and informed that Leo was already working on it. And yes - it was handled quickly and proffesionally. -- I am nothing if not net-Q! - ras@poppa.thick.net
On Tue, 27 Apr 1999, Sean Donelan wrote:
floating a "ha ha look - Abovenet crashed!" message on the NANOG mailing list.
Could be a few different reasons.
a) Curiousity b) Concern it may have a root cause shared by other providers c) Lack of notification via formal channels d) Spite e) All of the above
or a combo of b) and f) A fairly large network goes down, which could lead to priceless operational experience on bootstrapping from scratch. Avi already mentioned dampening issues with the SPF calculations. And how to architect this to prevent meltdown in the future. Partitioning the IGP areas, etc etc etc. Of course my original message was very badly phrased and for that I apologize. /vijay
participants (4)
-
Becki Kain -
Rich Sena -
Sean Donelan -
Vijay Gill