Check the prerequisites and post-upgrade tasks for snap-ins before proceeding with the upgrade.

Refer to the snap-in documentation.

Obtain information for the existing Avaya Breeze® platform servers.

Before upgrading Avaya Breeze® platform, upgrade the following in this order as needed:

See Upgrading Avaya Aura® System Manager and Upgrading Avaya Aura® Session Manager.

If only upgrading the Avaya Breeze® platform Element Manager, use the upgradeSolution script. Refer to Deploying Avaya Breeze® platform.

Upgrade Avaya Aura® Media Server.

See Deploying and Updating Avaya Aura® Media Server Appliance.

Enroll Avaya Aura® Media Server on System Manager.

See System Manager enrollment section in Implementing and Administering Avaya Aura® Media Server.

If you are using Avaya Aura® Media Server but not Engagement Assistant, remove the obsolete Avaya Aura® Media Server configuration.

See Removing obsolete Avaya Aura Media Server configuration.

Administer Avaya Aura® Media Server for REST.

See Administering Avaya Aura Media Server for REST

Assign Avaya Aura® Media Server for use with Avaya Breeze® platform.

See Assigning Avaya Aura Media Server for use with Avaya Breeze platform

If you are using cluster database and upgrading from pre-R 3.9, take a databse backup.

This is a precaution in case it becomes necessary to roll back to the pre-R3.9 release.

See Backing up a cluster database.

If using a cluster database on Avaya Breeze® platform 3.8.x or earlier, load and install the clusterDBMigrationService-3.9.0.0 service.

If you are using cluster database on Avaya Breeze® platform 3.9.x or later skip this step.

This service is pre-loaded on the Avaya Breeze® platform 3.9.x EM and versioned as a 3.9.x snap-in; however, the snap-in is compatible and intended to be installed on 3.8.1.1. and earlier Avaya Breeze® platform clusters.

See Installing the clusterDBMigration service.

Download the Avaya Breeze® platform OVA and patch file (if required) from PLDS.

See Downloading software from PLDS.

Verify that the enrollment password has not expired.

See Verifying the enrollment password status.

Change the state of the cluster you are upgrading to Deny New Service.

See Setting the cluster to Deny New Service status.

For pre-R 3.9.0

If the cluster database is enabled, take a backup which will use the clusterDBMigrationService-3.9.0.0 to update the schema for use with 3.9.

If you are using 3.9.0 or higher, take the cluster database backup.

See Backing up a cluster database.

Check the cluster Activity field is 0.

See Verifying there is no server activity.

Uninstall the Analytics Collector Snap-in and Engagement Call Control from the cluster.

See Uninstalling and deleting snap-ins

Remove any other solution snap-ins if required.

Refer to the snap-in documentation. for guidance on snap-ins that must be removed before upgrading.

Remove all Avaya Breeze® platform servers from the cluster.

See Removing the existing servers from the cluster

Shut down all the existing servers in the cluster.

See Shutting down the existing servers.

Deploy new servers using the new release OVA. Breeze 3.9 requires an additional 2GB of RAM and 5GB of disk per deployment profile. The presented profiles reflect this information.

See Deploying the replacement upgrade release servers.

Disable the secure grid if enabled

See Disabling the secure grid.

Upgrade the mandatory snap-ins and connector snap-ins, including the Authorization service if required by your solution.

See your snap-in documentation.

You must configure all customized resources (cpu/memorydisk sizes) again after you install the Avaya Breeze® platform OVA.

If you use the cluster database, ensure that the disk size configuration is appropriate for the snap-in that uses the database.

Configure the virtual machine automatic startup settings.

See Configure the new server automatic startup settings.

Change the customer password on first login.

See .Changing the customer password on first login.

Create multiple privileged user accounts.

See Creating multiple privileged user accounts.

Install the patch file if required.

See Installing the upgrade patch if required.

Set the preferred version for each snap-in.

See Setting preferred snap-in version.

Remove the clusterDBMigrationService-3.9.0.0 service.

See Removing the clusterDBMigrationService.

Edit the cluster and clear the Pre-3.8.1 Cluster cluster attribute if set.

See Editing the cluster attributes.

Add the new servers to the cluster.

See Adding the new servers to the cluster

Select Enable Database Auto Switchover (ElementsAvaya Breeze® Cluster Administration).

This is only required for multi-node clusters with a cluster database.

Optional: Enable Secure Grid.

See Enabling the secure grid.

Verify data replication between System Manager and Avaya Breeze® platform.

See Verifying replication status.

Run Avaya Breeze® platform maintenance tests for each server in the cluster.

See Running maintenance tests. Resolve errors before proceeding.

Verify the status of each of the new servers.

See Verifying the status of the new servers.

Install new snap-ins.

See Installing new and upgraded snap-ins.

If using a cluster database, restore the database.

See Restoring the cluster database.

For a multi-node cluster, reboot the cluster.

See Rebooting a cluster.

Add trust certificates.

For information, see Adding a trusted certificate to all Avaya Breeze platform servers in a cluster.

Set the cluster state back to Accept New Service.

See Setting the cluster back to Accepting New Service status.

Verify the Avaya Breeze® platform SIP entity link with Session Manager.

See Verifying the Avaya Breeze platform entity link connection.

Test Avaya Breeze® platform snap-ins to verify that they are functioning correctly.

–

After a successful upgrade, delete the previous Avaya Breeze® platform server images.

–

Configure System Manager to receive Avaya Breeze® platform alarms.

See the SNMP support information in Maintaining and Troubleshooting Avaya Breeze® platform.