Preparing for an AVP upgrade

Last Updated : Jun 10, 2026 |

About this task

Use this procedure to download the latest installation files required for the upgrade and to collect data from the existing Avaya Aura® Device Services servers to upgrade to the new Avaya Aura® Device Services release.

Perform the upgrade preparation procedure before the maintenance window so you can start the upgrade as soon as the maintenance window starts. This procedure does not alter the system and Avaya Aura® Device Services remains available.

Before you begin

Determine the keystore password you want to use when installing Avaya Aura® Device Services Release 10.2.x.

Procedure

  1. Record the currently installed version of the Avaya Aura® Device Services application.

    To upgrade to Release , you must have Avaya Aura® Device Services Release 10.1.1.x.

  2. Back up the cluster as described in Backing up Avaya Aura Device Services.

    When you create backup files for cluster nodes, you can specify a name for each backup file to keep the backup files organized. For example, if the server host name is server1.example.com, then the app backup —t —d /home/admin recover command creates the /home/admin/recover_server1.tar backup file.

  3. Download the application installer file and the OVA file of the same version that is used in the currently installed release.

    You can use these files in case the upgrade is aborted and you need to revert Avaya Aura® Device Services back to the currently installed version.

  4. Download the latest versions of the following files:

    • System layer update file.

    • Application installer file.

    • OVA file.

    For more information about system layer updates, see Preparing for an AVP upgrade.

  5. Log in to Avaya Aura® Device Services as an administrative user using an SSH connection.
  6. Run the following command to collect the current system logs: 
    app collectlogs collect

    Avaya Aura® Device Services creates a .zip file containing the logs in the /var/log/Avaya/collected-logs directory.

    Support teams can resolve issues that might occur on the new system by comparing the collected logs to the logs on the new system.

  7. Do the following to record server information and then save the output in a safe location:
    1. To obtain the fully qualified host name, run the following command: 
      hostname -f
    2. To obtain the IP address and the network mask, run the following command: 
      ifconfig -a | grep inet | grep -v 127.0.0.1
    3. To obtain the IP address of the default gateway, run the following command: 
      netstat -nrv | grep '^0.0.0.0'
    4. To obtain the DNS search list and DNS server IP address, run the following command: 
      cat /etc/resolv.conf
    5. To obtain the NTP server IP address, run the following command: 
      cat /etc/ntp.conf | grep "^server"
    6. Log in as the administrator and run the following commands to display the user name and primary group for the administrative account: 
      id --user --name
id --group --name
    7. If you want to use the same keystore password, obtain the existing keystore password by referencing notes from the original installation.

      If you do not want to use the same keystore password, record a new keystore password.

    8. Record the current System Manager enrollment password by referencing notes from the original installation.
  8. Copy the following files to an off-board storage location using a file transfer program, such as SFTP or SCP:

    • The .zip archive containing the logs.

    • Any other desired content from the /home directory.

  9. For each virtual machine in the cluster, record the network to which the virtual machine is attached, and use the original installation notes to record the OVA profile used while deploying the original OVA.
  10. Repeat steps 5 to 9 for all remaining nodes in the cluster.

Next Steps

Upgrade the existing AVP virtual machines.