Installing Unified Assurance on Multiple Redundant Servers

In production environments that require automatic failover for high availability, you install Oracle Communications Unified Assurance components across multiple paired redundant servers. Typically, this involves two presentation servers, two database servers, two Elasticsearch database servers, and two 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, its redundant pair, and multiple collection servers and their redundant pairs.

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

Multiple Redundant Server Installation Prerequisites and Directories

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

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

Multiple Redundant Server Installation Best Practices

Review the following best practices before starting an installation.

Adding a Single Server

When adding a single server to an environment that is using redundancy, to ensure database connections are done to the correct destination server, manually enable the Database Watchdog service on the new server by using the Services UI. See Services in Unified Assurance User's Guide for information about this UI.

IP Failover Using Keepalived

If you are not using a physical load balancer for your Unified Assurance system, you can use Keepalived for load balancing based on virtual IPs.

Keepalived is used for IP failover between two servers to facilities load balancing and high-availability for Linux based systems. It works using Virtual Router Redundancy Protocol (VRRP).

Note:

If the presentation servers are in different subnets, or if a firewall between the servers is blocking multicast traffic, Keepalived may need to be configured to use unicast instead of multicast. See Keepalived using unicast, track and notify scripts on linux-admins.net for more information.

The following example shows how to set up IP failover on your system using Keepalived.

Example: Setting Up IP Failover Using Keepalived

In this example, the following IP placeholders are used:

To install Keepalived:

  1. Install Keepalived using the yum command:

    yum install keepalived

  2. On the primary server, edit the Keepalived configuration file (/etc/keepalived/keepalived.conf), replacing the placeholders with your Unified Assurance system and network configuration.

    ! Configuration File for keepalived

global_defs {
   notification_email {
     <TO_EMAIL_ADDRESS1>
     <TO_EMAIL_ADDRESS2>
   }
   notification_email_from <FROM_EMAIL_ADDRESS1>
   smtp_server <SMTP_SERVER>
   smtp_connect_timeout 30
}

vrrp_instance VI_1 {
    state MASTER
    interface <INTERFACE_NAME>
    virtual_router_id 51
    priority 101
    advert_int 1
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        <SHARED_IP_ADDRESS>
    }
}

  3. On the backup server, edit the Keepalived configuration file (/etc/keepalived/keepalived.conf), replacing the placeholders with your Unified Assurance system and network configuration.

    ! Configuration File for keepalived

global_defs {
   notification_email {
     <TO_EMAIL_ADDRESS1>
     <TO_EMAIL_ADDRESS2>
   }
   notification_email_from <FROM_EMAIL_ADDRESS2>
   smtp_server <SMTP_SERVER>
   smtp_connect_timeout 30
}

vrrp_instance VI_1 {
    state MASTER
    interface <INTERFACE_NAME>
    virtual_router_id 51
    priority 100
    advert_int 1
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        <SHARED_IP_ADDRESS>
    }
}

    • Make sure to set the priority value to a lower value than the primary server's priority value. In this example, the primary server priority value is set to 101 and the backup server priority value is set to 100.

    • Set virtual_router_id to the same thing on the primary and backup server.

    Note:

    In the example, email notifications are set up on Keepalived changes. You could alternatively use the syslog option to send a syslog message when a change is detected.

  4. Start the Keepalived service by running the following command:

    service keepalived start

  5. Configure Keepalived to automatically start on system boot up: 

    chkconfig keepalived on

By default, the virtual IP address is assigned to primary server. If the primary server goes down, the virtual IP is automatically reassigned to the backup server. Run the following command to see the assigned virtual IP on an interface:

ip addr show <INTERFACE_NAME>

For example, the output might be:

2: <INTERFACE_NAME>:  mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether <MAC_ADDRESS> brd <NETMASK>:ff
    inet <PRIMARY_IP_ADDRESS>/24 brd <NETMASK>.255 scope global <INTERFACE_NAME>
    inet <SHARED_IP_ADDRESS>/32 scope global <INTERFACE_NAME>
    inet6 fe80::20c:29ff:fe6f:ed60/64 scope link
       valid_lft forever preferred_lft forever

Example: Verifying IP Failover Using Keepalived

  1. Shut down the primary server.

  2. Check that the IP address is automatically reassigned to the backup server by running the following command:

    ip addr show <INTERFACE_NAME>

    The output should contain the backup IP address.

  3. Restart the primary server and stop the backup server.

  4. Check that the IP address is automatically reassigned to the primary server by running the following command:

    ip addr show <INTERFACE_NAME>

    The output should contain the primary IP address.

  5. Check the following log file to ensure everything is working as it should:

    tailf /var/log/messages

    The output should contain something like the following:

    Mar 19 17:30:24 localhost Keepalived_vrrp[6958]: VRRP_Instance(VI_1) Transition to MASTER STATE
Mar 19 17:30:25 localhost Keepalived_vrrp[6958]: VRRP_Instance(VI_1) Entering MASTER STATE
Mar 19 17:30:25 localhost Keepalived_vrrp[6958]: VRRP_Instance(VI_1) setting protocol VIPs.
Mar 19 17:30:25 localhost Keepalived_healthcheckers[6957]: Netlink reflector reports IP <SHARED_IP_ADDRESS> added
Mar 19 17:30:25 localhost avahi-daemon[1407]: Registering new address record for <SHARED_IP_ADDRESS> on <INTERFACE_NAME>.IPv4.
Mar 19 17:30:25 localhost Keepalived_vrrp[6958]: VRRP_Instance(VI_1) Sending gratuitous ARPs on <INTERFACE_NAME> for

Additional Resources

For more information on the setup and configuration of Keepalived and virtual IP failover consult the following websites:

Preparing to Install Unified Assurance on Multiple Redundant Servers

To prepare the servers for the Unified Assurance installation:

  1. On the primary presentation server that will be part of the environment:

    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 the 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

  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. Upload the extracted RPM file from the primary presentation server to <installation_directory> on all other servers.

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

    1. Install the RPM 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

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

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

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

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

Installing Unified Assurance on the Presentation Servers

Installing on the presentation servers involves installing Unified Assurance on each server and then running RedundancyWizard on each server.

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

Installing Unified Assurance on the Primary Presentation Server

  1. Install Unified Assurance by running SetupWizard on the primary 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

      • Database.Redundancy

      • Presentation.Redundancy

      • 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

  2. 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 primary presentation server installation is complete. Proceed to Installing Unified Assurance on the Redundant Presentation Server.

Installing Unified Assurance on the Redundant 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 n then press Enter.

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

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

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

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

  8. When prompted Is this a redundant server?, enter y then press Enter.

  9. When prompted Enter the Host FQDN of this server's primary server:, enter the host FQDN of the primary presentation server then press Enter.

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

    • Presentation

    • Database.Redundancy

    • Presentation.Redundancy

    • Processing

    Note:

    A redundant server must have the same roles installed as the primary server.

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

    Setup Wizard installs Unified Assurance.

  12. Check the following log files for installation errors:

    • $A1BASEDIR/logs/SetupWizard.log

    • $A1BASEDIR/logs/Package.log

The redundant presentation server installation is complete. Proceed to Running RedundancyWizard on the Presentation Servers.

Running RedundancyWizard on the Presentation Servers

  1. On the redundant presentation server, go to the following directory:

    cd $A1BASEDIR/bin/redundancy/

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

    ./RedundancyWizard

  3. When prompted Proceed with configuring local server as redundant partner to [PRIMARY PRESENTATION SERVER]?, verify that the correct server is listed, enter y, then press Enter.

  4. Wait for the listener to activate.

  5. On the primary presentation server, go to the following directory:

    cd $A1BASEDIR/bin/redundancy/

  6. Start RedundancyWizard by running the following command as root:

    ./RedundancyWizard

  7. When shown the list of servers that will be used, verify that the correct servers and roles are listed.

  8. When prompted Is this correct?, enter y then press Enter.

  9. When prompted Allow this script to configure presentation redundancy?, enter y then press Enter.

  10. When prompted Allow this script to configure database redundancy?, enter y then press Enter.

  11. When prompted Allow this script to perform database synchronization?, enter y then press Enter.

  12. When prompted Please press [enter] after starting script on redundant server or type "e" to exit, press Enter.

  13. Wait for the wizard to finish synchronizing the data.

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

Installing Unified Assurance on the Database Servers

Installing on the database servers involves installing Unified Assurance on each server then running RedundancyWizard on each server. If you have multiple redundant pairs of database servers, perform the steps in this section on each pair in turn.

For example, if you have two redundant pairs, perform the installation in the following order:

  1. Install on the primary database server for pair 1.

  2. Install on the redundant database server for pair 1.

  3. Run RedundancyWizard for pair 1.

  4. Install on the primary database server for pair 2.

  5. Install on the redundant database server for pair 2.

  6. Run RedundancyWizard for pair 2.

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

Note:

The installation process is different on Elasticsearch database servers. See Installing Unified Assurance on the Elasticsearch Database Servers

Installing Unified Assurance on the Primary 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 primary presentation server then press Enter.

  5. When prompted Enter the Web FQDN of your Primary Presentation Server:, enter the web FQDN of the primary 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

    • Database.Redundancy

    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 primary presentation server and installed.

  10. Check the following log files for installation errors:

    • $A1BASEDIR/logs/SetupWizard.log

    • $A1BASEDIR/logs/Package.log

The primary database server installation is complete. Proceed to Installing Unified Assurance on the Redundant Database Server.

Installing Unified Assurance on the Redundant 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 primary presentation server then press Enter.

  5. When prompted Enter the Web FQDN of your Primary Presentation Server:, enter the web FQDN of the primary 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 y then press Enter.

  8. When prompted Enter the Host FQDN of this server's primary server:, enter the FQDN of the primary database server then press Enter.

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

    • Database.Redundancy

    Note:

    A redundant server must have the same roles installed as the primary server.

  10. 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 primary presentation server and installed.

  11. Check the following log files for installation errors:

    • $A1BASEDIR/logs/SetupWizard.log

    • $A1BASEDIR/logs/Package.log

The redundant database server installation is complete. Proceed to Running RedundancyWizard on the Database Servers.

Running RedundancyWizard on the Database Servers

  1. On the redundant database server, go to the following directory:

    cd $A1BASEDIR/bin/redundancy/

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

    ./RedundancyWizard

  3. When prompted Proceed with configuring local server as redundant partner to [PRIMARY DATABASE SERVER]?, verify that the correct server is listed, enter y, then press Enter.

  4. Wait for the listener to activate.

  5. On the primary database server go to the following directory:

    cd $A1BASEDIR/bin/redundancy/

  6. Start RedundancyWizard by running the following command as root:

    ./RedundancyWizard

  7. When shown The following servers will be used:, verify that the correct servers and roles are listed.

  8. When prompted Is this correct?, enter y then press Enter.

  9. When prompted Allow this script to configure database redundancy?, enter y then press Enter.

  10. When prompted Allow this script to perform database synchronization?, enter y then press Enter.

  11. When prompted Please press [enter] after starting script on redundant server or type "e" to exit, press Enter.

  12. When prompted Config update needed. This will restart your primary database server. Do you wish to proceed?, enter y then press Enter.

  13. When prompted Config update needed. This will restart your Graph database. Do you wish to proceed?, enter y then press Enter.

  14. When prompted Config update needed. This will restart your Metric database. Do you wish to proceed?, enter y then press Enter.

  15. Wait for the wizard to finish synchronizing the data.

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

Installing Unified Assurance on the Elasticsearch Database Servers

Installing on the Elasticsearch database servers involves installing Unified Assurance on each server. You do not need to run RedundancyWizard for Elasticsearch.

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

Installing Unified Assurance on the Primary Elasticsearch Database Server

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

    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 primary presentation server then press Enter.

    5. When prompted Enter the Web FQDN of your Primary Presentation Server:, enter the web FQDN of the primary 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.Historical

      • Database.Redundancy

    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 primary presentation server and installed.

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

      • $A1BASEDIR/logs/SetupWizard.log

      • $A1BASEDIR/logs/Package.log

  2. 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 then press Enter.

    4. When prompted What heap size should Elasticsearch use? [<value>]:, make a change if needed then 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 then press Enter.

    6. When provided information about analytics components and a list of servers, then prompted Are these servers correct? [n]:, review the list to verify the following:

      • Analytics UI: The primary presentation server.

      • Analytics DB: The primary database server with the Database.Historical roles.

      • Importer: The primary database server with the Database.Historical roles.

    7. If the servers listed are correct, enter y then press Enter. If they are incorrect, enter n, press Enter, and change the servers listed for each role as needed.

      AnalyticsWizard installs analytics and other related services.

The primary Elasticsearch database server installation is complete. Proceed to Installing Unified Assurance on the Redundant Elasticsearch Database Server.

Installing Unified Assurance on the Redundant Elasticsearch Database Server

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

    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 primary presentation server then press Enter.

    5. When prompted Enter the Web FQDN of your Primary Presentation Server:, enter the web FQDN of the primary 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 y then press Enter.

    8. When prompted Enter the Host FQDN of this server's primary server:, enter the FQDN of the primary Elasticsearch database server then press Enter.

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

      • Database.Historical

      • Database.Redundancy

      Note:

      A redundant server must have the same roles installed as the primary server.

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

      The files needed for the installation will then be downloaded from the primary presentation server and installed.

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

      • $A1BASEDIR/logs/SetupWizard.log

      • $A1BASEDIR/logs/Package.log

  2. 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 then press Enter.

    4. When prompted What heap size should Elasticsearch use? [<value>]:, make a change if needed then 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 then press Enter.

    6. When provided information about analytics components and a list of servers, then prompted Are these servers correct? [n]:, review the list to verify the following:

      • Analytics UI: The redundant presentation server.

      • Analytics DB: The redundant database server with the Database.Historical roles.

      • Importer: The redundant database server with the Database.Historical roles.

    7. If the servers listed are correct, enter y then press Enter. If they are incorrect, enter n, press Enter, and change the servers listed for each role as needed.

      AnalyticsWizard installs analytics and other related services.

The Elasticsearch database server installation process is complete. Proceed to Installing Unified Assurance on the Collection Servers.

Installing Unified Assurance on the Collection Servers

Installing on the collection servers involves installing Unified Assurance on each server. You do not need to run RedundancyWizard for collection servers.

Before beginning these steps, you must:

Installing Unified Assurance on the Primary 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 primary presentation server then press Enter.

  5. When prompted Enter the Web FQDN of your Primary Presentation Server:, enter the web FQDN of the primary 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 primary presentation server and installed.

  10. Update local installation files by running ConfigHelper as root:

    ./ConfigHelper

  11. Check the following log files for installation errors:

    • $A1BASEDIR/logs/SetupWizard.log

    • $A1BASEDIR/logs/Package.log

The primary collection server installation is complete. Proceed to Installing Unified Assurance on the Redundant Collection Server.

Installing Unified Assurance on the Redundant 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 primary presentation server then press Enter.

  5. When prompted Enter the Web FQDN of your Primary Presentation Server:, enter the web FQDN of the primary 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 y then press Enter.

  8. When prompted Enter the Host FQDN of this server's primary server:, enter the FQDN of the primary collection server then press Enter.

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

    Note:

    A redundant server must have the same roles installed as the primary server.

  10. 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 primary presentation server and installed.

  11. Update local installation files by running ConfigHelper as root:

    ./ConfigHelper

  12. Check the following log files for installation errors:

    • $A1BASEDIR/logs/SetupWizard.log

    • $A1BASEDIR/logs/Package.log

The installation process is complete.