You must upgrade all secondary NSX Manager appliances before upgrading any other NSX components.
Complete the following steps to upgrade a secondary NSX Manager appliance. Repeat these steps for all secondary NSX Manager appliances in the cross-vCenter NSX environment.
During the upgrade, you can choose to join the Customer Experience Improvement Program (CEIP) for NSX. See Customer Experience Improvement Program in the NSX Administration Guide for more information about the program, including how to join or leave the program.
Verify that the primary NSX Manager is upgraded.
Validate the NSX Manager file system usage, and perform a cleanup if file system usage is at 100 percent.
Login to NSX Manager and run show filesystems to show the /dev/sda2 filesystem usage.
If the usage is 100 percent, run the purge log manager and purge log system commands.
Reboot the NSX Manager appliance for the log cleanup to take effect.
Increase the NSX Manager virtual appliance's reserved memory to at least 16 GB before upgrading for NSX 6.2.x.
If you have Data Security in your environment, uninstall it before upgrading NSX Manager. See Uninstall NSX Data Security.
Back up your current configuration and download technical support logs before upgrading. See NSX Backup and Restore.
Download the upgrade bundle and check the MD5. See Download the NSX Upgrade Bundle and Check the MD5.
Make sure that you understand the operational impact of the NSX Manager upgrade while the upgrade is in progress. See Operational Impacts of NSX Upgrades.
- Click Upgrade, then click Choose File and browse to the VMware-NSX-Manager-upgrade-bundle-releaseNumber-NSXbuildNumber.tar.gz file. Click Continue to start the upload.
The upload status displays in the browser window.
- In the Upgrade dialog box, specify whether you want to enable SSH, and whether you want to participate in VMware's Customer Experience Improvement Program ("CEIP"). Click Upgrade to start the upgrade.
The upgrade status displays in the browser window.
Wait until the upgrade procedure completes and the NSX Manager login page appears.
- Log in to the NSX Manager virtual appliance again and confirm that the upgrade state is Complete, and the version and build number on the top right matches the upgrade bundle you just installed.
After upgrading NSX Manager, you must log out and log back in to the vSphere Web Client.
If the NSX plug-in does not display correctly in the vSphere Web Client, clear your browser's cache and history. If this step is not done, you might see an error similar to "An internal error has occurred - Error #1009" when making NSX configuration changes in the vSphere Web Client.
If the Networking and Security tab does not appear in the vSphere Web Client, reset the vSphere web client server:
In vCenter 5.5, open https://<vcenter-ip>:5480 and restart the Web Client server.
In the vCenter Server Appliance 6.0, log into the vCenter Server shell as root and run the following commands:
Command> shell.set --enabled True Command> shell localhost:~ # cd /bin localhost:~ # service-control --stop vsphere-client localhost:~ # service-control --start vsphere-client
In vCenter Server 6.0 on Windows, you can do this by running the following commands.
cd C:\Program Files\VMware\vCenter Server\bin service-control --stop vspherewebclientsvc service-control --start vspherewebclientsvc
It is recommended to use different Web Clients to manage vCenter Servers running different versions of NSX Managers to avoid unexpected errors when different versions of NSX plug-ins are running.
After the NSX Manager is upgraded, create a new NSX Manager backup file. See NSX Backup and Restore . The previous NSX Manager backup is only valid for the previous release.