Ports on the IaaS Windows servers must be configured before vRealize Automation installation.

Open ports between all IaaS Windows servers according to the following tables. Include the server that hosts the SQL database, if it is separate from IaaS. Alternatively, if site policies allow, you may disable firewalls between IaaS Windows servers and SQL Server.

Table 1. Incoming Ports

Port

Protocol

Component

Comments

443

TCP

Manager Service

Communication with IaaS components and vRealize Automation appliance over HTTPS

443

TCP

vRealize Automation appliance

Communication with IaaS components and vRealize Automation appliance over HTTPS

443

TCP

Infrastructure Endpoint Hosts

Communication with IaaS components and vRealize Automation appliance over HTTPS. Typically, 443 is the default communication port for virtual and cloud infrastructure endpoint hosts, but refer to the documentation provided by your infrastructure hosts for a full list of default and required ports

1433

TCP

SQL Server instance

MSSQL

Table 2. Outgoing Ports

Port

Protocol

Component

Comments

53

TCP, UDP

All

DNS

67, 68, 546, 547

TCP, UDP

All

DHCP

123

TCP, UDP

All

Optional. NTP

443

TCP

Manager Service

Communication with vRealize Automation appliance over HTTPS

443

TCP

Distributed Execution Managers

Communication with Manager Service over HTTPS

443

TCP

Proxy agents

Communication with Manager Service and infrastructure endpoint hosts over HTTPS

443

TCP

Management Agent

Communication with the vRealize Automation appliance

443

TCP

Guest agent

Software bootstrap agent

Communication with Manager Service over HTTPS

1433

TCP

Manager Service

Website

MSSQL

5480

TCP

All

Communication with the vRealize Automation appliance.

Also, because you enable DTC between all servers, DTC requires port 135 over TCP and a random port between 1024 and 65535. Note that the Prerequisite Checker validates that DTC is running and the required ports are open.