ServAssure Collection Platform applications can be configured to bind to non-default interfaces. To accomplish this, set up the default Ansible files to define the interface for each inventory host. If the explicit interface is not defined, Ansible selects the system default and configures it. There are two configurable variables that must be defined per host in the inventory:
use_eth_interface=<interface-name>
For example user_eth_interface=ens224 or user_eth_interface=eth3
use_custom_fqdn=<fqdn>
For example use_custom_fqdn="managernode1.alternate.domain.com" or use_custom_fqdn="managernode1"
The variable "use_eth_interface" must be the exact name of the interface that is desired on the host. The variable "use_custom_fqdn" is only required if the alternate interface is set up in DNS and the hostnames are resolvable across the cluster. If all hosts defined in the inventory use the same alternate interface with the same name, it can be configured in the site-vars file as the global interface to be used. If a custom interface is defined, but a hostname for the interface is not, then the IPv4 address of the host is used for application configuration.
The following example shows a ServAssure Collection Manager node with an alternate interface and no custom hostname:
[docsis_manager]
demo-testing-manager alias=manager1 rack=RAC1
use_eth_interface=ens224The following example show a ServAssure Collection Manager node with alternate interface set up in DNS with a different hostname than the system hostname:
[docsis_manager]
demo-testing-manager alias= manager1 use_eth_interface=ens224
use_custom_fqdn=manager1.alternate.domain.net
To validate if the correct configuration is prepared in the Ansible files, run the validate-interfaces.yml playbook in the tools directory of the ServAssure Collection Platform Ansible package. A debug message is generated, containing the interface, IPv4 address, and hostnames the applications will be configured with. In the event that the output contains discrepancies in the network details, the playbook also outputs a message on how to revisit and resolve the Ansible variables to correct the information.