Anyone know what happened this time? ---------- Forwarded message ---------- Date: Tue, 21 Nov 1995 21:55:09 -0700 (MST) To: cook@cookreport.com Subject: Utah outage (fwd) Forwarded message:
From spot.Colorado.EDU!westnet-site-people-request Tue Nov 21 12:59:14 1995 From: Chris Garner <cgarner@westnet.net> Message-Id: <199511211925.MAA15849@ubu.colorado.edu> Subject: Utah outage To: westnet-site-people@westnet.net Date: Tue, 21 Nov 1995 12:25:23 -0700 (MST) X-Mailer: ELM [version 2.4 PL24alpha3] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit
OUTAGE: Westnet in Utah All Westnet sites in Utah are currently down. The SprintLink lines from the University of Utah are all down due to the loss of SprintLink's Stockton 9 router. The lines went down at 11:20am. Backup routing through Idaho is running, but the T1 from Utah to Idaho is severely overloaded by the Utah traffic, meaning the sites are effectively down. -- -Chris (cgarner@westnet.net)
Gordon, I know what happened :-). The SprintLink Stockton 9 router lost power for a little over an hour. This was just a hardware failure, so I doubt it really belongs on NANOG. Routers will go down. If you are asking why we are backing up our Utah POP with a T1 then it's really related to costs. We can't afford multi T1 backup (we are one of the last not for profit regionals) and until recently, a T1 as backup allowed at least minimal connectivity (email, etc.). We seem to have passed a threshold that makes it useless (but that line is still useful as a backup for our Idaho POP). Of course that discussion doesn't belong on NANOG either. Your friend should have also gotten a later message from the SprintLink INSC outages list (forwarded into the westnet outages list) that described what happened, but I guess he didn't forward that to you. Just to make sure we have at least something that DOES belong on NANOG, I'd like to ask if we should create a centralized outages mailing list. SprintLink has an outages email list that they are starting to use in a useful way, it would be nice if MCI did the same. The old NSFnet nsr list was a big help. I'd see the messages go by and I knew pretty much who was having problems in case I got calls. I know in a commercial environment it can be viewed as a competitive disadvantage to let people know about your outages. Can we find a way around that? Maybe only allowing people who participate onto the mailing list? I'm thinking of a list just for outage announcements (not discussion of outages). It should probably only be for outages that affect large sites, or large numbers of sites (I doubt anyone outside the Granite School District needs to know if Olympus Junior High School loses power). Would SprintLink be willing a forward their outages mailing list into a centralized list, assuming other NSPs like MCI and ANS did the same? -- -Chris (cgarner@westnet.net)
Anyone know what happened this time? ---------- Forwarded message ---------- Date: Tue, 21 Nov 1995 21:55:09 -0700 (MST)
To: cook@cookreport.com Subject: Utah outage (fwd)
Forwarded message:
From spot.Colorado.EDU!westnet-site-people-request Tue Nov 21 12:59:14 1995 From: Chris Garner <cgarner@westnet.net> Message-Id: <199511211925.MAA15849@ubu.colorado.edu> Subject: Utah outage To: westnet-site-people@westnet.net Date: Tue, 21 Nov 1995 12:25:23 -0700 (MST) X-Mailer: ELM [version 2.4 PL24alpha3] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit
OUTAGE: Westnet in Utah
All Westnet sites in Utah are currently down. The SprintLink lines from the University of Utah are all down due to the loss of SprintLink's Stockton 9 router. The lines went down at 11:20am.
Backup routing through Idaho is running, but the T1 from Utah to Idaho is severely overloaded by the Utah traffic, meaning the sites are effectively down.
--
-Chris (cgarner@westnet.net)
participants (2)
-
Chris Garner -
Gordon Cook