Supported upgrade paths for Session Manager

Last Updated : Nov 28, 2023 |
Prolog information
The following table displays all the upgrade paths from earlier releases to Release 10.2.x.
For information about terms used in this table, see Glossary.
From offer
From Release
Session Manager
Branch Session Manager
To Software-only (VMware, KVM, RHVH, Hyper-V, AWS, GoogleCloud, or Azure) 10.2 (ISO)
To ASP 130 (OVA)/VMware 10.2 (OVA)
AVP
7.x
✓
Migration using CLI
Migration using CLI
7.1.3.x
✓
✓
Migration using CLI
Migration using CLI
8.0.1
✓
✓
Migration using CLI
Migration using CLI
8.1.x
✓
✓
Migration using CLI
Fully automated upgrade using SDM
VMware
7.x
✓
Migration using CLI
Migration using CLI
7.1.3.x
✓
✓
Migration using CLI
Migration using CLI
8.0.x
✓
✓
Migration using CLI
Migration using CLI
8.1.x
✓
✓
Migration using CLI
Fully automated upgrade using SDM
10.1.x
✓
✓
Migration using CLI
Fully automated upgrade using SDM
ASP 130
8.1.x
✓
✓
Migration using CLI
Fully automated upgrade using SDM
10.1.x
✓
✓
Migration using CLI
Fully automated upgrade using SDM
KVM/OpenStack/RHVH (OVA)
7.1.x
✓
✓
Migration using CLI
Migration using CLI
8.0.x
✓
✓
Migration using CLI
Migration using CLI
8.1.x
✓
✓
Migration using CLI
Migration using CLI
Software-only
8.0.x
✓
✓
Migration using CLI
NA
8.1.x
✓
✓
Migration using CLI
NA
10.1.x
✓
✓
Migration using CLI
NA
AWS (OVA)
7.1.x
✓
Migration using CLI
Migration using CLI
8.x
✓
Migration using CLI
Migration using CLI
Important:
  • 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, GoogleCloud, and Azure.
  • If the application supports the upgrade using Solution Deployment Manager, you can also use the CLI for upgrading that application.
  • To upgrade the application from Release 6.x to Release 10.x, upgrade the application from 6.x to 8.1.x, and then upgrade to Release 10.x. You cannot directly upgrade the Release 6.x system to Release 10.1 and later.
  • Before upgrading Session Manager to Release 10.2.x, Avaya recommends that the older Session Manager Release version must be on the latest version of its releases with the latest Security Service Pack (SSP). 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.
    When you are on a latest release, you can use the backupSM and restoreSM commands or the data migration utility to upgrade to Release 10.2.x.
  • To upgrade Session Manager from Release 7.0.x to Release 10.2 and later, first upgrade Session Manager Release 7.0.x to 10.1.x, and then upgrade to Release 10.2 and later.
    You cannot directly upgrade from Release 7.0.x to Release 10.2 and later. If you upgrade directly from Release 7.0.x to Release 10.2 and later, the upgrade might fail.
  • In a scenario where upgrade of more than one Session Manager is from releases 7.x and 8.x, Cassandra has two distinct clusters, one on Session Manager Release 7.x or 8.x and the other on Session Manager Release 10.2. In this case, the User Storage Data under System Status on System Manager shows failed. Therefore, it is recommended that you upgrade the Session Managers running Release 7.x and 8.x to release 10.2 as soon as possible.