Upgrading Session Manager from Release 7.x, 8.x, or 10.1.x to Release 10.2.x using data migration utility

Last Updated : Oct 18, 2023 |
Prolog information
Use this procedure to upgrade Session Manager using data migration utility.
You must perform this procedure to get data migration tool certificates to avoid the loss of alarming and configuration data.
  1. Log in to the Session Manager with the customer account.
  2. Go to the customer’s home directory. For example, cd /home/cust.
  3. Download the latest version of the data migration utility to the local directory.
  4. Run the dmutility-10.2.x.0.xxxxx.bin utility.
    ADDITIONAL INFORMATION: $ bash dmutility-10.2.x.0.xxxxx.bin

    Verifying signature...                                     [  OK  ]
    Checking integrity of install.sh                           [  OK  ]
    Checking integrity of sm_backup.sh                         [  OK  ]
    Checking integrity of cs_functions.sh                      [  OK  ]
    Mounted ISO image /tmp/tmp.GUqkp31591 to /iso
    Removing any previous backup files
    Backing up data
    Moving backup file to the current directory
    Data backup is complete.
    Copy /home/cust/Session_Manager_backup.tgz to a remote server before shutting
    down Session Manager.
  5. Copy the backup file to a remote server.
    ADDITIONAL INFORMATION:
    In most case, the backup file is placed in the current directory. The dmutility displays the exact location of the backup file in the output.
  6. Run the smconfig command and note the values of IP addresses, hostname, and other parameters.
    ADDITIONAL INFORMATION:
    These values are required to deploy the Session Manager Release 10.2.x OVA file.
  7. On the Session Manager Dashboard page, change Service State of the Session Manager server to Deny New Service.
  8. Run the shutdownSM command to shutdown Session Manager.
    ADDITIONAL INFORMATION: $ shutdownSM

    Note: It is strongly suggested that the Session Manager
    be in  Deny New Service state and that one waits for all
    active calls to end before shutting down the server.
    Active calls through this Session Manager will drop if
    it remains down too long.  New calls will immediately use
    an alternate Session Manager (if available) once
    this Session Manager is placed in the Deny New Service state.

    Do you really want to continue? (y or n)
  9. Deploy the Release 10.2.x Session Manager or Branch Session Manager OVA.
    ADDITIONAL INFORMATION:
    For information, see Deploying Avaya Aura® Session Manager and Avaya Aura® Branch Session Manager in Virtualized Environment on the Avaya Support website.
  10. On the newly deployed Session Manager, copy the backup file to the customer's home directory.
  11. Log in to the Session Manager with customer account.
  12. Run the upgradeSM command with the backup file as an argument to run the restore utility.
    ADDITIONAL INFORMATION: $ upgradeSM Session_Manager_backup.tgz
    Performing data migration
    VSP_PROGRESS[[Starting restore]]VSP_PROGRESS
    VSP_PROGRESS[[Stopping Session Manager]]VSP_PROGRESS
    ...
    Trust Management Initialization started.
    Trust Management Initialization with System Manager started.
    Trust Management Initialization completed.
    Upgrading saved certificates
    Saving upgrade files to /opt/Avaya/prev-upgrade
    Downloading System Manager root CA
    Waiting for WebSphere components to startup...
    Waiting for WebSphere components to startup...
    ...
    Waiting for Management components to startup...
    Waiting for Management components to startup...
    Thu Apr  9 16:06:37 MDT 2015: DRS Replication registration succeeded
    Please go to the System Manager Replication Page to check the synchronization state
  13. Run the patchSM <name of the *.bin file> command to apply the Release 10.2.x patch.
    ADDITIONAL INFORMATION:
    Go to the Session Manager Dashboard page and verify that both the Data Replication and the User Data Storage Status columns display green check marks.
  14. On the Session Manager Dashboard page, change Service State of the Session Manager server to Accept New Service.
  15. For VMware in customer provided Virtualized Environment, delete the old Session Manager virtual machine.