-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 %BGP-6-ASPATH: Invalid AS path xxx 3300 (64603) 2008 received from x.x.x.x: Confederation AS-path found in the middle provider x'd out to protect the innocent, but saw this from ALL ebgp peers. Thankfully our main vendor included a knob to emulate cisco's brokenness, so we magically stayed up. Regards, Matt - -- Matt Levine @Home: matt@deliver3.com @Work: matt@eldosales.com ICQ : 17080004 PGP : http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6C0D04CF "The Trouble with doing anything right the first time is that nobody appreciates how difficult it was." - -----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of cowie@renesys.com Sent: Sunday, October 07, 2001 7:37 PM To: nanog@merit.edu Cc: cowie@renesys.com Subject: BGP noise tonight? Say, our alarms went off tonight when we saw a roughly tenfold spike in BGP prefix announcement and withdrawal rates at RIPE's rrc00 and rrc03 collection points in Amsterdam. The trouble started around 20:00 GMT, hit its peak by about 21:00 GMT, and has trailed off slowly since then. Looking at the worst-behaved prefixes and AS paths led me to put in a call to the tech support center of an unnamed Major Provider, who confirmed that there had been a major BGP event but would provide no specifics. So, what's going on out there in the NOCs tonight? Inquiring minds want to know. --jim -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com> iQA/AwUBO8EqQMp0j1NsDQTPEQI33gCdFsTtzmzUJTBg0e0Hzr+S2fiYhIIAoJV2 WEflgOelB1Ym7Luw0pWVP329 =4pos -----END PGP SIGNATURE-----