After you convert your vCenter to subscription, you can manage your vCenter updates from the VMware Cloud Console in a single click. With the pre-update checks significantly reducing the operational effort and maintenance window, you can plan for updates more frequently and keep your vCenter up-to-date with all new features.
- Temporary network: The network for communication between the new appliance and the appliance you want to update.
- Troubleshooting network: The network for troubleshooting any update issues if the vCenter is unreachable.
- Ensure that your vSphere environment meets all the requirements. See System Requirements for vSphere+.
- Ensure that the Active Directory (AD) domain that contains the vCenter roles and privileges is federated with VMware Cloud. You must implement the connector-based authentication setup. See the Setting Up Enterprise Federation with VMware Cloud Services Guide.
- For vCenter instances in high availability (HA) mode:
- Only vCenter HA instances with Automatic configurations are supported. vCenter HA instances with Manual configurations are not supported.
- If the vCenter version is earlier than 8.0 Update 2, then the active vCenter, passive vCenter, and VMware Cloud Gateway must be in the same cluster. If the vCenter version is 8.0 Update 2 or later, then the active vCenter, passive vCenter, and VMware Cloud Gateway can be in different clusters.
- Ensure that the vCenter including the management vCenter is on the latest 7.x or 8.x patch.
- Download the latest version of the vCenter by using the Downloads option in the VMware Cloud Console. See Download Software Binaries.
- Update your vCenter to the latest version. See the vCenter Server Upgrade documentation.
- Depending on the upgrade path of your vCenter version, you might have to back up and restore the vCenter after the update. See https://kb.vmware.com/s/article/87864.
- If you plan to choose DHCP for IP assignment, ensure that the MAC Address Changes policy is set for all the hosts in the management cluster. See Configure the Security Policy.
- Verify that the network configuration meets the following requirements:
Network Requirement Temporary Network The temporary network and the vCenter network must be in the same subnet. Troubleshooting Network
- Choose a network that is not already connected to the vCenter for other purposes, such as backup and restore.
- The troubleshooting network must be on a subnet and VLAN different than the vCenter and VMware Cloud Gateway.
- The troubleshooting network must be routable from the vCenter network.
- Log in to the VMware Cloud Console at https://vmc.vmware.com.
- Use either of the following methods to navigate to the vCenter Updates tab:
- In the Enable Updates for vCenter notification, click Enable Updates.
- Go to Inventory, select the vCenter, and then click vCenter Updates.
- If the vCenter is self-managed, enter the network configuration details for both temporary network and troubleshooting network.
If the vCenter is configured for HA, for the temporary network IP assignment, select Static.
- Click Apply.
- vSphere+ creates a management resource pool and reserves the required hardware in the management cluster for vCenter updates. The vCenter and VMware Cloud Gateway are moved to the management resource pool. Do not change these management resource pool configurations. Do not move the vCenter out of this cluster.
- vSphere+ reserves the required CPU and memory in vCenter and VMware Cloud Gateway VMs for future updates.