Upgrading Session Manager from Release 7.x, 8.x, or 10.1.x to Release 10.2.x on Software-only and IaaS

Last Updated : Dec 04, 2023 |
Prolog information
Metadata
Keywords:
Use this procedure to upgrade Session Manager on Software-only and IaaS environments.
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.
You must perform this procedure to get data migration tool certificates to avoid the loss of alarming and configuration data.
Before you begin
Back up the call history using User Data Storage. For more information, see Administering Avaya Aura® Session Manager.
Session Manager stores call logs only when the Centralized Call History is enabled.
  1. Log on to the on-premises 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.0.0.xxxxx.bin utility.
    ADDITIONAL INFORMATION: $ bash dmutility-10.2.0.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:
    Usually, the backup file is /home/cust/Session_Manager_backup.tgz. The dmutility displays the exact location of the backup file as an output.
  6. 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)
  7. Deploy the Session Manager Release 10.2.x compatible application on your Software-only or IaaS environment.
    ADDITIONAL INFORMATION:
    For deploying the Session Manager application on Software-only or IaaS environment, see Deploying Avaya Aura® Session Manager in Software-Only and Infrastructure as a Service Environment.
  8. Update the IP address of Session Manager (Asset/ SIP IP and Management IP) on the Routing and Inventory page of System Manager. For more information, see Administering Avaya Aura® Session Manager.
  9. On the newly deployed Session Manager, copy the backup file to the customer's home directory.
  10. Log on to the Session Manager with the customer account and run the upgradeSM command 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
    Important:
    If the backup host name is different than the target host name, the restore operation fails because the certificates are associated with the host name. To avoid this issue, ensure that the backup host name is the same as the restore host name.
  11. On the System Manager web console, click ElementsSession Manager Dashboard.
  12. On the Session Manager Dashboard page, change Service State of the Session Manager server to Deny New Service.
  13. Run the patchSM <name of the *.bin file> command to apply the Release 10.2.x patch (if applicable).
    ADDITIONAL INFORMATION:
    Go to the Session Manager Dashboard page and verify that both the Data Replication and User Data Storage Status columns display green check marks.
  14. On the Session Manager Dashboard page, change the Service State of the Session Manager server to Accept New Service.