Optional Upgrade Sequence for Avaya components

Last Updated : Apr 16, 2026 |
Prolog information
Metadata
Keywords:
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. If you skip the upgrade sequence order, skip all the optional steps. For more information about the optional upgrade sequence, see 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 enables 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. You can upgrade individual components out of sequence where such configurations are certified to be interoperable.
See 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 use ASP130/S8300 5.0 or earlier, you must first upgrade or migrate to ASP130/S8300E-compatible hardware and ensure that the system is running a supported ASP R6/R7 software release before proceeding with the upgrade to Avaya Aura® R10.3.x.
To upgrade the Avaya Aura® applications to R10.3.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 Server.
Avaya Messaging R11.0 is compatible with Avaya Aura® R10.3.x. Upgrade Avaya Messaging to R11.0 or later before you upgrade Aura® components to R10.3.x.
Upgrade Avaya components in the following sequence. Skip any component that is not part of your solution.
  1. Hard endpoints — H.323 and SIP.
  2. Standalone Avaya WebLM.
    Note:
    To upgrade standalone WebLM, use the latest standalone WebLM R10.3.x. If you upgrade Communication Manager or Application Enablement Services to 10.3 and have a standalone WebLM in the setup, upgrade the standalone WebLM to R10.3. Otherwise, licensing for Communication Manager and Application Enablement Services fails.
  3. SAL Gateway.
  4. Avaya Aura® System Manager, which includes System Manager WebLM.
    Update System Manager based on your setup:
    • Non-Geography Redundancy setup: Update standalone System Manager.
    • Geography Redundancy setup: Update 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 Gateway R43.x, use Gateway R38.21.2 or later. If the Gateway runs older loads, the download fails and Gateway displays the following message: Incompatible software image. To resolve this issue, upgrade to 38.21.2 (G430) or 38.21.3 (G450).
    If you skip the order of sequence, skip all the optional steps.
    Important:
    Ensure that you read the Limitations 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 that you read the Limitations before you skip this step.
  14. Optional: Avaya Aura® Communication Manager Survivable Remote Servers (formerly known as Local Survivable Processor or LSP).
    Note:
    If you skip the order of sequence, skip all the optional steps.
    Important:
    Ensure that you read the Limitations 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 Server or ESS).
  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:
    Upgrade Avaya Messaging to R11.0 or later before upgrading Aura® components to R10.3.x.
  21. Avaya Aura® Web Gateway.
  22. Workplace Clients.
    Clients rely on Avaya Aura® Device Services in the 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 R10.3 before you upgrade Communication Manager to R10.3.
    Applications that System Manager supports do not follow the general Avaya Aura® Release numbering schema. For more information about the application versions that System Manager supports, see the Avaya Aura® Release Notes on the Avaya Support website.
  • Uninstall the old Solution Deployment Manager client and install the latest Solution Deployment Manager client.
    The 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 R10.3 OVA, the Solution Deployment Manager client version must be on R10.3. The Solution Deployment Manager client cannot be on R10.1 or R10.2.
For information about upgrading the application, see the application-specific upgrade guide on the Avaya Support website.
Related links
Optional Upgrade Sequence