Upgrading EMS or SBC using the CLI

Last Updated : Dec 05, 2024 |
Prolog information
Metadata
Keywords:
Any EMS or SBC can be upgraded using this procedure.
Avaya SBCs can be deployed as single or multiple systems. When deployed as multiple systems, you must upgrade use the following order:
  1. Upgrade the primary EMS.
  2. Upgrade the SBC systems in any order. For an HA pair, upgrade the secondary SBC first followed by the primary SBC to avoid failover conditions that might interfere with the upgrade.
  3. Upgrade the secondary EMS.
Note:
You can upgrade EMSs and SBCs simultaneously, when upgrading from Release 10.2.x to Release 10.2.1. However, you cannot rollback EMSs and SBCs simultaneously, when rolling back from Release 10.2.1 to Release 10.2.x.
  1. Log in to the CLI with administrator credentials.
  2. Using root permissions, move the upgrade tar file from the ipcs user home directory to /archive/urpackages directory.
  3. Ensure that the md5sum of the upgrade tar file matches the checksum given in the name of the file.
    ADDITIONAL INFORMATION:
    You can use the md5sum command to verify whether the md5sum and the checksum match.
  4. Run the following command to create a temporary directory:
    ADDITIONAL INFORMATION:
    mkdir /usr/local/ipcs/temp
    Where, temp is the name of the temporary directory.
    ADDITIONAL INFORMATION:
    If the temporary directory already exists in the system, use the following commands to change to the location of the directory, list the contents of the directory to make sure you want to remove all of the files, and delete the files in the temporary directory:
    cd /usr/local/ipcs/temp/
    ls
    rm -rf -i *
  5. Run the following command to access the temporary directory:
    ADDITIONAL INFORMATION:
    cd /usr/local/ipcs/temp
  6. Run the following command to extract the upgrade tar file in the temp directory:
    ADDITIONAL INFORMATION:
    tar -xvf /archive/urpackages/sbce-10.2.1.0-101-24795-5fc87450273ac40bc1d2eee3ba1c51c6.tar.gz
  7. Run the following command to make the script executable:
    ADDITIONAL INFORMATION:
    chmod +x ursbce.py
  8. Run the following command to start the upgrade:
    ADDITIONAL INFORMATION:
    ./ursbce.py -U --daemonize
    ADDITIONAL INFORMATION:
    Caution:
    Use the --daemonize option while using CLI-based upgrades over SSH. Without the --daemonize option, the upgrade fails if your connection drops because of inactivity.
  9. Wait for the system to reboot.
  10. Run the following command to verify the version of the system:
    ADDITIONAL INFORMATION:
    cat /etc/sbce-version
    The file /archive/log/icu/ursbce.log contains upgrade related logs.
Next steps
To verify whether the upgrade was successful, log in to the EMS server and on the Device Management page, verify the current SBC and EMS versions.
Note:
If the EMS server becomes non-functional before starting the upgrade or during the upgrade, then after the successful upgrade of EMS, use the sbceconfigurator.py update-connection-info command to update the version information of SBC in the EMS server.