Upgrading Communication Manager Release 8.1.x to Communication Manager Release 10.1.x on Avaya Solutions Platform S8300 using System Manager Solution Deployment Manager

Last Updated : Dec 04, 2023 |
Prolog information
Metadata
Keywords:
Use the procedure to upgrade Communication Manager main or survivable remote server (LSP) Release 8.1.x running on Appliance Virtualization Platform to Release 10.1.x on Avaya Solutions Platform S8300.
For migrating Communication Manager survivable remote server or main on Avaya Solutions Platform S8300 Release 5.1, only the CM Main Max User 1000 and CM Survivable Max User 1000 profiles are supported.
Note:
From Release 10.1, Appliance Virtualization Platform is no longer available. Therefore, if Communication Manager is deployed on Appliance Virtualization Platform Release 7.x or 8.0.x, then first upgrade Appliance Virtualization Platform to Release 8.1.x and then migrate Appliance Virtualization Platform 8.1.x to Avaya Solutions Platform S8300.
Before you begin
  1. Ensure to migrate Appliance Virtualization Platform to Avaya Solutions Platform S8300.
    For information, see Migrating from Appliance Virtualization Platform deployed on S8300 Server to Avaya Solutions Platform S8300.
  2. Ensure that System Manager is running on Release 10.2.
  3. Add a location in the System Manager Solution Deployment Manager, if it is already not available.
    For information, see Adding a location.
  4. If Appliance Virtualization Platform that was migrated to Avaya Solutions Platform S8300 Release 5.1 (Avaya Supplied ESXi 7.0) is available in Solution Deployment Manager on the Platforms tab, then first remove that Appliance Virtualization Platform and then add the Avaya Solutions Platform S8300 Release 5.1 (Avaya Supplied ESXi 7.0) host in the System Manager Solution Deployment Manager by using the FQDN only. Do not add an ASP S8300 Release 5.1 host using the IP address.
    Add the Avaya Solutions Platform S8300 host in the System Manager Solution Deployment Manager.
  5. Add Communication Manager in the inventory.
    For information about adding a Communication Manager instance to System Manager, see Adding or editing a standalone Communication Manager instance to System Manager
    For information about managing elements, see Administering Avaya Aura® System Manager.
  6. Ensure that elements that you want to upgrade are in sync with the elements displayed on the Upgrade Management page.
    To ensure that the elements are in sync, on the Communication Manager CLI, enter the following command: swversion -s. Communication Manager CLI displays the Communication Manager application details. The application details on the Communication Manager CLI must be same as the software details on the Upgrade Management page.
  1. On the System Manager web console, click ServicesSolution Deployment Manager Client.
  2. In the navigation pane, click Upgrade Management.
  3. Select Communication Manager and associated elements, and then click Pre-Upgrade ActionsRefresh Element(s).
  4. On the next page, click Schedule.
    ADDITIONAL INFORMATION:
    You can schedule the job now or for a later time.
  5. To verify the status of Communication Manager that you refreshed, click the icon on the Last Action Status column.
  6. After refresh is done, click Pre-Upgrade ActionsAnalyze.
  7. On the next page, click Schedule.
    ADDITIONAL INFORMATION:
    You can schedule the job now or for a later time.
  8. To verify the status of Communication Manager that you refreshed, click the icon on the Last Action Status column.
  9. After analyze is done, click Pre-upgrade ActionsPre-upgrade Check.
  10. On the Pre-upgrade Configuration page, do the following:
    1. Do one of the following:
      ADDITIONAL INFORMATION:
      • For same server, provide the mandatory parameters along with the same target host information.
        Following are the mandatory parameters:
        • Target platform: Select the platform on which Communication Manager is hosted
        • Data store: Select the existing host's data store
        • New Target platform: N/A
        • Data store: N/A
        • Upgrade Source: Select the upgrade source
        • Upgrade/update to: Select the target Communication Manager release (OVA/ISO)
        • Flexi Footprint: Select the appropriate footprint
      • For new target server, provide the mandatory parameters along with new target host information.
        Following are the mandatory parameters:
        • Target platform: Select the platform on which Communication Manager is hosted
        • Data store: Select the existing host's data store
        • New Target platform: Select the target platform on which Communication Manager should be hosted
        • Data store: Select the target host's data store
        • Upgrade Source: Select the upgrade source
        • Upgrade/update to: Select the target Communication Manager release (OVA/ISO)
        • Flexi Footprint: Select the appropriate footprint
      For information about parameters, see Preupgrade Configuration field descriptions.
    2. In the Job Schedule section, click Schedule.
      ADDITIONAL INFORMATION:
      You can schedule the job now or for a later time.
  11. On the Pre-upgrade Check Job Details page, ensure that the Pre-upgrade Check Status field displays .
  12. Click Upgrade ActionsUpgrade/Update.
  13. 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.
  14. To provide the upgrade configuration details, click Edit.
  15. On the Edit Upgrade Configuration page, perform the following:
    1. Do one of the following:
      ADDITIONAL INFORMATION:
      • 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.
      ADDITIONAL INFORMATION:
      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.
  16. On the Upgrade Configuration page, ensure that the Configuration Status field displays .
    ADDITIONAL INFORMATION:
    If the field displays , review the information on the Edit Upgrade Configuration page.
  17. Click Save.
  18. To save the configuration, click Save Configuration.
    ADDITIONAL INFORMATION:
    The update configuration is saved as a job in the Upgrade Jobs Status page.
  19. On the Upgrade Configuration page, click Upgrade.
  20. On the Job Schedule page, click one of the following:
    • Run Immediately: To perform the job.
    • Schedule later: To perform the job at a scheduled time.
  21. Click Schedule.
  22. Click Upgrade.
  23. Important:
    If you are upgrading from non-encrypted system to encrypted system, then do not select the Require Encryption Pass-Phrase at Boot-Time check box. Otherwise, your upgrade fails.
  24. On the Upgrade Management page, click .
    STEP RESULT:
    • After successful upgrade, the Last Action column displays Upgrade, and Last Action Status column displays .
    • The Last Action field displays with COMMIT_ROLLBACK_PENDING if Auto Commit is not selected. Auto-commit is supported for the same server migration only.
  25. To Commit or Rollback, do the following:
    1. On the Upgrade Management page, select the element.
    2. Click Upgrade ActionsCommit/Rollback Upgrade.
      STEP RESULT:
      The system displays the Job Schedule page.
    3. Select the action to be performed under the Upgrade Action column.
    4. Click Run Immediately to perform the job or click Schedule later to perform the job at a scheduled time.
    5. Click Schedule.
    ADDITIONAL INFORMATION:
    When you commit the changes, the system deletes the old virtual machine.
    When you rollback, the system deletes the newly created virtual machine and starts the old virtual machine automatically. If the old virtual machine does not start automatically, then manually start the old virtual machine.
  26. To view the upgrade status, perform the following:
    1. In the navigation pane, click Upgrade Job Status.
    2. In the Job Type field, click Upgrade.
    3. Click the upgrade job that you want to view.
  27. Verify that the upgrade of the application is successful.
    ADDITIONAL INFORMATION:
    At this step, the upgrade is complete from:
    • Release 7.x or 8.x to Release 10.1