Upgrading Unified Assurance on an Existing Linux System

You can upgrade Oracle Communications Unified Assurance on an existing Linux system by first upgrading your existing Linux 7 environment to Linux 8 and then updating to the latest version of Unified Assurance. This is also known as an in-place upgrade.

An in-place upgrade involves the following high-level steps:

  1. Preparing for the Linux and Unified Assurance upgrade by backing up key files and removing the old RPM.

  2. Upgrading your Linux 7 environment to Linux 8 using the Leapp utility. For information about using the Leapp utility, see Oracle Linux 8 Upgrading Systems With Leapp.

  3. Updating Unified Assurance packages on all servers.

In-Place Upgrade Process Placeholders

The in-place upgrade procedure uses the following placeholders, marked with angled brackets in the commands (<>):

In-Place Upgrade Prerequisites

For complete information about general system requirements for Unified Assurance, including system and hardware requirements, see Unified Assurance Architecture.

Additionally, on servers with the Database.Historical role, confirm that you will have enough memory available for the Elasticsearch and OpenSearch databases to be deployed simultaneously. You need both to support the migration process.

Until you finalize the migration process, both types of database will be running. OpenSearch requires approximately the same amount of memory as Elasticsearch, so the migration process requires at least twice the memory of your current Elasticsearch implementation. You can add more memory, or scale back your Elasticsearch heap size as needed. After finalizing the migration and removing Elasticsearch, you can scale up your OpenSearch heap size to use the full amount.

The heap size for Elasticsearch is set in the ES_JAVA_OPTS parameter in the $A1BASEDIR/vendor/elasticsearch/config/custom-env file.

When you run Package update, the application checks whether you have enough memory available for both databases. If so, it proceeds with the update. If not, it stops the update and prompts you to adjust your memory settings.

Performing an In-Place Upgrade

Perform all commands in this procedure as the root user.

To perform an in-place upgrade:

  1. For each Unified Assurance server, back up the Assure1.conf file, located in the UA_home/etc directory, to a safe location.

  2. For each Unified Assurance server, remove the Unified Assurance RPM using the noscripts flag with the following command:

    sudo yum --setopt=tsflags=noscripts erase Assure1

  3. Upgrade your Linux 7 environment to Linux 8 using the Leapp utility as described in Oracle Linux 8 Upgrading Systems With Leapp.

  4. Confirm that Linux prerequisites are met for all servers. See Linux Prerequisites.

  5. On the primary presentation server:

    1. If you are upgrading from version 5 to version 6.1, skip to the next step.

      If you are upgrading from version 6.0.x to version 6.1, reset the Unified Assurance packages to their base versions.

      a1mysql
UPDATE Packages SET PackageVersion = '6.0.0.0.0.0';

    2. Download the latest Unified Assurance release package from Oracle Software Delivery Cloud:

      https://edelivery.oracle.com

      The package contains the Oracle-Communications-Unified-Assurance-6.X.X.X.X-el8.zip collection file for installation.

    3. Extract the collection file to the location on the Unified Assurance primary presentation server where the packages were placed during the initial Unified Assurance installation. This is typically /opt/install/.

      unzip -d <installation_file_directory> Oracle-Communications-Unified-Assurance-6.X.X.X.X-el8.zip

  6. Copy the Assure1-6.X.X.X.X-X.el8.x86_64.rpm file to each of your Unified Assurance servers.

  7. On each of your Unified Assurance servers, starting with the primary presentation server:

    1. Install the latest Unified Assurance RPM for Linux 8:

      sudo dnf -y install Assure1-6.X.X.X.X-X.el8.x86_64.rpm

    2. Restore the backup of the Assure1.conf file and place it in the UA_home/etc/ directory.

    3. Start the Unified Assurance Broker:

      sudo systemctl start assure1-broker

    4. Remove the Linux 7 Unified Assurance packages by removing the contents of the UA_home/distrib/packages directory:

      rm -f <UA_home>/distrib/packages/*

  8. Set environment variables by doing one of the following:

    • Export the LD_LIBRARY_PATH:

      export LD_LIBRARY_PATH=<UA_home>/lib:<UA_home>/lib/private

    • Source the .bashrc file:

      source <UA_home>/.bashrc

  9. On the collection server, if you have the Flow Collector microservice deployed, you must stop all data coming from all deployed Flow Collector instances to the Historical database. Scale down the microservice by running the following command for all instances of Flow Collector, as the assure1 user:

    a1k scale --replicas=0 deploy <flow-collector-release-name> -n <namespace>

    where:

    • <flow-collector-release-name> is the name of the microservice instance. This is typically flow-collector, but may be slightly different if you have multiple instances of the microservice deployed to the same cluster.

    • <namespace> is the namespace where the microservice is deployed. This is typically a1-zone1-pri, but may be slightly different if you deployed the microservice to a different zoned namespace or a redundant cluster.

    See Managing Microservices and Flow Collector in Unified Assurance Implementation Guide for information about microservices.

  10. Run Package update for each of your Unified Assurance servers:

    • On the primary presentation server:

      1. Run Package update:

        $A1BASEDIR/bin/Package update --depot <installation_file_directory>

        Updated packages are copied from the directory you extracted them to into the internal package location on the primary presentation server, then packages that have updates on the primary presentation server are installed.

      2. If you are upgrading from version 5 to version 6, run flush-hosts:

        $A1BASEDIR/vendor/mysql/bin/mysqladmin flush-hosts

    • On the secondary presentation server, if you are upgrading from version 5 to version 6, restart the assure1 database, and then run Package update:

      systemctl start assure1-db
$A1BASEDIR/bin/Package update

    • On all other servers:

      $A1BASEDIR/bin/Package update

      Packages that have updates are downloaded from the primary presentation server and installed on the other server.

  11. If you are upgrading from version 5 to version 6:

    1. Run RedundancyWizard on each redundant presentation server pair and database server pair to resynchronize them. See:

    2. Enable DatabaseWatchdog on all servers. You can do this by using the Services UI.

    3. Remove all version 5 related directories. On each server, run:

      $A1BASEDIR/bin/SetupWizard --Finalize-Upgrade

    4. Removing all Neo4j version 4 related directories. On each Graph database server, run:

      $A1BASEDIR/bin/Package finalize-neo4j-upgrade

  12. Complete the Post Update Tasks, including migrating your Historical database.

The in-place upgrade is complete.