Upgrading Avaya Breeze platform nodes and Avaya Oceana snap-ins

Last Updated : Mar 24, 2025 |

About this task

Use this procedure to upgrade the existing Avaya Breeze® platform nodes by running the automated upgrade script.

The automated script does the following:

  • Uninstalls the older versions of all Avaya Oceana® snap-ins from clusters.

  • Deletes Avaya Oceana® snap-ins from System Manager.

  • Upgrades all Avaya Breeze® platform nodes.

  • Loads the latest versions of all Avaya Oceana® snap-ins in System Manager.

  • Installs Avaya Oceana® snap-ins to their relevant clusters.

Important:

Ensure that you deploy all Avaya Oceana® nodes on the same version of VMware ESXi.

Before you begin

  • Download the Oceana<Release_number>.zip artifacts file from PLDS.

  • Take a snapshot of System Manager.

    You can use the snapshot to recover the previous working state of System Manager. A snapshot is the only recovery mechanism to recover from catastrophic failures.

    After the successful migration or upgrade, you must remove the snapshot. System Manager and Avaya Oceana® do not support snapshots in production.

  • Take a snapshot of the existing Avaya Breeze® platform nodes.

    You can use the snapshot to recover the previous working state of the Avaya Breeze® platform to reattempt the automated or manual upgrade. A snapshot is the only recovery mechanism to recover from catastrophic failures. For information about how to take a snapshot, see Upgrading Avaya Breeze® platform.

    After the successful upgrade and post upgrade testing in production for a limited period, you must remove the snapshot. Avaya Breeze® platform and Avaya Oceana® do not support snapshots in production.

    Important:

    Remove all snapshots before placing Avaya Oceana® in production.

Procedure

  1. Copy the Oceana<Release_number>.zip artifacts file to the /swlibrary location on System Manager.
  2. Log in to the new System Manager virtual machine using an SSH client application, such as PuTTy.
  3. Run the following command as a cust user:

    upgradeSolution /swlibrary/Oceana<Release_number>.zip –cg <N> <Configuration Package> <OPTION>

    In this command:

    • Replace <N> with the Cluster Group number of the Oceana nodes being upgraded.

      There are two cluster group numbers for DR solutions. Ensure that you choose the correct cluster group number when using this command.

    • Replace <Configuration Package> with the configuration type to match with the deployment type.

      For example, Combined-4500 for Oceana_Large.

    • Replace <OPTION> with space-separated values depending on the required configuration to include non-mandatory snap-ins.

      For example, Chat GenericChannel Social AMC.

    For detailed information about these parameters, see Avaya Breeze platform upgrade script parameters.

    Important:

    • The current version of the command provides validation of these parameters.

    • Ensure that you carefully type all option values in the upgradeSolution command.

    • During the upgrade process, the script tries to determine the names of the current Avaya Oceana® Clusters and the current snap-ins installed on them. The script prompts for a confirmation if each cluster name corresponds to a specific cluster. For example, "Is Cluster 1 name Cluster1_CC (y/n)". If the prompted cluster name is incorrect and you press n, the script prompts again until you get the correct cluster name and press y.

      For these questions, the clusters refer to the naming conventions mentioned in Deploying Avaya Oceana®. For example, Cluster 1 refers to Common Cluster, Cluster 2 refers to Unified Agent Cluster, Cluster 3 refers to OCP Cluster, Cluster 4 refers to CoBrowse Cluster, and Cluster 5 refers to Zang and CRM cluster.

    • You can view the upgrade logs in the solution-upgrade.log file in the /var/log/Avaya folder on System Manager.