6.2

Table 2‑7. Incoming Ports for the vRealize Appliance
Port Protocol Comments
22 TCP Optional. SSH.
80 TCP Optional. Redirects to 443.
111 TCP, UDP RPC
443 TCP Access to the vRealize Automation console and API calls.
5480 TCP Access to virtual appliance Web management interface
5480 TCP Used by Management Agent
5488, 5489 TCP Internal. Used by vRealize Appliance for updates.
5672 TCP RabbitMQ messaging
8230, 8280, 8281 TCP Internal vRealize Orchestrator instance
8444 TCP Console proxy communication for vSphere VMware Remote Console connections
Table 2‑8. Outgoing Ports for the vRealize Appliance
Port Protocol Comments
25, 587 TCP, UDP SMTP for sending outbound notification emails
53 TCP, UDP DNS
67, 68, 546, 547 TCP, UDP DHCP
80 TCP Optional. For fetching software updates. Updates can be downloaded separately and
applied.
110, 995 TCP, UDP POP for receiving inbound notification emails
143, 993 TCP, UDP IMAP for receiving inbound notification emails
123 TCP, UDP Optional. For connecting directly to NTP instead of using host time.
443 TCP IaaS Manager Service over HTTPS
Communication with virtualization hosts over HTTPS
902 TCP ESXi network file copy operations and for VMware Remote Console (VMRC)
connections
5432 TCP, UDP Optional. For communicating with an Appliance Database.
7444 TCP Communication with SSO service over HTTPS
8281 TCP Optional. For communicating with an external vRealize Orchestrator instance .
Other ports may be required by specific vRealize Orchestrator plugins that communicate with external
systems. For more information, see the documentation for the vRealize Orchestrator plugin.
Infrastructure as a Service
The ports in the tables Incoming Ports for Infrastructure as a Service Components and Outgoing Ports for
Infrastructure as a Service must be available for use by the IaaS Windows Server.
Installation and Configuration
VMware, Inc. 28