Configuring servers preinstalled with Appliance Virtualization Platform

About this task

For newly purchased common servers, Appliance Virtualization Platform is preinstalled. This does not apply for migration. You must configure the customer network settings through the Solution Deployment Manager client that is installed on a computer that is running Windows. The media comes with the server. The new S8300D and S8300E servers require an installation at the customer site.

If the initial Appliance Virtualization Platform admin password for pre-installed servers is not provided, please contact your Avaya Professional Services or Business Partner Installer. For Common Server migrations, S8300D Server, and S8300E Server the password is assigned through the 7.1ks.cfg file. The password is encrypted in the file. Please contact the installer who created the 7.1ks.cfg file for the admin password.

	Note
	When possible, perform the deployment from the System Manager Solution Deployment Manager. Only when System Manager is unreachable, use the Solution Deployment Manager client that is installed on the computer.

Procedure

Turn on the server.
Install the Solution Deployment Manager client on the computer.
Configure the computer with the following:
- IP address: 192.168.13.5
- Netmask: 255.255.255.248
- Gateway: 192.168.13.1
Connect to NIC2 with a network cable.
Start an SSH session, log in to 192.168.13.6 with admin credentials.

The system prompts to change the password immediately.
To change the admin password, perform the following:
1. At the prompt, type the Appliance Virtualization Platform default password: AVaya@01
2. Type the new password.
  
  For more information about password rules, see "Password policy".
3. Type the password again.
  
  The system changes the host password.
To accept the EULA, in Do you accept the terms of this EULA? (Y)es/(N)o, type Y.

At the Enhanced Access Security Gateway (EASG) prompt, read the following messages, and type one of the following:

Enable: (Recommended)

By enabling Avaya Logins you are granting Avaya access to your system.
This is necessary to maximize the performance and value of your Avaya support entitlements, allowing Avaya to resolve product issues in a timely manner.
In addition to enabling the Avaya Logins, this product should be registered with Avaya and technically onboarded for remote connectivity and alarming. Please see the Avaya support site (support.avaya.com/registration) for additional information for registering products and establishing remote access and alarming.

Disable:

By disabling Avaya Logins you are preventing Avaya access to your system. 
This is not recommended, as it impacts Avaya’s ability to provide support for the product. Unless the customer is well versed in managing the product themselves, Avaya Logins should not be disabled.

1: To enable EASG.

Avaya recommends to enable EASG.

You can also enable EASG after deploying or upgrading the application by using the command: EASGManage --enableEASG.
2: To disable EASG.

Type cd /opt/avaya/bin.

Not all commands are available in the /opt/avaya/bin location, and must be run with ./. For example, ./nic_port. The system only runs the commands that are specified in the procedure from /opt/avaya/bin or as directed by Avaya Services. The system might get incorrectly configured if you run commands that are not specified in the procedure.

Most systems do not enable Out of Band Management. Use the set_oobm command only to enable Out of Band Management for the host and all virtual machines.
(Optional) To enable Out of Band Management on the Appliance Virtualization Platform host, type # ./set_oobm on.

The system displays Host Out of Band Management set up is complete.

At the prompt, do the following:

Type ./serverInitialNetworkConfig.

The host IP address details are mandatory. Though DNS and NTP values are optional, you must provide the values.

At the prompt, provide the following host details:

System is not in a default setup, please use SDM to change IP addresses
Do you wish to setup networking? (y/n)  y
Please enter IP address for the AVP host in the format x.x.x.x
For example 172.16.5.1
Please enter value    172.16.107.21
Please enter subnet mask for the AVP host in the format x.x.x.x
For example 255.255.255.0
Please enter value    255.255.255.0
Please enter a default gateway for the AVP host in the format x.x.x.x
For example 172.16.5.254
Please enter value    172.16.107.1
Please enter a hostname for the AVP host.
For example myhost
Please enter value    avphost
Please enter a domain for the AVP host.
For example mydomain.com
Please enter value    mydomain.com
Please enter a main DNS server for the AVP host.
For example 172.16.10.54
Please enter value    172.16.107.1
Please enter a secondary DNS server for the AVP host.
For example 172.16.10.54
Please enter value    172.16.107.2
Please enter a NTP server for the AVP host
For example 172.16.10.55
Please enter value    172.16.107.50
Stopping ntpd
watchdog-ntpd: Terminating watchdog process with PID 33560
Starting ntpd

To verify the vmk0 settings, type # esxcli network ip interface ipv4 get.

	Note
	Do not change the vmk1s address. vmk1s is fixed for the services port.

The system displays the following details:

Name  IPv4 Address   IPv4 Netmask     IPv4 Broadcast  Address Type  DHCP DNS
----  -------------  ---------------  --------------  ------------  --------
vmk1  192.168.13.6   255.255.255.248  192.168.13.7    STATIC           false
vmk0  172.16.107.21  255.255.255.0    172.16.107.255  STATIC           false

Start the Solution Deployment Manager client when connected to the services port.
Add a location.
Add the Appliance Virtualization Platform host as 192.168.13.6.
Check the version, and install the Release 7.1.3 feature pack on Appliance Virtualization Platform if required.
Deploy Utility Services.
Deploy other Avaya Aura^® applications that will reside on this Appliance Virtualization Platform host.
Install the Release 7.1.3 patch files for all Avaya Aura^® applications.