[c-nsp] L3VPN traceroute from ce--->vpn cloud---->ce

[Vinny_Abello at Dell.com]

In my experience and understanding of this based purely on observation, when you run BGP, traceroutes will check the BGP routing table on each hop for a matching route and display that AS number on the hop for the current active route in the BGP table. Since 65111 is a private AS, your CE is likely configured with BGP talking to a PE router which is feeding you matching routes for each hop (or maybe just a simple default route) which is why that AS number shows on each hop.

-Vinny

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Aaron
Sent: Friday, April 20, 2012 2:56 PM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] L3VPN traceroute from ce--->vpn cloud---->ce

What's the deal with the traceroute from CE (cisco device) via mpls l3vpn
showing some strange AS number ?  AS 65111 ?

 

...tracing from ce... so it's  ce--->pe--->p--->p--->pe----ce

 

Ce-router#traceroute 10.101.18.2

Type escape sequence to abort.
Tracing the route to 10.101.18.2

  1 1.2.3.17 0 msec 0 msec 0 msec
  2 10.101.1.34 [AS 65111] [MPLS: Labels 16022/16033 Exp 0] 4 msec 0 msec 4
msec
  3 10.101.1.2 [AS 65111] [MPLS: Labels 16022/16033 Exp 0] 0 msec 0 msec 0
msec
  4 10.101.1.6 [AS 65111] 0 msec 4 msec 0 msec
  5 10.101.18.2 [AS 65111] 0 msec *  0 msec



 

_______________________________________________
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/