AVAYA DOCUMENTATION CENTER
Find answers to your technical questions and learn how to use our products
No results found
Search suggestions:
- Use fewer tags and filters.
- Use different search terms.
Filters
AVAYA DOCUMENTATION CENTER
Find answers to your technical questions and learn how to use our products
No results found
Search suggestions:
- Use fewer tags and filters.
- Use different search terms.
Filters
Upgrading Avaya Aura® Communication Manager
Table of Contents
Type to filter navigation items by title
Supported upgrade paths for Communication Manager
Last Updated : Dec 08, 2021 |
Prolog information
Metadata
Keywords:
The following table displays all the upgrade paths from earlier releases to Release 10.1.
Note:
-
Before starting the application upgrade, upgrade the platform and hypervisor.
-
To upgrade System Manager, use Solution Deployment Manager Client. To upgrade applications other than System Manager, use System Manager Solution Deployment Manager.
-
Upgrade or migration using Solution Deployment Manager is only supported with the same IP Address of the application in a Software-only environment.Software-only upgrade is supported for VMware, KVM, RHVH, Hyper-V, AWS.
-
It is recommended that during manual upgrade process, you use xln backup and save translations method where server hardware (upgrade platform or environment) or operating system or hypervisor is changed.
For information about terms used in this table, see
Glossary.
Note:
For upgrading Communication Manager from Release 6.x to Release 10.3.x, first upgrade the entire Aura Solution from 6.x to 8.1.x, and then upgrade the Aura Solution to Release 10.3.x. You cannot directly upgrade the Release 6.x system to Release 10.1 and later.
|
From Offer
|
From Version
|
To Software Only 10.3
|
To ASP R6 / R7
|
To VMware 10.3
|
|---|---|---|---|---|
|
AVP
|
8.1.3.8
|
XLN Restore From CLI
|
XLN Restore From CLI
|
XLN Restore From CLI
|
|
VMware
|
8.1.3.8
|
XLN Restore From CLI
|
XLN Restore From CLI
|
XLN Restore From CLI
|
|
10.1
|
Full Backup Restore or XLN Restore From CLI
|
Full Backup Restore or XLN Restore From CLI
|
Full Backup Restore or XLN Restore From CLI
|
|
|
10.2
|
Full Backup Restore or XLN Restore From CLI
|
Full Backup Restore or XLN Restore From CLI
|
Full Backup Restore or XLN Restore From CLI
|
|
|
ASP R6 / R7
|
8.1.3.8
|
XLN Restore From CLI
|
XLN Restore From CLI
|
XLN Restore From CLI
|
|
10.1
|
Full Backup Restore or XLN Restore From CLI
|
Full Backup Restore or XLN Restore From CLI
|
Full Backup Restore or XLN Restore From CLI
|
|
|
10.2
|
Full Backup Restore or XLN Restore From CLI
|
Full Backup Restore or XLN Restore From CLI
|
Full Backup Restore or XLN Restore From CLI
|
|
|
IaaS
|
8.1.3.8
|
XLN Restore From CLI
|
XLN Restore From CLI
|
XLN Restore From CLI
|
|
10.1
|
Full Backup Restore or XLN Restore From CLI
|
Full Backup Restore or XLN Restore From CLI
|
Full Backup Restore or XLN Restore From CLI
|
|
|
10.2
|
Full Backup Restore or XLN Restore From CLI
|
Full Backup Restore or XLN Restore From CLI
|
Full Backup Restore or XLN Restore From CLI
|
Note:
Whenever the full backup is restored using SMI, check all the networking parameters are correct before you reboot your Communication Manager. For example, IP address, Netmask, and Gateway.