Deploying AE Services on ASP R6.0.x (KVM on RHEL 8.10) using Script

Last Updated : Sep 12, 2025 |

About this task

AE Services provides a KVM OVA that contains one qcow2 file:

AES-*-kvm.qcow2

Note:

  • Disk encryption is possible using the script-based deployment.

  • Always follow A1SC output for deployment of applications on the host(s). There should never be more than one instance of a specific application on the same host.

  • Deployment of applications MUST be performed one at a time and delete the artifacts prior to deploying the next application.

    Solution Deployment Manager and Solution Deployment Manager Client does not support KVM on RHEL 8.10 images for a virtualized environment.

Before you begin

  • Install ASP R6.0.x (KVM on RHEL 8.10).

    For more information, see Installing the Avaya Solutions Platform 130 Series at https://support.avaya.com/css/public/documents/101091802.

  • Download the AE Services KVM image from PLDS to your computer.

  • Login to the ASP R6.0.x CLI with custadm credentials.

  • Ensure that the staging folder exist:

    sudo ls -ld /var/lib/libvirt/staging

  • Ensure to remove the older images from the staging folder.

  • Ensure sufficient space is available in the staging folder to copy the KVM image.

  • If the staging folder does not exist, create it using the following commands:

    • sudo mkdir /var/lib/libvirt/staging

    • sudo chown custadm:wheel /var/lib/libvirt/staging

  • The chown command now allows custadm to write into the staging directory with sudo. For example, the permissions should look as follows:

    drwxr-x---. 2 custadm wheel 6 Oct 23 14:32 /var/lib/libvirt/staging

  • Copy the AE Services KVM image to the ASP R6.0.x host in /var/lib/libvirt/staging using winscp and custadm credentials.

  • Run the following command to verify the AE Services KVM image is available in the staging folder:

    sudo ls -lr /var/lib/libvirt/staging

Procedure

  1. Log in to the ASP R6.0.x CLI as a custadm user and verify the ASP version using the following command: swversion
  2. Go to the staging folder;

    sudo cd /var/lib/libvirt/staging

  3. Do the following:

ASP is on R6.0.0.0

ASP is on R6.0.0.1

  1. Run the following command to extract the OVA file: sudo tar -xvf AES-*-kvm.ova

    KVM OVA extracts the following files:

    • AES-*-kvm.ovf

    • AES-*-kvm.qcow2

    • AES-*-kvm.mf

    • AES-*-kvm.cert

    • ovf.py

    • install_vm.py

  2. Run the following script to deploy AE Services:

    sudo python3 install_vm.py

Run the following script to deploy AE Services: installVM AES-*.ova

ASP completes the auto-verification to ensure the following files are available: 

AES-*-KVM.ovf 
AES-*-kvm.qcow2
ovf.py
install_vm.py 
AES-*-kvm.mf
AES-*-KVM.cert
AES-*-KVM.cert: OK 
Verified OK
AES-*-kvm.qcow2: OK
AES-*-KVM.ovf: OK
install_vm.py: OK
ovf.py: OK
  1. Press ENTER to read the EULA.
  2. Press Y to accept the EULA.
  3. Enter a name for the AE Services virtual machine. For example, AES_VM.
  4. Select the required AE Services profile.

    For more information, see AES resource requirements and the supported footprints on ASP R6.0.x (KVM on RHEL 8.10)

  5. Select the network interfaces.

    ASP 6.0.x CLI displays the currently available network interface bridges and select the required bridge for AE Services.

    Note:
    AE Services requires two NICs:

    • NIC1 for Public IP address

    • NIC2 is for Out of Band Management (Optional)

    ASP 6.0.x CLI displays the currently available disk space and the required disk space to deploy AE Services.

  6. To configure the VM properties, enter Y in the Would you like to configure the VM properties? [y/n]: field, and continue providing the property details.
  7. In the AES Hostname field, enter a valid host name or a FQDN.

    If a FQDN is entered, FQDN also administers the local domain name. Valid characters are, a - z, A - Z, 0 - 9, and hyphen (-). The maximum length for the hostname is 15 characters.

  8. In the DNS Search Path field, enter a domain name of the AE Services virtual machine. For example, mydomain.com
  9. In the Password for cust field, enter the password for cust user. If this field is left blank, default password will be used. Reenter the password for cust user in the Confirm Password for cust field.

    The password length is a minimum of 14 characters and a maximum of 20 characters.

  10. In the Password for root field, enter the root password. If this field is left blank, default password will be used. Reenter the root password in the Confirm Password for root field.

    The password length is a minimum of 14 characters and a maximum of 20 characters.

  11. Optional In the NTP Server field, enter a valid NTP address or a hostname.

    You can type up to three NTP servers separated by a comma.

  12. Enable or disable Enhanced Avaya Security Gateway (EASG).
    Important:

    Avaya recommends to enable EASG.

    Note:

    Enable: (Recommended)

    By enabling Avaya Logins you are granting Avaya access to your system. This is necessary to maximize the performance and value of your Avaya support entitlements, allowing Avaya to resolve product issues in a timely manner.

    In addition to enabling the Avaya Logins, this product should be registered with Avaya and technically onboarded for remote connectivity and alarming. Please see the Avaya support site (support.avaya.com/registration) for additional information for registering products and establishing remote access and alarming.

    Disable:

    By disabling EASG, you are denying Avaya access to the system. This setting is not recommended as it can impact Avaya’s ability to provide support for the product. Unless the customer can manage the product, Avaya Services Logins should not be disabled.

    • Enter 1 to enable EASG.

    • Enter 2 to disable EASG.

  13. Enable or disable Data Encryption.

    By enabling Data Encryption, your Communication Product's Operational data and Log Files will be encrypted. You will be prompted to enter a pass-phrase that will be used to create/access an encryption key. Secondly, you will be asked to configure the option for local key storage.

    It is important to note that the encryption of the disk may have a performance impact. For further information, contact the Administration guide(s). Before you select an encryption option, please read the Data Privacy Guideline so that you may better understand these options.

    By disabling Data Encryption, your Communication Product's Operational data and Log Files will be left unencrypted.

    Enter 1 to Enable Encryption or enter 2 to Disable Encryption.

    1. In the Data Encryption field, if 1 is entered, do the following

      • In the Enter Encryption Passphrase field, enter the passphrase.

      • In the Confirm Enter Encryption Passphrase field, reenter the passphrase.

      • In the Require Encryption Passphrase at Boot-Time: (yes/no), enter the required value.

      If 1 is entered, you must enter the encryption passphrase whenever the AE Services reboots.

      If 2 is entered, there is no need to enter the encryption passphrase whenever the AE Services reboots.

      Important:

      You MUST remember the data encryption passphrase 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.

    2. In the Data Encryption Active field, if 2 is entered, no action is required.
  14. In the Default Gateway field, enter the default gateway address for the AE Services virtual machine.
  15. In the DNS field, enter the domain name servers for the AE Services virtual machine.
  16. In the Public IP Address field, enter the IP address for the AE Services interface.
  17. In the Public Netmask field, enter the netmask or prefix for the AE Services interface.
  18. In the Power on VM automatically after deploy?: [y/n] field, enter one of the following:

    • y: Indicates AE Services virtual machine is automatically powered-on after deployment.

    • n: Indicates user has to manually power on the AE Services virtual machine on KVM cockpit.

  19. In the Proceed?[y/n] field, enter one of the following:

    • y: AE Services deployment begins.

    • n: AE Services deployment cancels.

    Note:

    Once the AE Services virtual machine is successfully deployed, ASP R6.0.x displays the following message: Domain creation completed. Otherwise, repeat step 3 onwards.

  20. Log in to the KVM Cockpit web console as custadm in the following format: https://<IP address or FQDN of KVM host>:9090.
  21. If Web console is in Limited access mode, click on Turn on administrative access button.
    Note:

    VMs are not visible when in Limited access mode.

  22. For administration actions, on the top-right of the window, click on the Limited access or Turn on administrative access button.
  23. Navigate to System > Virtual Machines.

    Verify that the AE Services virtual machine is deployed.

  24. Click on the AE Services virtual machine.
  25. If the Power on VM automatically after deploy?: [y/n] field is set to n, then click Run to power on the virtual machine.

    If the Power on VM automatically after deploy?: [y/n] field is set to y, AE Services virtual machine starts automatically.

  26. On the AE Services virtual machine Console, accept EULA.
  27. Login to AE Services virtual machine using cust user credentials.
  28. Optional In the Overview section, enable AutoStart to automatically start the virtual machine whenever the host reboots.