Preupgrade Tasks
Perform the tasks in the following table in the order that they are listed.
Important |
You must perform the tasks in the order that they are listed in this table. Some tasks link to procedures in other parts of the guide. When you reach the end of a procedure, refer back to this table to determine what you must do next. Failure to perform upgrade tasks in the order listed in this table can cause the upgrade to fail. |
Note |
|
Step |
Task |
||
---|---|---|---|
1. |
In the Unified CCE Administration System Inventory tool, check the status of the alerts for the hosts and for each virtual machine (VM). Resolve any issues. Make sure that inventory alerts are at 0 before you continue. |
||
2. |
Shut down . Shut down Unified WIM and EIM. |
||
Reduce the impact of Side A services shutdown. Stopping Side A services to upgrade the components may force agents to sign out of their desktops and cause IP phones to rehome. If customers require agents to be active during the upgrade, you can reduce the impact of Side A shutdown by completing these preupgrade tasks. |
|||
3. |
Force phones to rehome to the Side B Unified Communications Manager Subscriber. Perform this step if the device pool for the agent phones contains only the Side A Unified Communications Manager Subscriber 1. In Unified Communications Manager Administration, add the Side B Unified Communications Manager Subscriber 2 as preferred and change the Subscriber 1 to secondary. Reset the phones after you change the device pool. You can skip this step if the device pool for the agent phones is configured with the Side A Unified Communications Manager Subscriber 1 as preferred and the Side B Unified Communications Manager Subscriber 2 as secondary. When you shut down Side A, Unified Communications Manager forces logout for agents using phones logged in to Subscriber 1 and rehomes their phones to Subscriber 2. |
||
4. |
Direct agents to sign in to the Side B Finesse Secondary node. |
||
5. |
Configure the Cisco IOS Enterprise Ingress Voice Gateway dial-peer priority so that calls are sent to the Side B Unified CVP Servers first, and then to the Side A Unified CVP Servers. |
||
6. |
To maintain reporting capabilities during the Side A upgrade, configure Unified Intelligence Center historical and real-time data sources to one of the following:
See Configure Unified Intelligence Center Data Sources for External HDS for steps to configure Unified Intelligence Center data sources. For the Datasource Host and Database Name fields, enter values for the Side B Unified CCE Data Server or External HDS with Side B as the Central Controller preferred side as needed. |
||
Complete Finesse preupgrade tasks |
|||
7. |
Save your current desktop layout configuration. Sign in to Finesse Administration on the primary Finesse node (https://FQDN of primary Finesse server/cfadmin). Copy the layout XML file from the Manage Desktop Layout gadget on the Desktop Settings tab. Save it as a text file on your local system.
|
||
Complete Unified CVP preupgrade tasks |
|||
8. |
Complete the Unified CVP Server and Operations Console preupgrade tasks on Unified CVP Server 1A, Unified CVP Server 1B, and the Unified CVP OAMP Server. You do not need to complete these tasks on Unified CVP Servers 2A and 2B because they are removed during the migration process. |
||
9. |
Change the Unified CVP scripts as required so they do not point to DNs and labels on Unified CVP Server 2A. |
||
Complete Unified Communications Manager preupgrade tasks |
|||
10. |
Complete Unified Communications Manager preupgrade tasks. |