Installing additional nodes to create a cluster

Last Updated : Mar 02, 2022 |

About this task

You can achieve redundancy and increase capacity by creating a cluster of Avaya Aura® Web Gateway nodes.

The installation procedure for each additional node is similar to the procedure for a single-server or initial node installation, with the addition of some cluster specific configuration. After installing an initial node, use this procedure to create a cluster of Avaya Aura® Web Gateway nodes. You can also use this procedure to add nodes to an existing cluster at a later time.

The virtual IP address and the IP addresses for all nodes of the cluster must be in the same network.

Important:

When creating or expanding a cluster, for each additional Avaya Aura® Web Gateway node you must use the same resource profile that you used for the initial node. Mixed resource profile clusters are not supported. The resource profiles are set when installing the Avaya Aura® Web Gateway OVA and cannot be modified after the OVA is deployed.
To avoid performance degradation of the cluster, an external load balancer is recommended for clusters with four or more nodes.

Before you begin

Install an initial Avaya Aura® Web Gateway node. For more information, see Installing the Avaya Aura Web Gateway.
Enable the virtual IP configuration on the initial node if you are using the internal load balancer for the cluster.
Configure the front-end FQDN on the initial node to match the FQDN assigned to the load balancer. If you need to update the front-end FQDN on the initial node, use the configuration utility.
Deploy a virtual machine on the same network as the initial node for each additional node required. For more information, see the procedures for the appropriate deployment type in Initial setup.

Procedure

Open the Linux shell using your Linux administrator account credentials.

The Linux administrator account is created during the deployment process.
Do one of the following:
- If you install Avaya Aura® Web Gateway using the OVA, run the following command:
```
app install
```
  When you run the app install command without specifying a build, then the system automatically picks up the current build in opt/Avaya. If you do specify a build by running app install csa-<version>.bin, then the system looks for that build first in your current working directory and then in opt/Avaya.
- If you install Avaya Aura® Web Gateway as a software-only application, run the following command:
```
app install <PATH>/<INSTALLER>
```
  In this command, <PATH> is the full path to the directory where you extracted the application binary when installing the system layer, and <INSTALLER> is the Avaya Aura® Web Gateway application binary. For example:
  
  app install /root/csa-swonly-10.1.0.0/csa-10.1.0.0.bin
The system displays the installation screen.

Important:
During the installation, do not resize the screen or the SSH console.
Select Cluster Configuration and do the following:
1. Set the Initial cluster node option to n (no).
2. Ensure that Local Node IP address is set to the IP address of the current node.
3. Set Cluster seed node to the IP address of the initial node.
4. Set User ID (UID) of product user on seed node to the user ID of the Linux administrator that was used to install the initial Avaya Aura® Web Gateway node.
  The default value is 4000.
  
  To determine the required UID, open the Linux shell on the initial node using your administrator credentials and then run the following command:
```
id -u <adminuser>
```
5. To save the changes on the system, select Apply and then select Continue.
6. Select Return to Main Menu and press Enter.
In the Cassandra Encryption menu, enable SSL encryption to secure Cassandra database communications between nodes in a cluster.
Important:
- If you want to enable Cassandra internode encryption, you must do so during the initial installation. This setting cannot be changed after the initial installation.
- If you enabled FIPS mode, ensure that Cassandra internode encryption remains enabled. If you disable Cassandra internode encryption, installation will fail.
Select Front-end host, System Manager and Certificate Configuration and do the following:
1. Select System Manager FQDN and enter the FQDN of the Avaya Aura® System Manager that signs the certificates for Avaya Aura® Web Gateway services.
2. Optional Select System Manager web admin username (o) and System Manager web admin password and provide the credentials.
3. Select System Manager HTTPS Port and type the port for contacting Avaya Aura® System Manager.
  
  The default port is 443.
4. Select System Manager Enrollment Password and type the Avaya Aura® System Manager enrollment password.
5. Select Keystore password and type a password for using the local keystore.
  
  The keystore password on additional nodes should match the keystore password for the initial node.
  
  Important:
  You must remember the keystore password for future reference. You need this password for other certificate management tasks.
6. Configure additional settings that are required for your system as described in Front-end host, System Manager, and certificate configuration.
  
  To return to the previous menu, select Return to Main Menu and press Enter.
Select Deployment settings and then press the Spacebar to select the deployment option that corresponds to the solution that you are installing.

You must configure the same deployment type that you configured on the initial node.

If you have conferencing in your solution, then select Team Engagement + Conferencing. Otherwise, you must select Team Engagement. Do not select Conferencing only.
To review the settings, select Continue and then select Accept and continue.

The system runs pre-install configuration checks.
To install the software, select Continue and then accept the license agreement.

Wait for several minutes while the installation proceeds.
Select Continue to start the configuration utility.

Important:
Do not change the settings in Front-end host, System Manager and Certificate Configuration without reentering the System Manager enrollment and keystore passwords before applying the changes.

Warning:
Do not configure the LDAP settings on nodes that you add to a cluster. The LDAP configuration is automatically configured for additional nodes when they connect to the initial node.
If this is the second node of a cluster and the virtual IP for internal load balancing is enabled on the initial node, then do the following:

Important:
The virtual IP must be enabled only for the initial node and the second node. Do not enable the virtual IP on any other nodes.
1. Select Clustering Configuration > Virtual IP Configuration.
2. Select Enable virtual IP and set the value to y (yes).
  
  The system displays additional Virtual IP configuration.
3. Configure all of the Virtual IP settings as described in Virtual IP configuration options.
  
  Important:
  You must use the same Virtual IP authentication password that you set on the initial node of the cluster.
4. To save the changes on the system, select Apply and then select Continue.
5. Select Return to Main Menu and press Enter.
To apply the changes, from the main menu, select Continue and then select Yes to start the services.

The system starts the services.
To exit the configuration tool, select Continue.

Next Steps

Set up the required certificates as described in Certificate configuration using the configuration utility.
Repeat this procedure to add the required number of nodes to the cluster.
After all of the required cluster nodes are installed, change the default Cassandra database password as described in Changing the Cassandra user name and password.
After all of the required cluster nodes are installed or if new nodes are added to an existing cluster, you must configure the RSA public and private keys on the initial node.

Send Feedback

AVAYA DOCUMENTATION CENTER

No results found