Upgrading System Manager from Release 7.1.3.x, 8.0.x, 8.1.x, or 10.1.x to Release 10.2.x through CLI

Last Updated : Jun 10, 2026 |

About this task

Use the procedure to upgrade System Manager from Release 7.1.3.x, 8.0.x, 8.1.x, or 10.1.x to Release 10.2.x running on VMware by using command-line interface.

Note:

For upgrading System Manager from Release 7.0.x to Release 10.2 and later, first upgrade System Manager Release 7.0.x to 10.1.x, and then upgrade to Release 10.2 and later. You cannot directly upgrade the Release 7.0.x system to Release 10.2 and later. If you upgrade the application directly from Release 7.0.x to Release 10.2 and later, the upgrade might fail.
For upgrading System Manager from Release 6.x to Release 10.1 and later, first upgrade System Manager Release 6.x to 8.1.x, and then upgrade to Release 10.1 and later. You cannot directly upgrade the Release 6.x system to Release 10.1 and later. If you upgrade the application directly from Release 6.3.x to Release 10.1 and later, the upgrade fails.

When you upgrade System Manager to Release 10.1.x and later by using the data migration utility from CLI, you need to provide the patch file along with backup to the data migration utility. Therefore, do not perform the patch installation separately.

Before you begin

Warning:

If you use the CLI procedure to upgrade System Manager to Release 10.2.x, the system does not retain the System Manager WebLM licenses that are installed on the old System Manager server. This will impact each product that is using the licenses from System Manager WebLM. During or after the upgrade, those prodFor more information about parauct might go in the license grace period mode or license error mode. To remediate this, after the upgrade, regenerate the licenses by using the new host ID. Ensure that all your Avaya License Activation Codes (LACs) for your system are available that is under contract with ‘Upgrade Advantage’ entitlement. Also, check that your account at Avaya PLDS website https://plds.avaya.com/ is functional to regenerate the license keys.

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.

Download the System Manager OVA, data migration utility, and patch files from the Avaya Support website at http://support.avaya.com.

Procedure

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

For information, see Verifying the current software version.
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.
Export the System Manager license keys and ensure you have a LAC available to regenerate this key once the new System Manager 10.2 instance is deployed.

Note:
If you fail to do this step, then you will lose all the System Manager licenses including the other installed product licenses.
Shut down the old System Manager.
Deploy the System Manager OVA on the supported ESXi version.

For information about the supported ESXi version, see Supported ESXi version.

For information about deploying System Manager on VMware, see Deploying the System Manager OVA on vCenter by using vSphere Client (HTML5) and Deploying the System Manager OVA by accessing the ESXi host directly.

Important:
It is recommended to use the same network parameters and system parameters that you recorded on the existing system. If you are not using any third-party certificates, then you can also use the different network parameters to configure the new system

For information about parameters, see Customer configuration data for System Manager.
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.
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.
```
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.
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.

Send Feedback

AVAYA DOCUMENTATION CENTER

No results found