Ping On Symantec Director Takes About a Minute To Respond
Article ID: 166761
Updated On:
Products
Issue/Introduction
Ping on Symantec Director takes about a minute to start responding.
Resolution
Director will try to do a reverse DNS (RDNS) look-up so it can display the hostname of the IP it's trying to ping. If the DNS server does not respond to the RDNS query, this will result in a delay in the ICMP request/response display. Below is a sample of the behavior and what can be seen on the packet capture taken from Director.
director # ping 10.150.1.50
(((delay of response)))
PING 10.150.1.50 (10.150.1.50): 56 data bytes
64 bytes from 10.150.1.50: icmp_seq=0 ttl=123 time=347.995 ms
64 bytes from 10.150.1.50: icmp_seq=1 ttl=123 time=93.107 ms
64 bytes from 10.150.1.50: icmp_seq=2 ttl=123 time=428.768 ms
64 bytes from 10.150.1.50: icmp_seq=3 ttl=123 time=241.038 ms
64 bytes from 10.150.1.50: icmp_seq=4 ttl=123 time=226.852 ms
64 bytes from 10.150.1.50: icmp_seq=5 ttl=123 time=273.100 ms
64 bytes from 10.150.1.50: icmp_seq=6 ttl=123 time=274.450 ms
^C
----10.150.1.50 PING Statistics----
7 packets transmitted, 7 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 93.107/269.330/428.768/104.330 ms
director #
director #
No. Time Source Destination Protocol Info
1977 92.996858 10.78.3.5 10.2.2.104 DNS Standard query PTR 50.1.150.10.in-addr.arpa
2052 97.999232 10.78.3.5 10.2.2.104 DNS Standard query PTR 50.1.150.10.in-addr.arpa
2218 108.009258 10.78.3.5 10.2.2.104 DNS Standard query PTR 50.1.150.10.in-addr.arpa
3924 128.019258 10.78.3.5 10.2.2.104 DNS Standard query PTR 50.1.150.10.in-addr.arpa
4544 168.029541 10.78.3.5 10.150.1.50 ICMP Echo (ping) request
4560 168.377415 10.150.1.50 10.78.3.5 ICMP Echo (ping) reply
4566 169.039177 10.78.3.5 10.150.1.50 ICMP Echo (ping) request
4567 169.132194 10.150.1.50 10.78.3.5 ICMP Echo (ping) reply
*********truncated*************
Feedback
