Start the Side B Unified
CVP components
|
1.
|
Start
Unified CVP Server 1B and then start the Unified CVP Reporting Server.
Note
|
You do
not need to start Unified CVP Server 2B as it is removed during the migration.
|
|
Upgrade the Side B Unified
CVP Servers
|
2.
|
Remove the
Unified CVP Server 2B VM.
|
3.
|
Update the
Cisco IOS Enterprise Ingress Voice Gateway dial-peer configuration to remove
Unified CVP Server 2B.
|
4.
|
Upgrade
Unified CVP Server 1B.
See
Upgrade the Unified Customer Voice Portal.
|
Upgrade Side B Cisco
Voice Gateway IOS Version if needed
|
5.
|
Upgrade
the Side B Cisco Voice Gateway IOS version to the minimum required by the
upgraded
HCS for CC release
(or later).
See
Upgrade Cisco Voice Gateway IOS Version.
See the
HCS for CC Compatibility Information at https://www.cisco.com/c/en/us/support/unified-communications/hosted-collaboration-solution-contact-center/products-device-support-tables-list.htmlfor IOS support information.
|
Upgrade the Side B
Finesse and Unified Intelligence Center VMs
|
6.
|
Power on
the Finesse Secondary node VM in the vSphere client.
|
7.
|
Upgrade
the VMware version on the Finesse Secondary VM.
See
Upgrade the Virtual Machine Hardware Version.
|
8.
|
Update
the settings on the Finesse Secondary VM.
See
Update VMware Settings for Cisco Finesse.
|
9.
|
Upgrade
the Finesse Secondary node.
See
Upgrade Finesse
|
10.
|
Power on
the Unified Intelligence Center Subscriber VM in the vSphere client.
|
11.
|
Upgrade
the VMware version on the Unified Intelligence Center Subscriber VM.
See
Upgrade the Virtual Machine Hardware Version.
|
12.
|
Update
the settings on the Unified Intelligence Center Subscriber VM.
See
Update VMware Settings for Cisco Unified Intelligence Center.
|
13.
|
Upgrade
the Unified Intelligence Center Subscriber.
See
Upgrade Cisco Unified Intelligence Center
Note
|
Your
configuration information migrates automatically to the upgraded version in the
active partition.
|
|
Prepare for Side B
Migration to
HCS for CC 2000
Agent Rogger Deployment
|
14.
|
Back up
and export the Side B SQL database.
See
Back Up Database.
|
Install the Side B
Unified CCE Rogger
|
15.
|
Create a
VM for the Side B Unified CCE Rogger.
Select
CCE Rogger from the drop-down list.
|
16.
|
Install
Microsoft Windows Server on the Side B Unified CCE Rogger VM.
|
17.
|
Install
VMware tools on the Side B Unified CCE Rogger VM.
|
18.
|
Configure the network adaptors for the Side B Unified CCE
Rogger.
See
Configure Network Adapters for Unified CCE Call Server and Unified CCE Data Server
.
|
19.
|
Install
antivirus software on the Side B Unified CCE Rogger.
|
20.
|
Configure the database drive for the Side B Unified CCE Rogger.
See
Configure Database Drive.
|
21.
|
Set
persistent static routes.
See
Set Persistent Static Routes.
|
22.
|
Run
Windows updates.
See
Run Windows Updates.
|
23.
|
Add the
Unified CCE Rogger to the domain.
|
24.
|
Install
Microsoft SQL Server.
|
25.
|
Install
Cisco Unified Contact Center Enterprise.
|
Configure the Side B
Unified CCE Rogger
|
26.
|
Add a
UCCE Instance in Web Setup.
See
Add a UCCE Instance.
|
27.
|
Configure SQL Server for the Logger database.
See
Configure SQL Server for CCE Components.
|
28.
|
Configure the Logger database and log.
See
Configure the Logger Database and Log.
|
29.
|
Import
the Side B SQL database that you previously backed up in step 24.
See
Outbound Option for High Availability: Preliminary Two-Way Replication Requirements
|
30.
|
Add a
Unified CCE Router component in Web Setup.
See
Add a Unified CCE Router Component.
|
31.
|
Add a
Unified CCE Logger component in Web Setup.
See
Add a Unified CCE Logger Component.
|
Convert the Side B
Unified CCE Data Server and Unified CCE Call Server
|
32.
|
Upgrade
the VMware version on the Side B Data Server VM.
See
Upgrade the Virtual Machine Hardware Version.
|
33.
|
Update
the settings on the Side B Data Server VM.
See
Update VMware Settings on the Unified CCE Data Server.
|
34.
|
Convert
the Side B Unified CCE Data Server to a Unified CCE AW-HDS-DDS.
See
Convert Unified CCE Data Server to Unified CCE AW-HDS-DDS.
|
35.
|
Update
the real-time and historical data sources for Unified Intelligence Center to
point to the Unified CCE AW-HDS-DDS.
You must update the historical data source database name to <instancename>_awdb.
|
36.
|
Upgrade
the VMware version on the Side B Call Server VM.
See
Upgrade the Virtual Machine Hardware Version.
|
37.
|
Update
the settings on the Side B Call Server VM.
See
Update VMware Settings on the Unified CCE Call Server.
|
38.
|
Remove
the Router from the Side B Unified CCE Call Server.
See
Remove the Router from the Unified CCE Call Server.
Note
|
If CTI
OS Server is present, remove it as well. CTI OS is no longer supported.
|
The Call
Server is now a PG.
|
39.
|
Run
the Unified CCE 11.6(1) installer on the Side B Unified CCE Rogger to upgrade
to Release 11.6(1).
See
Upgrade to Release 11.6(1).
|
40.
|
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
|
41.
|
Run
the Unified CCE 11.6(1) installer on the Side B Unified CCE AW-HDS-DDS (former
Data Server) to upgrade to Release 11.6(1).
See
Upgrade to Release 11.6(1).
|
42.
|
Run
the Unified CCE 11.6(1) installer on the Side B PG (former Call Server) to
upgrade to Release 11.6(1).
See
Upgrade to Release 11.6(1).
|
43.
|
Modify
the Side B PG to point to the Unified CCE Rogger.
See
Modify the PG.
|
44.
|
Modify
the dialer to point to the Unified CCE Rogger (if using Outbound Option).
See
Modify the Dialer.
|
Optional: Upgrade the
External HDS associated with Side B (if used)
|
45.
|
Upgrade
the VMware version on the External HDS associated with Side B.
See
Upgrade the Virtual Machine Hardware Version.
|
46.
|
Run
the Unified CCE 11.6(1) installer on the External HDS associated with Side B to
upgrade to Release 11.6(1).
See
Upgrade to Release 11.6(1).
|
47.
|
Update
the Central Controller connectivity to point to the Unified CCE Rogger.
See
Update the Central Controller Connectivity.
|
Optional: Install
language pack
|
48.
|
Install
the language pack on the Side B Unified CCE Rogger, AW-HDS-DDS, PG (formerly
Call Server), and External HDS (if used).
See
Install the Language Pack.
|
Upgrade Side B Unified
Communications Manager Subscriber 2
|
49.
|
Power on
the Unified Communications Manager Subscriber 2 VM in the vSphere client.
|
50.
|
Upgrade
the Side B Unified Communications Manager Subscriber 2.
See
Upgrade Cisco Unified Communications Manager
|
51.
|
Upgrade
JTAPI on the Side B PG (formerly Call Server).
See
Upgrade JTAPI on the Call Server.
|
Optional: Change
hostnames of the Unified CCE components
|
52.
|
Optional: Change the hostnames of the Unified CCE components
(AW-HDS-DDS and PG).
Note
|
You
can perform this task when you reboot each component as part of the upgrade. If
you do change the hostnames, you must also change them in the following places:
-
Finesse
-
PG
Setup
-
Unified Intelligence Center - Historical and real-time
-
Private network DNS entries
-
Live Data—If you change the hostname of the AW-HDS-DDS (former
Data Server), Live Data no longer connects to the AW-HDS-DDS after the Data
Server hostname is removed from DNS. To fix this, do the following:
-
Run the following CLI command on the CUIC-LD-IdS Publisher:
unset live-data aw-access secondary
-
Restart Cisco Tomcat on the Side B AW-HDS-DDS.
|
|