Search the VMware Knowledge Base (KB)
View by Article ID

Troubleshooting VXLAN Installation in NSX for vSphere 6.x (2124894)

  • 1 Ratings

Purpose

This article provides steps to troubleshoot issues related to the installation of Virtual Extensible LAN (VXLAN) in an NSX for vSphere Environment.

Resolution

To troubleshoot VXLAN installation issues:
  1. Ensure that the IP and FQDN that you wish to use for the vmkernel port (vmknic) exists and the name resolution is working correctly.
  2. Ensure the version of Virtual Distributed Switch (vDS) is version 5.5 or greater.
  3. Ensure that the NSX Manager is correctly connected to the vCenter Server with either IP address or hostname. For more information, see the Register vCenter Server with NSX Manager section in the NSX Installation and Upgrade Guide.
  4. Check the output of the command show log follow on the NSX manager appliance. For more information, see the NSX Manager Virtual Appliance Events section in the NSX Administration Guide.
  5. Check /var/log/vmware/hostd.log and /var/log/esxupdate.log file on the ESXi host for installation errors. For more information about these logs, see Location of ESXi 5.1 and 5.5 log files (2032076).
  6. Check the eam.log file on the vCenter Server to do a health check and ensure that the agents are installed correctly. Log path differs depending on the host Operating System of vCenter Server. For more information about these logs, see Location of vCenter Server log files (1021804).
  7. Ensure that the correct vSphere Installation Bundles (VIBs) /Modules are loaded:

    1. To see the available NSX VIBs, open this NSX Manager URL to download a zip file containing the files:

      https://NSX_Manager_IPaddress/bin/vdn/vibs/5.5/vxlan.zip

      Note
      : Prior to NSX 6.2.0, there was a single URL on NSX Manager from which VIBs for a certain version of the ESXi Host could be found. In other words, the administrator only needed to know a single URL, regardless of NSX version. In NSX 6.2.0 and later, the new NSX VIBs are available at different URLs. To find the correct VIBs, find the new VIB URL from https://NSX_Manager_IPaddress/bin/vdn/nwfabric.properties.The nwfabric.properties returns the correct download paths based on versions:

      # 5.1 VDN EAM Info
      VDN_VIB_PATH.1=/bin/vdn/vibs-6.2.0/5.1-2107743/vxlan.zip
      VDN_VIB_VERSION.1=2107743
      VDN_HOST_PRODUCT_LINE.1=embeddedEsx
      VDN_HOST_VERSION.1=5.1.*

      # 5.5 VDN EAM Info
      VDN_VIB_PATH.2=/bin/vdn/vibs-6.2.0/5.5-2983935/vxlan.zip
      VDN_VIB_VERSION.2=2983935
      VDN_HOST_PRODUCT_LINE.2=embeddedEsx
      VDN_HOST_VERSION.2=5.5.*

      # 6.0 VDN EAM Info
      VDN_VIB_PATH.3=/bin/vdn/vibs-6.2.0/6.0-2984108/vxlan.zip
      VDN_VIB_VERSION.3=2984108
      VDN_HOST_PRODUCT_LINE.3=embeddedEsx
      VDN_HOST_VERSION.3=6.0.
      *

    2. Open the zip file and examine the contents of the vib20 directory. Each folder within corresponds directly to an NSX VIB.
    3. Run this command on the command line of the ESXi host to see the VIBs that are loaded on your host:

      # esxcli software vib list

    4. Ensure that the list of VIBS on the host matches the list of VIBs in the zip file.

  8. Run this command to verify the MTU is configured to 1600 or above:

    # ping ++netstack=vxlan -d -s 1572 -I vmkx hostname_or_IP

    Where vmkx is the ID of your vmkernel port and where hostname_or_IP is the IP or hostname of your vmkernel port.

    This allows you to check the validity of all uplinks. If you are working in a multi-VTEP environment you can validate all uplinks by running a ping from each possible VTEP vmkernel source/destination interface to validate all paths.

    For more information about this MTU check, see the Verify the NSX Working State section in the NSX 6.2 Upgrade Guide.

Additional Information

See Also

Update History

08/20/2015 - Added NSX for vSphere 6.2 to Products, added note about VIB URL change in 6.2 and later

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.

Feedback

  • 1 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 1 Ratings
Actions
KB: