The document provides the procedures for upgrading Avaya Aura® System Manager from Release 7.1.3.x, 8.0.x, 8.1.x, or 10.1.x to System Manager Release 10.2.x.
Note:
Before upgrading System Manager to Release 10.2, Avaya recommends that the older System Manager Release version must be on the latest version of its releases. The latest version for Release 7.1.x, 8.0.x, and 8.1.x are Release 7.1.3.8, 8.0.1.2, and 8.1.3.8 respectively.
For upgrading System Manager from Release 7.0.x to Release 10.2 and later, first upgrade System Manager Release 7.0.x to 10.1.x, and then upgrade to Release 10.2 and later. You cannot directly upgrade the Release 7.0.x system to Release 10.2 and later. If you upgrade the application directly from Release 7.0.x to Release 10.2 and later, the upgrade might fail.
For upgrading System Manager from Release 6.x to Release 10.1 and later, first upgrade System Manager Release 6.x to 8.1.x, and then upgrade to Release 10.1 and later. You cannot directly upgrade the Release 6.x system to Release 10.1 and later. If you upgrade the application directly from Release 6.3.x to Release 10.1 and later, the upgrade fails.
If you upgrade System Manager from an older release like 7.1.3.x, 8.0.x, 8.1.x, or 10.1.x to Release 10.2.x, and the goal is to apply the latest Feature Pack or Service pack of 10.2.x, then you can install the latest service pack or feature pack of System Manager Release 10.2.x as part of the migration process. For an upgrade/migration, you should not install the mandatory patch manually. The data migration utility prompts you to install the mandatory patch or the latest service pack
For example, if you upgrade System Manager from Release 10.1.x to Release 10.2.x, then you can directly apply the Release 10.2.x patch as part of data migration. You do not need to apply the 10.2 GA patch (System_Manager_10.2.0.0_GA_Patch_rxxxxxxxxx.bin) in the intermediate step.
When upgrading to System Manager Release 10.2.x on VMware, the VMware ESXi version must be 7.0 or 8.0.
Note:
From Release 10.1 and later, Appliance Virtualization Platform is no longer available for deploying or upgrading the Avaya Aura® applications. To upgrade the Avaya Aura® applications, migrate Appliance Virtualization Platform to Avaya Solutions Platform 130 (KVM on RHEL 8.10) Release 6.0.
From Release 10.1 and later, Avaya Aura® applications will no longer have the Amazon Web Services (AWS). Alternately, you can continue to deploy the application by using the software-only offer. For more information, see the product-specific Software-only and Infrastructure As a Service Environments deployment guide.
Use the Solution Deployment Manager client Release 10.2.x to upgrade System Manager to Release 10.2.x from the following:
-
System Manager Release 7.1.3.x, 8.0.x, or 8.1.x running on Appliance Virtualization Platform on Avaya-provided server to the latest version of System Manager on Avaya Solutions Platform 130 (Avaya-supplied KVM on RHEL 8.10) Release 6.0 or on VMware 7.0 or 8.0 in a customer-provided Virtualized Environment.
System Manager Release 7.1.3.x, 8.0.x, 8.1.x, or 10.1.x running on VMware in customer-provided Virtualized Environment to the latest version of System Manager on Avaya Solutions Platform 130 (Avaya-supplied KVM on RHEL 8.10) Release 6.0 or on VMware 7.0 or 8.0 in a customer-provided Virtualized Environment.
System Manager Release 7.1.3.x, 8.0.x, 8.1.x, or 10.1.x running on VMware in customer-provided Virtualized Environment or System Manager Release 7.1.3.x, 8.0.x, or 8.1.x running on Appliance Virtualization Platform to latest version of System Manager in Software-only environment.
In relation to Avaya Aura® Messaging, note the following points. These points apply to Avaya Aura® Messaging only. Avaya IX™ Messaging, also known as Officelinx, is not impacted.
Starting with 10.2.x, if AAM is managed by System Manager then before upgrading System Manager, clean the AAM data from System Manager.
You must administer mailboxes natively in the AAM Management interface.
For more information, see Cleaning Avaya Aura Messaging communication profile data from System Manager.
