Fortinet Document Library

Version:


Table of Contents

6.2.3
Download PDF
Copy Link

execute ping

This command runs a ping request to a host by specifying its IPv4 address. Pings are often used to test IP-layer connectivity during troubleshooting.

Syntax

Execute ping <IPADDRESS>

Example

This example pings a host with the IP address 192.0.2.10.

execute ping 192.0.2.10

The CLI displays the following:

PING 192.0.2.10 (192.0.2.10): 56 data bytes
64 bytes from 192.0.2.10: icmp_seq=0 ttl=128 time=0.5 ms
64 bytes from 192.0.2.10: icmp_seq=1 ttl=128 time=0.2 ms
64 bytes from 192.0.2.10: icmp_seq=2 ttl=128 time=0.2 ms
64 bytes from 192.0.2.10: icmp_seq=3 ttl=128 time=0.2 ms
64 bytes from 192.0.2.10: icmp_seq=4 ttl=128 time=0.2 ms

--- 192.0.2.10 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.2/0.2/0.5 ms

The results indicate that a route exists between the FortiWeb Manager and 192.0.2.10. It also indicates that during the sample period, there was no packet loss, and the average response time was 0.2 milliseconds.

execute ping

This command runs a ping request to a host by specifying its IPv4 address. Pings are often used to test IP-layer connectivity during troubleshooting.

Syntax

Execute ping <IPADDRESS>

Example

This example pings a host with the IP address 192.0.2.10.

execute ping 192.0.2.10

The CLI displays the following:

PING 192.0.2.10 (192.0.2.10): 56 data bytes
64 bytes from 192.0.2.10: icmp_seq=0 ttl=128 time=0.5 ms
64 bytes from 192.0.2.10: icmp_seq=1 ttl=128 time=0.2 ms
64 bytes from 192.0.2.10: icmp_seq=2 ttl=128 time=0.2 ms
64 bytes from 192.0.2.10: icmp_seq=3 ttl=128 time=0.2 ms
64 bytes from 192.0.2.10: icmp_seq=4 ttl=128 time=0.2 ms

--- 192.0.2.10 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.2/0.2/0.5 ms

The results indicate that a route exists between the FortiWeb Manager and 192.0.2.10. It also indicates that during the sample period, there was no packet loss, and the average response time was 0.2 milliseconds.