A vRealize Automation large deployment comprises systems of 50,000 managed machines or fewer and includes the appropriate virtual machines, load balancers, and port configurations.

Support

A large deployment can support the following items.

  • 50,000 managed machines
  • 2500 catalog items
  • 100 concurrent machine provisions

Requirements

A large deployment must meet the appropriate system configuration requirements.

Virtual Appliances
  • vRealize Automation appliance 1: vrava-1.ra.local
  • vRealize Automation appliance 2: vrava-2.ra.local
  • vRealize Business for Cloud Appliance: vrb.ra.local
Windows Server Virtual Machines
  • Infrastructure Web Server 1: web-1.ra.local
  • Infrastructure Web Server 2: web-2.ra.local
  • Infrastructure Manager Server 1: manager-1.ra.local
  • Infrastructure Manager Server 2: manager-2.ra.local
  • Infrastructure DEM Server 1: dem-1.ra.local
  • Infrastructure DEM Server 2: dem-2.ra.local
  • Infrastructure Agent Server 1: agent-1.ra.local
  • Infrastructure Agent Server 2: agent-2.ra.local
  • Clustered MSSQL Database: mssql.ra.local
Load Balancers
  • vRealize Automation appliance Load Balancer: vrava.ra.local
  • Infrastructure Web Load Balancer: web.ra.local
  • Infrastructure Manager Service Load Balancer: manager.ra.local

Certificates

The host names used in this table are examples only.
Server Role CN or SAN
vRealize Automation appliance
SAN contains the following host names:
  • vrava.ra.local
  • vrava-1.ra.local
  • vrava-2.ra.local
Infrastructure Web Server
SAN contains the following host names:
  • web.ra.local
  • web-1.ra.local
  • web-2.ra.local
Infrastructure Manager Server
SAN contains the following host names:
  • manager.ra.local
  • manager-1.ra.local
  • manager-2.ra.local
vRealize Business for Cloud appliance CN = vrb.ra.local

Ports

Users require access to certain ports. All ports listed are default ports.

Server Role Port
vRealize Automation appliance Load Balancer 443, 8444 Port 88444 is required for the Virtual Machine Remote Console.

Administrators require access to certain ports, in addition to the ports that users require.

Server Role Port
vRealize Automation appliance 5480, 8443. Port 8443 is used for advanced identity management configuration.
vRealize Business for Cloud Server 5480
The system must support the appropriate inter-application communications.
Server Role Inbound Ports Outbound Ports for Service or System
vRealize Automation
vRealize Automation appliance HTTPS: 443

Adapter Configuration: 8443

Remote Console Proxy: 8444

Postgres: 5432

Rabbit MQ: 4369, 25672, 5671, 5672

ElasticSearch: 9300, 40002, 40003

Stomp: 61613

SSH: 22

Control-Center: 8283

LDAP: 389

LDAPS: 636

vRealize AutomationAppliance: 5432, 4369, 25672, 5671,5672, 9300, 40002, 40003.

vRealize Automation Infrastructure Web Load Balancer: 443

VMware ESXi: 902. Infrastructure Web requires access to vSphere Endpoint Port 443 to obtain a ticket for Virtual Machine Remote Console. The vRealize Automation appliance requires access to ESXi host Port 902 to proxy console data to the user.

Infrastructure Web Server HTTPS: 443

MSDTC: 443, 1024-65535. For information about how to narrow this range, see the Database Deployment section of vRealize Automation Deployment.

vRealize Automation Appliance Load Balancer: 443

vRealize Automation Appliance virtual appliance: 5480.

vSphere Endpoint: 443. Infrastructure Web requires access to vSphere Endpoint Port 443 to obtain a ticket for Virtual Machine Remote Console. The vRealize Automation appliance requires access to ESXi host Port 902 to proxy console data to the user.

MSSQL: 135, 1433, 1024 to 65535. For information about how to narrow this range, see the Database Deployment section of vRealize Automation Deployment.

Infrastructure Manager Server HTTPS: 443

MSDTC: 135,1024-65535. For information about how to narrow this range, see the Database Deployment section of vRealize Automation Deployment.

vRealize Automation Appliance Load Balancer: 443

vRealize Automation Infrastructure Web Load Balancer: 443

vRealize Automation Appliance: 443, 5480

MSSQL: 135, 1433, 1024 to 65535. For information about how to narrow this range, see the Database Deployment section of vRealize Automation Deployment.

Infrastructure DEM Server NA

vRealize Automation Appliance Load Balancer: 443

vRealize Automation Infrastructure Web Load Balancer: 443

vRealize Automation Infrastructure Manager Load Balancer: 443

vRealize Orchestrator Load Balancer: 8281

vRealize Automation Appliance: 5480.

Infrastructure Agent Server NA

vRealize Automation Infrastructure Web Load Balancer: 443

vRealize Automation Infrastructure Manager Load Balancer: 443

vRealize Automation Appliance: 5480.

MSSQL Database Server MSSQL: 1433

MSDTC: 135, 1024-65535. For information about how to narrow this range, see the Database Deployment section of vRealize Automation Deployment.

Infrastructure Web Server: 135, 1024-65535. For information about how to narrow this range, see the Database Deployment section of vRealize Automation Deployment.

Infrastructure Manager Server: 135, 1024-65535. For information about how to narrow this range, see the Database Deployment section of vRealize Automation Deployment.

vRealize Business for Cloud Server HTTPS: 443

SSH: 22

Virtual Appliance Management Console: 5480

vRealize Automation Appliance Load Balancer: 443

vRealize Automation Infrastructure Web Load Balancer: 443

Load balancers require access through the following ports.

Load Balancer Ports Balanced
vRealize Automation Appliance Load Balancer 443, 8444
vRealize Automation Infrastructure Web Load Balancer 443
vRealize Automation Manager Server Load Balancer 443

Graphics

Figure 1. Minimum footprint for vRealize Automation large configuration

Figure 2. Minimum footprint for vRealize Business for Cloud large configuration