8.0
Table Of Contents
- vCenter Server Installation and Setup
- Contents
- About vCenter Server Installation and Setup
- Introduction to vSphere Installation and Setup
- Deploying the vCenter Server Appliance
- File-Based Backup and Restore of vCenter Server
- Image-Based Backup and Restore of a vCenter Server Environment
- After You Deploy the vCenter Server Appliance
- Log In to vCenter Server by Using the vSphere Client
- Install the VMware Enhanced Authentication Plug-in
- Repoint vCenter Server to Another vCenter Server in a Different Domain
- Repoint a Single vCenter Server Node to an Existing Domain without a Replication Partner
- Repoint a vCenter Server Node to an Existing Domain with a Replication Partner
- Repoint a vCenter Server Node to a New Domain
- Syntax of the Domain Repoint Command
- Understanding Tagging and Authorization Conflicts
- vCenter Server Domain Repoint License Considerations
- Troubleshooting vCenter Server Installation or Deployment
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 vCenter Server appliance, similar to any network server, you can assign a
fixed IP address and an FQDN that is resolvable by a DNS server so that clients can reliably access
the service.
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.
You can use the nslookup command to verify that the DNS reverse lookup service returns an
FQDN when queried with the IP address and to verify that the FQDN is resolvable.
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.
vCenter Server Installation and Setup
VMware, Inc. 19