Fortinet black logo

CLI reference

execute ping

execute ping

Use this command to perform an ICMP ECHO request (a ping) to a host by specifying its FQDN or IP address.

Syntax

execute ping {<fqdn_str> | <host_ipv4>}

Variable

Description

Default

ping {<fqdn_str> | <host_ipv4>}

IP address or FQDN of the host.

Example 1

execute ping 172.16.1.10

The CLI displays the following:

PING 172.16.1.10 (172.16.1.10): 56 data bytes

64 bytes from 172.16.1.10: icmp_seq=0 ttl=128 time=0.5 ms

64 bytes from 172.16.1.10: icmp_seq=1 ttl=128 time=0.2 ms

64 bytes from 172.16.1.10: icmp_seq=2 ttl=128 time=0.2 ms

64 bytes from 172.16.1.10: icmp_seq=3 ttl=128 time=0.2 ms

64 bytes from 172.16.1.10: icmp_seq=4 ttl=128 time=0.2 ms

--- 172.16.1.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 of the ping indicate that a route exists between FortiWeb and 172.16.1.10. It also indicates that during the sample period, there was no packet loss and the average response time was 0.2 milliseconds (ms).

Example 2

execute ping 10.0.0.1

The CLI displays the following:

PING 10.0.0.1 (10.0.0.1): 56 data bytes

After several seconds with no output, the administrator stops the ping by pressing Ctrl + C. The CLI displays the following:

--- 10.0.0.1 ping statistics ---

5 packets transmitted, 0 packets received, 100% packet loss

The results of the ping indicate that the host might be down or there is no route between FortiNDR and 10.0.0.1.

execute ping

Use this command to perform an ICMP ECHO request (a ping) to a host by specifying its FQDN or IP address.

Syntax

execute ping {<fqdn_str> | <host_ipv4>}

Variable

Description

Default

ping {<fqdn_str> | <host_ipv4>}

IP address or FQDN of the host.

Example 1

execute ping 172.16.1.10

The CLI displays the following:

PING 172.16.1.10 (172.16.1.10): 56 data bytes

64 bytes from 172.16.1.10: icmp_seq=0 ttl=128 time=0.5 ms

64 bytes from 172.16.1.10: icmp_seq=1 ttl=128 time=0.2 ms

64 bytes from 172.16.1.10: icmp_seq=2 ttl=128 time=0.2 ms

64 bytes from 172.16.1.10: icmp_seq=3 ttl=128 time=0.2 ms

64 bytes from 172.16.1.10: icmp_seq=4 ttl=128 time=0.2 ms

--- 172.16.1.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 of the ping indicate that a route exists between FortiWeb and 172.16.1.10. It also indicates that during the sample period, there was no packet loss and the average response time was 0.2 milliseconds (ms).

Example 2

execute ping 10.0.0.1

The CLI displays the following:

PING 10.0.0.1 (10.0.0.1): 56 data bytes

After several seconds with no output, the administrator stops the ping by pressing Ctrl + C. The CLI displays the following:

--- 10.0.0.1 ping statistics ---

5 packets transmitted, 0 packets received, 100% packet loss

The results of the ping indicate that the host might be down or there is no route between FortiNDR and 10.0.0.1.