1.

Check the hardware platform

For ASP 130 R6, A1SC configurator output should be utilized to determine which applications are to be deployed on which server/host.

2.

Plan the staging and verification activities and assign the resources

This must include network topology, IP addressing, naming conventions, and application specific configuration and administration.

3.

Purchase the appropriate order codes

Reach out to the Avaya account team for detailed information on ordering ASP 130 R6.

Note that with the introduction of ASP 130 R6, there is no longer a license key present on the server. However, it is imperative that customers have a record in PLDS for each instance of the ASP 130 R6 server as customers and Avaya are subject to audits to ensure right to use royalties have been paid.

4.

Read the Avaya server documentation

Navigate to https://support.avaya.com and search for Avaya Solutions Platform, Release ASP 130 R6.

5.

Download the latest CMS software

Reference the CMS R21 Release Notes, Product Correction Notices, and software downloads for specific PLDS IDs links to the CMS KVM images.

The deployment process for Feature Packs, Service Packs, patches, and hot-fixes is the same regardless of the underlying hypervisor.