[31308] in North American Network Operators' Group
problems with uunet/worldcom/whoever-they-bought-this-week
daemon@ATHENA.MIT.EDU (Jim Mercer)
Tue Sep 19 01:54:42 2000
Date: Tue, 19 Sep 2000 01:52:52 -0400
From: Jim Mercer <jim@reptiles.org>
To: nanog@merit.edu
Message-ID: <20000919015251.B1762@reptiles.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Errors-To: owner-nanog-outgoing@merit.edu
ok, this is getting ludicrous.
[ cut to the chase, if you are a non-US uunet/worldcom/mci customer,
you can skip my diatribe and jump down to the bottom ]
this is the third monday night when we have had a major BGP/connectivity
outage with uunet.ca.
two mondays ago, (ie 3 weeks), we had an 11 hour combined outage of either
connectivity and/or BGP routing. this was topped off by them restoring
the config from an old backup, including a slew of old static routes.
last monday we had a 4 hour outage, similar issues.
tonight, we got:
18:30 me -> uunet.ca: so, what's the problem
uunet.ca: not sure, US-NOC is looking into it
19:15 me -> uunet.ca: any ETA?
uunet.ca: problem solved, although the CPU on the router is 100%
due to BGP recalc. should be OK soon.
21:30 me -> uunet.ca: so, what's the problem?
uunet.ca: bad ATM card, been replaced, back up, although the CPU
is 100% due to BGP recalc. should be OK soon.
01:30 me -> uunet.ca: so, what's the problem?
uunet.ca: US-NOC is saving the configs customer-by-customer and
will be rebooting the router RSN. no ETA.
i'm not sure, but a lot of major problems seem to have cropped up since
uunet.ca dumped their local technicians and went dependent on the US-NOC.
are other non-US uunet customers getting the same treatment?
--
[ Jim Mercer jim@reptiles.org +1 416 410-5633 ]
[ Reptilian Research -- Longer Life through Colder Blood ]
[ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ]
