Assess the infrastructure resource requirements for your deployment.

Key factors are:

• CPU usage

• Memory usage

• Storage requirements

• Network usage

• Supported capacity

Plan and resource all staging and verification activities.

This includes IP addressing, naming conventions, and application-specific configuration.

Purchase the appropriate order codes and licenses.

For customer-provided deployments: You must separately license each CMS instance, that is, each installation of an OVA. Ensure that all OVA files are accessible.

For Avaya Solutions Platform deployments: You no longer need a license key, but you must have a record in the Avaya Product Licensing and Delivery System (PLDS) of each instance of the server hypervisor.

Get the WebLM license server details and install the CMS license.

Use Avaya WebLM to manage product licenses obtained from PLDS. For more information, see Installing a license file on a WebLM server.

Ensure that you have the CMS software image for deployment.

A CMS R21.x VMware OVA is available on the Avaya Support website. You can use this to deploy CMS on your own customer-provided server.

For deployments on Avaya Solutions Platform, download the OVA with the CMS KVM images from the Avaya Support website. The KVM OVA can be used for Avaya Solutions Platform deployments and customer-provided deployments.