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.2 or later, if you are going migrate to Breeze 3.9.0.0.
2. System Manager 10.1.3.2 or later, if you are going migrate to Breeze 3.9.0.2.
3. 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.
|
See Upgrading Avaya Aura® System Manager documentation available on the Avaya Support website at https://support.avaya.com.
|
|
3
|
Change the state of the cluster DC1 and DC2 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
|
Load and install the clusterDBMigrationService 3.9.0.x on cluster DC1
|
|
|
6
|
If the cluster database is enabled, take a backup which will use the clusterDBMigrationService-3.9.0.x to update the schema for use with 3.9.0.x.
|
|
|
7
|
Deploy new Breeze Nodes using the new release OVA for both DC1 and DC2.
|
|
|
8
|
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.
|
|
9
|
Remove all Avaya Breeze® platform servers from the cluster DC1.
|
|
|
10
|
Wait for step 9 to complete and remove all Avaya Breeze® platform servers from the cluster DC2
|
|
|
11
|
Shut down all the existing Breeze Nodes servers in the cluster DC1.
|
|
|
12
|
Shut down all the existing Breeze Nodes servers in the cluster DC2.
|
|
|
13
|
Power on new 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.
|
|
14
|
Change the customer password on first login.
|
|
|
15
|
Verify data replication between System Manager and Avaya Breeze® platform.
|
|
|
16
|
Remove the clusterDBMigrationService 3.9.0.x on Cluster DC1
|
|
|
17
|
Un-assign all old services from the clusters on DC1 and DC2.
|
|
|
18
|
Delete all old services from System Manager.
|
|
|
19
|
Load the latest versions of Avaya Workspaces for Call Center Elite services in System Manager.
|
|
|
20
|
Assign latest versions of all services to the cluster DC1 and DC2.
|
|
|
21
|
Edit the cluster and clear the Pre-3.8.1 Cluster cluster attribute if set.
|
|
|
22
|
Re-configure Avaya Workspaces for Call Center Elite services attributes for Geo on both DC1 and DC2.
|
|
|
23
|
Add the new Breeze nodes servers to the cluster DC1.
|
|
|
24
|
Add the new Breeze nodes servers to the cluster DC2.
|
|
|
25
|
Verify the status of each of the new servers.
|
|
|
26
|
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.
|
|
27
|
Restore UCA database 3.8.1.1 on Cluster DC1.
|
|
|
28
|
Import LDAP certificate to Breeze nodes DC1 and DC2.
|
|
|
29
|
Configure common certificate.
|
|
|
30
|
Set cluster activity status in DC2 to Standby
|
Refer Configuring the cluster activity status in Data Center 2 in the Avaya Workspaces for Call Center Elite Disaster Recovery guide.
|
|
31
|
Reboot the cluster DC1.
|
|
|
32
|
Wait to Cluster DC1 comes up, Restore UCA database 3.8.1.1 on Cluster DC2.
|
|
|
33
|
Reboot the cluster DC2
|
|
|
34
|
Set the cluster state back to Accept New Service on DC1.
Note:
Still keep DC2 in Deny state
|
|
|
35
|
Check data replication between DC1 and DC2
|
Refer Verifying UCA data replication from DC1 to DC2 in the Avaya Workspaces for Call Center Elite Disaster Recovery guide.
|