Follow the workflow for upgrading NSX Federation appliances depending on the version you are upgrading from.
Upgrading your NSX Federation Deployment from NSX-T Data Center 3.1 to NSX-T Data Center 3.2
First upgrade the Local Manager (LM) appliances from 3.1 to 3.2. The Global Manager (GM) and Local Managers continue to sync if they are at different versions between 3.1 and 3.2. Upgrade the
Global Manager after the LM appliances. When upgrading the
Global Manager, first upgrade the standby GM cluster, immediately followed by active GM cluster upgrade. Both active and standby
Global Managers must have the same version.
Note: During upgrade, the Global Manager version 3.1 can continue to sync with Local Managers already added to it that have been upgraded to version 3.2. However, if you change the LM certificate or add a new Local Manager version 3.2, to the Global Manager version 3.1, the version mismatch causes communication problems between the Global Manager and Local Manager. Do not change the LM certificate or add a new Local Manager version 3.2 to a Global Manager version 3.1. Before you change the LM certificate or add a new Local Manager version 3.2, upgrade the Global Manager to 3.2.
| Task | Instructions |
|---|---|
| Review the upgrade checklist before you begin. | NSX-T Data Center Upgrade Checklist |
| Upgrade each Local Manager first. | Upgrading NSX-T Data Center. |
| Upgrade the Global Manager appliance after all Local Managers are upgraded to NSX-T Data Center 3.2.When upgrading the Global Manager, first upgrade the standby GM cluster, followed by active GM cluster upgrade. |
Note: When upgrading your NSX Federation deployment from
NSX-T Data Center 3.2.1 or later to
NSX-T Data Center 3.2.x, the upgrade is independent of the order of upgrade of the
Global Manager and
Local Manager appliances. The upgrade is also independent of the order of upgrade of the active and standby
Global Manager clusters.
After rolling back or restoring a
Global Manager node, make the following API call on each of the LM sites to force a sync between all LMs and the
Global Manager:
POST <LM>/infra/full-sync-action?action=request_full_sync
Upgrading your NSX Federation Deployment from NSX-T Data Center 3.0.2 to NSX-T Data Center 3.1.0
First upgrade the Local Manager appliances from 3.0.2 to 3.1.0. The Global Manager and Local Managers continue to sync if they are at different versions between 3.0.2 and 3.1.0. Upgrade the Global Manager last.
Note: During upgrade, the Global Manager at version 3.0.2 can continue to sync with Local Managers already added to it that have been upgraded to version 3.1.0. However, if you add a new Local Manager at version 3.1.0 to the Global Manager at version 3.0.2, the version mismatch causes communication problems between the Global Manager and Local Manager. Do not add a new Local Manager at version 3.1.0 to a Global Manager at version 3.0.2. To add a new Local Manager at version 3.1.0, first upgrade the Global Manager to 3.1.0.
| Task | Instructions |
|---|---|
| Review the upgrade checklist before you begin. | NSX-T Data Center Upgrade Checklist |
| Upgrade each Local Manager first.
Note: While upgrading Local Managers from the Global Manager, you can change the Local Manager's orchestrator node but it takes some time for the change to reflect on the Global Manager UI.
|
Upgrading NSX-T Data Center. |
| Upgrade the Global Manager appliance after all Local Managers are upgraded to NSX-T Data Center 3.1.0. |
