After you subscribe your vCenter to vSphere+, you can manage your vCenter updates from the VMware Cloud Console. The pre-update checks in the VMware Cloud Console significantly reduces the operational effort and the maintenance window. Therefore, you can plan for updates more frequently and keep your vCenter up-to-date with the latest features.
Note: Use the
VMware Cloud Console only to update
vCenter instances that are not managed by VxRail Manager. If you are using VxRail with VxRail Manager managing the
vCenter, use VxRail Manager to update the
vCenter.
To manage updates for your
vCenter from the
VMware Cloud Console, as a one-time activity, you must provide the following network configuration details for each
vCenter:
- 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.
Prerequisites
- Ensure that your vSphere environment meets all the requirements. See vSphere+ Requirements.
- Ensure that you have the Cloud Administrator role.
- For vCenter instances in high availability (HA) mode:
- You must use only vCenter HA instances with Automatic configurations. 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.
- For vCenter instances that are not self-managed:
- Ensure that you first enable updates for the vCenter that manages VMware Cloud Gateway before enabling updates for other vCenter instances connected to the same gateway.
- Ensure that the management vCenter manages its own VM.
- 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 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.
- Ensure 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.
Procedure
Results
- 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.
Note: 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.
What to do next
- Monitor your vSphere inventory, and explore vSphere+ services. See Using and Managing vSphere+.
- Whenever an update is available for your vCenter, vSphere+ displays a notification. You can update your vCenter from the VMware Cloud Console. See Update Your vCenter.