[Prev][Report an Error]

Sample Task—Ping Host

Figure 68 shows a sample Ping Host page. In this example, you are sending ping requests are sent to two destination hosts—10.10.2.2 and 2.2.2.2. The echo requests reaches 10.10.2.2 and does not reach 2.2.2.2.

To ping the host:

  1. Select Diagnose>Ping Host from the task bar.
  2. Next to Advanced options, click the expand icon (see Figure 68).
  3. Next to Remote Host, typ 10.10.2.2 to specify the host's IP address.
  4. Retain the default values in the following fields:
  5. Click Start.
  6. Repeat Steps 2 through 5 to ping destination host 2.2.2.2.

Figure 68: Ping Host Diagnose Page

Ping Host Diagnose Page

Figure 69 displays the results of a successful ping in the main pane, and Table 263 provides a summary of the ping host results and output.

Figure 69: Successful Ping Host Results Page

Successful Ping Host Results
Page

Table 263: J-Web Ping Host Results and Output Summary

Ping Host Result

Description

64 bytes from

Size of ping response packet, which is equal to the default value in the Packet Size box (56), plus 8.

10.10.2.2

IP address of the destination host that sent the ping response packet.

icmp_seq=number

Sequence numbers of packets from 0 through 9. You can use this value to match the ping response to the corresponding ping request.

ttl=56

Time-to-live hop-count value of the ping response packet.

100.834 ms

Total time between the sending of the ping request packet and the receiving of the ping response packet, in milliseconds. This value is also called round-trip time.

10 packets transmitted, 10 packets received, 0% packet loss

Ping packets transmitted, received, and lost. 10 ping requests (probes) were sent to the host, and 10 ping responses were received from the host. No packets were lost.

100.215/104.397/120.158/7.831 ms

  • 100.215—Minimum round-trip time
  • 104.397—Average round-trip time
  • 120.158—Maximum round-trip time
  • 7.831—Standard deviation of the round-trip times
  • ms—milliseconds

Figure 70 shows the output of an unsuccessful ping. There can be different reasons for an unsuccessful ping. This result shows that the local router did not have a route to the host 2.2.2.2 and thus could not reach it.

Figure 70: Unsuccessful Ping Host Results Page

Unsuccessful Ping Host
Results Page


[Prev][Report an Error]