Multi-Server Install Guide¶

Overview¶

A multi-server install is the default install configuration used in production environments. The usual configuration is one Presentation server, one Database server, one Elasticsearch Database server, and one 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.

Steps¶

Preparation¶

Get the collection files by logging into MOS, then going to the "Patches & Updates" tab.
Upload the files to the "/opt/install/" directory on the presentation server that will be part of the environment. (Create the directory, if it does not already exist.)
Unzip all of the collection files:
```
unzip p#-part#of#.zip
```
Extract the contents of the collection to the /opt/install/ directory:
```
cat Assure1-5.X.Y-ZZZ.tgz.part-* | tar -C /opt/install/ -xzv
```
Upload the RPM file to the "/opt/install/" directory on all servers that will be part of the environment. (Create the directory, if it does not already exist.)
Install the RPM on all servers that will be part of the environment using one of the following examples.
- This will install Assure1 into the /opt/assure1/ directory:
```
yum install /opt/install/Assure1-5.X.Y-ZZZ.x86_64.rpm
```
- Assure1 can be installed to a different directory by using the "rpm" installation command with the "prefix" flag. An example is shown below which will place the files in the "/opt/a1/" 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 install again using the "rpm" command.
```
rpm -ivh --prefix /opt/a1 /opt/install/Assure1-5.X.Y-ZZZ.x86_64.rpm
```

Base Installation¶

Presentation Server¶

The SetupWizard for installing Assure1 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.
Run the SetupWizard to begin the installation. The SetupWizard command must be run as root:
```
./SetupWizard --Depot /opt/install/:a1-local
```
When prompted Is this your Primary Presentation Server?, enter y and press Enter.
When prompted What is this install's Web FQDN? [FQDN]:, make a change if needed, then press Enter.
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. 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.
When prompted Do you accept all the license agreements? Must type "AGREE":, enter AGREE and press Enter.
The software will then be installed. Wait for this process to finish.
The following log files can be checked for errors that may have occurred during the install:
- $A1BASEDIR/logs/SetupWizard.log
- $A1BASEDIR/logs/Package.log
Enter the web-FQDN of the server into your browser to open up the UI login page. Login with:
- Username: admin
- Password: admin
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.

Database Server¶

The SetupWizard for installing Assure1 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.
Run the SetupWizard to begin the installation. The SetupWizard command must be run as root:
```
./SetupWizard
```
When prompted Is this your Primary Presentation Server?, enter n and press Enter.
When prompted Enter the Host FQDN of your Primary Presentation Server:, enter the host FQDN of the server, then press Enter.
When prompted Enter the Web FQDN of your Primary Presentation Server:, enter the web FQDN of the server, then press Enter.
When prompted Set Web FQDN for this server?, enter n and press Enter.
When prompted Is this a redundant server?, enter n and press Enter.
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
When prompted Do you accept all the license agreements? Must type "AGREE":, enter AGREE and press Enter.
The files needed for the installation will then be downloaded from the presentation server and installed.
The following log files can be checked for errors that may have occurred during the install:
- $A1BASEDIR/logs/SetupWizard.log
- $A1BASEDIR/logs/Package.log

Elasticsearch Database Server¶

The SetupWizard for installing Assure1 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.
Run the SetupWizard to begin the installation. The SetupWizard command must be run as root:
```
./SetupWizard
```
When prompted Is this your Primary Presentation Server?, enter n and press Enter.
When prompted Enter the Host FQDN of your Primary Presentation Server:, enter the host FQDN of the server, then press Enter.
When prompted Enter the Web FQDN of your Primary Presentation Server:, enter the web FQDN of the server, then press Enter.
When prompted Set Web FQDN for this server?, enter n and press Enter.
When prompted Is this a redundant server?, enter n and press Enter.
When prompted Comma-delimited list of roles to install (numeric):, enter the numerical values for the "Database.Historical" role, and then press Enter.
When prompted Do you accept all the license agreements? Must type "AGREE":, enter AGREE and press Enter.
The files needed for the installation will then be downloaded from the presentation server and installed.
The following log files can be checked for errors that may have occurred during the install:
- $A1BASEDIR/logs/SetupWizard.log
- $A1BASEDIR/logs/Package.log
The AnalyticsWizard for installing analytics is located in the $A1BASEDIR/bin/historical/ directory. Go to the directory:
```
cd $A1BASEDIR/bin/historical/
```
Run the AnalyticsWizard to begin the installation. The AnalyticsWizard command must be run as root:
```
./AnalyticsWizard
```
When prompted Allow this script to configure for analytics? [n]:, enter y and press Enter.
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).
When prompted What maximum machine learning size should Elasticsearch use (percent of system memory)? [60]:, make a change if needed, then press Enter.
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 presentation server.
- Analytics DB: This should be the database server with the "Database.Historical" roles.
- Importer: This should be the 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.
Analytics will then be installed, along with a variety of sub-services needed for proper functionality.

Collection Server¶

The SetupWizard for installing Assure1 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.
Run the SetupWizard to begin the installation. The SetupWizard command must be run as root:
```
./SetupWizard
```
When prompted Is this your Primary Presentation Server?, enter n and press Enter.
When prompted Enter the Host FQDN of your Primary Presentation Server:, enter the host FQDN of the server, then press Enter.
When prompted Enter the Web FQDN of your Primary Presentation Server:, enter the web FQDN of the server, then press Enter.
When prompted Set Web FQDN for this server?, enter n and press Enter.
When prompted Is this a redundant server?, enter n and press Enter.
When prompted Comma-delimited list of roles to install (numeric):, enter the numerical value for the "Collection" role, and then press Enter.
When prompted Do you accept all the license agreements? Must type "AGREE":, enter AGREE and press Enter.
The files needed for the installation will then be downloaded from the presentation server and installed.
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 "Getting started" and "Basic Setup" sections which are available in the navigation on the left, about how to use the Assure1 platform.