The following is a summary of new content for CMS Release 21.0:
Report scheduling
You can schedule a report in the CMS Web Client. Scheduling options include once, daily, weekly, or monthly. After setting up a schedule, use the Scheduler tab to view and manage your scheduled reports.
Automated CMS High Availability (HA) configuration
If two CMS servers are installed, use the new HA configuration process. Log in to the CMS server console as root, and enter the cmsadm command to access the HA configuration option. You can set up primary and secondary server roles and reverse the roles if needed.
Informix database upgrade
CMS now uses HCL Informix 14.10, replacing IBM Informix 12.10 used in previous releases.
Upgrades to Release 21.0
You can perform a full software or platform upgrade from Release 20.0 or earlier to Release 21.0. You can upgrade directly to Release 21.0 from Release 16.x and later.
KVM installation
CMS Release 21.0 supports KVM installation on:
Avaya Solutions Platform 130 R6 server (ASP 130 R6)
Customer-provided servers
Discontinued hardware-only platforms
CMS no longer supports hardware-only installations and upgrades. The following platforms are no longer supported:
Dell PowerEdge R630 and R730
HPE ProLiant DL380 Gen9
Data backup
The following backup products are no longer supported:
IBM Spectrum Protect (formerly Tivoli Storage Manager)
A range of database items has been expanded from integer (4-byte) to int8 (8-byte) format. Refer to the Avaya Call Management System Database Items and Calculations document for details.
The existing VMware image is still supported, but only for installation on customer-provided hardware.
The ASP 130 R5 server is now end-of-sale.
The ASP 130 R6 server supports KVM-based virtual machines.
Changes introduced in CMS R21 Feature Pack 2
You can configure CMS to use an enterprise authentication service, such as Avaya Identity and Access Management (IAM), to access the CMS Web Client.
You can schedule administration jobs from the Back Up Data screen.
You can enable or disable data collection for all ACDs from the Data Collection screen.
You can enter the enterprise ID on the User data screen.
The enterprise ID is validated for authentication when the primary user ID does not match a CMS username. Authentication may fail in customer environments where numeric IDs are used as the user principal name (UPN) in the enterprise SSO platform.
A mechanism that masks failover from Web Client users has been introduced. The cloud-based load balancer uses the CMS session to seamlessly redirect the Web Client link from one CMS server to another.
Previously, during a failover, users were logged out and had to log in again. With Feature Pack 2, users no longer need to re-enter their username and password after a failover. However, they must click Enterprise Sign In. This functionality works with Microsoft Azure and Okta.
