Deploying the OVA file by using vSphere Web Client for vCenter

Last Updated : Mar 03, 2025 |
Prolog information
The steps in this procedure use the vSphere Web Client, which runs in a web browser.
Before you begin
  • Obtain the Avaya Aura® MS OVA file. Save the file on the workstation where you will run vSphere Web Client to configure the new VM.
    Important:
    As noted in https://kb.vmware.com/s/article/84240, prior to vCenter 7.0 U2, there was minimal certificate verification done on OVA/OVF packages. Starting 7.0 U2, the OVF signing certificates are verified for their expiry, validity and checked if the signing certificate is trusted. This means that the entire chain of the signing certificate must be trusted against the VECS store. For more information on how to update the VECS store, see the PSN101084832u at the Avaya support website.
  • Obtain the following networking configuration settings for the new VM. These settings can be from an existing system if you are redeploying Avaya Aura® MS OVA.
    Important:
    If you plan to enroll media servers with Avaya Aura® System Manager, then the media servers and System Manager must use the same NTP server for time synchronization.
    • Hostname
    • IPv4 address
    • IPv4 Netmask
    • Gateway IPv4 address
    • Customer account login name
    • Customer account password
    • Time zone
    • (Optional) Network domain
    • (Optional) IPv4 address of the DNS servers
    • IPv4 address or hostname of the NTP servers
    • (Optional) IPv6 address
    • (Optional) IPv6 prefix length
    • (Optional) IPv6 gateway address
    • (Optional) Out of band management IPv4 address
    • (Optional) Out of band management IPv4 netmask
    • (Optional) Out of band management IPv4 gateway address
    • (Optional) Root account password
  • Ensure that you turn off the current Avaya Aura® MS VM appliance.
  1. Log in to the VMware® host by using the vSphere Web Client.
  2. In the vSphere Web Client navigator area on the left, click vCenter.
  3. In Inventory Trees, click Hosts and Clusters.
  4. Expand the inventory tree of hosts and clusters to locate and select the target deployment host.
  5. From the menu, right-click the host and select Deploy OVF Template.
  6. If the Client Integration Access Control window pops up, click Allow.
  7. For 1a Select source, select Local file, and click Browse.
  8. From the file filter drop-down menu in the lower right of the window, click OVA Packages (*.ova).
  9. Select the required Avaya Aura® MS OVA file and click Next.
  10. Confirm the properties of the OVA file that you selected on the Review details page and click Next.
  11. To accept the End User License Agreement, click Accept and Next.
  12. Enter a name for the new Avaya Aura® MS VM and click Next.
  13. Select the required deployment configuration profile in the Configuration field and click Next.
    ADDITIONAL INFORMATION:
    See application documentation for the recommended system profile.
    Important:
    The VM disk size is always 50 GB when using VMware® deployment tools. To manually extend the disk size above 50 GB, use standard VMware® procedures to edit the virtual hardware settings of a deployed VM.
  14. Expand the tree under the vCenter server and select the required datacenter folder and click Next.
  15. Select Thick Provision Lazy Zeroed for the virtual disk format.
  16. Select the required destination datastore, and click Next.
  17. Select the required destination network(s) and click Next.
  18. Expand Network Settings and configure the network details for the new VM on the Customize template page.
  19. Expand System Time Settings and configure the time settings.
  20. If required, expand IPv6 Address Settings and configure the IPv6 network details.
  21. If required, expand Out of Band Management Settings and configure the out of band network details.
  22. Expand Customer Login Settings and configure the account settings.
    ADDITIONAL INFORMATION:
    Note:
    The customer account password is temporary. You must change the password at first login.
  23. To enable customer access to the root account, expand the Advanced Settings and enable the Interactive Initial Boot option. Click Next.
    ADDITIONAL INFORMATION:
    Note:
    Setting this option requires you to access the VM console to complete the initial configuration. You will be prompted for the root password in the console session.
  24. On the Ready to complete page, verify the options. If the values are incorrect, click Back to make changes. Do not select the Power on after deployment option. If the values are correct, click Finish.
  25. Wait for the system to complete deployment. The time that the system requires to complete the deployment depends on the speed of the network connection and server. The system displays the progress in Recent TasksAll.
    ADDITIONAL INFORMATION:
    Tip:
    To alter the configuration settings later, run the netSetup command in a Linux® shell.
  26. Click the refresh arrow () located to the left of your login ID at the top of the vSphere web client page.
    ADDITIONAL INFORMATION:
    The system updates the inventory list and displays the new VM.
  27. Select the new VM in the inventory list of the vSphere web client window and click the Summary tab.
  28. Select Power On from the Actions menu.
  29. To open a console page on your VM, click Launch Console on the Summary tab.
    ADDITIONAL INFORMATION:
    A console window displays the progress of the VM system initializing. If the system prompts you to confirm or update the configuration due to input error, or after you selected Interactive Initial Boot, follow the prompts to complete the configuration.
  30. When the VM initialization is complete, the system displays a login prompt. Log in using the customer account that you set up earlier. You must change the password after login.
Next steps
Configure Avaya Aura® MS.
If this media server virtual appliance will be used as a Video Compositor, you must increase the system capacity. See Resizing an Avaya Virtual Appliance for use as a Video Compositor