You must upgrade the management domain before upgrading VI workload domains in your environment. In order to upgrade to VMware Cloud Foundation 4.3, the management domain must be at VMware Cloud Foundation 4.2.1, 4.2, 4.1.0.1, or 4.1.
The components in the management domain must be upgraded in the following order:
- SDDC Manager and VMware Cloud Foundation services.
- vRealize Suite Lifecycle Manager, vRealize Suite products, and Workspace ONE Access (if applicable).
- vRealize Suite Lifecycle Manager
- vRealize Log Insight
- vRealize Operations
- vRealize Automation
- Workspace ONE Access
Note: Note: All vRealize Suite upgrades are sequential. You may have to download and apply multiple bundles, depending on the current product versions in your environment. - NSX-T Data Center.
- vCenter Server.
- vSAN witness host (If you have stretched clusters in your environment).
- VxRail Manager and ESXi.
Component | Additional Information |
---|---|
SDDC Manager and VMware Cloud Foundation services | The VMware Cloud Foundation software bundle to be applied depends on the current version of your environment.
If you upgrading from
VMware Cloud Foundation 4.2.1, 4.2, or 4.1.0.1, you must apply the following bundles to the management domain:
If you upgrading from VMware Cloud Foundation 4.1, you apply the VMware Cloud Foundation Update bundle, which upgrades SDDC Manager, LCM, and VMware Cloud Foundation services, and also applies the configuration drift. |
vRealize Log Insight | After upgrading vRealize Log Insight, upgrade the vRealize Log Insight content packs. Content packs are plugins to vRealize Log Insight that provide pre-defined knowledge about specific types of events such as log messages. You must upgrade to the latest content packs for use with vRealize Log Insight.
|
Workspace ONE Access | If you had Workspace ONE Access in your pre-upgrade environment, you must upgrade it using vRealize Suite Lifecycle Manager.
|
NSX-T Data Center |
Upgrading
NSX-T Data Center involves the following components:
The upgrade wizard provides some flexibility when upgrading NSX-T Data Center for workload domains. By default, the process upgrades all NSX Edge clusters in parallel, and then all host clusters in parallel. Parallel upgrades reduce the overall time required to upgrade your environment. You can also choose to upgrade NSX Edge clusters and host clusters sequentially. The ability to select clusters allows for multiple upgrade windows and does not require all clusters to be available at a given time.
The
NSX Manager cluster is upgraded only if the
Upgrade all host clusters setting is enabled on the NSX-T Host Clusters tab. New features introduced in the upgrade are not configurable until the
NSX Manager cluster is upgraded.
|
vCenter Server |
Take a file-based backup of the
vCenter Server appliance before starting the upgrade. See
Manually Back Up vCenter Server.
Note: After taking a backup, do not make any changes to the
vCenter Server inventory or settings until the upgrade completes successfully.
If the upgrade fails, resolve the issue and retry the failed task. If you cannot resolve the issue, restore vCenter Server using the file-based backup. See Restore vCenter Server. Once the upgrade successfully completes, use the vSphere Client to change the vSphere DRS Automation Level setting back to the original value for each vSphere cluster that is managed by the vCenter Server. See KB 87631 for information about using VMware PowerCLI to change the vSphere DRS Automation Level. |
vSAN witness host | See Upgrade vSAN Witness Host for VMware Cloud Foundation. |
ESXi | By default, the upgrade process upgrades the ESXi hosts in all clusters in a domain in parallel. If you have multiple clusters in the management domain or in a VI workload domain, you can select which clusters to upgrade. You can also choose to upgrade the clusters in parallel or sequentially. If you are using external (non-vSAN) storage, updating and patching is a manual task and falls outside of SDDC Manager lifecycle management. To ensure supportability after an ESXi upgrade, consult the vSphere HCL and your storage vendor. |