[c-nsp] N7K, NX-OS 6.0(2) link-local OSPFv3

[Tim Durack]

On Fri, Mar 23, 2012 at 2:01 PM, Tim Durack <tdurack at gmail.com> wrote:
> Simple link-local OSPFv3 config:

> CORE-2# ping6 2001:DB8:4:1::1
> PING6 2001:DB8:4:1::1 (2001:DB8:4:1::1): 56 data bytes
> ping6: sendto: No route to host
> Request 0 timed out
> ping6: sendto: No route to host
> Request 1 timed out
> ping6: sendto: No route to host
> Request 2 timed out
> ping6: sendto: No route to host
> Request 3 timed out
> ping6: sendto: No route to host
> Request 4 timed out
>
> --- 2001:DB8:4:1::1 ping6 statistics ---
> 5 packets transmitted, 0 packets received, 100.00% packet loss
>
> This works on a 6500/SUP720/12.2(33)SXI, but not an N7K/NX-OS/6.0(2)
> What am I missing?

Turns out NX-OS is using the interface link-local as a source to ping
a unicast destination, even though the router as a host has a unicast
address.

You can force ping6 source:

CORE-1# ping6 2001:DB8:4:2::2 source 2001:DB8:4:1::1
PING6 2001:DB8:4:2::2 (2001:DB8:4:2::2) from 2001:DB8:4:1::1: 56 data bytes
64 bytes from 2001:DB8:4:2::2: icmp_seq=0 time=2.307 ms
64 bytes from 2001:DB8:4:2::2: icmp_seq=1 time=2.094 ms
64 bytes from 2001:DB8:4:2::2: icmp_seq=2 time=1.894 ms
64 bytes from 2001:DB8:4:2::2: icmp_seq=3 time=1.702 ms
64 bytes from 2001:DB8:4:2::2: icmp_seq=4 time=1.678 ms

This is not an obvious change from IOS to NX-OS. I'm also not sure
that this follows rfc3484 "Default Address Selection for Internet
Protocol version 6"

-- 
Tim:>