Avaya Breeze platform deployment checklist

Last Updated : Nov 24, 2025 |

The following table lists the procedures required to deploy Avaya Breeze® platform.

#

Action

Reference/Notes

1.

Record information that you will require for the deployment.

See Key customer configuration information

2.

Install or upgrade System Manager if required and download the latest System Manager hot fix.

You can use System Manager Release 10.1.2 or later. See Avaya Breeze platform compatibility

Note:

Avaya Breeze® platform 3.9 and later releases require Avaya Aura® System Manager 10.1.2 or later, with higher Breeze patch versions requiring later System Manager updates.

Refer to the corresponding Breeze Release Notes for version-specific System Manager requirements.

3.

Download Avaya Breeze® platform software and license files from PLDS.

Download patch files (if required) from PLDS.

See Downloading software from PLDS

4.

Verify that the enrollment password is not expired.

See Verifying the enrollment password status

5.

Deploy the Avaya Breeze® platform OVA.

Choose the procedure that corresponds to your OVA deployment method.

The Avaya Breeze® platform management FQDN assigned to the management network interface must be registered in DNS. For assistance, contact Avaya Support.

Important:

  • Avoid installing multiple OVAs on the same LAN simultaneously unless you are using VCenter or Solution Deployment Manager for the installation. If you install an OVA with vSphere, it boots with a static, fixed IP address associated with eth0. If you load a second OVA on the same network before running CEnetSetup on the first, an address conflict occurs. One or both VMs will not be configurable.

  • The Avaya Breeze® platform node where Engagement Designer is installed and System Manager must be in the same domain.

6.

Change the customer password on first login.

See Changing the customer password on first login

7.

Configure virtual machine automatic startup settings.

See Configure the new server automatic startup settings

8.

Install the patch file.

See Patching the Avaya Breeze platform

9.

Create multiple privileged user accounts (optional).

See Creating multiple privileged user accounts

10.

Install the Avaya Breeze® platform license file.

See Installing the Avaya Breeze platform license file

11.

Administer the SIP entity.

See Administering an Avaya Breeze platform SIP Entity

12.

Administer the SIP entity link.

See Administering the Avaya Breeze platform Entity Link

13.

Enable implicit user applications for SIP users.

See Enabling implicit users applications for SIP users

14.

Administer the Avaya Breeze® platform instance.

See Administering an Avaya Breeze platform instance

15.

Verify the entity link connection.

See Verifying the Avaya Breeze platform entity link connection

16.

Verify the replication status.

See Verifying replication status

17.

Verify the management link.

See Verifying the management link

18.

Assign the server to an Avaya Breeze® platform cluster. If one does not already exist for this server, create the cluster.

See Creating a new cluster

19.

Add a trust certificate to all servers.

See Adding a trusted certificate to all Avaya Breeze platform servers in a cluster

20.

Add individual trust certificates.

See Adding trusted CA certificates

21.

Replace an identity certificate.

See Replacing an identity certificate

22.

Change the state of the server to accept new service.

See Accepting new service

23.

Configure the alarming setup. Configure System Manager to receive Avaya Breeze® platform alarms.

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

24.

If you have cluster databases enabled, set up scheduled backups for the cluster database.

See Administering Avaya Breeze® platform.

25.

For Communication Manager, route inbound ISDN calls.

See Routing inbound ISDN calls

26.

For Communication Manager, route outbound ISDN calls.

See Routing outbound ISDN calls

27.

Enable FIPS (optional).

FIPS is a cryptographic security standard. If FIPS is not already enabled by default for your deployment, you can enable it manually. For more information, see Enabling FIPS.

If you want to disable FIPS when you no longer need it, see Disabling FIPS.
Related information
Deployment process checklists