Ports on the vRealize Automation appliance are usually preconfigured in the OVF or OVA that you deploy.

The following ports are used by the vRealize Automation appliance.

Table 1. Incoming Ports

Port

Protocol

Comments

22

TCP

Optional. Access for SSH sessions

80

TCP

Optional. Redirects to 443

443

TCP

Access to the vRealize Automation console and API calls

443

TCP

Access for machines to download the guest agent and software bootstrap agent

5480

TCP

Access to the virtual appliance Web management interface

5480

TCP

Used by the Management Agent

5488, 5489

TCP

Internally used by the vRealize Automation appliance for updates

4369, 25672, 5671, 5672

TCP

RabbitMQ messaging

8230, 8280, 8281, 8283

TCP

Internal vRealize Orchestrator instance.

8444

TCP

Console proxy communication for vSphere VMware Remote Console connections.

Table 2. Outgoing Ports

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

Communication with IaaS Manager Service and infrastructure endpoint hosts over HTTPS

443

TCP

Communication with the software bootstrap agent over HTTPS

902

TCP

ESXi network file copy operations and VMware Remote Console connections.

5050

TCP

Optional. For communicating with vRealize Business for Cloud.

5432

TCP, UDP

Optional. For communicating with an Appliance Database

8281

TCP

Optional. For communicating with an external vRealize Orchestrator instance

Other ports might be required by specific vRealize Orchestrator plug-ins that communicate with external systems. See the documentation for the vRealize Orchestrator plug-in.