The management domain in your environment must be upgraded before you upgrade VI workload domains. In order to upgrade to VMware Cloud Foundation 4.4/4.4.1, all VI domains must be at VMware Cloud Foundation 4.1 or higher. If any VI workload domain is at a version lower than 4.1, you must upgrade it to 4.1 and then upgrade to 4.4/4.4.1.
- NSX-T Data Center.
- vCenter Server.
- vSAN witness host (If you have stretched clusters in your environment).
- VxRail Manager and ESXi.
- Workload Management on clusters that have vSphere with Tanzu. Workload Management can be upgraded through vCenter Server. See Working with vSphere Lifecycle Manager.
Component | Additional Information |
---|---|
NSX-T Data Center |
Upgrading
NSX-T Data Center involves the following components:
VI workload domains can share the same NSX Manager cluster and NSX Edge clusters. When you upgrade these components for one VI workload domain, they are upgraded for all VI workload domains that share the same NSX Manager or NSX Edge cluster. You cannot perform any operations on the VI workload domains while NSX-T Data Center is being upgraded. 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 | If your VI workload domain contains Workload Management enabled clusters, ensure that Workload Management is at version 1.17 or higher. If Workload Management is at a lower version, upgrade Workload Management to at least version 1.17 before upgradingvCenter 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. |
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. |