When you upgrade the NSX instances in the SDDC, you upgrade each functional group of components of the NSX deployment in Region A and Region B.

About this task

Upgrading NSX for vSphere is a multi-step operation where you must upgrade the NSX Managers paired instances for Cross-vCenter Networking and Security, the NSX Controller nodes, the ESXi VIBs, and the NSX Edge devices. This upgrade operation is split between the management cluster pairs and the shared edge and compute cluster pairs.

You might perform the upgrades of these components in different maintenance windows.

Table 1. NSX Nodes in the SDDC

Region

Role

IP Address

FQDN

Region A

NSX Manager for the management cluster that is running as primary

172.16.11.65

sfo01m01nsx01.sfo01.rainpole.local

NSX Controller 1 for the management cluster

172.16.11.118

-

NSX Controller 2 for the management cluster

172.16.11.119

-

NSX Controller 3 for the management cluster

172.16.11.120

-

NSX Manager for the shared edge and compute cluster that is running as primary

172.16.11.66

sfo01w01nsx01.sfo01.rainpole.local

NSX Controller 1 for the shared edge and compute cluster

172.16.31.118

-

NSX Controller 2 for the shared edge and compute cluster

172.16.31.119

-

NSX Controller 3 for the shared edge and compute cluster

172.16.31.120

-

Region B

NSX Manager for the management cluster that is running as secondary

172.17.11.65

lax01m01nsx01.lax01.rainpole.local

NSX Manager for the shared edge and compute cluster that is running as secondary

172.17.11.66

lax01w01nsx01.lax01.rainpole.local

Note:

VMware Validated Design 4.1 introduces a new convention for host and object names in the SDDC. The step-by-step upgrade guidance uses the new names for both the pre- and post-upgrade SDDC setups. For information about the new convention, see Mapping Component Names Between Versions 4.0 and 4.1 of VMware Validated Design.

Important:

You might receive a number of false alerts from vRealize Operations Manager and vRealize Log Insight during this upgrade procedure of NSX components.

Prerequisites

  • Download the NSX update bundle VMware-NSX-Manager-upgrade-bundle-6.3.x-xxxxxxx.tar.gz on the Windows host that has access to your data center.

  • Review Operational Impacts of NSX Upgrade from NSX Upgrade Guide to understand the impact that each component might have on your VMware Validated Design environment.

  • Verify that any virtual networking integration within the environment has been quiesced of all activities, including but not limited to: users ordering new virtual machines backed by virtual wires over the Cloud Management Platform (CMP); third-party integration that automates the ordering or deployment of new virtual machines that are backed by virtual wires; and administrators manually creating new NSX-based components.

    Without quiescing the environment, rollback operations might be disrupted by generated orphaned objects. You might also have to extend the time of the maintenance windows.

  • Validate the NSX Manager file system usage, and perform a cleanup if file system usage is at 100 percent.

    1. Open an SSH connection using the admin account to the NSX Manager instance you are upgrading and run the show filesystems command to show the filesystem usage.

    2. If the filesystem usage is at 100 percent, enter Privileged mode and purge the logs by running the following commands.

      enable
      purge log manager
      purge log system
      
    3. Reboot the NSX Manager appliance for the log cleanup to take effect.

  • Back up the NSX configuration and download technical support logs before upgrading. See Backing Up and Restoring the NSX Instances in Region A and Backing Up and Restoring the NSX Instances in Region B from the VMware Validated Design Backup and Restore documentation.

  • Take a backup of the NSX Manager pair, both the primary and secondary, and of NSX Controller virtual machines. For more information, see Back Up and Restore NSX Manager from NSX Upgrade Guide.

  • Verify that all of the controllers are in normal, connected state.

  • Get the current version of the NSX VIBs on the hosts in the management cluster and in the shared edge and compute cluster.

    1. Log in to one of the hosts in the cluster via the ESXi Host Client, and using the Packages section, search for esx-v.

    2. Note the current version of the following VIBs.

      • esx-vsip

      • esx-vxlan

What to do next

Verify that NSX components function flawlessly after the upgrade. See Validate NSX for vSphere in the Operational Verification documentation.