[98932] in North American Network Operators' Group
Re: 3561 policy meltdown overnight?
daemon@ATHENA.MIT.EDU (Jared Mauch)
Sat Aug 25 13:43:08 2007
Date: Sat, 25 Aug 2007 13:30:35 -0400
From: Jared Mauch <jared@puck.nether.net>
To: Eric Spaeth <eric@spaethco.com>
Cc: nanog@merit.edu
In-Reply-To: <46D0604E.8010502@spaethco.com>
Errors-To: owner-nanog@merit.edu
On Sat, Aug 25, 2007 at 12:01:02PM -0500, Eric Spaeth wrote:
>
> LayeredTech operates out of both the Savvis and Databank facilities in
> the DFW area -- many customers on their Savvis network were hit hard.
>
> "We are currently experiencing issues upstream from our Savvis IDC.
> Savvis was performing un-scheduled maintainence on a backbone devices
> which has caused a peering issue and sever or 100% packet loss for most
> hosts on the Savvis network."
>
> Source:
> http://ltstatus.com/index.php/2007/08/25/savvis-idc-networking-issues-backbone-routers-failure/
Yeah, interesting.. I'm still seeing routing leaks coming out
of 3561 right now, leaking of level3 routes to sprint (for example). i'm
not measuring the duration of the leak, just that it was sent and
accepted enough to show up in route-views.
http://puck.nether.net/bgp/leakinfo.cgi?search=do&search_aspath=3356+3561+1239&recent=25
My scripts don't pick up "all" of the updates files that
are available from routeviews, just the most recent one. I suspect
the entire dataset might show a larger set of information. Maybe i'll
work on making my script more robust in that fashion next.
- Jared
--
Jared Mauch | pgp key available via finger from jared@puck.nether.net
clue++; | http://puck.nether.net/~jared/ My statements are only mine.
