[c-nsp] 3/11 (invalid or corrupt AS path)
Tomas Caslavsky
tomas at caslavsky.cz
Mon Feb 16 13:07:01 EST 2009
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 <vegasnetman at 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 at 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 at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
More information about the cisco-nsp
mailing list