The following is a list of incoming ports through which vRealize Components listen :
|
Port |
Protocol |
Comments |
|
22 |
TCP |
SSH |
|
80 |
TCP |
Redirects to 443 |
|
111 |
TCP, UDP |
RPC |
|
443 |
TCP |
Access to vRealize Automation console and API |
|
5480 |
TCP |
Access to web management UI |
|
5488, 5489 |
TCP |
Management |
|
7444 |
TCP |
SSO over HTTPS |
|
8230, 8280, 8281 |
TCP |
Internal vRealize Orchestrator instance |
The following table shows the list of outgoing ports:
|
Port |
Protocol |
Comments |
|
25, 587 |
TCP, UDP |
SMTP for sending notification emails |
|
53 |
TCP, UDP |
DNS |
|
67, 68, 546, 547 |
TCP, UDP |
DHCP |
|
80 |
TCP |
Optional for fetching updates |
|
110, 995 |
TCP, UDP |
POP for receiving notification email |
|
143, 993 |
TCP, UDP |
IMAP for receiving notification email |
|
123 |
TCP, UDP |
NTP sync directly instead of using host time |
|
443 |
TCP |
IaaS manager service over HTTPS |
IaaS components are installed onto a Windows host and include the model manager, the management interface, execution managers, and the database. The model manager that's installed with vRA includes all of the default models that are available from VMware.
A model is a collection of elements that make up a provisioning process and includes a data model, logic, event definitions, security, and the specification of how a Distributed Execution Manager (DEM) communicates with an external system. The database holds the configuration, workflows, and information about all of the objects in a vRA environment.
vRA has a vRA appliance and an IaaS component. The identity appliance is a Linux-based virtual appliance that provides single sign-on capabilities to vRA. vRA VA is also Linux-based and provides the user interface and several common services. The IaaS component is installed onto a Windows host and contains the management services, agents, model manager, and execution managers that process and execute the requested workflows.