Planning checklist for ASP R6.0.x (KVM on RHEL 8.10)

Last Updated : Dec 04, 2024 |

Ensure that the customer completes the following before deploying the Session Manager Open Virtualization Application (OVA) on Avaya-supplied Avaya Solutions Platform 130.

#

Action

Links/Notes

1

Assess and verify the resource requirements with the customer.

The key factors are:

  • CPU utilization

  • Memory usage

  • Storage requirements

  • Network utilization

  • Supported capacity

See Supported footprints of Session Manager on ASP R6.0.x (KVM on RHEL 8.10).

2

Enter the required information in the Customer Configuration Data worksheet.

See Customer configuration data.

3

Verify the customer has the required hardware at the customer site.

See Supported hardware for ASP R6.0.x (KVM on RHEL 8.10).

3

Download the required software.

See Downloading software from PLDS.

4

Licenses:

  1. Obtain the License Activation Code (LAC).

  2. Install the license file.

See Installing a license file.

5

Verify you have the necessary resources for the SAL Gateway.

See SAL Gateway.

6

Register for PLDS and activate license entitlements.

Go to the Avaya Product Licensing and Delivery System at https://plds.avaya.com/.
Note:

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

With the introduction of Avaya Solutions Platform R6.0.x there is no longer a specific license key needed as was present with Avaya Solutions Platform 5.1.x and earlier versions running on ESXi. However, it is imperative that customers have a record in PLDS for each and every instance of the server hypervisor as customers and Avaya will be subject to audits to ensure right to use royalties have been paid.