Upgrading Unified Assurance

Learn about how to upgrade Oracle Communications Unified Assurance to version 7.

About Upgrades

Upgrading means moving between major version numbers (for example, version 6.1.1 to version 7).

Updating means moving between minor versions (for example, version 6.1.0 to version 6.1.1) or moving to the latest patch. For more information about updating, see Updating Unified Assurance.

Because upgrades often require schema updates and microservice cluster teardowns, they involve some downtime. Perform the upgrade during a scheduled maintenance window.

Supported Upgrade Paths

You can upgrade to version 7 from version 6.1.1.5.0 and later. Because this does not require an operating system upgrade, you upgrade in-place on the same server.

If you are using an earlier version of Unified Assurance, you must first upgrade or update to at least 6.1.1.5.0 before moving to version 7.

Upgrading

To upgrade to Unified Assurance version 7:

  1. If you are on an earlier version of Unified Assurance than 6.1.1.5.0, upgrade or update to this or any later patch.

  2. Optionally, back up your system, including the Assure1.conf file, located in the UA_home/etc directory.

  3. Review your microservice cluster configuration, including any deployed microservices and their configurations. Make note of any custom details so that you can recreate the cluster.

    Caution:

    The upgrade process deletes any existing microservice clusters.

  4. Download the latest Unified Assurance software, including the release package and the latest available patch, and extract the contents of the collection files to an installation directory. This is typically /opt/install, and is referred to as <installation_directory> in the documentation. You will use this as the depot for upgrading the primary presentation server.

    See Downloading the Latest Unified Assurance Software for more information about where to get the software and how to extract the collection file.

  5. Upgrade each Unified Assurance server by running the following commands on each server in sequence, starting with the primary presentation server:

    1. Initialize the upgrade:

      $A1BASEDIR/bin/SetupWizard --Upgrade --Depot <depot>

      where <depot> is the location where you stored the release RPM, either the local directory or your remote depot. See SetupWizard in Unified Assurance Implementation Guide for more information about the SetupWizard options.

      The --Depot option is only required for the primary presentation server. Each additional server sources the RPM from the primary presentation server.

      Note:

      If there are any failures during the upgrade, you may see an error stating that SetupWizard has already been successfully run on this server. In this case, run the following to perform the upgrade:

      $A1BASEDIR/bin/Package upgrade

    2. Finalize the upgrade:

      $A1BASEDIR/bin/SetupWizard --Finalize-Upgrade

      This performs additional cleanup of unused files and packages.

  6. After finalizing the upgrade on all servers, recreate your microservice cluster and redeploy relevant microservices. See Microservice Cluster Setup and Managing Microservice in Unified Assurance Implementation Guide.

  7. If you have purchased licenses for any Network Performance Management report packs, set up Network Performance Management. See About Network Performance Management in Unified Assurance Network Performance Management Reporting Guide for more information.