Deploying the Avaya Aura Device Services OVA using the Host Client connected directly to the ESXi host

Last Updated : Jun 05, 2026 |

About this task

Use this procedure to deploy Avaya Aura® Device Services OVA on vCenter using the Host Client. This procedure also applies to deploying Avaya Aura® Device Services on Avaya Solutions Platform 130 or an equivalent server.

Note:

If you choose to install a standalone Avaya Aura® Device Services at present, but in future decide to move to a cluster that uses a virtual IP, the original standalone node needs to be reconfigured with the original virtual IP as the front-end FQDN. Accordingly, the new FQDN addition for Avaya Aura® Device Services must be notified to your clients.

To avoid this scenario, you can plan in advance and add a virtual IP for the front end FQDN of the standalone node. This would make the transition from a standalone node to a cluster easier in the future.

Before you begin

Obtain the latest OVA from PLDS.

In an Avaya environment, deploy Session Manager. For more information about deploying Session Manager, see Deploying Avaya Aura® Session Manager.

Procedure

Log in to the Host Client at https://<ESXI_HOST>/UI.

In this URL, <ESXI_HOST> is the IP address or FQDN of the ESXi host where you want to deploy your virtual machine.
Right-click the ESXi host and select Create/Register VM.

The Host Client displays the New Virtual Machine window.
On the Select creation type page, select Deploy a virtual machine from an OVF or OVA file.
Click Next.
On the Select OVF and VMDK files page, do the following:
1. In Name for the virtual machine, type a name for the virtual machine.
2. In Click to select files or drag/drop, upload the OVA file to the Host Client.
3. Click Next.
On the Select storage page, select an appropriate data storage for your virtual machine and click Next.
On the License agreements page, do the following:
1. Read the End User License Agreement (EULA).
2. To accept the EULA, click I agree.
3. Click Next.
On the Deployment options page, do the following:
1. In Network mappings, select an appropriate network.
2. In Deployment type, select an Avaya Aura® Device Services profile that matches your deployment requirements.
  
  Important:
  If you deploy the OVA for a non-seed node in a cluster, you must use the same resource profile that you used for the seed node.
  
  For more information about resource profile specifications, see Avaya Aura Device Services virtual machine resource requirements. The Host Client also displays basic system requirements for the profile below the field.
3. In Disk provisioning, select the appropriate disk format.
  
  If you select the Thick option, the entire disk space required for the virtual machine is reserved and unavailable for other virtual machines to use. If you select the Thin option, unused space is available for other virtual machines.
4. Clear the Power on automatically check box.
5. Click Next.
On the Additional Settings page, keep the default values and click Next.
On the Ready to complete page, review the virtual machine settings and click Finish.
Wait until the virtual machine is deployed.

Important:
Do not refresh the browser page while deployment is in progress.
To ensure that the virtual machine automatically starts after a hypervisor reboot, right-click your virtual machine and select Autostart > Enable.

If you do not enable autostart, you must manually start the virtual machine when the hypervisor reboots.

Note:
You must enable the autostart functionality on the ESXi host for the virtual machine autostart to function.
To start the virtual machine, right-click the virtual machine and select Power > Power On.
Access the virtual machine console.
Follow the system prompts to configure the remaining OVA settings as appropriate.
You must configure data encryption settings, network settings, and Linux administration account settings.
Note:
When configuring the Default Search List, ensure that the list includes the domains for:
- Avaya Aura® Device Services
- Avaya Meetings Server Management
- System Manager and LDAP

Next Steps

Optionally, enable the Enhanced Access Security Gateway as described in Enabling the Enhanced Access Security Gateway from the CLI. The EASG functionality enables Avaya support personnel to access your Avaya Aura® Device Services system and resolve product issues in real-time. Avaya recommends that you enable EASG during installation.
Install the Avaya Aura® Device Services application.

Send Feedback

AVAYA DOCUMENTATION CENTER

No results found