[c-nsp] ipv6 tunnels and static routes

[Mohacsi Janos]

On Thu, 31 Mar 2005, Bernhard Schmidt wrote:

> On 2005-03-31, Pierfrancesco Caci <p.caci at seabone.net> wrote:
>
> [6PE Setup]
>
>> Pings and traceroutes done on the GSR where the tunnel is defined work properly:
> [...]
>> ...while from another router:
>>
>> R_7206A-MI_MM_19#ping 2001:41A8:604::1
>>
>> Type escape sequence to abort.
>> Sending 5, 100-byte ICMP Echos to 2001:41A8:604::1, timeout is 2 seconds:
>> .....
>> Success rate is 0 percent (0/5)
>>
>> R_7206A-MI_MM_19#trace 2001:41A8:604::1
>>
>> Type escape sequence to abort.
>> Tracing the route to 2001:41A8:604::1
>>
>>   1 2001:41A8:600::1E 12 msec 8 msec 12 msec
>>   2  *  *  *
>
> I have never used 6PE so I'm not really sure, but I guess it could be
> connected with the source address selection of your second cisco. Cisco
> chooses the IPv6 address of the egress interface as source address for
> your trace and ping. If the egress interface has no IPv6 address it
> might become confused and use something like mapped addresses and would
> break.
>
> When you enter traceroute without options it will ask you for a source
> address, try using a local address to R_7206A-MI_MM_19 there.
>
> As said, I never used 6PE, but I guess this could be the case here.
>

Traceroute6 might not work (MPLS P routers are not visible in 
traceroute) while there is IPv6 connectivity:
try configuring 'no tag-switching ip propagate-ttl' on PE routers.
Regards,


Janos Mohacsi
Network Engineer, Research Associate
NIIF/HUNGARNET, HUNGARY
Key 00F9AF98: 8645 1312 D249 471B DBAE  21A2 9F52 0D1F 00F9 AF98

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