6.0.2

Table 2‑4. Ports Required for Communication Between Components (Continued)
Port Protocol Description Required for
Used for Node-to-
Node
Communication
5480 TCP vCenter Server Appliance Web user
interface (HTTPS)
Appliance
deployments of
n
vCenter Server
n
Platform Services
Controller
No
6500 TCP/UDP ESXi Dump Collector port
I You can change this port
number during the vCenter Server
installations on Windows.
Windows
installations and
appliance
deployments of
vCenter Server
No
6501 TCP Auto Deploy service
I You can change this port
number during the vCenter Server
installations on Windows.
Windows
installations and
appliance
deployments of
vCenter Server
No
6502 TCP Auto Deploy management
I You can change this port
number during the vCenter Server
installations on Windows.
Windows
installations and
appliance
deployments of
vCenter Server
No
7444 TCP Secure Token Service Windows
installations and
appliance
deployments of
Platform Services
Controller
n
vCenter Server to
Platform Services
Controller
n
Platform Services
Controller to
vCenter Server
9443 TCP vSphere Web Client HTTPS Windows
installations and
appliance
deployments of
vCenter Server
No
11711 TCP vCenter Single Sign-On LDAP - For backward
compatibility with
vSphere 5.5 only.
vCenter Single Sign-
On 5.5 to
Platform Services
Controller 6.0
11712 TCP vCenter Single Sign-On LDAPS - For backward
compatibility with
vSphere 5.5 only.
vCenter Single Sign-
On 5.5 to
Platform Services
Controller 6.0
Custom Ports
If you congured custom ports for Auto Deploy or vSphere ESXi Dump Collector, these custom ports are
migrated to the conguration of the target vCenter Server Appliance. For example, if you congured Auto
Deploy to use port 6545, the conguration is migrated to the target vCenter Server Appliance. Other custom
ports are not supported in the vCenter Server Appliance.
Chapter 2 vCenter Server Appliance Requirements
VMware, Inc. 15