Upgrading duplex Communication Manager Release 7.x or 8.x or 10.1.x to duplex Communication Manager Release 10.2.x and migrating to a new server by using System Manager Solution Deployment Manager

Last Updated : Jul 08, 2025 |
Prolog information
Metadata
Keywords:
In duplex Communication Manager servers, you need to first upgrade the standby Communication Manager server, and then the active Communication Manager server.
Use the procedure to upgrade duplex Communication Manager to Release 10.2.x from:
  • Release 7.x running on Appliance Virtualization Platform or on VMware.
  • Release 8.x running on Appliance Virtualization Platform or on VMware.
  • Release 10.1.x running on Appliance Virtualization Platform or on VMware.
    Note:
    From Release 10.1, Appliance Virtualization Platform is no longer available. Therefore, if Communication Manager Release 8.1.x and earlier is on the Appliance Virtualization Platform host, then migrate Appliance Virtualization Platform to Avaya Solutions Platform 130 Release 5.x before upgrading Communication Manager to Release 10.1. Migration of Appliance Virtualization Platform is supported from Avaya Solutions Platform 120 (Dell PowerEdge R640).
The procedure covers upgrades and migration to a new server.
Before you begin
  • Ensure that the duplex Communication Manager is prepared for migration.
    For more information, see Preparing duplex Communication Manager servers for upgrade.
  • Ensure that the server that you are going to upgrade is in maintenance mode. For that, log in to the command line interface of the server, and then type the command server —b.
  • Ensure that System Manager is running on Release 10.2.
  • Add a location.
    For information, see Adding a location.
  • Add the ESXi, vCenter, Appliance Virtualization Platform, or Avaya Solutions Platform 130 host.
    For information about adding the host, see Adding an ESXi, or Avaya Solutions Platform 130 host.
    For information about adding vCenter, see Adding a vCenter to Solution Deployment Manager.
    Important:
    • If the application is running on the ESXi version that is not supported with Release 10.2, then first upgrade the ESXi to a supported ESXi version.
      For information about the supported ESXi version, see Supported ESXi version.
      For information about upgrading ESXi, see the VMware product documentation.
    • If ESXi is managed by vCenter, ensure that the vCenter version is same or higher than the ESXi version.
    • If the application is running on the server that is not supported with Release 10.2.x, then deploy Avaya Solutions Platform 130.
      For information about supported servers, see Supported servers for Avaya Aura applications
  • Select the Communication Manager virtual machine and click More ActionsRe-establish connection to establish the trust.
    For information, see Re-establishing trust for Solution Deployment Manager elements.
  • Ensure that elements that you want to upgrade are in sync with the elements displayed on the Upgrade Management page.
  • Make a note of the Network configuration, Duplication Parameters, and Server role details. You may require these details during the upgrade.
  1. To start upgrading the standby Communication Manager server, do the following:
    1. On the System Manager web console, click ServicesSolution Deployment Manager.
    2. In the navigation pane, click Upgrade Management.
    3. Perform refresh, analyze, download the entitled version, analyze, and run the preupgrade check for the standby Communication Manager server.
      ADDITIONAL INFORMATION:
      After the second analyze operation, the status column displays Ready for Upgrade.
    4. Select the standby Communication Manager or System Platform, and click Upgrade ActionsUpgrade/Update.
    5. On the Upgrade Configuration page, click Edit.
    6. On the Edit Upgrade Configuration page, provide the mandatory parameters along with new target host information, latest patch file, and credentials.
      ADDITIONAL INFORMATION:
      Note:
      Auto-commit is not supported if you are migrating to a new target server.
      ADDITIONAL INFORMATION:
      Important:
      If you are upgrading from non-encrypted Communication Manager to encrypted Communication Manager, then do not select the Require Encryption Pass-Phrase at Boot-Time check box. Otherwise, your upgrade fails.
      ADDITIONAL INFORMATION:
      For information about parameters, see Edit Upgrade Configuration field descriptions.
    7. Complete the details, and click Save.
    8. Schedule the upgrade of the standby Communication Manager.
    9. Check the job status for upgrade job.
      STEP RESULT:
      The system upgrades the standby Communication Manager to the latest release, and restores the data on the same Communication Manager system.
  2. To configure the newly upgraded standby Communication Manager server, do the following:
    1. Log in to the standby Communication Manager System Management Interface (SMI).
    2. Click AdministrationServer (Maintenance)Server Configuration, and configure the following parameters:
      ADDITIONAL INFORMATION:
      • Network Configuration
      • Duplication Parameters
      • Server role
    3. To release the server busy out state, from the command line interface of the standby Communication Manager, type server -r.
      ADDITIONAL INFORMATION:
  3. To busy out the server, from the active Communication Manager command line interface, type server -b.
  4. Verify that all elements associated with Communication Manager, such as TN Boards, media gateways, and media modules get registered with the new active server and the calls get processed with the new active server.
  5. To start upgrading the Communication Manager server that was active earlier, do the following:
    1. On the System Manager web console, click ServicesSolution Deployment Manager.
    2. In the navigation pane, click Upgrade Management.
    3. Perform refresh, analyze, download the entitled version, analyze, and run the preupgrade check for the Communication Manager server.
      ADDITIONAL INFORMATION:
      After the second analyze operation, the status column displays Ready for Upgrade.
    4. Select the active Communication Manager or System Platform, and click Upgrade ActionsUpgrade/Update.
    5. On the Upgrade Configuration page, click Edit.
    6. On the Edit Upgrade Configuration page, provide the mandatory parameters along with new target host information, latest patch file, and credentials.
      ADDITIONAL INFORMATION:
      For information about parameters, see Edit Upgrade Configuration field descriptions.
    7. Complete the details, and click Save.
    8. Schedule the upgrade of the active Communication Manager.
    9. Check the job status for upgrade job.
      STEP RESULT:
      The system upgrades the active Communication Manager to the latest release, restores the data, and installs the feature pack file that you uploaded corresponding to the latest feature pack release.
  6. To configure the newly upgraded active Communication Manager server, do the following:
    1. Log on to the SMI of the active Communication Manager.
    2. Click AdministrationServer (Maintenance)Server Configuration
      ADDITIONAL INFORMATION:
      • Network Configuration
      • Duplication Parameters
      • Server role
    3. To release the server busy out state, from the command line interface of the standby Communication Manager, type server -r.
      ADDITIONAL INFORMATION:
      The standby server becomes active because no duplication link is available between the active Communication Manager and the new standby Communication Manager.
    4. To interchange the roles of standby and active Communication Manager servers from the command line interface of the active or standby Communication Manager server, type server -i.
      ADDITIONAL INFORMATION:
      The standby server becomes the main Communication Manager server, and starts processing calls.
Related links
Upgrading Communication Manager from Release 7.1.3.8 or 8.1.3.8 or 10.1.x to 10.2.x on ASP 130 or VMware