Installing Unified Assurance on a Single Server

You can install all Oracle Communications Unified Assurance components on a single server. You can use a single server installation as a test server or for proof of concepts. Oracle does not recommend single server installations for prolonged network monitoring.

Single 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:

• /opt: The Unified Assurance parent directory.

• /opt/install: The Unified Assurance installation directory.

• /opt/assure1: The Unified Assurance home directory created by the RPM installation and set as $A1BASEDIR.

Installing Unified Assurance on a Single Server

To install Unified Assurance on a single server:

1. 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.

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

   /opt/install

   The documentation refers to this directory as <installation_directory>.

3. Move the collection file to <installation_directory>.

4. Extract the contents of the collection file:

   unzip -d <installation_directory> Oracle-Communications-Unified-Assurance-6.W.X.Y.Z-el8.zip
   

5. Install the RPM on the server by running one of the following commands:

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

     yum install <installation_directory>/Assure1-6.V.W.X.Y-ZZZ.el8.x86_64.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
     

6. 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.

7. Run one of the following commands as root:

   • Export LD_LIBRARY_PATH:

     export LD_LIBRARY_PATH=$A1BASEDIR/lib:$A1BASEDIR/lib/private
     

   • Source the .bashrc file:

     source $A1BASEDIR/.bashrc
     

   Note:

   By default, $A1BASEDIR is set to /opt/assure1/. If you used a custom home directory, this will be different.

8. Enable temporary files to run by redirecting the root tmp directory to the Unified Assurance tmp directory with the following command:

   export TMP=$A1BASEDIR/tmp
   

   This is required to run the SetupWizard application that installs Unified Assurance.

9. Install Unified Assurance by running SetupWizard:

   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 and press Enter.

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

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

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

      Setup Wizard installs Unified Assurance.

   7. Check the following log files for installation errors:

      • $A1BASEDIR/logs/SetupWizard.log

      • $A1BASEDIR/logs/Package.log

10. Install analytics by running AnalyticsWizard:

    1. Go to the following directory:

       cd $A1BASEDIR/bin/historical/
       

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

       ./AnalyticsWizard
       

    3. When prompted Allow this script to configure for analytics? [n]:, enter y and press Enter.

    4. When prompted What heap size should Elasticsearch use? [<value>]:, make a change if needed and press Enter.

       Note:

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

    5. When prompted What maximum machine learning size should Elasticsearch use (percent of system memory)? [60]:, make a change if needed and press Enter.

    6. When provided information about analytics components and a list of servers, then prompted Are these servers correct? [n]:, enter y and press Enter.

       AnalyticsWizard installs analytics and other related services.

11. 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 installation process is complete.