Upgrading to System Manager Release 10.2.x on Software-only through CLI

Last Updated : Jun 10, 2026 |

About this task

Use the procedure to:

  • Release 10.1.x on Avaya-provided server, VMware/ KVM in customer-provided Virtualized Environment, AWS/ Google Cloud / Microsoft Azure on IaaS, or Software-only environment.

  • Upgrade System Manager from Release 8.0.x or 8.1.x on VMware/ KVM OVA in customer-provided Virtualized Environment, AWS OVA to the System Manager Release 10.2.x on Software-only IaaS offer.

  • Upgrade the System Manager Release 7.1.3.x AWS instance to the System Manager Release 10.2.x on Software-only offer.

Note:

Use this procedure to upgrade Avaya Aura® application Release 8.1.x on Nutanix to Avaya Aura® application Release 10.2.x in the Software-only environment.

Procedure

  1. Log on to the old System Manager web console.
  2. Record the software version of old System Manager from the About link.

    For information, see Verifying the current software version.

  3. Create a System Manager remote backup by using System Manager web console.
    Note:

    Use the backup for restoring the data while using the data migration utility and also in case if the upgrade fails.

  4. Shut down the old System Manager.
  5. Deploy the System Manager Release 10.2 application.

    For information, see Deploying Avaya Aura® System Manager in Software-Only and Infrastructure as a Service Environments.

  6. Log in to the System Manager command-line interface of the new system.
  7. Copy the following files to the /swlibrary location on System Manager.

    • Data Migration Utility

    • Latest patch

    • System Manager backup file that you created in Step 3.

  8. Do the following:
    1. Create a snapshot of the System Manager system.
    2. Ensure that the System Manager web console is accessible.
    3. Check the server time before you run the data migration utility to upgrade System Manager.
    4. To run the data migration utility, type the following command: 
      upgradeSMGR /swlibrary/<DMUtility_bin file name>.bin -m -v

      You must provide the absolute path of the data migration utility.

    5. In Enter the location of backup file (full path), type the absolute path of the backup file. 
      /swlibrary/<backupfile name.*>

      The system validates the backup file and displays the parameters.

      Note:

      If you provide the System Manager Release 6.x backup file, the system displays a message. For example:

      System Manager 10.1 does not support direct migration from version <6.x>.

    6. In Enter the patch file, type the absolute path of the patch file: 
      /swlibrary/<patch file name>.bin

      For example, /swlibrary/System_Manager_R10.2.0.0.xxxxxxxxx.bin.

      The system validates the patch file and displays the following message:

      You are about to run the System Manager Data Migration utility. The System Manager will be inaccessible for approximately 60 minutes, depending on the resources available on the system.

    7. To continue, type Y.

      The system displays the following message:

      WARNING:- The system is now going down for a halt and will be inaccessible for some time.
Remote broadcast message (<Day Month DD HH:MM:SS Year>):
INFO:- System Manager Data Migration would now be executed in background process. For details, see System Manager Data Migration logs in the /var/log/Avaya/datamigration/data_migration.log.
  9. Log on to System Manager CLI to monitor the upgrade.

    The upgrade takes about 80 to 90 minutes. However, the duration depends on the factors such as the number of users, backup size, hardware used, and the number of resources shared during the upgrade.

    As part of running the data migration utility, the system performs the patch installation in the background that takes about 60–90 minutes.

    You can monitor the progress of System Manager:

    • Data Migration Utility from the /var/log/Avaya/datamigration/data_migration.log file.

    • Patch from the /var/log/Avaya/SMGR_Patch.log file.

    After the upgrade is successful, the system displays the messages:

    • For Data Migration Utility: <Day Month Date HH:MM:SS IST Year #### Data Migration Utility Completed Successfully. ####

    • For Patch: <Day Month Date HH:MM:SS IST Year #### ########Patch execution completed Successfully.

  10. Verify the software version of the new System Manager.
  11. Perform one of the following:

    • If the upgrade and patch installation is successful, remove the patch bin file, backup file, data migration utility, log off from the system, and remove the snapshot.

      Note:

      Snapshots occupy the system memory and degrade the performance of the virtual application. Therefore, delete the snapshot after you verify the patch installation or the system upgrade.

    • If the upgrade or patch installation fails, use the snapshot to restore the system to the original state.

      To collect logs, you can run the collectLogs command. System Manager creates a LogsBackup_xx_xx_xx_xxxxxx.tar.gz file at /swlibrary directory. Copy the LogsBackup_xx_xx_xx_xxxxxx.tar.gz file to remote server and share the file with Avaya Support Team.

Next Steps

  • Regenerate new licenses for all components from PLDS by using the associated LACs.

  • Install all the regenerated license file on System Manager Release 10.2.x.