Select Configuration, Network, Network Settings to access the network configuration settings. Here, basic network information is shown in the Default Gateway and Network Interfaces fields. These fields are the only required settings, except for an AWS AMI instance where a DNS server is the only required setting. If necessary, specify information necessary for DNS routing. For an AMI instance, the DNS setting is provided by the AMI instance and you must enter that value.
DNS Servers: Specify the name or IP address of one or more DNS servers (one per line).
Note: If you use a hostname for an NTP server, a DNS server is required here. If you remove all DNS servers, ensure that any configured NTP servers use IP addresses instead. See Configure Date/Time Settings for details.
Note: Licensing no longer includes the NIC to generate the hardware identification string. This change allows NICs to be added to running machines without breaking the licensing.
You can set up Network Teaming, also known as NIC teaming, bonding, or aggregation, to combine multiple network cards together for enhanced performance or redundancy. A "bond" is set up among multiple network interfaces. This feature is available on the hardware appliance and VMware.
Note: NIC Teaming is available in VMware, configured in vSphere. Before you set up Network Teaming in CA Privileged Access Manager, ensure that no conflicts exist with the vSphere configuration.
CA Privileged Access Manager supports two Modes for Network Teaming:
Network interfaces are teamed together as a "bond." CA Privileged Access Manager supports up to four interfaces for teaming on a hardware appliance. On a VMware instance, you can use up to half of the existing teaming interfaces, or up to its maximum index. Assume that each VMware bond must have at least two interfaces. For example, if a VMware instance has seven network adapters, then the maximum allowed bond interfaces is three (BOND1, BOND2, and BOND3).
To set up a bond for network teaming, follow these steps:
Enter an IPv4 or IPv6 Address as a virtual network adapter for the bond.
Note: Each Bond should be configured to use a different subnet. Using the same subnet results in errors.
To see the status of a Network Team, select its row in the Network Teaming list, and click the Status button. The Network Team Status window opens. The following information appears: