Deploying Avaya WebLM on ASP R6.0.x (KVM on RHEL 8.10) using Script

Last Updated : Dec 20, 2024 |

About this task

Use this procedure to run a Command Line Interface (CLI) script to create a virtual machine. Verify that you successfully created the virtual machine by logging in to KVM Cockpit to view the list of virtual machines.

Avaya WebLM provides a KVM OVA that contains one qcow2 file:

WebLM-*.qcow2

Note:

  • 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 Avaya WebLM KVM image from PLDS to your computer.

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

  • Ensure that the staging folder exists:

    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 Avaya WebLM KVM image to the ASP R6.0.x host in /var/lib/libvirt/staging using winscp and custadm credentials.

  • Ensure you are logged into the ASP R6.0.x CLI. If not, login to the ASP R6.0.x CLI with custadm credentials.

    Note:

    All the commands listed in the below points must be prefaced with sudo:

  • Run the following command to verify the Avaya WebLM KVM image is available in the staging folder:

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

  • Go to /var/lib/libvirt/staging folder, and run the following command to extract the ova file: sudo tar -xvf WebLM-*.ova

    KVM OVA file extracts the following files:

    • WebLM-*.ovf

    • WebLM-*.mf

    • WebLM-*.cert

    • install_vm.py

    • ovf.py

    • WebLM-*.qcow2

Procedure

  1. Log in to the ASP R6.0.x CLI and go to the staging folder:

    sudo cd /var/lib/libvirt/staging

  2. Run the following script to deploy Avaya WebLM:

    sudo python3 install_vm.py

  3. Press ENTER to read the EULA.
  4. Press Y to accept the EULA.
  5. Enter a name for the Avaya WebLM virtual machine. For example, WebLM_Main.
  6. Select the required Avaya WebLM profile.

    For more information, see Supported footprint of WebLM on KVM

  7. Select the network interfaces.

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

    ASP 6.0.x CLI displays the currently available disk space and the required disk space to deploy Avaya WebLM.

  8. 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:
    1. Please enter the IPv4 Address to assign to the VM. For example, x.x.x.x
    2. Please enter the Netmask to assign to the VM. For example, m.m.m.m
    3. Please enter the IPv4 Address of your default gateway. For example, x.x.x.x
    4. Please enter the IP Address of your DNS server. For example, x.x.x.x

      You can type multiple IP's seperated by a comma.

    5. Please enter the Short Hostname to assign to the VM. For example, xyz
    6. Optional IPv6 Address. Please enter IPv6 address
    7. Optional IPv6 Network Prefix. Please enter IPv6 Network Prefix
    8. Optional IPv6 Gateway. Please enter IPv6 Gateway
    9. Please enter the Domain Name to assign to the VM, enter valid domain name for the virtual machine.
    10. Optional Please enter the default Search List, enter the valid search list.
    11. Please provide NTP Server IP/FQDN, enter the valid NTP server IP or FQDN.

      You can type multiple IP or FQDN seperated by a comma.

    12. Please enter the WebLM command line user name, enter valid user name for the Avaya WebLM. For example: cust.

      Do not use user names such as admin, csadmin.

      Do not use: initial, admin, csadmin, postgres, root, bin, daemon, adm, sync, dbus, vcsa, ntp, chrony, saslauth, sshd, tcpdump, xfs, rpc, rpcuser, nfsnobody, craft, inads, init, rasaccess, sroot, postgres, smgr, nortel.

    1. In the Please enter the WebLM command line user password field, enter the password for Avaya WebLM command line user.
    2. In the Confirm Please enter the WebLM command line user password field, re-enter the password
    3. In the Please enter the WebLM UI admin user password field, enter the password for Avaya WebLM UI admin.
    4. In the Confirm Please enter the WebLM UI admin user password field, re-enter the password.
  9. 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.

  10. In the Do you want to set a root password?(yes/no) field, enter the required value.
  11. In the Root Password field, enter the root password. If this field is left blank, default password will be used. Reenter the root password in the Confirm Root Password field.
  12. In the Power on VM automatically after deploy?: [y/n] field, enter one of the following:

    • y: Indicates Avaya WebLM virtual machine is automatically powered-on after deployment.

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

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

    • y: Avaya WebLM deployment begins.

    • n: Avaya WebLM deployment cancels.

    Note:

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

  14. Log in to the KVM Cockpit web console as custadm in the following format: https://<IP address or FQDN of KVM host>:9090.
  15. 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.

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

    The Avaya WebLM is deployed.

  18. 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, the virtual machine starts automatically.

  19. Login to Avaya WebLM virtual machine using cust user credentials.

    During the first login, change the cust user password.

  20. Optional In the Overview section, enable AutoStart to automatically start the virtual machine whenever the host reboots.