Re: [c-nsp] 3/11 (invalid or corrupt AS path)
Hi List,
Read this useful blog entry,
*http://www.renesys.com/blog/2009/02/the-flap-heard-around-the-worl.shtml*
It does not present a solution, but explains the cause in detail.
--
Regards,
M Usman Ashraf
On Wed, Feb 18, 2009 at 1:15 AM, Rodney Dunn rod...@cisco.com wrote:
Here is my update to NANOG...
I'll post again once I have a further update.
Date: Tue, 17 Feb 2009 15:11:57 -0500
From: Rodney Dunn rod...@cisco.com
To: Ivan Pepelnjak i...@ioshints.info
Subject: Re: anyone else seeing very long AS paths?
Cc: na...@nanog.org
Ivan,
It is confusing but from what I have tested you have it correct.
The confusing part comes from multiple issues.
a) The documentation about the default maxas limit being 75 appears to be
incorrect. I'll get that fixed.
b) Prior to CSCee30718 there was a hard limit of 255. After that fix
AS sets of more than 255 should work.
c) CSCeh13489 implemented the maxas command to mark it as invalid and
not send.
There does appear to be an issue when you cross the 255 boundary
and the next hop router sends a notification back.
I've got it recreated in the lab and we are working to clearly understand
why that is. I'll post an update once we have more.
The way to prevent it is the upstream device that crosses the 255 boundary
on sending needs to use the maxas limit command to keep it less than 255.
It doesn't work on the device that receives the update with the AS path
larger than 255.
Rodney
-=-
On Mon, Feb 16, 2009 at 03:32:11PM -0500, Rodney Dunn wrote:
We are working on that. I'll let you know once I have more.
Rodney
On Tue, Feb 17, 2009 at 12:41:34AM +0500, M Usman Ashraf wrote:
Hi List,
We have just experience the same problem on SRC but with a different
reason,
%BGP-3-NOTIFICATION: sent to neighbor X.X.X.X 3/11 (invalid or corrupt
AS path)
518 bytes 50020202 02009531 23012306 71B9BAFC BA
23w4d: BGP: X.X.X.X Bad attributes
Feb 16 21:26:04.918 pst: %BGP-4-MSGDUMP: unsupported or mal-formatted
message
received from X.X.X.X:
022C 0200 0002 1140 0101 0050
0202 0202
0095 3123 0123 0671 B9BA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA
FCBA FCBA
FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA
FCBA FCBA
FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA
FCBA FCBA
FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA
FCBA FCBA
FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA
FCBA FCBA
FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA
FCBA
FCBA--
Any idea of reason? or what can be a bad message for BGP that can tear
down
adjacency ?
Regards,
M Usman Ashraf
On Tue, Feb 17, 2009 at 12:07 AM, Rodney Dunn rod...@cisco.com
wrote:
That would have to be *real* old code.
That was fixed back in the 12.1(4)
and 12.0(10)S3 days.
On Mon, Feb 16, 2009 at 01:25:32PM -0500, Tim Donahue wrote:
Joe Provo wrote:
On Mon, Feb 16, 2009 at 06:14:08PM +0100, Grzegorz Janoszka
wrote:
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
[snip]
No, it is not software error, it is extremly long as-path:
The message itself, correct. The flapping sessions observed on
some
code, the long path is indeed triggering some bug. It is
immaterial
if it is the revival of an ld bug or a new one, there are folks
flapping over this (and related) paths. Providers without some
level
of sanity filters (really need many-multiples the current
diameter of
the net?) should be shamed into limiting their customer's
prepends.
According to the NANOG thread on this, it would seem that the bug
would
be CSCdr54230.
Tim
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] 3/11 (invalid or corrupt AS path)
Here is my update to NANOG...
I'll post again once I have a further update.
Date: Tue, 17 Feb 2009 15:11:57 -0500
From: Rodney Dunn rod...@cisco.com
To: Ivan Pepelnjak i...@ioshints.info
Subject: Re: anyone else seeing very long AS paths?
Cc: na...@nanog.org
Ivan,
It is confusing but from what I have tested you have it correct.
The confusing part comes from multiple issues.
a) The documentation about the default maxas limit being 75 appears to be
incorrect. I'll get that fixed.
b) Prior to CSCee30718 there was a hard limit of 255. After that fix
AS sets of more than 255 should work.
c) CSCeh13489 implemented the maxas command to mark it as invalid and
not send.
There does appear to be an issue when you cross the 255 boundary
and the next hop router sends a notification back.
I've got it recreated in the lab and we are working to clearly understand
why that is. I'll post an update once we have more.
The way to prevent it is the upstream device that crosses the 255 boundary
on sending needs to use the maxas limit command to keep it less than 255.
It doesn't work on the device that receives the update with the AS path
larger than 255.
Rodney
-=-
On Mon, Feb 16, 2009 at 03:32:11PM -0500, Rodney Dunn wrote:
We are working on that. I'll let you know once I have more.
Rodney
On Tue, Feb 17, 2009 at 12:41:34AM +0500, M Usman Ashraf wrote:
Hi List,
We have just experience the same problem on SRC but with a different reason,
%BGP-3-NOTIFICATION: sent to neighbor X.X.X.X 3/11 (invalid or corrupt AS
path)
518 bytes 50020202 02009531 23012306 71B9BAFC BA
23w4d: BGP: X.X.X.X Bad attributes
Feb 16 21:26:04.918 pst: %BGP-4-MSGDUMP: unsupported or mal-formatted
message
received from X.X.X.X:
022C 0200 0002 1140 0101 0050 0202
0202
0095 3123 0123 0671 B9BA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA
FCBA
FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA
FCBA
FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA
FCBA
FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA
FCBA
FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA
FCBA
FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA
FCBA--
Any idea of reason? or what can be a bad message for BGP that can tear down
adjacency ?
Regards,
M Usman Ashraf
On Tue, Feb 17, 2009 at 12:07 AM, Rodney Dunn rod...@cisco.com wrote:
That would have to be *real* old code.
That was fixed back in the 12.1(4)
and 12.0(10)S3 days.
On Mon, Feb 16, 2009 at 01:25:32PM -0500, Tim Donahue wrote:
Joe Provo wrote:
On Mon, Feb 16, 2009 at 06:14:08PM +0100, Grzegorz Janoszka wrote:
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
[snip]
No, it is not software error, it is extremly long as-path:
Re: [c-nsp] 3/11 (invalid or corrupt AS path)
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. No, it is not software error, it is extremly long as-path: AS path: 3356 29113 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 I -- Grzegorz Janoszka ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] 3/11 (invalid or corrupt AS path)
(Forgot to CC c-nsp) Someone is advertising a block with insane long prepend. We added it to our filter list and it seems most providers have filtered out that route by now. Our 28xx decided to flip out with IBGP. IOS 12.4(21). Is this a bug? Is there a bugID on this or a workaround to filter insane route? Can I filter prefix by how big it is? It's this route. #sh ip bgp 94.125.216.0 BGP routing table entry for 94.125.216.0/21, version 92436 Paths: (2 available, best #1, table Default-IP-Routing-Table) Flag: 0x820 Not advertised to any peer x.x.x.x from y.y.y.y (z.z.z.z) Origin IGP, metric 10, localpref 100, valid, external, best Community: 13697912 13697913 209 1299 29113 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 4 On Mon, Feb 16, 2009 at 11:55 AM, Ozar vegasnet...@gmail.com 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 ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] 3/11 (invalid or corrupt AS path)
On Mon, Feb 16, 2009 at 06:14:08PM +0100, Grzegorz Janoszka wrote: 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 [snip] No, it is not software error, it is extremly long as-path: The message itself, correct. The flapping sessions observed on some code, the long path is indeed triggering some bug. It is immaterial if it is the revival of an ld bug or a new one, there are folks flapping over this (and related) paths. Providers without some level of sanity filters (really need many-multiples the current diameter of the net?) should be shamed into limiting their customer's prepends. -- RSUC / GweepNet / Spunk / FnB / Usenix / SAGE ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] 3/11 (invalid or corrupt AS path)
Hello, I have spoken with AS29113 admin and they will fix( block or what ) issue with their customer AS47868 Regards Tomas Jay Nakamura wrote: (Forgot to CC c-nsp) Someone is advertising a block with insane long prepend. We added it to our filter list and it seems most providers have filtered out that route by now. Our 28xx decided to flip out with IBGP. IOS 12.4(21). Is this a bug? Is there a bugID on this or a workaround to filter insane route? Can I filter prefix by how big it is? It's this route. #sh ip bgp 94.125.216.0 BGP routing table entry for 94.125.216.0/21, version 92436 Paths: (2 available, best #1, table Default-IP-Routing-Table) Flag: 0x820 Not advertised to any peer x.x.x.x from y.y.y.y (z.z.z.z) Origin IGP, metric 10, localpref 100, valid, external, best Community: 13697912 13697913 209 1299 29113 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 47868 4 On Mon, Feb 16, 2009 at 11:55 AM, Ozar vegasnet...@gmail.com 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 ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] 3/11 (invalid or corrupt AS path)
Joe Provo wrote: On Mon, Feb 16, 2009 at 06:14:08PM +0100, Grzegorz Janoszka wrote: 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 [snip] No, it is not software error, it is extremly long as-path: The message itself, correct. The flapping sessions observed on some code, the long path is indeed triggering some bug. It is immaterial if it is the revival of an ld bug or a new one, there are folks flapping over this (and related) paths. Providers without some level of sanity filters (really need many-multiples the current diameter of the net?) should be shamed into limiting their customer's prepends. According to the NANOG thread on this, it would seem that the bug would be CSCdr54230. Tim ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] 3/11 (invalid or corrupt AS path)
That would have to be *real* old code. That was fixed back in the 12.1(4) and 12.0(10)S3 days. On Mon, Feb 16, 2009 at 01:25:32PM -0500, Tim Donahue wrote: Joe Provo wrote: On Mon, Feb 16, 2009 at 06:14:08PM +0100, Grzegorz Janoszka wrote: 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 [snip] No, it is not software error, it is extremly long as-path: The message itself, correct. The flapping sessions observed on some code, the long path is indeed triggering some bug. It is immaterial if it is the revival of an ld bug or a new one, there are folks flapping over this (and related) paths. Providers without some level of sanity filters (really need many-multiples the current diameter of the net?) should be shamed into limiting their customer's prepends. According to the NANOG thread on this, it would seem that the bug would be CSCdr54230. Tim ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] 3/11 (invalid or corrupt AS path)
Hi List,
We have just experience the same problem on SRC but with a different reason,
%BGP-3-NOTIFICATION: sent to neighbor X.X.X.X 3/11 (invalid or corrupt AS
path) 518 bytes 50020202 02009531 23012306 71B9BAFC BA
23w4d: BGP: X.X.X.X Bad attributes
Feb 16 21:26:04.918 pst: %BGP-4-MSGDUMP: unsupported or mal-formatted
message received from X.X.X.X:
022C 0200 0002 1140 0101 0050 0202
0202
0095 3123 0123 0671 B9BA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA
FCBA
FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA
FCBA
FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA
FCBA
FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA
FCBA
FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA
FCBA
FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA
FCBA--
Any idea of reason? or what can be a bad message for BGP that can tear down
adjacency ?
Regards,
M Usman Ashraf
On Tue, Feb 17, 2009 at 12:07 AM, Rodney Dunn rod...@cisco.com wrote:
That would have to be *real* old code.
That was fixed back in the 12.1(4)
and 12.0(10)S3 days.
On Mon, Feb 16, 2009 at 01:25:32PM -0500, Tim Donahue wrote:
Joe Provo wrote:
On Mon, Feb 16, 2009 at 06:14:08PM +0100, Grzegorz Janoszka wrote:
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
[snip]
No, it is not software error, it is extremly long as-path:
The message itself, correct. The flapping sessions observed on some
code, the long path is indeed triggering some bug. It is immaterial
if it is the revival of an ld bug or a new one, there are folks
flapping over this (and related) paths. Providers without some level
of sanity filters (really need many-multiples the current diameter of
the net?) should be shamed into limiting their customer's prepends.
According to the NANOG thread on this, it would seem that the bug would
be CSCdr54230.
Tim
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] 3/11 (invalid or corrupt AS path)
We are working on that. I'll let you know once I have more.
Rodney
On Tue, Feb 17, 2009 at 12:41:34AM +0500, M Usman Ashraf wrote:
Hi List,
We have just experience the same problem on SRC but with a different reason,
%BGP-3-NOTIFICATION: sent to neighbor X.X.X.X 3/11 (invalid or corrupt AS
path)
518 bytes 50020202 02009531 23012306 71B9BAFC BA
23w4d: BGP: X.X.X.X Bad attributes
Feb 16 21:26:04.918 pst: %BGP-4-MSGDUMP: unsupported or mal-formatted message
received from X.X.X.X:
022C 0200 0002 1140 0101 0050 0202
0202
0095 3123 0123 0671 B9BA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA
FCBA
FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA
FCBA
FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA
FCBA
FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA
FCBA
FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA
FCBA
FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA FCBA
FCBA--
Any idea of reason? or what can be a bad message for BGP that can tear down
adjacency ?
Regards,
M Usman Ashraf
On Tue, Feb 17, 2009 at 12:07 AM, Rodney Dunn rod...@cisco.com wrote:
That would have to be *real* old code.
That was fixed back in the 12.1(4)
and 12.0(10)S3 days.
On Mon, Feb 16, 2009 at 01:25:32PM -0500, Tim Donahue wrote:
Joe Provo wrote:
On Mon, Feb 16, 2009 at 06:14:08PM +0100, Grzegorz Janoszka wrote:
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
[snip]
No, it is not software error, it is extremly long as-path:
The message itself, correct. The flapping sessions observed on some
code, the long path is indeed triggering some bug. It is immaterial
if it is the revival of an ld bug or a new one, there are folks
flapping over this (and related) paths. Providers without some level
of sanity filters (really need many-multiples the current diameter of
the net?) should be shamed into limiting their customer's prepends.
According to the NANOG thread on this, it would seem that the bug would
be CSCdr54230.
Tim
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] 3/11 (invalid or corrupt AS path)
On Mon, Feb 16, 2009 at 20:32, Rodney Dunn rod...@cisco.com wrote: We are working on that. I'll let you know once I have more. We've got one of these on our node running SRB3. It was trigerred on only one session when being announced to a customer. ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] 3/11 (invalid or corrupt AS path)
One of those what? All I want is: sh ver sh log sh ip bgp nei on a box that SENT the BGP notification on receipt of the update. Don't send it if the BGP session when down because the notification was received. rodney On Mon, Feb 16, 2009 at 09:00:02PM +, Marko Milivojevic wrote: On Mon, Feb 16, 2009 at 20:32, Rodney Dunn rod...@cisco.com wrote: We are working on that. I'll let you know once I have more. We've got one of these on our node running SRB3. It was trigerred on only one session when being announced to a customer. ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] 3/11 (invalid or corrupt AS path)
I don't know if it's related or not but one of my borders and another nearly identical box much further into the network logged these with 18 seconds of each other: Feb 16 10:23:38 10.64.0.1 968577: 968585: Feb 16 10:23:37 CST: %BGP-6-BIGCHUNK: Big chunk pool request (522) for aspath. Replenishing with malloc Both are running 12.4(15)Tn releases. Justin Rodney Dunn wrote: One of those what? All I want is: sh ver sh log sh ip bgp nei on a box that SENT the BGP notification on receipt of the update. Don't send it if the BGP session when down because the notification was received. rodney On Mon, Feb 16, 2009 at 09:00:02PM +, Marko Milivojevic wrote: On Mon, Feb 16, 2009 at 20:32, Rodney Dunn rod...@cisco.com wrote: We are working on that. I'll let you know once I have more. We've got one of these on our node running SRB3. It was trigerred on only one session when being announced to a customer. ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] 3/11 (invalid or corrupt AS path)
On Mon, Feb 16, 2009 at 03:45:29PM -0600, Justin Shore wrote: I don't know if it's related or not but one of my borders and another nearly identical box much further into the network logged these with 18 seconds of each other: Feb 16 10:23:38 10.64.0.1 968577: 968585: Feb 16 10:23:37 CST: %BGP-6-BIGCHUNK: Big chunk pool request (522) for aspath. Replenishing with malloc Related, but that's just an informational I've had to go and do a rather unexpectedly large request for memory, but I have, just thought I would mention it message. -- Euan Galloway ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] 3/11 (invalid or corrupt AS path)
That's fine. It just means we fell back to malloc a block that could hold it. On Mon, Feb 16, 2009 at 03:45:29PM -0600, Justin Shore wrote: I don't know if it's related or not but one of my borders and another nearly identical box much further into the network logged these with 18 seconds of each other: Feb 16 10:23:38 10.64.0.1 968577: 968585: Feb 16 10:23:37 CST: %BGP-6-BIGCHUNK: Big chunk pool request (522) for aspath. Replenishing with malloc Both are running 12.4(15)Tn releases. Justin Rodney Dunn wrote: One of those what? All I want is: sh ver sh log sh ip bgp nei on a box that SENT the BGP notification on receipt of the update. Don't send it if the BGP session when down because the notification was received. rodney On Mon, Feb 16, 2009 at 09:00:02PM +, Marko Milivojevic wrote: On Mon, Feb 16, 2009 at 20:32, Rodney Dunn rod...@cisco.com wrote: We are working on that. I'll let you know once I have more. We've got one of these on our node running SRB3. It was trigerred on only one session when being announced to a customer. ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
