cancel
Showing results for 
Search instead for 
Did you mean: 

Traceroute

Clay_Chappell
Occasional Advisor

Traceroute

I get a strange result when performing a traceroute from all NICs on one particular segment to all NICs on another particular segment:
traceroute to sys31729 (10.10.52.113), 30 hops max, 40 byte packets
1 sys31729 (10.10.52.113) 0.869 ms 0.730 ms 0.706 ms
2 sys31729 (10.10.52.113) 0.784 ms 0.766 ms 0.758 ms
3 sys31729 (10.10.52.113) 0.835 ms 0.775 ms 0.786 ms
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
.
.
.
timeout

Works fine going the other way though:
C:\>tracert ftuxps04

Tracing route to ftuxps04 [10.102.8.23]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.10.52.2
2 <1 ms <1 ms <1 ms 10.14.0.1
3 <1 ms <1 ms <1 ms 10.14.11.2
4 <1 ms <1 ms <1 ms ftuxps04 [10.102.8.23]

This effects all NICs going from segment A to segment B only. Works fine between all other segments and from B to A
3 REPLIES
Laurent Menase
Honored Contributor

Re: Traceroute

are there mutiple interfaces configure on your system?

traceroute take the first one by default without looking at the routing table.

so you need to be sure to specify the right local address/interface

else only network trace may help you
Clay_Chappell
Occasional Advisor

Re: Traceroute

All servers have the same network config: two NICs configured into an Auto Port Aggregate. There is only one IP per server. All servers on several segments are all the same. Only all servers on this one segment have this issue. Our network folks claim there is nothing different with the switch. I think differently.
Laurent Menase
Honored Contributor

Re: Traceroute

so meas that the routers don't answer to the request.