Skip to main content
Cisco SD-WAN
Support
Product Documentation
Viptela Documentation

ping

ping—Verify that a network device is reachable on the network, by sending ICMP ECHO_REQUEST packets to them. This command is effectively identical to the standard UNIX ping command.

Command Syntax

ping (hostname | ip-address)
ping vpn vpn-id (hostname | ip-address)
ping [count number] [rapid] [size bytes] [source (interface-name | ip-address)] [wait seconds] vpn vpn-id (hostname | ip-address)

Options

Device to Ping
(hostname | ip-address)
Name or IPv4 or IPv6 address of the host to ping. For an IPv4 address in a service VPN, you can ping the primary and the secondary addresses.
Number of Ping Requests to Send
count number
Number of ping requests to send. If you do not specify a count, the command operates until you interrupt it by typing Control-C.
Rapid Pinging
rapid
Send five ping requests in rapid succession and display abbreviated statistics, only for packets transmitted and received, and percentage of packets lost.
Size of Ping Request Packets
size bytes
Size of the packet to send.
Default: 64 bytes (56 bytes of data plus 8 bytes of ICMP header)
Source of Ping Packets
source (interface-name | ip-address)
Interface or IP address from which to send to ping packets. You cannot specify the loopback0 interface in this option.
Time to Wait between Each Ping Packet
wait seconds
Time to wait for a response to a ping packet.
Default: 1 second
VPN in which to Ping
vpn vpn-id
Specify the VPN into which to send the ping packets.

Output Fields

Field

Explanation

bytes

Number of bytes transmitted in the ping packets. The packets are the specified data bytes size plus 8 bytes for the ICMP header.

data bytes

Size of the data in the ping packets.

from

IP address from which ping responses were received.

packet loss

Percentage of ping packets for which a response was not received.

packets received

Number of responses received to ping packets.

packets transmitted

Number of ping packets transmitted.

PING address

IP address to which the ping packets were sent.

ping statistics

Statistics for this ping operation.

round-trip min/avg/max

Minimum, average, and maximum round-trip times for sending a ping packet and receiving a response, in milliseconds.

seq

Sequence number of the ping packet response. The first response is 0.

time

Round-trip time for sending this ping packet and receiving a response, in milliseconds.

Example Output

Viptela# ping vpn 0 10.0.14.4
PING 10.0.14.4 (10.0.14.4): 56 data bytes
64 bytes from 10.0.14.4: seq=0 ttl=63 time=0.642 ms
64 bytes from 10.0.14.4: seq=1 ttl=63 time=0.788 ms
64 bytes from 10.0.14.4: seq=2 ttl=63 time=0.685 ms
64 bytes from 10.0.14.4: seq=3 ttl=63 time=0.666 ms
64 bytes from 10.0.14.4: seq=4 ttl=63 time=0.713 ms
64 bytes from 10.0.14.4: seq=5 ttl=63 time=0.846 ms
^C
--- 10.0.14.4 ping statistics ---
6 packets transmitted, 6 packets received, 0% packet loss
round-trip min/avg/max = 0.642/0.723/0.846 ms
Viptela# ping vpn 0 rapid 10.0.12.2
Defaulting count to 5
!!!!! 
--- 10.0.12.2 statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
Viptela# ping vpn 0 10.0.12.3
PING 10.0.12.3 (10.0.12.3): 56 data bytes
64 bytes from 10.0.12.3: seq=0 ttl=64 time=8.127 ms
64 bytes from 10.0.12.3: seq=1 ttl=64 time=0.475 ms
64 bytes from 10.0.12.3: seq=2 ttl=64 time=0.336 ms
64 bytes from 10.0.12.3: seq=3 ttl=64 time=0.576 ms
64 bytes from 10.0.12.3: seq=4 ttl=64 time=0.578 ms
^C
--- 10.0.12.3 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.336/2.018/8.127 ms
 vEdge# show interface
                                  IF      IF                                                                TCP
                                  ADMIN   OPER    ENCAP                                      SPEED          MSS                 RX       TX
VPN  INTERFACE  IP ADDRESS        STATUS  STATUS  TYPE   PORT TYPE  MTU   HWADDR             MBPS   DUPLEX  ADJUST  UPTIME      PACKETS  PACKETS
--------------------------------------------------------------------------------------------------------------------------------------------------
0    gre4       172.0.101.15/24   Up      Up      null   service    1500  0a:01:0f:0f:00:00  0      full    1420    0:00:06:09  0        0
0    ge0/0      10.1.15.15/24     Up      Up      null   transport  1500  00:0c:29:9c:a2:be  10     full    1420    0:00:26:44  9986     10696
0    ge0/1      10.1.17.15/24     Up      Up      null   service    1500  00:0c:29:9c:a2:c8  10     full    1420    0:00:17:13  3        8
0    ge0/2      -                 Down    Up      null   service    1500  00:0c:29:9c:a2:d2  10     full    1420    0:00:26:47  3        0
0    ge0/3      10.0.20.15/24     Up      Up      null   service    1500  00:0c:29:9c:a2:dc  10     full    1420    0:00:17:13  11       9
0    ge0/6      57.0.1.15/24      Up      Up      null   service    1500  00:0c:29:9c:a2:fa  10     full    1420    0:00:17:13  3        9
0    ge0/7      10.0.100.15/24    Up      Up      null   service    1500  00:0c:29:9c:a2:04  10     full    1420    0:00:26:21  753      641
0    system     172.16.255.15/32  Up      Up      null   loopback   1500  00:00:00:00:00:00  10     full    1420    0:00:15:52  0        0
1    gre1       -                 Up      Down    null   service    1500  38:00:01:0f:00:00  -      -       1420    -           0        0
1    ge0/4      10.20.24.15/24    Up      Up      null   service    1500  00:0c:29:9c:a2:e6  10     full    1420    0:00:17:10  714      717
1    ge0/5      56.0.1.15/24      Up      Up      null   service    1500  00:0c:29:9c:a2:f0  10     full    1420    0:00:17:10  1        47
1    loopback0  10.20.30.15/24    Up      Up      null   service    1500  00:00:00:00:00:00  10     full    1420    0:00:00:20  0        0
512  eth0       10.0.1.15/24      Up      Up      null   service    1500  00:50:56:00:01:0f  1000   full    0       0:00:26:39  8156     5313

vEdge# ping vpn 1 10.20.25.16 source 10.20.30.15
Ping in VPN 1
PING 10.20.25.16 (10.20.25.16) from 10.20.30.15 : 56(84) bytes of data.
64 bytes from 10.20.25.16: icmp_seq=1 ttl=64 time=1.45 ms
64 bytes from 10.20.25.16: icmp_seq=2 ttl=64 time=1.61 ms
^C
--- 10.20.25.16 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 1.458/1.534/1.611/0.085 ms
vEdge# ping vpn 1 10.20.25.16 source loopback0
Ping in VPN 1
PING 10.20.25.16 (10.20.25.16) from 10.20.30.15 : 56(84) bytes of data.
64 bytes from 10.20.25.16: icmp_seq=1 ttl=64 time=1.05 ms
^C
--- 10.20.25.16 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.054/1.054/1.054/0.000 ms
vm5# ping vpn 1 10.20.25.16 source ge0/4
Ping in VPN 1
PING 10.20.25.16 (10.20.25.16) from 10.20.24.15 : 56(84) bytes of data.
64 bytes from 10.20.25.16: icmp_seq=1 ttl=64 time=1.35 ms
64 bytes from 10.20.25.16: icmp_seq=2 ttl=64 time=1.44 ms
^C
--- 10.20.25.16 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 1.350/1.397/1.444/0.047 ms
vEdge#

Release Information

Command introduced in Viptela Software Release 14.1.
In Release 16.3, add support for IPv6 host addresses in VPN 0.
In Release 17.2.2, add support for pinging secondary IPv4 addresses.

Additional Information

tools nping
traceroute

  • Was this article helpful?