The upgrade of the appliance is a migration of the old version to the new version, which includes deploying a new appliance of version 8.0. You can deploy the new vCenter Server appliance on an ESXi host 6.7 or later, or on a vCenter Server instance 6.7 or later. Your system must also meet specific software and hardware requirements.
When you use Fully Qualified Domain Names, verify that the client machine from which you are deploying the appliance and the network on which you are deploying the appliance use the same DNS server.
Before you deploy the new appliance, synchronize the clocks of the target server and all vCenter Server instances on the vSphere network. Unsynchronized clocks might result in authentication problems and can cause the installation to fail or prevent the appliance services from starting. See Synchronizing Clocks on the vSphere Network.
Hardware Requirements for the vCenter Server Appliance
When you deploy the vCenter Server appliance, you can select to deploy an appliance that is suitable for the size of your vSphere environment. The option that you select determines the number of CPUs and the amount of memory for the appliance.
The hardware requirements for a vCenter Server appliance depend on the size of your vSphere inventory.
| Number of vCPUs | Memory | |
|---|---|---|
| Tiny environment (up to 10 hosts or 100 virtual machines) | 2 | 14 GB |
| Small environment (up to 100 hosts or 1,000 virtual machines) | 4 | 21 GB |
| Medium environment (up to 400 hosts or 4,000 virtual machine) | 8 | 30 GB |
| Large environment (up to 1,000 hosts or 10,000 virtual machines) | 16 | 39 GB |
| X-Large environment (up to 2,000 hosts or 35,000 virtual machines) | 24 | 58 GB |
Storage Requirements for the vCenter Server Appliance
When you deploy the vCenter Server appliance, the ESXi host or DRS cluster on which you deploy the appliance must meet minimum storage requirements. The required storage depends not only on the size of the vSphere environment and the storage size, but also on the disk provisioning mode.
The storage requirements are different for each vSphere environment size and depend on your database size requirements.
| Default Storage Size | Large Storage Size | X-Large Storage Size | |
|---|---|---|---|
| Tiny environment (up to 10 hosts or 100 virtual machines) | 579 GB | 2019 GB | 4279 GB |
| Small environment (up to 100 hosts or 1,000 virtual machines) | 694 GB | 2044 GB | 4304 GB |
| Medium environment (up to 400 hosts or 4,000 virtual machine) | 908 GB | 2208 GB | 4468 GB |
| Large environment (up to 1,000 hosts or 10,000 virtual machines) | 1358 GB | 2258 GB | 4518 GB |
| X-Large environment (up to 2,000 hosts or 35,000 virtual machines) | 2283 GB | 2383 GB | 4643 GB |
Software Requirements for the vCenter Server Appliance
The VMware vCenter Server appliance can be deployed on ESXi 6.7 hosts or later, or on vCenter Server instances 6.7 or later.
You can deploy the vCenter Server appliance using the GUI or CLI installer. You run the installer from a network client machine that you use to connect to the target server and deploy the appliance on the server. You can connect directly to an ESXi 6.7 host on which to deploy the appliance. You can also connect to a vCenter Server 6.7 instance to deploy the appliance on an ESXi host or DRS cluster that resides in the vCenter Server inventory.
For information about the requirements for network client machine, see System Requirements for the vCenter Server Installer.
Required Ports for vCenter Server
The vCenter Server system must be able to send data to every managed host and receive data from the vSphere Client. To enable migration and provisioning activities between managed hosts, the source and destination hosts must be able to receive data from each other through predetermined TCP and UDP ports.
vCenter Server is accessed through predetermined TCP and UDP ports. If you manage network components from outside a firewall, you might be required to reconfigure the firewall to allow access on the appropriate ports. For the list of all supported ports and protocols in vSphere, see the VMware Ports and Protocols Tool™ at https://ports.vmware.com.
During installation, if a port is in use or is blocked using a denylist, the vCenter Server installer displays an error message. You must use another port number to proceed with the installation. There are internal ports that are used only for inter-process communication.
VMware uses designated ports for communication. Additionally, the managed hosts monitor designated ports for data from vCenter Server. If a built-in firewall exists between any of these elements, the installer opens the ports during the installation or upgrade process. For custom firewalls, you must manually open the required ports. If you have a firewall between two managed hosts and you want to perform source or target activities, such as migration or cloning, you must configure a means for the managed hosts to receive data.
To configure the vCenter Server system to use a different port to receive vSphere Client data, see the vCenter Server and Host Management documentation.
DNS Requirements for the vCenter Server Appliance
When you deploy the new vCenter Server appliance, in the temporary network settings, you can assign a static IP address and an FQDN that is resolvable by a DNS server. After the upgrade, the appliance frees this static IP address and assumes the network settings of the old appliance.
When you deploy the vCenter Server appliance with a static IP address, you ensure that in case of system restart, the IP address of the appliance remains the same.
Before you deploy the vCenter Server appliance with a static IP address, you must verify that this IP address has a valid internal domain name system (DNS) registration.
When you deploy the vCenter Server appliance, the installation of the web server component that supports the vSphere Client fails if the installer cannot look up the fully qualified domain name (FQDN) for the appliance from its IP address. Reverse lookup is implemented using PTR records.
If you plan to use an FQDN for the appliance system name, you must verify that the FQDN is resolvable by a DNS server, by adding forward and reverse DNS A records.
nslookup -nosearch -nodefname FQDN_or_IP_address
If you use DHCP instead of a static IP address for the vCenter Server appliance, verify that the appliance name is updated in the domain name service (DNS). If you can ping the appliance name, the name is updated in DNS.
Ensure that the ESXi host management interface has a valid DNS resolution from the vCenter Server and all vSphere Client instances. Ensure that the vCenter Server has a valid DNS resolution from all ESXi hosts and vSphere Client.
vSphere Client Software Requirements
Use of the vSphere Client requires a supported web browser.
