Enables you to send User Datagram Protocol (UDP) or ICMP echo messages or to a remote IP device.
|count||Specifies the number of ping requests to send.|
|start-size||Specifies the size, in bytes, of the packet to be sent, or the starting size if incremental packets are to be sent.|
|continuous||Specifies that UDP or ICMP echo messages to be sent continuously. This option can be interrupted by pressing [Ctrl] + C.|
|end-size||Specifies an end size for packets to be sent.|
|udp||Specifies that the ping request should use UDP instead of ICMP.|
|dont-fragment||Sets the IP to not fragment the bit.|
|ttl||Sets the TTL value.|
|tos||Sets the TOS value.|
|interval||Sets the time interval between sending out ping requests.|
|vr||Specifies the virtual route to
use for sending out the echo message. If not specified,
VR-Default is used.
Note: User-created VRs are supported only on the platforms listed for this feature in the Switch Engine 32.2 Feature License Requirements document.
|ipv4||Specifies IPv4 transport.|
|ipv6||Specifies IPv6 transport.
Note: If you are contacting an IPv6 link local address, you must specify the VLAN you are sending the message from: ping ipv6 link-local address %vlan_name host .
|host||Specifies a host name or IP address (either v4 or v6).|
|from||Uses the specified source address. If not specified, the address of the transmitting interface is used.|
|with record-route||Sets the traceroute information.|
The ping command is used to test for connectivity to a specific host.
You use the ipv6 variable to ping an IPv6 host by generating an ICMPv6 echo request message and sending the message to the specified address. If you are contacting an IPv6 link local address, you must specify the VLAN you are sending the message from, as shown in the following example (you must include the % sign):
ping ipv6 link-local address %vlan_name host.
The ping command is available for both the user and administrator privilege level.
When the IPv6 host ping fails, the following error message appears:
Error: cannot determine outgoing interface. Link local address must be of form LLA% vlan_name.
Due to upgrading ExtremeXOS 30.1 to 4.14 Linux kernel, ping success to local IP addresses does not depend on link-layer status. Earlier releases of ExtremeXOS had customized Linux behavior that meant that pinging a local VLAN interface would fail when the local interface was down. However, in ExtremeXOS 30.1, pinging a local VLAN interface that is down will result in a successful ping.
If you have an asymmetric routing to a specific destination (where the traffic from the source to the destination uses one path, and the return traffic uses another), use this command with option 7, with record-route.
ping <destination address> with record-route
ping <destination address> from <source-address> with record-route
For more information about this option, see enable ip-option record-route.
The following example enables continuous ICMP echo messages to be sent to a remote host:
ping continuous 220.127.116.11
The following example uses the with record-route option:
ping 10.2.1.1 from 10.2.1.2 with record-route Ping(ICMP) 10.2.1.1: 4 packets, 8 data bytes, interval 1 second(s). 16 bytes from 10.2.1.1: icmp_seq=0 ttl=63 time=10 ms RR: 10.2.1.2 10.2.0.21 10.2.1.1 10.2.1.1 10.2.0.1 10.2.1.2
This command was first available in ExtremeXOS 10.1.
The ipv6 option was added in ExtremeXOS 11.2.
The IPv6 error message was modified in ExtremeXOS 15.2.
Ping success to local IP addresses not depend on link-layer status added in ExtremeXOS 30.1.
This command is available on ExtremeSwitching 5320, 5420, 5520, and 5720 series switches.