[j-nsp] traceroute in mpls vpn's not showing P hops
Shamen Snyder
shamen.snyder at gmail.com
Thu Aug 24 10:24:51 EDT 2017
Are you setting icmp-tunneling on all the routers? It be helpful to see
your configuration.
On Thu, Aug 24, 2017 at 7:44 AM, Aaron Gould <aaron1 at gvtc.com> wrote:
> I removed all rsvp and label-switched-path configs for a moment… then with
> only mpls l3vpn configs, I turned on the icmp-tunneling. Still don’t see p
> hops on traceroute
>
>
>
> r1 at lab-mx104:r1> traceroute 1.1.10.2 wait 1
>
> traceroute to 1.1.10.2 (1.1.10.2), 30 hops max, 40 byte packets
>
> 1 1.1.0.2 (1.1.0.2) 0.469 ms 0.401 ms 0.366 ms
>
> 2 * * *
>
> 3 * * *
>
> 4 1.1.10.1 (1.1.10.1) 0.648 ms 0.583 ms 0.500 ms
>
> 5 1.1.10.2 (1.1.10.2) 0.647 ms 0.653 ms 0.541 ms
>
>
>
> On ingress pe, I did this “set protocols mpls no-propagate-ttl”
>
>
>
> r1 at lab-mx104:r1> traceroute 1.1.10.2 wait 1
>
> traceroute to 1.1.10.2 (1.1.10.2), 30 hops max, 40 byte packets
>
> 1 1.1.0.2 (1.1.0.2) 0.458 ms 0.402 ms 0.414 ms
>
> 2 1.1.10.1 (1.1.10.1) 0.497 ms 0.413 ms 0.455 ms
>
> 3 1.1.10.2 (1.1.10.2) 0.646 ms 0.641 ms 0.669 ms
>
>
>
> This is all inside one mx104 running about 9 logical-systems.
>
>
>
> -Aaron
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
More information about the juniper-nsp
mailing list