Installing Unified Assurance on Multiple Servers

In production environments, you install Oracle Communications Unified Assurance components across multiple servers. Typically, this involves one presentation server, one database server, one Historical database server, and one or more collection servers. However, because a single server can have one or more roles associated to it, you could set up different configurations of combined and separate servers. For example, you could have a single combined presentation and database server and multiple collection servers, or a single combined presentation and collection server with a separate database server, or other combinations.

See Understanding Server Roles in Unified Assurance Concepts for information about server roles.

Multiple Server Installation Prerequisites and Directories

Before starting an installation, ensure that you have completed all tasks described Linux Prerequisites.

By default, Unified Assurance uses the following directories, though you can choose to use different ones:

Preparing to Install Unified Assurance on Multiple Servers

To prepare the servers for the Unified Assurance installation:

  1. On the presentation server that will be part of the environment, 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.

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

  2. On all other servers in the environment:

    1. If there is not an /install subdirectory under the home directory, create it. The default directory structure is:

      /opt/install

    2. Copy the extracted RPM file from the presentation server to <installation_directory> on all other servers.

      The version of the RPM must be the same on all servers in the environment. If you are installing a patch, use the patch RPM rather than the release RPM.

  3. On all servers in the environment, including the presentation server:

    1. Install the RPM by running one of the following commands:

      • To install Unified Assurance into the default /opt/assure1/ home directory:

        dnf install <installation_directory>/Assure1-6.V.W.X.Y-ZZZ.el8.x86_64.rpm

        where 6.V.W.X.Y-ZZZ is the version number you are installing. For example, 6.1.0.2.0-584.

        If you are installing a patch, use the patch RPM rather than the release RPM.

      • To install Unified Assurance into a custom home directory:

        Caution:

        The following rpm command does not automatically install the required dependencies, and some dependency errors may occur. To resolve them, install the missing dependencies, then rerun the command.

        rpm -ivh --prefix <custom_home_directory> <installation_directory>/Assure1-6.V.W.X.Y-ZZZ.el8.x86_64.rpm

    2. Run the following command as root:

      source <UA_home>/.bashrc

      Note:

      By default, <UA_home> is /opt/assure1/. If you used a custom home directory, this will be different.

    3. If SELinux is enabled, confirm that the assure1 directory has the correct permissions, ownerships, and security context:

      1. From the Unified Assurance home directory's parent directory (typically the opt directory), run the following command:

        ls -l

      2. In the response, confirm that the permissions and ownership for the Unified Assurance home directory (typically assure1) match the following:

        drwx------. 11 assure1 assure1 4096 <date_time> <UA_home>

      3. Change to the Unified Assurance home directory (typically assure1) and run the following command:

        ls -lZ

      4. In the response, confirm that the permissions, ownership, and security contexts match the following:

        drwxr-xr-x.  3 assure1 assure1 system_u:object_r:bin_t:s0 4096 <date_time> bin
drwxr-xr-x. 12 assure1 assure1 system_u:object_r:etc_t:s0  149 <date_time> distrib
drwxr-xr-x.  3 assure1 assure1 system_u:object_r:etc_t:s0   57 <date_time> etc
drwxr-xr-x.  2 assure1 assure1 system_u:object_r:etc_t:s0  102 <date_time> legal
drwxr-xr-x.  3 assure1 assure1 system_u:object_r:lib_t:s0  106 <date_time> lib
drwxr-xr-x.  3 assure1 assure1 system_u:object_r:etc_t:s0   67 <date_time> logs
drwxr-xr-x.  2 assure1 assure1 system_u:object_r:etc_t:s0   33 <date_time> tmp
drwxr-xr-x.  3 assure1 assure1 system_u:object_r:etc_t:s0   17 <date_time> var
drwxr-xr-x.  3 assure1 assure1 system_u:object_r:etc_t:s0   18 <date_time> vendor

      If any permissions, ownership, and security contexts do not match, consult with your local system administrator.

Server preparation is complete. Proceed to Installing Unified Assurance on the Presentation Server.

Installing Unified Assurance on the Presentation Server

Before beginning these steps, you must prepare the server as described in Preparing to Install Unified Assurance on Multiple Servers.

To install Unified Assurance on the presentation server:

  1. Go to the following directory:

    cd $A1BASEDIR/bin/

  2. Start SetupWizard by running the following command as root:

    ./SetupWizard --Depot <installation_directory>/:a1-local

  3. When prompted Is this your Primary Presentation Server?, enter y then press Enter.

  4. When prompted What is this install's Web FQDN? [FQDN]:, make a change if needed then press Enter.

  5. When prompted Comma-delimited list of roles to install (numeric):, enter the numerical values for the following roles, and then press Enter:

    • Presentation

    • Processing

      Note:

      The Processing role is installed on the presentation server to split the overall load across the servers in the environment. It is not required to be on the presentation server specifically, but it does need to be installed on a server somewhere in the environment. If the applications run as part of this role become too much for the server, you may need to migrate the role to a dedicated system.

  6. When prompted Do you accept all the license agreements? Must type "AGREE":, enter AGREE then press Enter.

    Setup Wizard installs Unified Assurance.

  7. Check the following log files for installation errors:

    • $A1BASEDIR/logs/SetupWizard.log

    • $A1BASEDIR/logs/Package.log

  8. Change the default password:

    1. In a browser, enter the web FQDN of the server.

    2. Log in using admin as the username and password.

    3. From the Configuration menu, select AAA, then Users.

    4. Select the admin user account.

    5. In the Password and Repeat Password fields, enter a new secure password of your choice and click Submit.

      See Users in Unified Assurance User's Guide for information about the fields in this interface.

The presentation server installation is complete. Proceed to Installing Unified Assurance on the Database Server.

Installing Unified Assurance on the Database Server

Before beginning these steps, you must prepare the server as described in Preparing to Install Unified Assurance on Multiple Servers and install the presentation server as described in Installing Unified Assurance on the Presentation Server.

Note:

The installation process is different on Historical database servers. See Installing Unified Assurance and Analytics Components on Historical Database Servers.

To install Unified Assurance on the database server:

  1. Go to the following directory:

    cd $A1BASEDIR/bin/

  2. Start SetupWizard by running the following command as root:

    ./SetupWizard

  3. When prompted Is this your Primary Presentation Server?, enter n then press Enter.

  4. When prompted Enter the Host FQDN of your Primary Presentation Server:, enter the host FQDN of the presentation server then press Enter.

  5. When prompted Enter the Web FQDN of your Primary Presentation Server:, enter the web FQDN of the presentation server then press Enter.

  6. When prompted Set Web FQDN for this server?, enter n then press Enter.

  7. When prompted Is this a redundant server?, enter n then press Enter.

  8. When prompted Comma-delimited list of roles to install (numeric):, enter the numerical values for the following roles then press Enter:

    • Database.Event

    • Database.Graph

    • Database.Metric

    Note:

    Depending on the load for each database, you can install the different database roles on separate servers. For example, you could install the Event and Graph databases on the same server and the Metric database on a separate server. Larger organizations may need to keep all three separate.

  9. When prompted Do you accept all the license agreements? Must type "AGREE":, enter AGREE then press Enter.

    The files needed for the installation are downloaded from the presentation server and installed.

  10. Check the following log files for installation errors:

    • $A1BASEDIR/logs/SetupWizard.log

    • $A1BASEDIR/logs/Package.log

The database server installation process is complete. Proceed to Installing Unified Assurance on Historical Database Servers.

Installing Unified Assurance and Analytics Components on Historical Database Servers

Before beginning these steps, you must prepare the servers as described in Preparing to Install Unified Assurance on Multiple Servers and install the presentation servers as described in Installing Unified Assurance on the Presentation Server.

You can install the Historical database in the following configurations in a non-redundant multi-server Unified Assurance environment:

After completing the initial setup, you can add more nodes at any time by installing the Historical.Database role on new servers and running AnalyticsWizard to add them to the cluster.

You install Unified Assurance and analytics components on Historical database servers in two stages. First, you run SetupWizard on each server to install Unified Assurance. Then, you run AnalyticsWizard on each server, and AnalyticsWizard chooses where to install the analytics components based on the servers where SetupWizard has been run. This approach, rather than running both wizards on the same server before moving on to the next server, lets you decide which nodes to use for the MySQL Replication Data Importer component that synchronizes data from the Event database to the Historical database.

Installing Unified Assurance on Historical Database Servers

Repeat the following steps on all Historical database servers:

  1. Go to the following directory:

    cd $A1BASEDIR/bin/

  2. Start SetupWizard by running the following command as root:

    ./SetupWizard

  3. When prompted Is this your Primary Presentation Server?, enter n then press Enter.

  4. When prompted Enter the Host FQDN of your Primary Presentation Server:, enter the host FQDN of the presentation server then press Enter.

  5. When prompted Enter the Web FQDN of your Primary Presentation Server:, enter the web FQDN of the presentation server then press Enter.

  6. When prompted Set Web FQDN for this server?, enter n then press Enter.

  7. When prompted Is this a redundant server?, enter n then press Enter.

  8. When prompted Comma-delimited list of roles to install (numeric):, enter the numerical value for the Database.Historical role then press Enter.

  9. When prompted Do you accept all the license agreements? Must type "AGREE":, enter AGREE then press Enter.

    The files needed for the installation are downloaded from the presentation server and installed.

  10. Check the following log files for installation errors::

    • $A1BASEDIR/logs/SetupWizard.log

    • $A1BASEDIR/logs/Package.log

After running SetupWizard on all Historical database servers, proceed to Installing Analytics Components on Historical Database Servers.

Installing Analytics Components on Historical Database Servers

Repeat the following steps on all Historical database servers:

  1. If you are setting up the first server in a Historical database cluster, skip to the next step.

    If you are adding a server to an existing cluster, confirm that the cluster is in green or yellow status:

    1. From the main Unified Assurance navigation menu, select Analytics, then Events, then Administration, and then Console.

    2. Enter the following request in the console and click the arrow to run the request:

      GET _cluster/health

      The response should contain "status": "green" or "status": "yellow". Either status means all primary shards are allocated to nodes.

  2. On the database server, go to the following directory:

    cd $A1BASEDIR/bin/historical/

  3. Start AnalyticsWizard by running the following command as root:

    ./AnalyticsWizard

  4. When prompted Allow this script to configure for analytics?, enter y then press Enter.

  5. When prompted to enter the heap size, make a change if needed then press Enter.

    Note:

    By default, the heap size is set to thirty percent of the total system memory, rounded down. You can change this for different environments, with a minimum recommended value of 512 megabytes (512m).

  6. Do one of the following:

    • If you are setting up the first server in a Historical database cluster:

      1. AnalyticsWizard automatically identifies the servers to use for each analytics component. When prompted Are these servers correct?, review the list to verify the following:

        • Analytics UI: The presentation server.

        • Analytics DB: A database server with the Database.Historical role. You cannot change this.

        • Importer: A database server with the Database.Historical role.

      2. If the servers listed are correct, enter y then press Enter. To make a change to the server for the MySQL Replication Data Importer service, enter n, press Enter, and change the server as needed.

        You can use any Historical database server (with the Database.Historical role) that will be part of the same cluster.

        You are also prompted to change the UI server. However, because you should only have one internal presentation server, and the Analytics UI can only be installed on a server with the Presentation.Internal role, the default server is the only valid option.

      3. When prompted for the OpenSearch cluster name, make a change if needed, and press Enter.

    • If you are setting up an additional server in a cluster, when prompted whether you want to join the node to the existing cluster, enter y and press Enter.

    AnalyticsWizard installs analytics and other related services and sets up the cluster.

  7. If you are setting up the first server in the cluster, the Historical database server installation process is complete. Proceed to Installing Unified Assurance on the Collection Server.

    If you are adding a server to an existing cluster, update the number of replicas for each index. See Increasing Replicas for Indexes for more information.

Installing Unified Assurance on the Collection Server

Before beginning these steps, you must:

To install Unified Assurance on the collection server:

  1. Go to the following directory:

    cd $A1BASEDIR/bin/

  2. Start SetupWizard by running the following command as root:

    ./SetupWizard

  3. When prompted Is this your Primary Presentation Server?, enter n then press Enter.

  4. When prompted Enter the Host FQDN of your Primary Presentation Server:, enter the host FQDN of the presentation server then press Enter.

  5. When prompted Enter the Web FQDN of your Primary Presentation Server:, enter the web FQDN of the presentation server then press Enter.

  6. When prompted Set Web FQDN for this server?, enter n then press Enter.

  7. When prompted Is this a redundant server?, enter n then press Enter.

  8. When prompted Comma-delimited list of roles to install (numeric):, enter the numerical value for the Collection role then press Enter.

  9. When prompted Do you accept all the license agreements? Must type "AGREE":, enter AGREE then press Enter.

    The files needed for the installation are downloaded from the presentation server and installed.

  10. Check the following log files for installation errors:

    • $A1BASEDIR/logs/SetupWizard.log

    • $A1BASEDIR/logs/Package.log

The installation process is complete.