vRealize Automation supports multiple network interface controllers (NICs). After installation, you can add NICs to the vRealize Automation appliance or IaaS Windows server.
About this task
Multiple NICs might be needed for some vRealize Automation deployments, for example:
You want separate user and infrastructure networks.
You need an additional NIC so that IaaS servers can join an Active Directory domain.
For more information about multiple NIC scenarios, see this VMware Cloud Management blog post.
For three or more NICs, be aware of the following limitations.
VIDM needs access to the Postgres database and Active Directory.
In an HA cluster, VIDM needs access to the load balancer URL.
The preceding VIDM connections must come through the first two NICs.
NICs after the second NIC must not be used or recognized by VIDM.
NICs after the second NIC must not be used to connect to Active Directory.
Use the first or second NIC when configuring a directory in vRealize Automation.
Completely install vRealize Automation to your vCenter environment.
- In vCenter, add NICs to each vRealize Automation appliance.
- Right click the appliance and select Edit Settings.
- Add VMXNETn NICs.
- If it is powered on, restart the appliance.
- Log in to the vRealize Automation appliance management interface as root.
- Select Network, and verify that multiple NICs are available.
- Select Address, and configure the IP address for the NICs.
Table 1. Example NIC Configuration
IPv4 Address Type
- Verify that all vRealize Automation nodes can resolve each other by DNS name.
- Verify that all vRealize Automation nodes can access any load balanced FQDNs for vRealize Automation components.
- If you are using Split-Brain DNS, verify that all vRealize Automation nodes and VIPs have the same FQDN in DNS for each node IP and VIP.
- In vCenter, add NICs to IaaS Windows servers.
- Right click the IaaS server and select Edit Settings.
- Add NICs to the IaaS server virtual machine.
- In Windows, configure the added IaaS server NICs and their IP addresses. See the Microsoft documentation if necessary.
What to do next
(Optional) If you need static routes, see Configure Static Routes.