Find answers to your technical questions and learn how to use our products
Search suggestions:
Find answers to your technical questions and learn how to use our products
Search suggestions:
|
No.
|
Task
|
Notes
|
|---|---|---|
|
1
|
Obtain information for the existing Avaya Breeze® platform servers.
|
|
|
2
|
Before upgrading Avaya Breeze® platform, upgrade the following in this order as needed:
1. System Manager 10.1.3.2 or later,
if you are going migrate to Breeze 3.9.0.2.
2. System Manager 10.1.3.6 or later,
if you are going migrate to Breeze 3.9.0.3.
3. ACM 9.1.0.1.
|
Refer to Upgrading Avaya Aura® System Manager documentation available on the Avaya Support website at https://support.avaya.com.
|
|
3
|
Change the state of the cluster you are upgrading to Deny New Service.
|
|
|
4
|
Apply Breeze EM 3.9.0.x patch on SMGR.
|
See Running the upgradeSolution script for System Manager. Refer to Deploying Avaya Breeze® platform documentation available on the Avaya Support website at https://support.avaya.com.
|
|
5
|
Take cluster database backup.
|
|
|
6
|
Remove all Avaya Breeze® platform servers from the cluster.
|
|
|
7
|
Shut down all the existing servers in the cluster.
|
|
|
8
|
Deploy new servers using the new release OVA.
|
|
|
9
|
You must configure all customized resources (cpu/memory/disk sizes) again after you install the Avaya Breeze® platform OVA.
|
Breeze 3.9.0.0/3.9.0.1/3.9.0.2/3.9.0.3 require an additional 2GB of memory per profile due to running with RHEL 8. If you have not updated your Breeze since 3.9.0.0/3.9.0.1, in addition to this you are also adding 5 GB for disk. All profiles have been increased to support this additional memory requirement and disk requirement.
|
|
10
|
Power on Breeze nodes.
|
Power on one-by-one and ensure initTM command completed before power on the next one. By default, the initTM command is ran in the first time machine powers on. If there is an error or having incorrect server information, re-run initTM command and correct information.
|
|
11
|
Change the customer password on first login.
|
|
|
12
|
Verify data replication between System Manager and Avaya Breeze® platform.
|
|
|
13
|
Load the latest versions of Breeze services version 3.9.0.x: PacketbeatService and MetricbeatService in System Manager.
|
|
|
14
|
Swap Breeze 3.9.0.x services version.
|
|
|
15
|
Delete all old services from System Manager.
|
|
|
16
|
Edit the cluster and clear the Pre-3.8.1 Cluster cluster attribute if set.
|
|
|
17
|
Add the new servers to the cluster.
|
|
|
18
|
Verify the status of each of the new servers.
|
|
|
19
|
Select Enable Database Auto Switchover and Is Load Balancer enabled? (Elements > Avaya Breeze® > Cluster Administration).
|
This is only required for multi-node clusters with a cluster database.
|
|
20
|
Restore the database.
|
|
|
21
|
Import LDAP certificate to Breeze nodes.
|
|
|
22
|
Configure common certificate.
|
|
|
23
|
Re-check Avaya Workspaces for Call Center Elite services attributes.
|
|
|
24
|
For a multi-node cluster, reboot the cluster.
|
|
|
25
|
Set the cluster state back to Accept New Service.
|