Multi-Server Redundant Install

Overview

A multi-server redundant install is another install configuration used in production environments that require automatic failover for high availability. The usual configuration are two Presentation servers, two Database servers, two Elasticsearch Database servers, and two or more Collection servers, however, a single server can have one or more roles associated to it. This means that it is also possible to setup a combination Presentation/Database server and then one or more Collection servers, or a combination Presentation/Collection server with a separate Database server, etc.

See the Understanding Server Roles documentation for additional information around roles that are available.

Dependencies

• See the Prerequisites for CentOS7 or RHEL7 documentation before starting an installation.

• 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

Best Practices

Adding a single server

When adding a single server to an environment that is using redundancy, the Database Watchdog service (Unified Assurance Database Watchdog Utility) must be manually enabled on the new server to ensure database connections are done to the correct destination server. This is done on the Services UI:

Configuration -> Broker Control -> Services

IP Failover using KeepAlived

If you are not using a physical load balancer for your Unified Assurance system, there is the option of using KeepAlived for load balancing based on virtual IP's.

KeepAlived is used for IP failover between two servers. It facilities for load balancing and high-availability for Linux based systems. It works using VRRP (Virtual Router Redundancy Protocol). The following example illustrates how to set up IP failover on your system using KeepAlived.

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. Additional information is available in the linux-admins.net Keepalived using unicast guide http://www.linux-admins.net/2015/02/keepalived-using-unicast-track-and.html.

Server Scenario

• LB1 Server: 192.168.10.111 - primary load balancer server

• LB2 Server: 192.168.10.112 - backup load balancer server

• Virtual IP: 192.168.10.121 - virtual IP address managed by KeepAlived

Installation

1. Install KeepAlived using the yum command:

   yum install keepalived

2. On the primary server, edit the KeepAlived configuration file (/etc/keepalived/keepalived.conf). Replace the square-bracket ( [] ) values with your Unified Assurance system and network configuration.

   ! Configuration File for keepalived
   
   global_defs {
      notification_email {
        [[e-mail]]
        [[e-mail]]
      }
      notification_email_from [[e-mail]]
      smtp_server [localhost]
      smtp_connect_timeout 30
   }
   
   vrrp_instance VI_1 {
       state MASTER
       interface [eth1]
       virtual_router_id 51
       priority 101
       advert_int 1
       authentication {
           auth_type PASS
           auth_pass 1111
       }
       virtual_ipaddress {
           [192.168.10.121]
       }
   }
   

3. On the backup server, edit the KeepAlived configuration file (/etc/keepalived/keepalived.conf). Replace the square-bracket ( [] ) values with your Unified Assurance system and network configuration.

   ! Configuration File for keepalived
   
   global_defs {
      notification_email {
        [[e-mail]]
        [[e-mail]]
      }
      notification_email_from [[e-mail]]
      smtp_server [localhost]
      smtp_connect_timeout 30
   }
   
   vrrp_instance VI_1 {
       state MASTER
       interface [eth1]
       virtual_router_id 51
       priority 100
       advert_int 1
       authentication {
           auth_type PASS
           auth_pass 1111
       }
       virtual_ipaddress {
           [192.168.10.121]
       }
   }
   

   • Make sure to set the priority value to a lower value than the primary server "priority" value (in this example, the primary server "priority" value is set to 101, while the backup server "priority" value is set to 100).

   • virtual_router_id should be the same on both primary and backup servers.

   Note:

   In the above example, email notifications are setup on KeepAlived changes. A Syslog option is also available, to send a Syslog message when a change is detected.

4. Start the KeepAlived service using the following command:

   service keepalived start

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

   chkconfig keepalived on

6. By default, the virtual IP address will be assigned to primary server. In the event that the primary server goes down, the virtual IP will automatically be assigned to the backup server. The following command will show the assigned virtual IP on an interface:

   ip addr show eth1

   Sample Output

   2: eth1:  mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
       link/ether 00:0c:29:6f:ed:60 brd ff:ff:ff:ff:ff:ff
       inet 192.168.10.111/24 brd 192.168.1.255 scope global eth1
       inet 192.168.10.121/32 scope global eth1
       inet6 fe80::20c:29ff:fe6f:ed60/64 scope link
          valid_lft forever preferred_lft forever
   

Verifying IP Failover

1. Shut down the primary server and check if the IP address is automatically assigned to the backup server.

   ip addr show eth1

2. Next, start the primary server again and stop the backup server. Check to ensure that the IP address is automatically assigned to the primary server.

   ip addr show eth1

3. Examine the log file to ensure everything is working as it should.

   tailf /var/log/messages

   Sample Output

   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 192.168.10.121 added
   Mar 19 17:30:25 localhost avahi-daemon[1407]: Registering new address record for 192.168.10.121 on eth1.IPv4.
   Mar 19 17:30:25 localhost Keepalived_vrrp[6958]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth1 for
   

Further Information

For more information on the setup and configuration of KeepAlived and virtual IP failover consult the following guides:

• tecadmin.net IP Failover guide: https://tecadmin.net/ip-failover-setup-using-keepalived-on-centos-redhat/

• cyberciti.biz IP Failover & KeepAlived guide: http://www.cyberciti.biz/faq/rhel-centos-fedora-keepalived-lvs-cluster-configuration

Steps

Preparation

1. Get the collection file and place it in the /opt/install/ directory on the server. (Create the directory, if it does not already exist.)

2. Extract the contents of the collection to the /opt/install/ directory:

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

3. Install the RPM on the server using the following syntax. By default, this will install Unified Assurance into the /opt/assure1/ directory:

   yum install /opt/install/Assure1-6.V.W.X.Y-ZZZ.x86_64.rpm
   

   Note:

   Unified Assurance can be installed to a different directory by using the "rpm" installation command with the "prefix" flag.

   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 install again using the "rpm" command.

   An example is shown below which will place the files in the "/opt/a1/" directory:

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

4. Do one of the following before running SetupWizard.

   • Export the LD_LIBRARY_PATH:

     export LD_LIBRARY_PATH=$A1BASEDIR/lib

   • or source the .bashrc file:

     source $A1BASEDIR/.bashrc

Base Installation

Primary Presentation Server

1. The SetupWizard for installing Unified Assurance is located in the $A1BASEDIR/bin/ directory. Go to the directory:

   cd $A1BASEDIR/bin/
   

   Note:

   The default $A1BASEDIR is /opt/assure1/. This may be different if a custom path was used in the preparation step.

2. Run the SetupWizard to begin the installation. The SetupWizard command must be run as root and must include the --Depot flag:

   ./SetupWizard --Depot /opt/install/: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, 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. While it is not required to be on the presentation server, it will still 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, the role may need to be migrated to be on a dedicated system.

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

7. The files needed for the installation will then be downloaded and installed.

8. The following log files can be checked for errors that may have occurred during the install:

   • $A1BASEDIR/logs/SetupWizard.log

   • $A1BASEDIR/logs/Package.log

9. Enter the web-FQDN of the server into your browser to open up the UI login page. Login with:

   • Username: admin

   • Password: admin

10. Navigate to the Users UI and select the admin user account.

    Configuration -> AAA -> Users

    Note:

    As a best practice, it is advised to update/change the administrator password to a password of your choosing.

Redundant Presentation Server

1. The SetupWizard for installing Unified Assurance is located in the $A1BASEDIR/bin/ directory. Go to the directory:

   cd $A1BASEDIR/bin/
   

   Note:

   The default $A1BASEDIR is /opt/assure1/. This may be different if a custom path was used in the preparation step.

2. Run the SetupWizard to begin the installation. The SetupWizard command must be run as root:

   ./SetupWizard
   

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

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

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

6. When prompted Set Web FQDN for this server?, enter y and 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 and press Enter.

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

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

    Note:

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

    • Presentation

    • Database.Redundancy

    • Presentation.Redundancy

    • Processing

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

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

13. The following log files can be checked for errors that may have occurred during the install:

    • $A1BASEDIR/logs/SetupWizard.log

    • $A1BASEDIR/logs/Package.log

Run Redundancy Wizard on Presentation Servers

1. On the redundant presentation server, the RedundancyWizard for the automated configuration of Unified Assurance redundancy is located in the $A1BASEDIR/bin/redundancy/ directory. Go to the directory:

   cd $A1BASEDIR/bin/redundancy/
   

   Note:

   The default $A1BASEDIR is /opt/assure1/. This may be different if a custom path was used in the preparation step.

2. Run RedundancyWizard to begin the configuration. The RedundancyWizard command must be run as root:

   ./RedundancyWizard
   

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

4. Wait for the listener to activate.

5. On the primary presentation server, the RedundancyWizard for the automated configuration of Unified Assurance redundancy is located in the $A1BASEDIR/bin/redundancy/ directory. Go to the directory:

   cd $A1BASEDIR/bin/redundancy/
   

   Note:

   The default $A1BASEDIR is /opt/assure1/. This may be different if a custom path was used in the preparation step.

6. Run RedundancyWizard to begin the configuration:

   ./RedundancyWizard
   

7. When shown The following servers will be used:, verify the servers listed and their role is correct. At the prompt Is this correct?, enter y and press Enter.

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

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

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

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

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

Primary Database Server

1. The SetupWizard for installing Unified Assurance is located in the $A1BASEDIR/bin/ directory. Go to the directory:

   cd $A1BASEDIR/bin/
   

   Note:

   The default $A1BASEDIR is /opt/assure1/. This may be different if a custom path was used in the preparation step.

2. Run the SetupWizard to begin the installation. The SetupWizard command must be run as root:

   ./SetupWizard
   

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

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

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

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

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

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

   Note:

   Depending on the load per database, the different database roles can be installed on separate servers. One possible combination are the Event and Graph databases can be put on the same server while keeping the Metric database separate, but larger organizations may need to keep all three separate.

   • Database.Event

   • Database.Graph

   • Database.Metric

   • Database.Redundancy

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

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

11. The following log files can be checked for errors that may have occurred during the install:

    • $A1BASEDIR/logs/SetupWizard.log

    • $A1BASEDIR/logs/Package.log

Redundant Database Server

1. The SetupWizard for installing Unified Assurance is located in the $A1BASEDIR/bin/ directory. Go to the directory:

   cd $A1BASEDIR/bin/
   

   Note:

   The default $A1BASEDIR is /opt/assure1/. This may be different if a custom path was used in the preparation step.

2. Run the SetupWizard to begin the installation. The SetupWizard command must be run as root:

   ./SetupWizard
   

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

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

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

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

7. When prompted Is this a redundant server?, enter y and press Enter.

8. When prompted Enter the Host FQDN of this server's primary server:, enter the FQDN of the primary database server and 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:

   Note:

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

   • Database.Event

   • Database.Graph

   • Database.Metric

   • Database.Redundancy

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

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

12. The following log files can be checked for errors that may have occurred during the install:

    • $A1BASEDIR/logs/SetupWizard.log

    • $A1BASEDIR/logs/Package.log

Run Redundancy Wizard on Database Servers

1. On the redundant database server, the RedundancyWizard for the automated configuration of Unified Assurance redundancy is located in the $A1BASEDIR/bin/redundancy/ directory. Go to the directory:

   cd $A1BASEDIR/bin/redundancy/
   

   Note:

   The default $A1BASEDIR is /opt/assure1/. This may be different if a custom path was used in the preparation step.

2. Run RedundancyWizard to begin the configuration. The RedundancyWizard command must be run as root:

   ./RedundancyWizard
   

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

4. Wait for the listener to activate.

5. On the primary database server, the RedundancyWizard for the automated configuration of Unified Assurance redundancy is located in the $A1BASEDIR/bin/redundancy/ directory. Go to the directory:

   cd $A1BASEDIR/bin/redundancy/
   

   Note:

   The default $A1BASEDIR is /opt/assure1/. This may be different if a custom path was used in the preparation step.

6. Run RedundancyWizard to begin the configuration:

   ./RedundancyWizard
   

7. When shown The following servers will be used:, verify the servers listed and their role is correct. At the prompt Is this correct?, enter y and press Enter.

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

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

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

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

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

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

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

Primary Elasticsearch Database Server

1. The SetupWizard for installing Unified Assurance is located in the $A1BASEDIR/bin/ directory. Go to the directory:

   cd $A1BASEDIR/bin/
   

   Note:

   The default $A1BASEDIR is /opt/assure1/. This may be different if a custom path was used in the preparation step.

2. Run the SetupWizard to begin the installation. The SetupWizard command must be run as root:

   ./SetupWizard
   

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

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

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

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

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

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

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

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

11. The following log files can be checked for errors that may have occurred during the install:

    • $A1BASEDIR/logs/SetupWizard.log

    • $A1BASEDIR/logs/Package.log

12. The AnalyticsWizard for installing analytics is located in the $A1BASEDIR/bin/historical/ directory. Go to the directory:

    cd $A1BASEDIR/bin/historical/
    

13. Run the AnalyticsWizard to begin the installation. The AnalyticsWizard command must be run as root:

    ./AnalyticsWizard
    

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

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

    Note:

    The <value> will be set to half of the total system memory, rounded down. This can be changed for different environments, with a minimum recommended value of 512 megabytes (512m).

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

17. When provided information about analytics components and a list of servers, then prompted Are these servers correct? [n]:, generally speaking, the values should be like this:

    • Analytics UI: This should be the primary presentation server.

    • Analytics DB: This should be the primary database server with the "Database.Historical" roles.

    • Importer: This should be the primary database server with the "Database.Historical" roles.

    If the servers listed are correct, enter y and press Enter, otherwise, enter n and press Enter. The servers listed for each role can be changed, if necessary.

18. Analytics will then be installed, along with a variety of sub-services needed for proper functionality.

Redundant Elasticsearch Database Server

1. The SetupWizard for installing Unified Assurance is located in the $A1BASEDIR/bin/ directory. Go to the directory:

   cd $A1BASEDIR/bin/
   

   Note:

   The default $A1BASEDIR is /opt/assure1/. This may be different if a custom path was used in the preparation step.

2. Run the SetupWizard to begin the installation. The SetupWizard command must be run as root:

   ./SetupWizard
   

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

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

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

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

7. When prompted Is this a redundant server?, enter y and press Enter.

8. When prompted Enter the Host FQDN of this server's primary server:, enter the FQDN of the primary elasticsearch database server and 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:

   Note:

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

   • Database.Historical

   • Database.Redundancy

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

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

12. The following log files can be checked for errors that may have occurred during the install:

    • $A1BASEDIR/logs/SetupWizard.log

    • $A1BASEDIR/logs/Package.log

13. The AnalyticsWizard for installing analytics is located in the $A1BASEDIR/bin/historical/ directory. Go to the directory:

    cd $A1BASEDIR/bin/historical/
    

14. Run the AnalyticsWizard to begin the installation. The AnalyticsWizard command must be run as root:

    ./AnalyticsWizard
    

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

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

    Note:

    The <value> will be set to half of the total system memory, rounded down. This can be changed for different environments, with a minimum recommended value of 512 megabytes (512m).

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

18. When provided information about analytics components and a list of servers, then prompted Are these servers correct? [n]:, generally speaking, the values should be like this:

    • Analytics UI: This should be the redundant presentation server.

    • Analytics DB: This should be the redundant database server with the "Database.Historical" roles.

    • Importer: This should be the redundant database server with the "Database.Historical" roles.

    If the servers listed are correct, enter y and press Enter, otherwise, enter n and press Enter. The servers listed for each role can be changed, if necessary.

19. Analytics will then be installed, along with a variety of sub-services needed for proper functionality.

Primary Collection Server

1. The SetupWizard for installing Unified Assurance is located in the $A1BASEDIR/bin/ directory. Go to the directory:

   cd $A1BASEDIR/bin/
   

   Note:

   The default $A1BASEDIR is /opt/assure1/. This may be different if a custom path was used in the preparation step.

2. Run the SetupWizard to begin the installation. The SetupWizard command must be run as root:

   ./SetupWizard
   

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

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

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

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

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

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

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

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

11. Run the ConfigHelper to update some local installation files. The ConfigHelper command must be run as root:

    ./ConfigHelper
    

12. The following log files can be checked for errors that may have occurred during the install:

    • $A1BASEDIR/logs/SetupWizard.log

    • $A1BASEDIR/logs/Package.log

Redundant Collection Server

1. The SetupWizard for installing Unified Assurance is located in the $A1BASEDIR/bin/ directory. Go to the directory:

   cd $A1BASEDIR/bin/
   

   Note:

   The default $A1BASEDIR is /opt/assure1/. This may be different if a custom path was used in the preparation step.

2. Run the SetupWizard to begin the installation. The SetupWizard command must be run as root:

   ./SetupWizard
   

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

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

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

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

7. When prompted Is this a redundant server?, enter y and press Enter.

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

9. When prompted Comma-delimited list of roles to install (numeric):, enter the numerical values for the "Collection" role, and 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 and press Enter.

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

12. Run the ConfigHelper to update some local installation files. The ConfigHelper command must be run as root:

    ./ConfigHelper
    

13. The following log files can be checked for errors that may have occurred during the install:

    • $A1BASEDIR/logs/SetupWizard.log

    • $A1BASEDIR/logs/Package.log

Post Installation

After the above steps are done, the base installation is now completed. Please review the additional documentation available in the other books which are available in the navigation on the left, about how to use the Unified Assurance platform.

---

Title and Copyright Information

Installation Guide

F59702-01

Copyright © 2022, Oracle and/or its affiliates.