Packaged CCE 11.5 to 11.6 Upgrade
Migrate and Upgrade Side A
Before you begin, check the following to confirm that call activity has ended on Side A:
-
In Unified CVP Diagnostic Portal, check that no Side A ports are in use.
-
In the Unified Communications Manager RTMT tool, check that phones have migrated to Side B.
For best results, place upgrade media ISOs on local data stores. Make sure to remove them when the upgrade is complete.
Step |
Task |
||
---|---|---|---|
Upgrade the Side A Unified CVP VMs |
|||
1. |
Upgrade the Unified CVP OAMP Server. |
||
2. |
Upgrade Unified CVP Server 1A. |
||
3. |
Obtain and transfer the license now if you don't have an external Unified CVP Reporting Server. For an external Unified CVP Reporting Server, you can transfer the upgrade license to all Unified CVP components after you upgrade the external server. See Obtain and Transfer the Upgrade License for Unified CVP. |
||
4. |
Transfer scripts and media files to the gateways not currently being used by Side B. If all gateways are being used, perform this step during the cutover to Side B. |
||
Upgrade Side A Cisco Voice Gateway IOS Version if needed |
|||
5. |
Upgrade the Side A Cisco Voice Gateway IOS version to the minimum required by the upgraded Packaged CCE release (or later). See Upgrade Cisco Voice Gateway IOS Version. See the Cisco Packaged CCE Software Compatibility Matrix at https://www.cisco.com/c/en/us/support/customer-collaboration/packaged-contact-center-enterprise/products-device-support-tables-list.html for IOS support information. |
||
Upgrade External Unified CVP Reporting Server (if used) |
|||
6. |
Complete the Unified CVP Reporting Server preupgrade tasks. |
||
7. |
Unload the data from the Unified CVP Reporting Server. |
||
8. |
Uninstall the Unified CVP Reporting Server. See Uninstall the Unified CVP Component from the Reporting Server VM. |
||
9. |
Install the External Unified CVP Reporting Server. |
||
10. |
Load data on the Unified CVP Reporting Server. |
||
11. |
Save and deploy the Unified CVP Reporting Server in the Operations Console. |
||
12. |
Transfer the upgrade license. See Obtain and Transfer the Upgrade License for Unified CVP. |
||
Upgrade the Side A Finesse and Unified Intelligence Center VMs |
|||
13. |
Upgrade the Finesse Primary node. See either: |
||
14. |
Upgrade the Unified Intelligence Center Publisher node. See either:
|
||
Prepare for Side A Migration to Packaged CCE 2000 Agent Rogger Deployment |
|||
15. |
Back up and export the Logger database and the Outbound Option (if used) pccebaA database. See Back Up Database. |
||
16. |
Back up and export your network configuration. |
||
17. |
Run Windows updates. See Run Windows Updates. |
||
Convert the Side A Unified CCE Data Server and Unified CCE Call Server |
|||
18. |
Run the Unified CCE Release 11.6(1) installer on the Side A Unified CCE Rogger. See Install Cisco Unified Contact Center Enterprise Release 11.6(1). |
||
19. |
Disable configuration changes on the Unified CCE Rogger. Change the following registry key to 1: HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\ICM\<instance name>\RouterA\Router\CurrentVersion\Configuration\Global\DBMaintenance |
||
20. |
Run the Unified CCE Release 11.6(1) installer on the Side A Unified CCE AW-HDS-DDS. See Install Cisco Unified Contact Center Enterprise Release 11.6(1). |
||
21. |
Run the Unified CCE 11.6(1) installer on the Side A PG. See Install Cisco Unified Contact Center Enterprise Release 11.6(1). |
||
Optional: Upgrade the External HDS associated with Side A (if used) |
|||
22. |
Run the Unified CCE Release 11.6(1) installer the External HDS associated with Side A. See Install Cisco Unified Contact Center Enterprise Release 11.6(1). |
||
Optional: Install language pack |
|||
23. |
Install the language pack on the Side A Unified CCE Rogger, AW-HDS-DDS (former Data Server), PG (former Call Server), and External HDS associated with Side A (if used). |
||
Upgrade the Side A Unified Communications Manager Publisher and Subscriber 1 |
|||
24. |
Upgrade the Side A Unified Communications Manager Publisher. See either: |
||
25. |
Upgrade the Side A Unified Communications Manager Subscriber 1. See either:
|
||
26. |
Upgrade the Unified Communications Manager License. |
||
27. |
Upgrade JTAPI on the Side A PG.
|
Migrate and Upgrade Side B
For best results, place the upgrade media ISOs on local data stores. Make sure to remove them when the upgrade is complete.
Step |
Task |
||
---|---|---|---|
Start the Side B Unified CVP components |
|||
1. |
Start Unified CVP Server 1B and then start the Unified CVP Reporting Server.
|
||
Upgrade the Side B Unified CVP Servers |
|||
2. |
Upgrade Unified CVP Server 1B. |
||
3. |
Obtain and transfer the license now if you don't have an on-box Unified CVP Reporting Server. If you have an on-box Unified CVP Reporting Server, you can transfer the upgrade license to all Unified CVP components after you upgrade the Unified CVP Reporting Server. See Obtain and Transfer the Upgrade License for Unified CVP. |
||
Upgrade the on-box Unified CVP Reporting Server (if used) |
|||
4. |
Complete the Unified CVP Reporting Server preupgrade tasks. |
||
5. |
Unload the data from the Unified CVP Reporting Server. |
||
6. |
Uninstall the Unified CVP Reporting Server. See Uninstall the Unified CVP Component from the Reporting Server VM. |
||
7. |
Install the Unified CVP Reporting Server. |
||
8. |
Load data on the Unified CVP Reporting Server. |
||
9. |
Save and deploy the Unified CVP Reporting Server in the Operations Console. |
||
10. |
Transfer the upgrade license. See Obtain and Transfer the Upgrade License for Unified CVP. |
||
Upgrade Side B Cisco Voice Gateway IOS Version if needed |
|||
11. |
Upgrade the Side B Cisco Voice Gateway IOS version to the minimum required by the upgraded Packaged CCE release (or later). See Upgrade Cisco Voice Gateway IOS Version. See the Cisco Packaged CCE Software Compatibility Matrix at https://www.cisco.com/c/en/us/support/customer-collaboration/packaged-contact-center-enterprise/products-device-support-tables-list.html for IOS support information. |
||
Upgrade the Side B Finesse and Unified Intelligence Center VMs |
|||
12. |
Power on the Finesse Secondary node VM in the vSphere client. |
||
13. |
Upgrade the Finesse Secondary node. See either: |
||
14. |
Power on the Unified Intelligence Center Subscriber VM in the vSphere client. |
||
15. |
Upgrade the Unified Intelligence Center Subscriber. See either:
|
||
Prepare for Side B Migration to Packaged CCE 2000 Agent Rogger Deployment |
|||
16. |
Back up and export the Side B SQL database. See Back Up Database. |
||
Convert the Side B Unified CCE Data Server and Unified CCE Call Server |
|||
17. |
Run the Unified CCE 11.6(1) installer on the Side B Unified CCE Rogger to upgrade to Release 11.6(1). See Install Cisco Unified Contact Center Enterprise Release 11.6(1). |
||
18. |
Disable configuration changes on the Side B Unified CCE Rogger. Change the following registry key to 1: HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\ICM\<instance name>\RouterB\Router\CurrentVersion\Configuration\Global\DBMaintenance |
||
19. |
Run the Unified CCE 11.6(1) installer on the Side B Unified CCE AW-HDS-DDS to upgrade to Release 11.6(1). See Install Cisco Unified Contact Center Enterprise Release 11.6(1). |
||
20. |
Run the Unified CCE 11.6(1) installer on the Side B PG to upgrade to Release 11.6(1). See Install Cisco Unified Contact Center Enterprise Release 11.6(1). |
||
Optional: Upgrade the External HDS associated with Side B (if used) |
|||
21. |
Run the Unified CCE 11.6(1) installer on the External HDS associated with Side B to upgrade to Release 11.6(1). See Install Cisco Unified Contact Center Enterprise Release 11.6(1). |
||
Optional: Install language pack |
|||
22. |
Install the language pack on the Side B Unified CCE Rogger, AW-HDS-DDS, PG (formerly Call Server), and External HDS (if used). |
||
Upgrade Side B Unified Communications Manager Subscriber 2 |
|||
23. |
Power on the Unified Communications Manager Subscriber 2 VM in the vSphere client. |
||
24. |
Upgrade the Side B Unified Communications Manager Subscriber 2. See either: |
||
25. |
Upgrade JTAPI on the Side B PG.
|
Sync Side A to Side B 11.6
After the migration and upgrade, you must sync side A to side B. See Sync Side A to Side B for more information.