Deploying the Avaya Aura Device Services OVA using the vSphere Client

Last Updated : Jun 10, 2026 |

About this task

Use this procedure to deploy the Avaya Aura® Device Services OVA on vCenter using the vSphere Client.

This procedure applies to vSphere Client Release 7.0.3. If you use another version of the vShpere Client, the steps might differ from the steps described in this procedure.

FQDNs, where mentioned in the procedure, are mandatory.

Note:

If you choose to install a standalone Avaya Aura® Device Services at present but in the future decide to move to a cluster that uses a virtual IP, the original standalone node needs to be re-configured 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 and add a virtual IP for the front-end FQDN of the standalone node. This planning 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

  1. Log in to the vSphere Client at https://<VCENTER>/UI.

    In this URL, <VCENTER> is the IP address or FQDN of the vCenter server.

    Deploying the Avaya Aura® Device Services using vApp

  2. Optional To deploy Avaya Aura® Device Services using vApp, do the following:
    1. Right-click an appropriate cluster or ESXi host where you want to deploy the OVA and select New vApp.

      The vSphere Client displays the New vApp window.

    2. On the Select Creation type page, select one of the following:

      • Create a new vApp

      • Clone an existing vApp

    3. On the Select a name and location page, do the following:

      • In the field next to vApp name, enter the unique name for the virtual machine.

      • In the Select a folder or datacenter section, select the folder or datacenter where you want to deploy the VM.

      • Click Next.

    4. On the Resource allocation page, select or enter the required field based on your specific deployment profile.

      For more information, refer to Avaya Aura Device Services virtual machine resource requirements.

    5. On the Review and finish page, review the entered details and click Finish.
    6. To deploy more than one Avaya Aura® Device Services instances, create a child vApp under the parent vApp.
  3. Right-click an appropriate cluster or ESXi host where you want to deploy the OVA and select Deploy OVF Template.

    The vSphere Client displays the Deploy OVF Template window.

  4. To download the OVA file, on the Select an OVF template page, do one of the following:

    • To download the OVA file from a web location, select URL and provide the complete network path to the OVA file.

    • To download the OVA file from the local computer, select Local file and click Upload files and select the OVA file.

  5. Click Next.
  6. On the Select a name and folder page, do the following:
    1. In Virtual machine name, enter a name for the virtual machine.
    2. In Select a location for the virtual machine, select an appropriate location for the virtual machine.

      By default, this is the location selected in step 3.

    3. Click Next.
  7. On the Select a compute resource page, do the following:
    1. In Select the destination compute resource, select an appropriate ESXi host for the virtual machine.

      By default, this is the location selected in step 3.

    2. Ensure that the Compatibility area displays the Compatibility check succeeded message.
    3. Click Next.
  8. On the Review details page, do the following:
    1. Ensure that the Publisher field contains the Entrust Code Signing CA - OVCS1 (Trusted certificate) entry.
    2. Verify the OVA template details.
    3. Click Next.
  9. On the License agreements page, do the following:
    1. Read the End User License Agreement (EULA).
    2. To accept the EULA, select I accept all license agreements check box.
    3. Click Next.
  10. On the Configuration page, 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 use for the seed node.

    For more information about resource profile specifications, see Avaya Aura Device Services virtual machine resource requirements. The vSphere Client also displays the basic system requirements for the profile in the Description area.

  11. Click Next.
  12. On the Select storage page, do the following:
    1. In Select virtual disk format, select the appropriate disk format.

      If you select Thick provision, the entire disk space required for the virtual machine is reserved and unavailable for other virtual machines to use. If you select Thin provision, unused space is available for other virtual machines.

    2. In the Datastore table, select an appropriate data store for the virtual machine.
    3. Ensure that the Compatibility area displays the Compatibility check succeeded message.
    4. Click Next.
  13. On the Select networks page, for each source network, select an appropriate destination network.
  14. Click Next.
  15. On the Customize template page, configure the following parameters:
    1. In Enhanced Access Security Gateway (EASG), configure EASG settings.
    2. In Disk Encryption Settings, configure disk encryption settings.
    3. In Management Network Settings, configure network settings, such as the IP address, FQDN, network mask, and DNS.
    4. In Account login Details, configure credentials for a Linux administrator user, including the user name, password, and group.

    For more information about the disk encryption and EASG fields, see the respective sections in VM Deployment Configuration Parameters, Network Parameters, and Data Encryption field descriptions.

    Note:

    • If you do not provide the details in the mandatory fields, you cannot power on the virtual machine even if the deployment is successful. The vSphere Client displays the number of remaining mandatory settings that you must configure at the top of the Customize template page.

    • The vSphere Client validates the inputs that you provide. If the inputs are invalid, the system prompts you to provide the inputs again on the virtual machine console.

  16. Click Next.
  17. On the Ready to complete page, review the configuration details and then click Finish to complete the virtual machine deployment.
  18. Optional After you complete Avaya Aura® Device Services deployment process using vApp, move Avaya Aura® Device Services VM from the child vApp to the parent vApp.

Next Steps

Install the Avaya Aura® Device Services application.