Traceroute showing own ip address before last hop

hairul_cisco · ‎01-07-2016

Hi,

We recently migrated to N9K configured with vxlan bgp evpn. After migration, I noticed that whenever we performed a traceroute to any host connected to the leaf switch, the client's own ip address will be inserted before the last hop.

Example:

Windows client 192.168.99.10 traceroute to 10.3.4.1

Tracing route to 10.3.4.1 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.99.1 (gateway)
2 2 ms 4 ms 1 ms 10.129.0.3 (Core switch)
3 <1 ms <1 ms <1 ms 10.3.255.51 (leaf switch 1)
4 <1 ms <1 ms <1 ms 192.168.99.10 (own ip address)
5 <1 ms <1 ms <1 ms 10.3.4.1

Trace complete.

Linux client 192.168.99.15 traceroute to 10.3.4.1

traceroute to 10.3.4.1 (10.3.4.1), 30 hops max, 60 byte packets
1 192.168.99.1 (192.168.99.1) 0.397 ms 0.381 ms 0.356 ms
2 10.129.0.3 (10.129.0.3) 0.706 ms 0.753 ms 0.932 ms
3 10.3.255.51 (10.3.255.51) 1.228 ms 1.461 ms 1.644 ms
4 * * *
5 10.3.4.1 (10.3.4.1) 0.898 ms 0.954 ms 1.035 ms

Traffic path:

Client(192.168.99.x)-Gateway-Core Switch-Leaf 1-Spine-Leaf 4-host(10.3.4.1)

Any ideas why?

hairul_cisco · ‎01-11-2016

Calling for cisco gurus to throwing up some ideas.

I did contacted TAC but their reply is not too promising, they just mentioned it's related to MS Windows cosmetic message, which I could not accept it since we only seeing this behavior once we introduced N9k in our network..