Upgrade the Primary NSX Manager in Cross-vCenter NSX

<

The first step in the NSX infrastructure upgrade process is the primary NSX Manager appliance upgrade.

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.

Caution:

Running with NSX Manager appliances of different versions in a cross-vCenter NSX environment is not supported. Once you upgrade the primary NSX Manager appliance, you must upgrade the secondary NSX Manager appliances.

Prerequisites

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.

Procedure

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.

Results

If you are logged in to the vSphere Web Client during the upgrade, you will see synchronization issue warnings on the Networking and Security > Installation > Management page. This is because you have NSX Manager appliances with different versions of NSX. You must upgrade the secondary NSX Manager appliances before proceeding with any other part of the upgrade.

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: