vRealize Automation supports multiple network interface controllers (NICs). Before running the installer, it is possible to add NICs to the vRealize Automation appliance or IaaS Windows server.

If you need multiple NICs to be in place before running the vRealize Automation installation wizard, add them after deploying in vCenter but before starting the wizard. Reasons that you might want additional NICs in place early include the following examples:

  • 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.

Prerequisites

Deploy the vRealize Automation appliance OVF and Windows virtual machines, but do not log in or start the installation wizard.

Procedure

  1. In vCenter, add NICs to each vRealize Automation appliance.
    1. Right click the newly deployed appliance and select Edit Settings.
    2. Add VMXNETn NICs.
    3. If it is powered on, restart the appliance.
  2. Log in to the vRealize Automation appliance command line as root.
  3. Configure the NICs by running the following command for each NIC.

    Make sure to include the default gateway address. You can configure static routes after finishing this procedure.

    /opt/vmware/share/vami/vami_set_network network-interface (STATICV4|STATICV4+DHCPV6|STATICV4+AUTOV6) IPv4-address netmask gateway-v4-address

    For example:

    /opt/vmware/share/vami/vami_set_network eth1 STATICV4 192.168.100.20 255.255.255.0 192.168.100.1

  4. Verify that all vRealize Automation nodes can resolve each other by DNS name.
  5. Verify that all vRealize Automation nodes can access any load balanced FQDNs for vRealize Automation components.
  6. 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.
  7. In vCenter, add NICs to IaaS Windows servers.
    1. Right click the IaaS server and select Edit Settings.
    2. Add NICs to the IaaS server virtual machine.
  8. 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, follow the guidelines in Configure Static Routes before continuing with installation.

  • Log in to the browser-based administration interface to run the consolidated Installation Wizard or to manually configure the appliance.

    https://vrealize-automation-appliance-FQDN:5480

  • Alternatively, you can skip logging in so that you can take advantage of vRealize Automation silent or API based installation.