Installing additional non-seed nodes

Last Updated : Jun 05, 2026 |

About this task

Use this procedure to install a second node or any subsequent node in the cluster.

You can enable the following features only when installing or upgrading Avaya Aura® Device Services:

  • IPv6

    Note:

    AWS, Microsoft Azure, and GCP software-only deployments do not support IPv6.

  • Utility Server

  • Onboard Open LDAP

  • SSO/OAuth2

You cannot enable these features using the Avaya Aura® Device Services administration portal or configuration utility.

Note:

Avaya recommends that you install Avaya Aura® Device Services in a Tmux session. If the SSH session terminates while the installation operation is in progress, you can re-connect to the Tmux session and complete the installation operation. For more information about the Tmux utility, see Using the Tmux utility.

Before you begin

If you are planning to use certificates specific to your organization instead of System Manager certificates, ensure that you have the cert-chain.pem certificate chain file created during the seed node installation. For more information, see step 3 of Installing Avaya Aura Device Services.

Procedure

  1. Log in to Avaya Aura® Device Services as the administrative user.

    You must use the administrative user defined during OVA deployment for logging in to Avaya Aura® Device Services.

  2. To start a Tmux session, run the following command: 
    tmux new-session -s <NAME>

    In this command, <NAME> is a Tmux session name of your choice. For example:

    tmux new-session -s AADS_INSTALLATION
  3. Do one of the following:

    • If you install Avaya Aura® Device Services using the Avaya-provided OVA, go to the /opt/Avaya/ directory and run the following command:

      app install

    • If you install Avaya Aura® Device Services 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® Device Services application binary. For example:

      app install /root/aads-swonly-10.2.0.0.70/aads-10.2.0.0.70.bin

    The system displays the Avaya Aura® Device Services Installer dialog box.

    Important:

    Do not resize the SSH console while installing and configuring Avaya Aura® Device Services.

  4. When prompted, type the administrative user password.
  5. Optional If you want to enable the Utility Server, do the following:
    1. In the Initial Installation Configuration screen, select Utility Server.
    2. In the Utility Server menu, select Utility Server again and then select Yes.
    3. Select Return to Main Menu and press Enter.
    Important:

    • If you install a cluster, you must either enable the Utility Server on all nodes or leave it disabled on all nodes. You cannot enable the Utility Server on some cluster nodes and disable it on other nodes.

    • If you do not enable the Utility Server, you cannot generate configuration files for endpoints using the Dynamic Configuration service. For more information, see Administration of the Dynamic Configuration service in Administering Avaya Aura® Device Services.

  6. Optional If you want to enable OAuth, do the following:
    1. In the Initial Installation Configuration screen, select OAuth.
    2. In the OAuth menu, select OAuth again and then select Yes.
    3. Select Return to Main Menu and press Enter.

    OAuth is unavailable if you enabled FIPS mode.

  7. Optional If you want to enable IPv6 support, do the following:
    1. In the Initial Installation Configuration screen, select Enable IPv6.
    2. In the Enable IPv6 menu, select IPv6 support and then select Yes.
    3. Select Return to Main Menu and press Enter.
    Important:

    AWS, Microsoft Azure, and GCP software-only deployments do not support IPv6.

  8. In the Initial Installation Configuration screen, select Cluster Configuration and press Enter.
  9. In the Clustering screen, set Initial cluster node to n.
  10. In the Clustering screen, set Local node IP address to the IP address of the new Avaya Aura® Device Services node and then press Enter.
  11. In the Clustering screen, set Cluster seed node to the IP address of the seed node or the first cluster node and then press Enter.
  12. In Cassandra Datacenter name, configure a Cassandra datacenter for the node as follows:

    • To add the node to an existing datacenter, provide the name of one of the already existing datacenters on Avaya Aura® Device Services.

    • To add the node to a new datacenter, provide a name of your choice for that datacenter.

    • To add the node to the default dc1 datacenter, leave the field blank.

    Avaya Aura® Device Services logically groups nodes with the same Cassandra datacenter name and configures specific Cassandra replication policies for the members of the datacenter.

  13. In the Clustering screen, set User ID of product user on seed node, type the UID of the seed node, and then click Enter.
  14. Select Return to Main Menu and then press Enter.
  15. In the Initial Installation Configuration screen, select Front-end host, System Manager and Certificate Configuration and press Enter.
  16. In the Front-end host, System Manager and Certificate Configuration screen, set values for the following:

    • System Manger FQDN

    • System Manager version

    • System Manager HTTPS port

    • System Manager Enrollment Password

    • Local Front-end host

    • Keystore password

      Ensure that the keystore password is at least 8 characters long.

      Important:

      The values that you specify on this screen must match the values provided for the seed node except for the local front-end host.

  17. Do one of the following:

    • If you are planning to use System Manager for certificates, in Use System Manager for certificates, select Yes and proceed to step 17.

    • If you are planning to use certificates that are specific for your organization and signed by a third-party CA, in Use System Manager for certificates, select No and perform step 16.

  18. If you use certificates that are specific for your organization, do the following:
    1. For each of the REST, OAM, and NODE interface certificate configuration options, in Is the interface certificate in PKCS12 format?, select one of the following:

      • Yes, if your interface certificate has the PKCS12 format.

      • No, if your interface certificate has the PEM format.

    2. If you use identity certificates in the PKCS12 format, configure the following settings:

      • For each of the REST, OAM, and NODE interface certificate configuration options, in Interface PKCS12 file, enter the path to the identity.p12 file.

      • For each of the REST, OAM, and NODE interface certificate configuration options, in Interface PKCS file password, enter the password for the identity.p12 file.

        If you provide an incorrect password, Avaya Aura® Device Services displays a warning message. You cannot continue installing Avaya Aura® Device Services until you enter the correct password.

    3. If you use identity certificates in the PEM format, configure the following settings:

      • For each of the REST, OAM, and NODE interface certificate configuration options, in Interface PEM certificate file, enter the path to the identity certificate file.

      • For each of the REST, OAM, and NODE interface certificate configuration options, in Interface PEM key file, enter the path to the key file for the identity certificate.

    4. Select Signing authority certificate configuration.
    5. In Is the Signing Authority certificate in PKCS12 format?, select No.
    6. In Signing Authority PEM certificate file, enter the path to the cert-chain.pem certificate chain file.
  19. Select Return to Main Menu and then press Enter.
  20. In the Initial Installation Configuration screen, select Session Manager Configuration and press Enter.
  21. In the Session Manager Configuration screen, set values for the following parameters:

    • Session Manager Management IP

    • Session Manager Asset IP

  22. Select Return to Main Menu and then press Enter.
  23. Optional If your cluster uses Open LDAP, do the following:
    1. In the Initial Installation Configuration screen, select Onboard Open LDAP.
    2. Select Onboard Open LDAP again and then select Yes.
      Important:

      For Open LDAP parameters values, you must use the same values that you used while deploying the seed node. Otherwise, data replication between nodes might not work as expected.

    3. In Directory Manager, enter a name for the Open LDAP administrator.
    4. In Domain Name, provide the domain name of your company.
    5. In Administrator’s password, provide a password for the Open LDAP administrator.
    6. Select Return to Main Menu and press Enter.
  24. Select Continue and then press Enter.
  25. In the Configuration Summary screen, verify the values, select Accept and Continue and then press Enter.

    The installer performs pre-install checks.

  26. In the Results of configuration checks screen, select Continue and then press Enter.

    Avaya Aura® Device Services displays the End User License Agreement.

  27. Select Accept and then press Enter.

    Avaya Aura® Device Services displays the progress of the tasks in the Running Installer Script window. Avaya Aura® Device Services installs the required RPMs, downloads certificates from System Manager, creates database schema, and performs the required initial configuration. After successful installation, Avaya Aura® Device Services displays the Results of Installation Script screen.

  28. Select Continue and then press Enter.
  29. In the Main Menu screen, select Clustering Configuration and then press Enter.
  30. In the Clustering Configuration screen, select Virtual IP Configuration and then press Enter.
    Important:

    If you are using an external load balancer, do not configure a virtual IP address.

  31. In the Virtual IP Configuration screen, set values for the following parameters:
    1. Set Enable virtual IP to y.
    2. Set Virtual IP address to the virtual IPv4 address that you want to use.
    3. If you enabled IPv6, set Virtual IPv6 address to the virtual IPv6 address you want to use.
    4. Set Virtual IP interface to the required value.
    5. Set Virtual IP master node to n.
    6. Set Virtual IP router ID to the required value.
    7. Set Virtual IP authentication password to the password you set on the seed node.
  32. Select Apply and then press Enter.
  33. In the Clustering Configuration screen, select Return to Main Menu and then press Enter
  34. If you chose to enable the Utility Server, in the Main menu screen, select Utility Server Configuration and press Enter.

    If you do not need the Utility Server, continue from step 36. Steps from 32 to 35 are for the Utility Server configuration.

    Important:

    If you are deploying a cluster, you must configure cluster settings in Clustering Configuration before configuring Utility Server settings. The cluster configuration steps are described earlier in this procedure.

  35. In the Utility Server Configuration screen, update the following parameters:
    1. Set Utility Server VIP to a virtual IPv4 address that you want to use for the Utility Server.

      You cannot use the Avaya Aura® Device Services cluster virtual IP address as the Utility Server virtual IP address.

    2. If you enabled IPv6, set Utility Server Ipv6 VIP to a virtual IPv6 address that you want to use for the Utility Server.
    3. Set Utility Server FQDN to a FQDN that you want to use for the Utility Server.

      In AWS cluster deployments, you must use the following scheme for a non-seed node Utility Server FQDN:

      <Utility Server Host Name><number>.<Domain Name>

      In this scheme, <number> is the number of a node reduced by one. For example, if the cluster has three nodes, the Utility Server host name is aads716-us, and the domain name is avaya.in, then the Utility Server FQDN is aads716-us1.avaya.in for the second node, or the first non-seed node, and aads716-us2.avaya.in for the third node, or the second non-seed node in the cluster. The Utility Server FQDN of the seed node is aads716–us0.avaya.in.

      For more information about Utility Server VIP and FQDNs in AWS deployments, see Utility Server VIP and FQDN in AWS cluster deployments.

    4. Set System Manager Enrollment Password to the System Manager enrollment password.

      The System Manager enrollment password is configured in the System Manager console under Home > Services > Security > Certificates > Enrollment Password.

    When a Utility Server FQDN or VIP is updated on a node, the changes are propagated to all other nodes in the cluster. However, you still must configure Utility Server settings on each node in order to set the firewall redirection rules and certificate configuration on each node.

  36. Select Apply and press Enter.
  37. Select Continue and press Enter.
  38. Optional In the Main Menu screen, select Add a Certificate to the TrustStore and then press Enter.

    This step is optional if you use a certificate different from the System Manager certificate.

  39. Select Continue and then press Enter.

    Avaya Aura® Device Services prompts you to restart services.

  40. Select Yes and then press Enter.
  41. In the Results of service AADS restart screen, select Continue and then press Enter.

    Avaya Aura® Device Services service installation is completed.

Next Steps

  • After all additional nodes are installed, configure the SSH/RSA Public and Private keys on the seed node.

  • If you enabled OAuth, do the following after all additional nodes are installed:

  • If you installed Open LDAP, after all additional nodes are installed and configured, enable Open LDAP replication. For more information, see Enabling Open LDAP replication.