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

Successful vmkping ensures that the 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.

Procedure

  1. Log in to vCenter Server by using the vSphere Client.
    1. Open a Web browser and go to https://sfo01m01vc01.sfo01.rainpole.local/ui.
    2. Log in using the following credentials.
      Setting Value
      User name administrator@vsphere.local
      Password vsphere_admin_password
  2. From the Home menu, select Networking and Security.
  3. Click Installation and Upgrade, and click the Host Preparation tab.
  4. Select 172.16.11.65 from the NSX Manager drop-down menu.
  5. In the Hosts table, under the vmkNIC column, click View Details for sfo01m01esx01.sfo01.rainpole.local and sfo01m01esx04.sfo01.rainpole.local hosts.
  6. Note the vmk4 IP address of sfo01m01esx01.sfo01.rainpole.local and sfo01m01esx04.sfo01.rainpole.local hosts.
  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.
      Setting Value
      User name root
      Password esxi_root_password
  8. Verify that the ESXi hosts can ping other VTEPs by running the following command.
    vmkping -I vmk4 -S vxlan -s 8800 -d 172.16.14.210
    Note: In the syntax vmkping -I <VTEP-VMK> -S vxlan -s 8800 -d <Remote-VTEP-IP>, the address 172.16.14.210 is the remote VTEP IP address of sfo01m01esx04.sfo01.rainpole.local host.
  9. Repeat the procedure on the sfo01m01esx04.sfo01.rainpole.local host with destination IP as the VTEP address of sfo01m01esx01.sfo01.rainpole.local host.
  10. Repeat the procedure for the remaining ESXi hosts from all the 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 Switched Virtual Interfaces (SVIs).