| Requirements | vRealize Suite Lifecycle Manager | VMware Identity Manager | vRealize Automation |
|---|---|---|---|
| Total Disk Size | 78 GB | 60 GB | 236 GB (Only for single node Installation) |
| Virtual CPU | 2 | 8 | 12 |
| Memory/RAM Size | 6 GB | 16 GB | 40 GB |
| System Partition | 10 GB | 8 GB | 50 GB |
| Data Partition | 50 GB | 144 GB | |
| Metrics Partition | 20 GB | ||
| Logs Partition | 22 GB | ||
| Swap Size | 8 GB | 6 GB | |
| Tomcat Partition | 10 GB | ||
| var Partition | 10 GB | ||
| db Partition | 10 GB | 10 GB | |
| Maximum Network Latency | 5 ms between each cluster node | ||
| Maximum Storage Latency | 20 ms for each disk IO operation from any vRA node |
vRealize Easy Installer supports
- VMware Identity Manager 3.3.1 (for import only) and 3.3.2
- vRealize Automation 8.0.0 and later.
Each vRealize Automation node requires a network setup. The network requirements for vRealize Automation are:
- Single, static IPv4 and Network Address
- Reachable DNS server set manually
- Valid, Fully-qualified domain name, set manually that can be resolved both forward and in reverse through the DNS server
vRealize Automation can currently be accessed over port 443. The 443 port is secured with a self-signed certificate that is generated during the installation. When using an external load balancer, it must be set up to balance on port 443. The table provides an overview of the Ports and Port number used for vRealize Automation.
| Product | Releases | Port | Protocol | Source | Destination | Purpose |
| vRealize Automation | 8.0 | 443 | TCP | vRealize Automation | VMWare Identity Manager | Component Communication |
| vRealize Automation | 8.0 | 443 | TCP | vRealize Automation | vRealize Lifecycle Manager | Component Communication |
| vRealize Automation | 8.0 | 8008 | TCP | vRealize Automation | vRealize Automation | Health Monitor |
| vRealize Automation | 8.0 | 22 | TCP | Vmware Identity Manager | vRealize Automation | Access for SSH sessions |
| vRealize Automation | 8.0 | 443 | TCP | User | vRealize Lifecycle Manager | Communication |
| vRealize Automation | 8.0 | 443 | TCP | User | VMWare Identity Manager | Communication |
| vRealize Automation | 8.0 | 443 | TCP | User | vRealize Automation | Communication |
| vRealize Automation | 8.0 | 22 | TCP | vRealize Lifecycle Manager | VMWare Identity Manager | Access for SSH sessions |
| vRealize Automation | 8.0 | 22 | TCP | vRealize Lifecycle Manager | vRealize Automation | Access for SSH sessions |
| vRealize Automation | 8.0 | 10250 | TCP | vRealize Automation | vRealize Automation | Intra-cluster communication |
| vRealize Automation | 8.0 | 6443 | TCP | vRealize Automation | vRealize Automation | Intra-cluster communication |
| vRealize Automation | 8.0 | 8285 | UDP | vRealize Automation | vRealize Automation | Intra-cluster communication |
| vRealize Automation | 8.0 | 2379 | TCP | vRealize Automation | vRealize Automation | Intra-cluster communication |
| vRealize Automation | 8.0 | 2380 | TCP | vRealize Automation | vRealize Automation | Intra-cluster communication |
| vRealize Automation | 8.0 | 500 | UDP | vRealize Automation | vRealize Automation | Intra-cluster communication |
| vRealize Automation | 8.0 | 4500 | UDP | vRealize Automation | vRealize Automation | Intra-cluster communication |
Roles for LCM in vCenter
The clocks for vRealize Lifecycle Manager, VMware Identity Manager, vRealize Automation, and vRealize Orchestrator components must be synced to the same timezone. UTC+0 is recommended.
vRealize Automation and VMware Identity Manager appliances require and use these ports:
- vRealize Automation
- Port: 443
- Health Monitor Port: 8008
- Health Monitor URL: /health
- VMware Identity Manager
- Port: 443
- Health Monitor Port: 443
- Health Monitor URL: /SAAS/API/1.0/REST/system/health/heartbeat
vRealize Automation 8 requires a configured vRealize Orchestrator instance for extensibility functionality.
vRealize Automation 8 supports both an external and embedded vRealize Orchestrator instance. For optimized performance with vRealize Automation 8, configure an embedded vRealize Orchestrator instance.