Verify that ESXi hosts can ping all other VTEP interfaces using the vmkping command.

Ensures hosts VTEPs can communicate with each other using jumbo frames and that the vxlan is functioning.

Expected Outcome

Successful vmkping between the two VTEP interfaces.


  1. Log in to vCenter Server by using the vSphere Web Client.
    1. Open a Web browser and go to https://sfo01m01vc01.sfo01.rainpole.local/vsphere-client.
    2. Log in using the following credentials.



      User name




  2. From the Home menu, select Networking & Security.
  3. Click Installation and Upgrade, and click the Logical Network Preparation tab.
  4. Select from the NSX Manager drop-down menu.
  5. Click the VXLAN Transport tab and expand the sfo01-m01-mgmt01 cluster.
  6. Under VMKNic IP Addressing, note the vmk4 IP address of sfo01m01esx01.sfo01.rainpole.local and sfo01m01esx04.sfo01.rainpole.local.
  7. Log in to the ESXi host by using Secure Shell (SSH) client.
    1. Open an SSH connection to the sfo01m01esx01.sfo01.rainpole.local host.
    2. Log in using the following credentials.



      User name




  8. Verify that the ESXi hosts can ping other VTEPs by running the following command.

    Region of the ESXi Host


    Region A

    vmkping -I vmk4 -S vxlan -s 8800 -d


    In the syntax vmkping -I VTEP-VMK -S vxlan -s 8800 -d Remote-VTEP-IP, the address is the remote VTEP IP address of sfo01m01esx04.sfo01.rainpole.local.

  9. Repeat the procedure on the sfo01m01esx04.sfo01.rainpole.local host with destination IP as the VTEP address of sfo01m01esx01.sfo01.rainpole.local.
  10. Repeat the procedure for other ESXi hosts from different vCenter servers.

What to do next

If you encounter issues while performing this procedure, use the following troubleshooting tips:

Troubleshooting Tips

  • Ensure that VTEPs have a valid IP address.

  • Ensure that the jumbo frame setting is enabled on switch ports and SVIs.