Search the VMware Knowledge Base (KB)
View by Article ID
Minimum recommended version for NSX for vSphere with GID, ESXi, and vCenter Server (2144295)
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 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:
|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:
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).
- VMware NSX for vSphere 6.1.x release train is scheduled for end of support in January 2017. For more information, see the VMware Product Lifecycle Matrix.
- VMware NSX for vSphere 6.2.2 delivers a security patch to address CVE-2015-7547, also known as the glibc vulnerability, and includes bug fixes documented in the Known Issues section in the NSX for vSphere 6.2.2 Release 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.
<errorDesc>Live vib installation failed. An immediate reboot is required to clear live vib installation failure.</errorDesc>
<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>
- 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).
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.