v5 to v6 Upgrade Guide

Overview

Upgrading Assure1 v5 to Unified Assurance v6 allows an existing installation to gain the benefits of the latest functionality and enhancements available. Upgrades should be taken seriously and planned ahead of time. If you have access to a development instance, upgrades should be performed on there before planning your production upgrade.

The major changes provided from upgrading to Unified Assurance are:

Note:

Data will be migrated from the old database to the new database via database dump during the upgrade. Depending on the sizes, it may take some time. Plan for reporting if needed.

Note:

The upgrade process updates every single package installed on each server. While this is ongoing the functionality will be disrupted. Redundancy Wizard must be re-run for redundant pairs after the upgrade is complete.

The upgrade happens in place.

Prerequisites

  1. Your Assure1 v5 installation must be updated to at least Update 5.5.9.

  2. All data needs to be migrated from OrientDB to Neo4j prior to upgrade; Neo4j needs to be the active graph database and not OrientDB.

  3. The Database Watchdog should be disabled and stopped on all servers. If not the UI will become inaccessible during the upgrade.

  4. If upgrading a redundant presentation server pair, ensure the assure1 database on the redundant server is stopped while the primary server gets upgraded and running when the redundant server gets upgraded. Run the following as root to stop start the assure1 database:

    systemctl stop / start assure1-db

  5. If your Assure1 v5 installation contains any custom (non Assure1 default) MySQL tables / databases etc; ensure that they are compatible with MySQL EE prior to starting the upgrade; otherwise the upgrade may fail.

WARNING:

If you do not follow the pre-requisites, your upgrade may fail completely in some cases!

Preparation

  1. If you have a development environment, it is suggested you upgrade this environment first to get a feel for the process.

  2. Backup all systems prior to upgrade. See following guide: Backup and Restore

  3. Create a backup plan that includes this document, the prior upgrade experience notes, and rollback steps from backups if needed.

  4. Plan a maintenance window for the upgrade.

Dependencies

  1. See the above Prerequisites section before starting an upgrade.

  2. The Oracle-Communications-Unified-Assurance-6.W.X.Y.Z.zip collection file should be downloaded from the Oracle Communications Support Site before beginning this process, and placed in the /opt/install/ directory on the primary presentation server (or wherever the collection file was placed during the initial installation).

  3. When running commands as root, one of the following must be done after installing the RPM.

    • Export the LD_LIBRARY_PATH:

      export LD_LIBRARY_PATH=$A1BASEDIR/lib

    • or source the .bashrc file:

      source $A1BASEDIR/.bashrc

Upgrade Steps

Starting with your primary presentation server, upgrade to Unified Assurance v6

  1. On the primary presentation server, extract the contents of the collection to the /opt/install/ directory (or wherever the packages were placed during the initial installation):

    unzip -d /opt/install/ Oracle-Communications-Unified-Assurance-6.W.X.Y.Z.zip

  2. Upload the RPM file to the "/opt/install/" directory on all other servers that will be part of the environment.

  3. Use one of the following examples to update the RPM on all servers:

    • If Assure1 was installed into the /opt/assure1/ directory:

      yum update --nogpgcheck Assure1-6.V.W.X.Y-ZZZ.x86_64.rpm

    • If Assure1 was installed to a different directory, then the "rpm" update command with the "prefix" flag needs to be used to update it. An example is shown below which assumes "/opt/a1/" is install directory:

      WARNING:

      Using the "rpm" command will not automatically install the required dependencies, and some dependency errors may come up if using this method. Install the missing dependencies, then update again using the "rpm" command.

      rpm -Uvh --prefix /opt/a1 /opt/install/Assure1-6.V.W.X.Y-ZZZ.x86_64.rpm

  4. Do one of the following before running Package update, RedundancyWizard or SetupWizard.

    • Export the LD_LIBRARY_PATH:

      export LD_LIBRARY_PATH=$A1BASEDIR/lib

    • or source the .bashrc file:

      source $A1BASEDIR/.bashrc

  5. Run Package Update, starting with the primary presentation server:

    $A1BASEDIR/bin/Package update --Depot /opt/install/:a1-local

    Updated packages will be copied from the directory they were extracted and copied into the internal package location on the primary presentation server. After the package file copy process is complete, packages that have updates on the primary presentation server will be installed. Wait for this process to finish. The "Installing" progress bar will show 100%.

  6. It is advised to run flush-hosts on the primary presentation server prior to updating each server:

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

  7. After the primary presentation server has been updated, other servers in the installation can be updated by running package Update on them:

    $A1BASEDIR/bin/Package update

    WARNING:

    If updating the redundant partner for the presentation server remember to first start the assure1-db again.

  8. Packages that have updates available will be downloaded from the primary presentation server to the other servers. After the download process is complete, packages that have updates on the server will be installed.

  9. Wait for this process to finish. The "Installing" progress bar will show 100% when the package update process is complete.

  10. Once all servers are successfully updated to Unified Assurance v6 rerun Redundancy Wizard on all redundant presentation and Event/Metric/Graph database server pairs.

    $A1BASEDIR/bin/redundancy/RedundancyWizard

  11. Verify system is working as expected.

  12. Finalize upgrade by removing all v5 related directories. On each system, run:

    $A1BASEDIR/bin/SetupWizard --Finalize-Upgrade

    WARNING:

    If you do not run Finalize-Upgrade Package upgrades may fail.

Potential issues

  1. If Database Watchdog was not disabled and stopped prior to the upgrade, the upgrade process will not fail; however, the UI will be unreachable. Instead of using the Server UI to run the updates the command needs to be run manually using the Unified Assurance Package Manager. To be able to access to UI again after the upgrade. To resolve this:

    • Delete the following file on the presentation server:

      $A1BASEDIR/var/DBAvailability.json

    • When access to the UI is restored navigate to the Service UI and restart the Database Watchdog on all servers it is running on.

  2. If the redundant database is not stopped when upgrading the presentation server, the package Update process will fail. in this case stop the database on the redundant partner and then rerun package update.