Optional Upgrade Sequence for Avaya components

Last Updated : Apr 16, 2026 |
Prolog information
Metadata
Keywords:
Upgrade Avaya components and solution in the following sequence. If any of the Avaya components are not part of your solution, you can skip that particular component and move to the next component.
If you choose the Optional Upgrade Sequence feature, you can upgrade the core Communication Manager before you upgrade your Survivable Remote Servers (LSP). In the following Optional Upgrade Sequence, you can skip steps 12 to 14. Note that if you skip the order of sequence, skip all the optional steps. For more information, read Optional Upgrade Sequence.

Disclaimer on Upgrade Sequence Flexibility

While Avaya recommends following the documented upgrade sequence to maintain solution stability and validated integration, the sequence allows flexibility in specific scenarios. Avaya supports component versions that may be ahead or behind others in the upgrade path, provided they are documented in the Product Compatibility Matrix published on the Avaya Support site. Customers may upgrade individual components out of sequence where such configurations are certified to be interoperable.
Refer to the Product Compatibility Matrix before performing any upgrades out of sequence.
For the latest and most accurate compatibility information, go to http://support.avaya.com/CompatibilityMatrix/Index.aspx.
Note:
If you are using ASP130/S8300 5.0 or earlier, you must first upgrade to ASP130/S8300 5.1 or 6.0 before upgrading to Avaya Aura® Release 10.2.x.
To upgrade the Avaya Aura® applications to Release 10.2.x, upgrade the hypervisor to a supported version.
For information about the supported ESXi version, see Supported ESXi version.
For information about the supported KVM version, see Supported ASP R6.0.x (KVM on RHEL 8.10) version.
With Aura® R10.2.x, Avaya Messaging R11.0 is compatible. Upgrade Avaya Messaging to R11.0 or later before upgrading Aura® components to R10.2.x.
  1. Hard Endpoints- H.323 and SIP
  2. Standalone Avaya WebLM.
    Note:
    With Avaya Aura® Release 10.2, standalone WebLM is not available. To upgrade standalone WebLM, use the latest standalone WebLM Release 10.1.3.x. If you upgrade Communication Manager or Application Enablement Services to 10.2 and have a standalone WebLM in the setup, upgrade the standalone WebLM to Release 10.1.3.1 or later. Otherwise, the licensing for Communication Manager and Application Enablement Services will not work.
  3. SAL Gateway
  4. Avaya Aura® System Manager includes System Manager WebLM and System Manager Solution Deployment Manager.
    In the:
    • Non-Geography Redundancy setup, update standalone System Manager.
    • Geography Redundancy setup, update the primary System Manager.
  5. Avaya Aura® Session Manager, Core Session Managers only
  6. Avaya Breeze® platform and other Snap-ins
  7. Avaya Call Management System
  8. Avaya Experience Portal
  9. Avaya Oceana®
  10. Avaya Aura® Device Services
  11. Avaya Aura® Media Server
  12. Optional: G4XX Media Gateways
    Note:
    To successfully upgrade to Release 43.x, use Gateway 38.21.2 or later. If the gateway runs older loads, the download fails and displays the following message: Incompatible software image. To resolve, upgrade to 38.21.2 (G430) / 38.21.3 (G450).
    If you skip the order of sequence, skip all the optional steps.
    Important:
    Ensure to read the Limitations of Optional Upgrade Sequence before you skip this step.
  13. Optional: Avaya Aura® Branch Session Manager
    Note:
    If you skip the order of sequence, skip all the optional steps.
    Important:
    Ensure to read the Limitations of Optional Upgrade Sequence before you skip this step.
  14. Optional: Avaya Aura® Communication Manager Survivable Remote Servers formerly known as Local Survivable Processors.
    Note:
    If you skip the order of sequence, skip all the optional steps.
    Important:
    Ensure to read the Limitations of Optional Upgrade Sequence before you skip this step.
  15. Avaya Aura® Application Enablement Services
  16. Avaya Aura® Presence Services Snap-in on Avaya Breeze® platform
  17. Avaya Aura® Communication Manager Survivable Core Servers, formerly known as Enterprise Survivable Servers
  18. Avaya Aura® Communication Manager feature servers and evolution servers
    In a duplex configuration, update the following:
    • Standby Communication Manager server
    • Active Communication Manager server
  19. Avaya IP Office™ platform
  20. Avaya Messaging, formerly known as Avaya IX™ Messaging and Officelinx
    Important:
    Avaya Messaging must be upgraded to R11.0 or later before upgrading Aura® components to R10.2.x.
  21. Avaya Aura® Web Gateway
  22. Workplace Clients
    Clients are dependent on Avaya Aura® Device Services in Avaya Aura® Platform.
  23. Avaya Session Border Controller (ASBCE)
Note:
  • System Manager is an integral part of the Avaya Aura® solution.
  • System Manager must be on the same or higher release than the application you are upgrading. For example, you must upgrade System Manager to 10.2 before you upgrade Communication Manager to 10.2.
    All applications supported by System Manager do not follow the general Avaya Aura® Release numbering schema. Therefore, for application versions System Manager supports, see Avaya Aura® Release Notes on the Avaya Support website.
  • Uninstall the old Solution Deployment Manager Client and install the latest Solution Deployment Manager Client.
    Solution Deployment Manager Client must be on the same or higher release than the OVA you are deploying. For example, if you are deploying Communication Manager 10.2 OVA, Solution Deployment Manager Client version must be on Release 10.2. Solution Deployment Manager Client cannot be on Release 10.1 or Release 8.1.
For information about upgrading the application, see the application-specific upgrade guide on the Avaya Support website.
Related links
Optional Upgrade Sequence