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
|
|
|
|
2
|
Enter the required information in the Customer Configuration Data worksheet.
|
|
|
|
3
|
Verify the customer has the required hardware at the customer site.
|
|
|
|
3
|
Download the required software.
|
|
|
|
4
|
Licenses:
-
Obtain the License Activation Code (LAC).
-
Install the license file.
|
|
|
|
5
|
Verify you have the necessary resources for the SAL Gateway.
|
|
|
|
6
|
Register for PLDS and activate license entitlements.
|
|
|
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.