Follow the workflow for upgrading NSX Federation appliances depending on the version you are upgrading from.

Starting with NSX 4.1.1 and later, Global Manager (GM) and Local Manager (LM) upgrades can occur in any order. The GM and LM continue to sync if they are at different versions between 4.0 and 4.1. If you are upgrading from releases prior to NSX 4.1.1, you must first manually upgrade the standby GM cluster from the GM UI, followed by the active GM cluster. Both active and standby Global Managers must have the same version.

Also starting with NSX 4.1.1, Global Managers support the same interoperability as Local Managers, for example, from 3.2.3 to 4.1.2. Refer to the Local Manager (LM) and Global Manager (GM) Upgrade table for LM and GM version compatibility. Prior to NSX 4.1.1 interoperability was N+1, and N-1. Starting with NSX 4.1.1 and later, you can upgrade from NSX 3.2 to 4.1.2 to support the following releases (N+2 and N-2).

For example:
  • If you have 3.2 LMs and 3.2 GMs, all can be upgraded to NSX 4.0 and 4.1.2, but not NSX 4.1.0.
  • If you have 3.2 LMs and 4.1.2 the standby GM, then the active GM, LMs cannot be upgraded to NSX 4.0. Upgrade them directly to NSX 4.1.2.
Note: Upgrade from NSX 3.2.2 or 3.2.3 to 4.0.1 or 4.0.1.1 is not supported. The reason is that the General Availability (GA) of NSX 3.2.2 occurred after the GA of NSX versions 4.0.1 and 4.0.1.1. Some capabilities and important fixes in NSX 3.2.2 might not be available in versions 4.0.1 or 4.0.1.1 due to the chronological order in which these versions were released. Instead, you can upgrade from NSX 3.2.2 or 3.2.3 to 4.1.2.
The Local Manager (LM) and Global Manager (GM) Upgrade table shows the software and the valid versions that will continue to sync with both the earlier and the latest LM and GM versions.
Table 1. Local Manager (LM) and Global Manager (GM) Upgrade
From \ To 4.1.0 4.1.x
3.1 First upgrade to 3.2 First upgrade to 3.2
3.2 Not applicable. Use case not supported because an LM 3.2 cannot be managed by a GM 4.1.0. Note: After 3.2.2 may be upgraded to 4.1.1. Supported*
4.0 Supported* Supported*
4.1.0 Not applicable Supported*
4.1.1 Not applicable Supported*

For table asterisk (*), refer to the Interoperability Matrix for the supported minor release versions at https://interopmatrix.vmware.com/Upgrade?productId=912.

Upgrade VMware Cloud Foundation Deployments with NSX Federation

The VMware Cloud Foundation™ Deployments with Local Manager (LM) and Global Manager (GM) Upgrade table shows the software and the valid versions that are on the upgrade path for NSX Federation in a VMware Cloud Foundation (VCF) environment.

Note: For prior releases of VMware Cloud Foundation, you must first upgrade to VCF 4.5.x.
Table 2. VMware Cloud Foundation Deployments with Local Manager (LM) and (GM) Upgrade
From/To Steps

VCF 4.5 to 5.0

LM 3.2.1.2 to 4.1.0.2

GM 3.2.1.2 to 4.1.0.2
  1. Manually upgrade the standby GM, then the active GM from 3.2.1.2 to 4.0.1.1. GM 4.0.1.1 is compatible with VCF 4.5 with LM 3.2.1.2.
  2. Upgrade from VCF 4.5 to 5.0 with SDDC Manager, which upgrades from LM 3.2.1.2 to 4.1.0.2.
  3. Manually upgrade the standby GM, then the active GM from 4.0.1.1 to 4.1.0.2.

VCF 4.5.1 to 5.0

LM 3.2.2.1 to 4.1.1

GM 3.2.2.1 to 4.1.1
  1. Manually upgrade the standby GM, then the active GM from 3.2.2.1 to 4.1.1. GM 4.1.1 is compatible with VCF 4.5.1 with LM 3.2.2.1.
  2. Upgrade from VCF 4.5.1 to 5.0 with SDDC Manager, which upgrades from LM 3.2.2.1 to 4.1.0.2.
  3. Apply the VCF async patch tool to upgrade from LM 4.1.0.2 to 4.1.1. Refer to https://docs.vmware.com/en/VMware-Cloud-Foundation/services/ap-tool/GUID-49818DF1-94EA-4C85-8CB6-6EFFCE5F8060.html

VCF 4.5.1 to 5.0

LM 3.2.2.1 to 4.1.2.1

GM 3.2.2.1 to 4.1.2.1
  1. Manually upgrade the standby GM, then the active GM from 3.2.2.1 to 4.1.2.1. GM 4.1.2.1 is compatible with VCF 4.5.1 with LM 3.2.2.1.
  2. Upgrade from VCF 4.5.1 to 5.0 with SDDC Manager, which upgrades from LM 3.2.2.1 to 4.1.0.2.
  3. Apply the VCF async patch tool to upgrade from LM 4.1.0.2 to 4.1.2.1. Refer to https://docs.vmware.com/en/VMware-Cloud-Foundation/services/ap-tool/GUID-49818DF1-94EA-4C85-8CB6-6EFFCE5F8060.html

VCF 4.5.2 to 5.0

LM 3.2.3.1 to 4.1.x

GM 3.2.3.1 to 4.1.x

 No upgrade path.

VCF 4.5 to 5.1

LM 3.2.1.2 to 4.1.2.1

GM 3.2.1.2 to 4.1.2.1
  1. Manually upgrade the standby GM, then the active GM from 3.2.1.2 to 4.0.1.1. GM 4.0.1.1 is compatible with VCF 4.5 with LM 3.2.1.2.
  2. Upgrade from VCF 4.5 to 5.1 with SDDC Manager, which upgrades from LM 3.2.1.2 to 4.1.2.1.
  3. Manually upgrade the standby GM, then the active GM from 4.0.1.1 to 4.1.2.1.

VCF 4.5.1 to 5.1

LM 3.2.2.1 to 4.1.2.1

GM 3.2.2.1 to 4.1.2.1
  1. Manually upgrade the standby GM, then the active GM from 3.2.2.1 to 4.1.2.1. GM 4.1.2.1 is compatible with VCF 4.5.1 with LM 3.2.2.1.
  2. Upgrade from VCF 4.5.1 to 5.1 with SDDC Manager, which upgrades from LM 3.2.2.1 to 4.1.2.1.

VCF 4.5.2 to 5.1

LM 3.2.3.1 to 4.1.2.1

GM 3.2.3.1 to 4.1.2.1
  1. Manually upgrade the standby GM, then the active GM from 3.2.3.1 to 4.1.2.1. GM 4.1.2.1 is compatible with VCF 4.5.2 with LM 3.2.3.1.
  2. Upgrade from VCF 4.5.2 to 5.1 with SDDC Manager, which upgrades from LM 3.2.3.1 to 4.1.2.1.