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
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
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
(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
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
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
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
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
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:
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
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.
___
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,
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.
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:
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
15 matches
Mail list logo
