To help ensure a successful NSX upgrade, be sure to check the release notes for upgrade issues, make sure that you are using the correct upgrade sequence, and make sure that the infrastructure is properly prepared for the upgrade.
Downgrades are not supported:
Always capture a backup of NSX Manager before proceeding with an upgrade.
Once NSX Manager has been upgraded successfully, NSX cannot be downgraded.
VMware recommends doing upgrade work in a maintenance window as defined by your company.
The following guidelines can be used as a pre-upgrade checklist.
Verify that vCenter meets the system requirements for NSX. See System Requirements for NSX.
If any Guest Introspection or Network Extensibility partner services are deployed, verify compatibility before upgrading:
In most circumstances, NSX can be upgraded without impacting partner solutions. However, if your partner solution is not compatible with the version of NSX to which you are upgrading, you will need to upgrade the partner solution to a compatible version before upgrading NSX.
Consult the VMware Compatibility Guide for Networking and Security. See http://www.vmware.com/resources/compatibility/search.php?deviceCategory=security.
Consult the partner documentation for compatibility and upgrade details.
If you have Data Security in your environment, uninstall it before upgrading NSX. Data Security is not supported in NSX 6.3.x. See Uninstall NSX Data Security.
If you have a hardware gateway (hardware VTEP) installed in your environment, upgrade to NSX 6.3.0 and 6.3.1 is blocked. You must contact VMware support to proceed with the upgrade. See https://kb.vmware.com/kb/2148511 for more information. Upgrade to NSX 6.3.2 is allowed.
If you have any NSX 5.5 or earlier NSX Edge appliances, you must upgrade them to NSX 6.x before upgrading to NSX 6.3.x.
The NSX Controller cluster must contain three controller nodes. If it has fewer than three, you must add additional nodes before starting the upgrade. See "Deploy NSX Controller Cluster" in the NSX Installation Guide for steps to add controller nodes.
Determine which NSX Managers must be upgraded in the same maintenance window.
If you have a cross-vCenter NSX environment, you must upgrade the primary and all secondary NSX Managers to the same NSX version in a single maintenance window.
If you have multiple NSX Managers connected to vCenter Server systems that use the same SSO server, not all combinations of NSX Manager version are supported. You must plan the upgrade of your NSX Managers so that you have a supported configuration at the end of the maintenance window
All NSX Managers using the same version of NSX is supported.
NSX Managers using different version of NSX is supported if at least one NSX Manager has NSX 6.4.0 or later installed, and all other NSX Managers have NSX 6.3.3 or later installed.
Verify that you have a current backup of the NSX Manager, vCenter and other NSX components. See NSX Backup and Restore.
Create a Tech Support Bundle.
Ensure that forward and reverse domain name resolution is working, using the nslookup command.
If you are using a vSphere version earlier than vSphere 6.0 U3, and vSphere Update Manager is in use in the environment, ensure that the bypassVumEnabled flag is set to true in vCenter. This setting configures EAM to install the VIBs directly to the ESXi hosts even when VUM is installed or not available. See http://kb.vmware.com/kb/2053782.
Download and stage the upgrade bundle, validate with md5sum. See Download the NSX Upgrade Bundle and Check the MD5.
As a best practice, quiesce all operations in the environment until all sections of the upgrade are complete.
Do not power down or delete any NSX components or appliances before instructed to do so.