The following table identifies the key customer configuration information required during the deployment and configuration process for Application Enablement Services:
|
Required data for Application Enablement Services
|
Example value
|
|
Hostname or fully qualified domain name for the Application Enablement Services virtual machine.
|
aesserver1
|
|
DNS search path.
Note:
If you leave this value blank, you must modify or add search <dns search path> in the file etc/resolv.conf after you deploy the Application Enablement Services virtual machine successfully.
|
example.com
|
|
Default gateway address of the Application Enablement Services virtual machine.
|
123.45.67.254
|
|
Domain name servers for the Application Enablement Services virtual machine.
|
123.45.1.2
|
|
IP address of the Application Enablement Services virtual machine interface for eth0, the public interface.
|
123.45.67.89
|
|
Netmask or prefix for the Application Enablement Services virtual machine interface for eth0 (Public interface).
|
255.255.255.0
|
|
IP address of the Application Enablement Services virtual machine interface for eth1 (Private interface).
|
123.45.67.90
|
|
Enter the Netmask or prefix for the Application Enablement Services virtual machine interface for eth1 (Private interface).
|
255.255.255.0
|
|
IP address of the Application Enablement Services virtual machine interface for eth2 (Out of Band Management interface).
|
|
|
Netmask or prefix for the Application Enablement Services virtual machine interface for eth2 (Out of Band Management interface).
|
|
|
Network Time Protocol (NTP) hostname or IP address.
|
|
Note:
-
DHCP is activated only after you configure it from the command line after initial deployment.
-
DHCP does not start when you start Application Enablement Services for the first time.
-
Avaya recommends that you should not use DHCP with Application Enablement Services.