You must upgrade all secondary NSX Manager appliances before upgrading any other NSX components.

About this task

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 NSX Manager upgrade in a cross-vCenter NSX environment, do not make any changes to universal objects until the primary and all secondary NSX Managers are upgraded. This includes create, update, or delete of universal objects, and operations involving universal objects (for example, apply a universal security tag to a VM).

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.

Prerequisites

  • 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.

    1. Login to NSX Manager and run show filesystems to show the filesystem usage.

    2. If the usage is 100 percent, run the purge log manager and purge log system commands.

    3. Reboot the NSX Manager appliance for the log cleanup to take effect.

  • Verify the NSX Manager virtual appliance reserved memory meets the system requirements before upgrading.

    See System Requirements for NSX.

  • If you have Data Security in your environment, uninstall it before upgrading NSX Manager. See Uninstall NSX Data Security. Data Security has been removed from NSX 6.3.x.

  • 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.

  • You must upgrade all NSX Managers in a cross-vCenter NSX environment in the same maintenance window.

  • Plan to upgrade all NSX Managers that are connected to vCenter Server systems using the same SSO server (including vCenter Server systems in Enhanced Linked Mode) in the same maintenance window. If you cannot, see https://kb.vmware.com/kb/2127061 for a workaround.

Procedure

  1. Log in to the NSX Manager virtual appliance.
  2. From the home page, click Upgrade.
  3. 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.

  4. 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.

  5. Log in to the NSX Manager virtual appliance again, and from the home page click Upgrade. 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

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.

What to do next

Upgrade NSX Controller Cluster in Cross-vCenter NSX