[166441] in North American Network Operators' Group
Re: BGP failure analysis and recommendations
daemon@ATHENA.MIT.EDU (Courtney Smith)
Thu Oct 24 22:19:03 2013
From: Courtney Smith <courtneysmith@comcast.net>
Date: Thu, 24 Oct 2013 22:18:49 -0400
In-Reply-To: <mailman.3549.1382595181.1246.nanog@nanog.org>
To: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Oct 24, 2013, at 2:13 AM, nanog-request@nanog.org wrote:
> Message: 7
> Date: Wed, 23 Oct 2013 22:40:34 -0400
> From: JRC NOC <nospam-nanog@jensenresearch.com>
> To: nanog@nanog.org
> Subject: BGP failure analysis and recommendations
> Message-ID:
> <5.1.0.14.0.20131023214304.0396ead0@authsmtp.jensenresearch.com>
> Content-Type: text/plain; charset=3D"us-ascii"; format=3Dflowed
>=20
> Hello Nanog -
>=20
> On Saturday, October 19th at about 13:00 UTC we experienced an IP =
failure=20
> at one of our sites in the New York area.
> It was apparently a widespread outage on the East coast, but I haven't =
seen=20
> it discussed here.
>=20
> We are multihomed, using EBGP to three (diverse) upstream providers. =
One=20
> provider experienced a hardware failure in a core component at one =
POP.
> Regrettably, during the outage our BGP session remained active and we=20=
> continued receiving full routes from the affected AS. And our =
prefixes=20
> continued to be advertised at their border. However basically none of =
the=20
> traffic between those prefixes over that provider was delivered. The =
bogus=20
> routes stayed up for hours. We shutdown the BGP peering session when =
the=20
> nature of the problem became clear. This was effective. I believe that =
all=20
> customer BGP routes were similarly affected, including those belonging =
to=20
> some large regional networks and corporations. I have raised the =
questions=20
> below with the provider but haven't received any information or =
advice.
>=20
>=20
Did you provider provide an official written RFO yet? =20
Courtney Smith
courtneysmith@comcast.net
() ascii ribbon campaign - against html e-mail=20
/\ www.asciiribbon.org - against proprietary attachments
