This is a discussion on traceroute delays, fails on loopback? - Aix ; I am getting an odd delay on traceroutes on a private connection through a private vlan switch , being used for oracle 10G interconnect. The traceroutes work, but there is a 5-10 second delay in the response. Traceroute -v shows ...
I am getting an odd delay on traceroutes on a private connection
through a private vlan switch , being used for oracle 10G
The traceroutes work, but there is a 5-10 second delay in the
Traceroute -v shows that it is trying the loopback first , failing
multiple times, then returning the good response. Pings are normal
duration, entstats don't show any errors. All the other interfaces on
the cluster behave normally.
Both ip's are in the hosts tables on each box, it doesn't look like a
name resolution issue..behaves the same way with numeric or named
Anyone know what would cause it to hit and fail on 127.0.0.1 first? (
note that a direct traceroute to 127.0.0.1 is ok)
sample output plus partial netstat -r follows. Thanks.
[ROOT:apadb255n1]/# traceroute -v apadb255n2-private
trying to get source for apadb255n2-private
source should be 192.168.248.144
traceroute to apadb255n2-private (192.168.248.145) from 192.168.248.144
(192.168.248.144), 30 hops max
outgoing MTU = 1500
here is the oddity:
36 bytes from 127.0.0.1 to 127.0.0.1: icmp type 3 (Dest Unreachable)
.....etc etc etc...
repeats this about 20 times , then returns the expected response:
apadb255n2-private (192.168.248.145) 36 bytes to 192.168.248.144 0 ms
[ROOT:apadb255n1]/# netstat -r|grep pri
192.168.248.0 apadb255n1-privat UHSb 0 0 en1 -
192.168.248/24 apadb255n1-privat U 201 91357459 en1 -
apadb255n1-priva localhost UGHS 53 39861 lo0 -
192.168.248.255 apadb255n1-privat UHSb 0 4 en1 -