The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Testing VMkernel network connectivity with the vmkping command (1003728)
This article provides you with the steps to perform a vmkping test between your ESX hosts.
The vmkping command sources a ping from the local VMkernel port.
To initiate a vmkping test from the console of an ESX Server host:
Connect to the ESX/ESXi host using an SSH session. For information see Tech Support Mode for Emergency Support (1003677) and Using Tech Support Mode in ESXi 4.1 and 5.0 (1017910).
In the command shell, run the command:
# vmkping x.x.x.x
where x.x.x.x is the hostname or IP address of the server that you want to ping.
If you have Jumbo Frames configured in your environment, run the vmkping command with the -s and -d options.
# vmkping -d -s 8972 x.x.x.x
Note: If you have more then one vmkernel port on the same network (such as a heartbeat vmkernel port for iSCSI) then all vmkernel ports on the host on the network would need to be configured with Jumbo Frames (MTU: 9000) too. If there are other vmkernel ports on the same network with a lower MTU then the vmkping command will fail with the -s 8972 option. Here in the command -d option sets DF (Don't Fragment) bit on the IPv4 packet.
- In ESXi 5.1 and later, you can specify which vmkernel port to use for outgoing ICMP traffic with the -I option:
# vmkping -I vmkX x.x.x.x
- ICMP response behavior has changed in ESXi 5.1. For more information, see Change to ICMP ping response behavior in ESXi 5.1 (2042189).
- In releases prior to ESXi 5.1, the host will automatically select the vmkernel port based on the host's vmkernel routing/forwarding table. To display the host's vmkernel routing table, use the esxcfg-route -l command.
- Verification of your MTU size can be obtained from a SSH session by using
esxcfg-nics -lOutput should be similar to:# esxcfg-nics -lName PCI Driver Link Speed Duplex MAC Address MTU Descriptionvmnic0 0000:02:00.00 e1000 Up 1000Mbps Full 00:50:56:17:0a:60 9000 Intel Corporation 82545EM Gigabit Ethernet Controller (Copper)vmnic1 0000:02:01.00 e1000 Up 1000Mbps Full 00:50:56:17:0a:65 9000 Intel Corporation 82545EM Gigabit Ethernet Controller (Copper)esxcfg-vmknic -lOutput should be similar to:# esxcfg-vmknic -lInterface Port Group/DVPort IP Family IP Address Netmask Broadcast MAC Address MTU TSO MSS Enabled Typevmk1 iSCSI IPv4 10.10.10.10 255.255.255.0 10.10.10.255 00:50:56:XX:XX:64 9000 65535 true STATICA successful ping response is similar to:# vmkping 10.0.0.1
PING server(10.0.0.1): 56 data bytes
64 bytes from 10.0.0.1: icmp_seq=0 ttl=64 time=10.245 ms
64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.935 ms
64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.926 ms--- server ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.926/4.035/10.245 msAn unsuccessful ping response is similar to:# vmkping 10.0.0.2
PING server (10.0.0.2) 56(84) bytes of data.--- server ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 3017ms
- If you see intermittent ping success, this might indicate you have incompatible NICs teamed on the VMotion port. Either team compatible NICs or set one of the NICs to standby.
- If you do not see a response when pinging by the hostname of the server, initiate a ping to the IP address. Initiating a ping to the IP address allows you to determine if the problem is a result of an issue with hostname resolution. If you are testing connectivity to another VMkernel port on another server remember to use the VMkernel port IP address because the server's hostname usually resolves to the service console address on the remote server.
- In vSphere 5.5 VXLAN has its own vmkernel networking stack therefore ping connectivity testing between two different vmknics on the transport VLAN must be done from the ESXi console with the either of this syntax:
vmkping ++netstack=vxlan <vmknic IP> -d -s <packet size>
esxcli network diag ping --netstack=vxlan --host <vmknic IP> --df --size=<packet size>
- ESXi 5.5 で正しくジャンボフレームの設定を行っているにも関わらず、ジャンボフレームを使用した ping が失敗し、次のエラーが表示される： sendto() failed (Message too long) (2105718)
This Article Replaces
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.