Search the VMware Knowledge Base (KB)
View by Article ID
Minimum recommended version for NSX for vSphere with GID, ESXi, and vCenter Server (2144295)
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 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:
|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.|
|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:|
NSX-vRO plugin 1.0.3 or later
|VMware Integrated Openstack (VIO)
Critical Fixes in VMware vSphere 6.0 Update 3 for NSX for vSphere 6.x
- vSphere 6.0 Update 3 resolves the issue documented in Knowledge Base article Duplicate VTEPs in ESXi hosts after rebooting vCenter Server (2144605).
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.