Deploying the application OVA by accessing the ESXi host directly

Last Updated : Oct 11, 2023 |
Prolog information
Metadata
Keywords:
Use this procedure to deploy the application OVA on Avaya Solutions Platform 130 and equivalent server.
Note:
Enabling of encryption is not supported when deploying Communication Manager on ESXi host directly.
Before you begin
When you deploy or upgrade Avaya Aura® applications on Avaya Solutions Platform 130 ensure to:
  • Update the Dell R660xs BIOS and firmware to the latest release.
  • Enable the iDRAC and connect it to an ethernet switch.
    Note:
    After deploying OVA directly from host, you must check that HDD size matches your profile.
  1. To access the ESXi host, do the following:
    1. On the web browser, type the ESXi host FQDN or IP address.
    2. In User name, type the username of the ESXi host.
    3. In Password, type the password of the ESXi host.
    4. Click Log in.
  2. Right-click an ESXi host and select Create/Register VM.
    ADDITIONAL INFORMATION:
    The system displays the New virtual machine dialog box.
  3. On the Select creation type page, select Deploy a virtual machine from an OVF or OVA file.
  4. Click Next.
  5. On the Select OVF and VMDK file page, do the following:
    1. Type a name for the virtual machine.
    2. Click to select files or drag and drop the OVA file from your local computer.
  6. Click Next.
  7. On the Select storage page, select a datastore, and click Next.
  8. To accept the End User License Agreement on the License agreements page, click I Agree.
  9. Click Next.
  10. On the Deployment options page, perform the following:
    1. From Network mappings, select the required network.
    2. From Disk provisioning, select Thick provision lazy zeroed.
    3. From Deployment type, select profile.
      ADDITIONAL INFORMATION:
      For more information about supported footprints, see Supported footprints of Communication Manager on VMware.
    4. Clear Power on automatically.
  11. Click Next.
  12. On the Additional settings page, click Next.
    ADDITIONAL INFORMATION:
    Note:
    Entering IP or Naming data under Additional settings will not carry forward to the virtual machine. This information must be entered manually later in the implementation process.
  13. On the Ready to complete page, review the settings, and click Finish.
    ADDITIONAL INFORMATION:
    Wait until the system deploys the OVA file successfully.
  14. To edit the virtual machine settings, click the VM radio option and perform the following:
    • Click Actions Edit Settings to edit the required parameters.
      Expand the Memory setting for Communication Manager deployed as an LSP, and set the value of the Reservation parameter to None.
      Note:
    • Click Save to save the reservation changes.
    ADDITIONAL INFORMATION:
    Note:
    Ensure that the virtual machine is powered down to edit the settings.
  15. To ensure that the virtual machine automatically starts after a hypervisor reboot, click the VM radio option, and click Actions Autostart Enable.
    ADDITIONAL INFORMATION:
    Note:
    If you do not enable autostart, manually start the virtual machine after the hypervisor reboot. Autostart must be enabled on the Host for the virtual machine autostart to function.
  16. To start the virtual machine, if application is not already powered on, perform one of the following steps:
    • Click the VM radio option and click Actions Power Power On.
    • Right-click the virtual machine and click Power Power On.
    • Navigate to HostVirtual Machines, select the virtual machine and click ActionsPowerPower On.
    ADDITIONAL INFORMATION:
    The system starts the application virtual machine. When the system starts for the first time, configure the parameters for the application.
  17. Click Actions Console, select the open console type, verify that the system startup is successful, then input the application configuration parameters.
    ADDITIONAL INFORMATION:
    Log in as craft/craft01, then input the application configuration parameters explained in the Configuration chapter.