Application Deployment field descriptions

Last Updated : Jun 06, 2026 |

Select Location and Platform

Name

Description

Select Location

The location name.

Select Platform

The platform name that you must select.

Platform FQDN

The platform FQDN.

Data Store

The data store for the application.

The page populates the capacity details in the Capacity Details section.

Capacity Details

The system displays the CPU and memory details of the ESXi host. The fields are read-only.

Note:

If the host is in a cluster, the system does not display the capacity details of CPU and memory. Ensure that the host resource requirements are met before you deploy the virtual machine.

Name

Description

Name

The resource name.

Full Capacity

The maximum capacity.

Free Capacity

The available capacity.

Reserved Capacity

The reserved capacity.

Status

The configuration status.

Provide admin and root Credentials

The system displays the Provide admin and root Credentials section for OS.

Name

Description

Platform IP

The platform IP.

Platform FQDN

The platform FQDN.

Admin User of OS

The admin username of OS.

Admin Password of OS

The admin password of OS.

Root User of OS

The root user of OS.

OVA Details

Name

Description

Application Name

The name of the application.

ME Deployment

The option to perform the Midsize Enterprise deployment.

The option is available only while deploying Communication Manager simplex OVA.

URL

The option to specify the URL or absolute path from where you can get the OVA or ISO file.

OVA from software library

The option to specify the software library where the OVA or ISO file is saved.

Select Software Library

The default path provided during the installation of the Solution Deployment Manager client. The default path is C:\Program Files\Avaya\SDMClient\Default_Artifacts.

The field is available only when you click OVA from software library.

Browse

The option to specify the location from where you can get the OVA or ISO file.

Select OVA

The URL or absolute path to the OVA or ISO file of the application that you must provide. For example, C:\Program Files\SDM\<Application OVA_10.2.x.ova>

The field is available only when you click Browse.

Note:

System Manager validates any file that you upload during deployment and accepts only the OVA or ISO file type. System Manager filters uploaded files based on file extension and mime types or bytes in the file.

When you select OVA from software library, you can select the OVA or ISO file of the application that you want to deploy.

Submit File

The field is available only when you click Browse.

Selects the OVA or ISO file of the application that you want to deploy.

Flexi Footprint

The footprint size supported for the selected application.

Important:
  • Ensure that the required memory is available for the footprint sizes that you selected. The upgrade operation might fail due to insufficient memory.

  • Ensure that the application contains the footprint size values that are supported.

Communication Manager Configuration Parameters

Name

Description

CM IPv4 Address

The IPv4 address of the Communication Manager virtual machine.

CM IPv4 Netmask

The IPv4 network mask of the Communication Manager virtual machine.

CM IPv4 Gateway

The IPv4 default gateway of the Communication Manager virtual machine.

CM IPv6 Address

The IPv6 address of the Communication Manager virtual machine.

The field is optional.

CM IPv6 Network Prefix

The IPv6 network prefix of the Communication Manager virtual machine.

The field is optional.

CM IPv6 Gateway

The IPv6 gateway of the Communication Manager virtual machine.

The field is optional.

Out of Band Management IPv4 Address

The IPv4 address of the Communication Manager virtual machine for out of band management.

The field is optional network interface to isolate management traffic on a separate interface from the inband signaling network.

Out of Band Management IPv4 Netmask

The IPv4 subnet mask of the Communication Manager virtual machine for out of band management.

Out of Band Management IPv6 Address

The IPv6 address of the Communication Manager virtual machine for out of band management.

The field is optional network interface to isolate management traffic on a separate interface from the inband signaling network.

Out of Band Management IPv6 Network Prefix

The IPv4 subnet mask of the Communication Manager virtual machine for out of band management.

CM Hostname

The hostname of the Communication Manager virtual machine.

NTP Server(s)

The IP address or FQDN of the NTP server.

Separate the IP addresses with commas (,).

You can type up to three NTP servers.

The application supports only the NTP server. It does not support the NTP pool.

DNS Server(s)

The DNS IP address of the Communication Manager virtual machine.

Search Domain List

The search list of domain names. For example, mydomain.com. Separate the search list names with commas (,).

WebLM Server IPv4 Address

The IPv4 address of the reachable WebLM server. The field is mandatory.

EASG User Access

Enables or disables Avaya Logins for Avaya Services to perform the required maintenance tasks.

The options are:

  • 1: To enable EASG.

  • 2: To disable EASG.

Avaya recommends that you enable EASG.

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

CM Privileged Administrator User Login

The login name for the privileged administrator. You can change the value at any point of time. The field is mandatory.

CM Privileged Administrator User Password

The password for the privileged administrator. You can change the value at any point of time. The field is mandatory.

Confirm Password

The password required to be confirmed. The field is mandatory.

Data Encryption

Note:

Data Encryption is supported only for Appliance Virtualization Platform Release 8.x or earlier, Avaya Solutions Platform 130, and VMware Virtualized Environment.

For more information, see the application-specific Data Privacy Guidelines on the Avaya Support website.

Name

Description

Data Encryption

Enables or disables the data encryption.

The options are:

  • 1: To enable the data encryption.

  • 2: To disable the data encryption.

Important:
  • An encrypted system cannot be changed to a non-encrypted system without a new OVA installation and vice-versa.

  • While using vCenter, when you enable data encryption and do not enter the encryption passphrase, the system does not block the deployment due to vCenter limitation. Therefore, ensure that you enter the encryption passphrase, if data encryption is enabled.

  • In case the administrator forgets to add the passphrase at deployment time, then the boot will proceed with a blank passphrase. The administrator has to just press enter to proceed, because the passphrase is blank. The administrator will be prompted to set the passphrase, only after the Release 8.1.2 and later patch is installed and the system is rebooted.

  • On Solution Deployment ManagerWhen the Data Encryption field is set to 1, the system enables the Encryption Pass-Phrase and Re-enter Encryption Pass-Phrase fields to enter the encryption passphrase.

  • On vCenter or ESXiWhen the Data Encryption field is set to 1, enter the encryption passphrase in the Password and Confirm Password fields.

Encryption Pass-Phrase

This field is applicable when data encryption is enabled.

The passphrase for data encryption.

When you deploy the application by using Solution Deployment Manager, the system applies the passphrase complexity rules.

When you deploy the application by using vCenter or ESXi, the system does not apply the passphrase complexity rules.

Re-enter Encryption Pass-Phrase

The passphrase for data encryption.

Require Encryption Pass-Phrase at Boot-Time

If the check box is selected, you need to type the encryption passphrase whenever the application reboots. By default, the Require Encryption Pass-Phrase at Boot-Time check box is selected.

Important:

You must remember the data encryption pass-phrase as the system prompts you to enter the encryption passphrase with every reboot of the application.

If you lose the data encryption passphrase, the only option is to reinstall the OVA.

If the check box is not selected, the application creates the Local Key Store and you are not required to type the encryption passphrase whenever the application reboots. This might make the system less secure.

You can also set up the remote key server by using the encryptionRemoteKey command after the deployment of the application.

Customer Root Account

Note:

The Customer Root Account field is applicable only in case of deploying application OVA on Appliance Virtualization Platform Release 8.x or earlier, Avaya Solutions Platform 130, and VMware by using Solution Deployment Manager. The system does not display the Customer Root Account field, when you deploy an application:

  • OVA on VMware by using vSphere Client (HTML5).

  • ISO on Red Hat Enterprise Linux by using Solution Deployment Manager.

Name

Description

Enable Customer Root Account for this Application

Enables or disables the customer root account for the application.

Displays the ROOT ACCESS ACCEPTANCE STATEMENT screen. To accept the root access, click Accept.

When you accept the root access statement, the system displays the Customer Root Password and Re-enter Customer Root Password fields.

Customer Root Password

The root password for the application

Re-enter Customer Root Password

The root password for the application

Network Parameters

When you deploy the application on VMware, the system displays the Select a Network Mapping for VM Network Interfaces section.

Name

Description

Public

The port number that is mapped to public port group.

You must configure Public network configuration parameters only when you configure Out of Band Management. Otherwise, Public network configuration is optional.

Duplication Link

The connection for server duplication.

The field is available only when you deploy duplex Communication Manager.

Out of Band Management

The port number that is mapped to the out of band management port group.

Button

Description

Deploy

Displays the EULA acceptance screen. To accept EULA and start the deployment process, click Accept.