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

Minimum recommended version for NSX for vSphere with GID, ESXi, and vCenter Server (2144295)

  • 1 Ratings
Language Editions

Purpose

This article provides information on the recommended minimum version for VMware NSX for vSphere 6.2.x, ESXi, vCenter Server and Guest Introspection Driver (GID).

Resolution

This table lists the minimum recommended version for NSX for vSphere with Guest Introspection Driver (GID), ESXi, and vCenter Server. VMware advises that customers run at least the minimum release based on critical bug fixes identified as having a general impact in an NSX environment.  

As always, please review the NSX Release Notes and/or contact your VMware technical support representative for more information on specific issues before selecting a release.  

 

Product or Functional Component

Minimum Recommended Release

VMware NSX
VMware NSX for vSphere 6.2.2

For customers who use SSL VPN, VMware advises a minimum recommended release of NSX for vSphere 6.2.4 and a review of CVE-2016-2079

For customers who plan to use logical switching and vSphere 6.0U2, VMware advises a minimum recommended release of NSX for vSphere 6.2.4 and a review of Duplicate VTEPs in ESXi hosts after rebooting vCenter Server (KB 2144605).

Important points to consider when selecting a 6.2.x release: 
  • Upgrades from NSX 6.1.x: Virtual machines lose network connectivity after vMotion under the following conditions: Distributed Firewall (DFW) is enabled in the environment and; NSX for vSphere setup upgraded from NSX-V 6.1.x release to NSX-V 6.2.3a/6.2.3b/6.2.4 release and virtual machines are later migrated between upgraded ESXi hosts. For more information, see KB 2146171.
  • Endpoint: NSX Endpoint in vSphere is available as a free download for customers who purchased vSphere with vShield Endpoint (Essential Plus and above). VMware recommends installing NSX 6.2.4 to manage vShield Endpoint running on vSphere 6.0 and prior. There is currently no compatible version of vShield Endpoint for vSphere 6.5. Alternately, for customers using vCNS Manager specifically to manage vShield Endpoint for agentless anti-virus, Technical Guidance under the VMware End of Availability process is available until March 31, 2017.  See KB 2144733.
  • vSphere 6.5 Interoperability: All versions of VMware NSX 6.2.x currently are not supported with vSphere 6.5. Initiating a host preparation of a vSphere 6.5 host with NSX 6.2.x will fail and report an “incompatible VIBs” error.  For more information, see KB 2147548.
VMware vSphere 5.5.x/6.0.x
VMware vSphere 5.5 U3/6.0 Update 2

Important points to consider when selecting a vSphere release: 
  • There is a known issue with vSphere 6.0 and NSX objects. For more information, see Duplicate VTEPs in ESXi hosts after rebooting vCenter Server (2144605).  When selecting vSphere 6.0U2, VMware advises running NSX for vSphere 6.2.4.   
  • If you are running or considering an upgrade to ESXi 6.0P3, please see the NSX Release Notes and Issue 1732337/1724222: NSX Manager fails to push firewall rules to ESXi 6.0 P03 host.  This issue occurs when /dev/random call is blocked which affects NSX operation on password generation.  For a workaround, contact VMware technical support. See also KB 2146873.
Guest Introspection
VMware Tools 10.1.0 and later (last changed February 1, 2017)

Note: VMware Tools 10.0.9 resolves a critical known issue with earlier versions and provides Windows 10 support. For more information, see Slow VMs after upgrading VMware Tools in NSX and vCloud Networking and Security (KB 2144236).

Additional notes:

Critical Fixes in VMware vSphere 6.0 Update 2 for NSX for vSphere 6.x

  • Critical EAM and esxupdate fixes to address Network connectivity issues after upgrading or repreparing ESXi hosts in a VMware NSX/VCNS environment (KB 2107951).
  • New esxupdate error code with An immediate reboot is required to clear live vib installation failure is reported when there is a live VIB installation failure caused by jumpstart plugins, rc scripts or init.d scripts. The system then is recovered to the state before the failed transaction. In addition, EAM returns this error code to NSX. For more information, see Installed Live VIB might not function properly and be lost after a reboot section in the VMware ESXi 6.0 Update 2 Release Notes.

    <error errorClass="LiveInstallationError">
      <errorCode>29</errorCode>
      <errorDesc>Live vib installation failed. An immediate reboot is required to clear live vib installation failure.</errorDesc>
      <vibs>[]</vibs>
      <msg>Error in running ['/etc/init.d/initd_test', 'start', 'install']:
    Return code: 1
    Output: Starting :
    It is not safe to continue. Please reboot the host immediately to discard the unfinished update.</msg>
    </error>


  • On newly prepared NSX hosts, ESX Agent Manager (EAM) accurately reports a partial installation status of the live NSX for vSphere VIBs to NSX Manager for display in the Host Preparation tab. On a failure, the live VIB is not reported as installed.
  • If the vSphere host is not rebooted, installing other VIBs does not carry the failed live NSX VIB to the alt-bootbank.
  • Support available to increase or decrease the vSphere ESX Agent Manager's (EAM) logging levels dynamically without restarting EAM. For more information, see Troubleshooting vSphere ESX Agent Manager (EAM) with NSX (KB 2122392).

See Also

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: