nanog mailing list archives

Re: 3/11 (invalid or corrupt AS path)


From: Dave Israel <davei () otd com>
Date: Mon, 16 Feb 2009 12:03:17 -0500


We're seeing them from AS 48438, coming across to us as an Optional
Transitive Attribute which our force-10s are not parsing (but cheerfully
passing along to our clients, who are then flapping their peers because
of it.)   Sample route; 91.210.248.0/23

Ozar wrote:
I am starting to see random BGP neighbor messages from multiple neighbors on
different boxes.

%BGP-3-NOTIFICATION: received from neighbor X.X.X.X 3/11 (invalid or corrupt
AS path) 516 bytes

I dont see much documentation on this, and we are in the process of opening
a TAC case, just curious if anyone else has seen these and may be able to
shed some light.

Thanks
  


Current thread: