tracert 10.54.64.17 Tracing route to 10.54.64.17 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms switch1.abc.com [10.50.0.1] 2 14 ms 4 ms 8 ms 192.168.77.74 3 5 ms 5 ms 4 ms 192.168.77.122 4 3 ms 3 ms 3 ms 192.168.77.121 5 2 ms 2 ms 2 ms agate.abc.com [10.54.0.254] 6 2 ms 2 ms 2 ms 10.54.64.17 So my machine is able to reach 10.54.64.17, it clearly shows it pass through agate.abc.com[10.54.0.254], but when I ssh into agate.abc.com
ping -I 10.54.0.254 10.54.64.17 PING 10.54.64.17 (10.54.64.17) from 10.54.0.254 : 56(84) bytes of data. to prove ping is working, I try .15 and it's getting response.
# ping -I 10.54.0.254 10.54.64.15 PING 10.54.64.15 (10.54.64.15) from 10.54.0.254 : 56(84) bytes of data. 64 bytes from 10.54.64.15: icmp_seq=1 ttl=64 time=0.120 ms 64 bytes from 10.54.64.15: icmp_seq=2 ttl=64 time=0.050 ms How is this possible? what's going on with the network?
[link] [comments]
