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

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.

IMPORTANT: Please note that this knowledge base article will be retired in the very near future. For the most up-to-date information, see the latest version of the NSX for vSphere 6.x Release Notes.

Product or Functional Component

Minimum Recommended Release

VMware NSX
VMware recommends NSX 6.2.6 for new deployments and at minimum running NSX 6.2.2 based on critical bug fixes identified as having a general impact in an NSX environment.

For existing deployments running a release earlier than 6.2.6, please review the NSX Release Notes and/or contact your VMware technical support representative for more information on specific issues before planning an upgrade.

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 recommends a minimum of 5.5U3 and 6.0U3 in NSX environments. See also the VMware Product Interoperability Matrix for interoperability information.

Notes:
  • NSX 6.2.x is not compatible with vSphere 6.5.
  • vSphere 6.0U3 resolves the issue of duplicate VTEPs in ESXi hosts after rebooting vCenter server. See VMware Knowledge Base article 2144605 for more information.
  • For Distributed Service Insertion, ESXi versions 5.5 Patch 10 and ESXi 6.0U3 or later are recommended. See VMware Knowledge Base article 2149704 for more information.
Guest Introspection Guest Introspection-based features in NSX are compatible with specific VMware Tools versions. To enable the optional Thin Agent Network Introspection Driver component packaged with VMware Tools, you must upgrade to one of:
  • VMware Tools 10.0.8 and later to resolve Slow VMs after upgrading VMware Tools in NSX / vCloud Networking and Security (VMware Knowledge Base article 2144236).
  • VMware Tools 10.0.9 and later for Windows 10 support.
vRealize Orchestrator
 NSX-vRO plugin 1.0.3 or later
VMware Integrated Openstack (VIO)
 VIO 2.5.1
vCloud Director
  • VCD 8.0 if migrating from vCNS to NSX
  • VCD 8.10.1 if already on NSX

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

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: