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

Last Updated : Sep 12, 2023 |
Prolog information
Metadata
Keywords:
For upgrading duplex Communication Manager servers, you must use the following upgrade sequence:
1. Upgrade Standby Communication Manager
2. Upgrade Active Communication Manager
Use the procedure to upgrade duplex Communication Manager to Release 10.2.x from:
  • Release 7.1.3.8 running on Appliance Virtualization Platform or on VMware.
  • Release 8.1.3.8 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 on the same server.
Before you begin
  • Ensure that the duplex Communication Manager is prepared for migration.
  1. To upgrade the standby Communication Manager, 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. Ensure that the existing server that you are going to upgrade is in the maintenance mode. Log in to the CLI of the standby and type the command server -b.
    5. Select the standby Communication Manager or System Platform and click Upgrade ActionsUpgrade/Update.
    6. On the Upgrade Configuration page, click Edit.
    7. On the Upgrade Configuration page, select the Override preupgrade check check box.
      ADDITIONAL INFORMATION:
      When you select the check box, the upgrade process continues even when the recommended checks fail in preupgrade check.
    8. To provide the upgrade configuration details, click Edit.
    9. On the Edit Upgrade Configuration page, perform the following:
      ADDITIONAL INFORMATION:
      1. Do one of the following:
        • For same server, provide the mandatory parameters along with same target host information, latest OVA/ISO file, and credentials.
        • For new target server, provide the mandatory parameters along with new target host information, latest OVA/ISO file, and credentials.
          Note:
          Auto-commit is supported for the same server migration only.
      2. Complete the parameters as mentioned in the Edit Upgrade Configuration field descriptions
        Important:
        If you are upgrading from non-encrypted Communication Manager to encrypted Communication Manager, complete the details as mentioned in the Edit Upgrade Configuration field descriptions.
      3. Complete the details, and click Save.
    10. On the Upgrade Configuration page, ensure that the Configuration Status field displays .
  2. From the command line interface of the standby Communication Manager, perform the following:
    ADDITIONAL INFORMATION:
    1. To release the server from the busy out state, type server -r.
    2. Type server, and ensure that the duplication link is active and the standby server refreshes.
  3. From the command line interface, on the active Communication Manager, interchange the standby and active Communication Manager, type server -i.
  4. To start the upgrade of the current 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. 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 same target host information, latest patch file, and credentials.
      ADDITIONAL INFORMATION:
      Note:
      Auto-commit is supported for the same server migration only.
      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 Communication Manager.
    9. On the Upgrade Management page, in the Release Status column, verify that the status is Paused.
    10. For Avaya-provided server in Avaya Aura® Virtualized Appliance environment, install the Appliance Virtualization Platform host, and add the Appliance Virtualization Platform host from Application Management.
    11. To resume the upgrade process, click Upgrade ActionsResume to resume the upgrade process.
    12. On the Resume Configuration, select the Appliance Virtualization Platform host and datastore.
    13. Check the job status for upgrade job.
      STEP RESULT:
      At this point, the two Communication Manager systems get upgraded.
  5. Do the following:
    1. Type server, and ensure that the duplication link is active and the standby server refreshes.
    2. 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.
      STEP RESULT:
      The duplication link becomes active and the standby Communication Manager server refreshes.
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