Before you add vRealize Automation to Cloud Foundation you must prepare the host names and IP addresses for the each of the vRealize Automation components. Each must be added in DNS with a fully qualified domain name (FQDN) that maps the host name to the IP address.
Ensure that you create the prerequisite forward (A) and reverse (PTR) DNS records for vRealize Automation and its shared components.
The installation of vRealize Automation deploys vRealize Suite Lifecycle Manager and an NSX Edge used to load balance vRealize Suite product services within the management domain. These components are shared between both vRealize Automation and vRealize Operations and are automatically installed when either product is installed. The shared components are only installed once.
The following components require host names and IP addresses:
-
All vRealize Automation virtual appliances and vRealize Automation IaaS virtual machines.
- Microsoft SQL Server for the vRealize Automation IaaS database server instance.
For more infomation, see vRealize Automation のための Microsoft SQL Server の構成.
-
The NSX Edge used to load balance vRealize Suite product services.
This is required only if you have not previously configured it as part of adding vRealize Operations to your Cloud Foundation system.
- All vRealize Automation virtual servers configured on the NSX Edge load balancer.
- vRealize Suite Lifecycle Manager virtual appliance.
This is required only if you have not previously configured it as part of adding vRealize Operations to your Cloud Foundation system.
The following table provides an example of the information to be collected for the cloud management layer. For illustration purposes, this example uses a fictional DNS root domain named rainpole.local. Modify the example information for your organization's configuration.
| Component Group | Hostname | DNS Zone | IP Address | Network | Description |
|---|---|---|---|---|---|
| vRealize Automation | vra01svr01 | rainpole.local | 172.16.16.80 | vRealize | Virtual IP address of the vRealize Automation Appliance |
| vra01svr01a | rainpole.local | 172.16.16.81 | vRealize Automation Appliance | ||
| vra01svr01b | rainpole.local | 172.16.16.82 | vRealize Automation Appliance | ||
| vra01svr01c | rainpole.local | 172.16.16.83 | vRealize Automation Appliance | ||
| vra01iws01 | rainpole.local | 172.16.16.84 | Virtual IP address of the vRealize Automation IaaS Web Servers | ||
| vra01iws01a | rainpole.local | 172.16.16.85 | vRealize Automation IaaS Web Server | ||
| vra01iws01b | rainpole.local | 172.16.16.86 | vRealize Automation IaaS Web Server | ||
| vra01ims01 | rainpole.local | 172.16.16.87 | Virtual IP address of the vRealize Automation IaaS Manager Service | ||
| vra01ims01a | rainpole.local | 172.16.16.88 | vRealize Automation IaaS Manager Service and DEM Orchestrator | ||
| vra01ims01b | rainpole.local | 172.16.16.89 | vRealize Automation IaaS Manager Service and DEM Orchestrator | ||
| vra01dem01a | rainpole.local | 172.16.16.90 | vRealize Automation DEM Worker | ||
| vra01dem01b | rainpole.local | 172.16.16.91 | vRealize Automation DEM Worker | ||
| sfo01ias01a | rainpole.local | 172.16.11.92 | Management | vRealize Automation Proxy Agent | |
| sfo01ias01b | rainpole.local | 172.16.11.93 | vRealize Automation Proxy Agent | ||
| vrslcm01svr01a | rainpole.local | 172.16.16.78 | vRealize | vRealize Suite Lifecycle Manager (Shared component with vRealize Automation and vRealize Operations) |
|
| sfo01m01lb01 | rainpole.local | 172.16.16.79 | NSX Edge Load Balancer (Shared component with vRealize Automation and vRealize Operations) |
||
| Microsoft SQL Server | vra01mssql01 | rainpole.local | 10.0.0.10 | Any accessible network | Microsoft SQL Server for vRealize Automation |
