6.5.1

Table 4‑3. Ports Required for Communication Between Components (Continued)
Port Protocol Description Required for
Used for Node-to-Node
Communication
11711 TCP vCenter Single Sign-On LDAP
For backward compatibility with vSphere
5.5 only.
Windows installations
and appliance
deployments of
Platform Services
Controller
During upgrade from
vSphere 5.5 only.
vCenter Single Sign-On
5.5 to
Platform Services
Controller 6.5
11712 TCP vCenter Single Sign-On LDAPS
For backward compatibility with vSphere
5.5 only.
Windows installations
and appliance
deployments of
Platform Services
Controller
During upgrade from
vSphere 5.5 only.
vCenter Single Sign-On
5.5 to
Platform Services
Controller 6.5
To configure the vCenter Server system to use a different port to receive vSphere Web Client data, see
the vCenter Server and Host Management documentation.
For more information about firewall configuration, see the vSphere Security documentation.
DNS Requirements for vCenter Server and
Platform Services Controller on Windows
You install or upgrade vCenter Server, like any other network server, on a host machine with a fixed IP
address and well-known DNS name, so that clients can reliably access the service.
Assign a static IP address and host name to the Windows server that will host the vCenter Server system.
This IP address must have a valid (internal) domain name system (DNS) registration. When you install
vCenter Server and the Platform Services Controller, you must provide the fully qualified domain name
(FQDN) or the static IP of the host machine on which you are performing the install or upgrade. The
recommendation is to use the FQDN.
Ensure that DNS reverse lookup returns an FQDN when queried with the IP address of the host machine
on which vCenter Server is installed. When you install or upgrade vCenter Server, the installation or
upgrade of the Web server component that supports the vSphere Web Client fails if the installer cannot
look up the fully qualified domain name of the vCenter Server host machine from its IP address. Reverse
lookup is implemented using PTR records.
If you plan to use an FQDN for the virtual machine or physical server, you must verify that the FQDN is
resolvable.
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
vSphere Installation and Setup
VMware, Inc. 284