[c-nsp] Incorrect ASN in Traceroute
Paul Stewart
paul at paulstewart.org
Wed Aug 7 14:17:46 EDT 2013
Hehe sorry for the flashbacks ;)
In this particular instance, we had a BGP peer that was slipping us a
default route. That route was actually making it into the BGP tables
locally (but not chosen as best route thankfully!). Guess I need to look
at tighter filtering again geesh.
So with the default route in the BGP tables, when the 7200 was doing an
ASN lookup for local addresses it was matching 0.0.0.0/0 from BGP and
associating that to their ASN.
Cheers,
Paul
On 2013-08-07 12:27 PM, "Mark Tinka" <mark.tinka at seacom.mu> wrote:
>On Wednesday, August 07, 2013 05:45:25 PM Paul Stewart
>wrote:
>
>> Found the issue - sorry for the noise
>
>Funny you should mention this.
>
>When 12.2(33)SRC first launched for the 7200, I uncovered a
>bug where IPv6 traceroutes would display AT&T's AS2686 in
>the path as a local ASN.
>
>I don't actually recall ever having this issue fixed by
>Cisco, but it disappeared after an upgrade.
>
>This was so weird.
>
>Mark.
More information about the cisco-nsp
mailing list