Find answers to your technical questions and learn how to use our products
Search suggestions:
Find answers to your technical questions and learn how to use our products
Search suggestions:
Use this procedure to install a standalone Avaya Aura® Web Gateway or the initial node for an Avaya Aura® Web Gateway cluster.
Do not use this procedure to install additional nodes to a cluster. For more information on installing additional nodes, see Installing additional nodes to create a cluster.
Deploy the Avaya Aura® Web Gateway OVA.
Start the virtual machine.
If you are planning to use FIPS, enable it as described in Enabling FIPS mode. You cannot enable FIPS mode during or after Avaya Aura® Web Gateway installation. You cannot use the OAuth authentication feature when FIPS mode is enabled.
The Linux administrator account is created during the deployment process.
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.
During the installation, do not resize the screen or the SSH console.
These are the default values.
To return to the previous menu, select Return to Main Menu and press Enter.
If you want to enable Cassandra internode encryption, you must enable it 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.
The default value is the FQDN assigned to the local server.
For a cluster deployment that uses the internal load balancer, you must configure Front-end IP or FQDN as the FQDN corresponding to the virtual IP address of the internal load balancer.
For a cluster deployment that uses an external load balancer, you must configure Front-end IP or FQDN as the FQDN corresponding to the external load balancer.
The default port is 443.
You must remember the Keystore password for future references. You need this password for any certificate management tasks.
To return to the previous menu, select Return to Main Menu and press Enter.
If you have conferencing in your solution, then select Team Engagement + Conferencing. Otherwise, you must select Team Engagement. Do not select Conferencing only.
The system runs pre-install configuration checks.
Wait for several minutes while the installation proceeds.
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.
For more information on LDAP configuration, see LDAP configuration.
The virtual IP address is used for redundancy management of the internal load balancer in a cluster.
To avoid performance degradation of the cluster, an external load balancer is recommended for clusters with four or more nodes.
For a cluster deployment that uses an external load balancer, you must configure Front-end IP or FQDN as the FQDN corresponding to the external load balancer.
If you use an external load balancer, do not configure the virtual IP settings that enable the internal load balancer.
The system displays additional Virtual IP configuration.
You must configure the initial node as the Virtual IP master node. In a cluster, you must configure one additional node as the Virtual IP backup node.
You must save the Virtual IP authentication password. You need this password when configuring the second node in the cluster as the virtual IP backup node.
The system starts the services.
Set up the required certificates as described in Certificate configuration using the configuration utility.
Install additional nodes to create a cluster.
Change the following default passwords:
The default Cassandra database password as described in Changing the Cassandra user name and password. If you install a cluster, install all required additional nodes before changing the password.
The default password for automatic backups. For more information, see Changing the default password for automatic backups.