Upgrading the Avaya Aura Device Services application

Last Updated : Jun 08, 2026 |

About this task

Use this procedure to upgrade the Avaya Aura® Device Services application layers on the existing virtual machines.

Note:

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

Before you begin

  • Back up your Avaya Aura® Device Services Release 10.1.1.x system.

  • Download the system layer update file and the latest binary installer file.

  • Upgrade to the latest system layer release on all nodes.

    Important:

    You must apply the system layer update to all nodes in the cluster before starting the upgrade process. Otherwise, the upgrade will fail.

  • Determine whether you need to enable the Utility Server.

Procedure

In a cluster environment, perform steps 1 to 12 on the seed node first, then on the backup node, and then on all other non-seed nodes in the cluster.

  1. Log in to a node as an administrator using an SSH connection.
  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_UPGRADE
  3. Optional To enable IPv6 support for ESXi deployments, run the following command to enable IPv6 at the system layer: 
    sys ipv6config set
    Tip:

    For general information about the sys ipv6config command, run the following command:

    sys ipv6config -h
    Important:

    AWS deployments do not support IPv6.

  4. Run the following command to remove the inactive Avaya Aura® Device Services version: 
    app removeinactive
  5. Transfer the binary file to the administrator home folder on Avaya Aura® Device Services by using a file transfer tool of your choice.
  6. Run the following command to make the file executable: 
    chmod 755 aads-<version>.bin
    For example: 
    chmod 755 aads-10.1.1.0.16.bin
  7. Run the following command to start the upgrade: 
    app upgrade aads-<version>.bin

    For example:

    app upgrade aads-10.1.1.0.16.bin
  8. When the system prompts you to enable the Utility Server, do one of the following:

    • If want to enable the Utility Server, select Yes.

    • If you do not want to enable the Utility Server, select No.

    Important:

    You must either enable the Utility Server on all nodes or disable it on all nodes. You cannot enable the Utility Server on some cluster nodes and disable it on other nodes.

  9. When the system prompts you to enable onboard Open LDAP, do one of the following:

    • If you want to enable onboard Open LDAP, select Yes.

    • If you do not want to enable onboard Open LDAP, select No.

    Note:

    If you enable onboard Open LDAP when upgrading, you will not be able to roll back to the previously installed release.

  10. When the system prompts you to enable OAuth, do one of the following:

    • If want to enable OAuth, select Yes.

    • If you do not want to enable OAuth, select No.

  11. Optional When the system prompts you to enable IPv6, do the following:

    • If you want to enable IPv6, select Yes and then provide virtual IPv6 addresses of your choice for Avaya Aura® Device Services and the Utility Server, if it is enabled.

    • If you do not want to enable IPv6, select No.

    This step is only applicable if you enabled IPv6 at the system layer in step 3.

  12. Follow the system prompts to complete the upgrade procedure.
  13. In a cluster environment, repeat the steps above on the backup node and then on all other non-seed cluster nodes.
  14. If you enabled OAuth, on the seed node, configure Keycloak settings as described in Configuring Keycloak settings in Deploying Avaya Aura® Device Services.
  15. If you enabled IPv6, on all nodes, configure the virtual IPv6 address and Utility Server virtual IPv6 address using the Avaya Aura® Device Services configuration utility.
  16. If you use onboard Open LDAP, enable Open LDAP replication on all nodes in the cluster.

    For more information, see Enabling Open LDAP replication.

  17. Log in to the seed node as an administrative user using an SSH connection.
  18. Run the svc aads restart command to restart Avaya Aura® Device Services.
  19. In a cluster environment, repeat steps 17 and 18 on all other cluster nodes.
  20. If you use Avaya Aura® Device Services in an Avaya Aura® environment, verify that DRS replication is working for all nodes on System Manager.

    For more information, see Checking for DRS synchronization.

  21. From the seed node, run the following commands to generate personal information metadata: 
    cdto misc
sudo ./clearPhoneNumberLastSync.sh
  22. From the Avaya Aura® Device Services web administration portal, perform synchronization with LDAP.

    For more information, see Setting up user synchronization with the LDAP server.

Next Steps

  • If you enabled the Utility Server and you need to migrate data from a legacy 7.1 Utility Services machine, complete Migrating Utility Server data.

  • If you want to use Advanced Intrusion Detection Environment (AIDE), create a baseline database as described in AIDE tool management.