No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

An Incorrect ping Command Is Used

Publication Date:  2015-06-19 Views:  46 Downloads:  0
Issue Description
Hardware configuration:
Twelve 1 TB hard disks, one LSISAS1068E controller card, and hard disks in slots 0 and 1 configured with RAID 1

Software configuration:
SUSE11 SP1 64-bit

Symptom:

After the ping 192.168.3.100 –i 192.168.3.10 command is executed on the server operating system (OS), the response packet is received after 3 minutes, as shown in Figure 1.

Figure 1 Ping response packet cannot be received shortly


Handling Process
Syntax: ping [-dfnqrRv][-c<number of completion times>][-i<interval in seconds>][-I<network UI>][-l<preset loading>][-p<example format>][-s<packet size>][-t<TTL value>][host name or IP address]

NOTE:
The ping uses the Internet Control Message Protocol (ICMP) to send a message that will be sent back as a response. If a remote host sends back the message as the response, the host runs normally.

Parameters in the command are described as follows:

-d: uses the socket SO_DEBUG function.

-c<number of completion times>: sets the number of required responses.

-f: detects the limit.

-i<interval in seconds>: specifies the interval between sending and receiving packets.

-I<network UI>: uses the specified network user interface (UI) to send packets.

-l<preset loading>: specifies the packets sent before the required packets are sent.

-n: outputs values only.

-p<example format>: sets the example format to fill a packet.

-q: displays only summary lines at startup time and when finished.

-r: disregards normal routing tables and sends packets directly to a remote host.

-R: records the routing process.

-s<packet size>: sets the packet size.

-t<TTL value>: sets the time to live (TTL) value.

-v displays the command execution process in details.


In conclusion, the customer can use the ping 192.168.3.100 –I 192.168.3.10 command for testing. Figure 2 shows the command output.

Figure 2 ping packet testing

Root Cause
A parameter in the ping command is incorrect. The ping 192.168.3.100 –I 192.168.3.10 command instead of the ping 192.168.3.100 –i 192.168.3.10 command needs to be used.

Solution
Run the ping 192.168.3.100 –I 192.168.3.10 command.

END