Use the Network Configuration page to configure the IP-related settings for the virtual machine.
Note:
Some changes made on the Network Configuration page can affect the settings on other pages under the Server Configuration page. Ensure that all the pages under Server Configuration have the appropriate configuration information.
Using the Network Configuration page, you can configure or view the settings of the hostname, alias host name, DNS domain name, DNS search list, DNS IP addresses, server ID, and default gateway.
If the configuration setting for a field is blank, you can configure that setting on the Network Configuration page.
Note:
While configuring a survivable server that has ESS and LSP configured, users must ensure that the Server ID must be unique for each survivable server and main server.
The virtual machine uses virtual NICs on virtual switches internal to the hypervisor.
The system uses eth0 in most cases except for duplication traffic. Use eth1 for the duplication IP address. Use eth2 for the Out-of-Band Management interface IP address.
For information about Out-of-Band management, see Avaya Aura® Communication Manager Feature Description and Implementation.
The Network Configuration page displays the network interfaces that Communication Manager uses. The setting is eth0 for all Communication Managers except CM_Duplex. For CM_Duplex, the network interfaces are eth0, eth1, and eth2.
To activate the new settings on the virtual machine, you must restart Communication Manager after configuring the complete settings of the virtual machine. Too many restarts can escalate to a full Communication Manager reboot.
To deploy Duplex Communication Manager using Software-Only offer on Openstack, you must configure Alias IP. For more information on configuring Duplex Communication Manager, see Deploying Avaya Aura® Communication Manager in Virtualized Environment.
To deploy Duplex Communication Manager using Software-Only offer on Microsoft Azure, you must configure the load balancer.
