You can upgrade
to Packaged CCC Release 10.0(1) from any version of Packaged CCE Release 9.
NTP Configuration
Packaged CCE has an increased dependence on time synchronization. Properly configuring NTP is critical for reliability of reporting data and cross-component communication. It's important to implement the requirements outlined in NTP and time synchronization.
Base
Configuration
Before you
upgrade to Release 10.0(1), refer to the Base Configuration chapter in the
Appendix:
Base Configuration Updates. You must manually add
requirements that were added to the base configuration subsequent to the
Packaged CCE 9.0(x) release from which you are upgrading.
System
Requirements
This table shows
hardware and software changes since Release 9.0(x). See also
System Requirements for fresh installs.
Item
Release 10.0 requirement
VMware Host
ESXi
Server 5.1. Sides A and B must be on the same version.
Cisco Unified Communications Manager
Unified CM 9.1(1) and later maintenance releases
Unified CM 10.0(1) and later maintenance releases
Anti-virus software
One
of:
Symantec
Endpoint Protection 12.1
Trend Micro
Server Protect version 5.8
McAfee VirusScan
Enterprise 8.8i
Software licenses
Upgrade Unified CVP
license using the Cisco Product Upgrade tool (PUT)
Upgrade the Unified
Communications Manager license using the Communications Manager interface.
Upgrade
sequence
In the same maintenance window, follow this sequence to upgrade all
Packaged CCE components.
Upgrade Cisco Finesse and run VM Settings Utility for Finesse
Upgrade Unified CVP and run VM Settings Utility for CVP
Upgrade CCE Servers and run VM Settings Utility for CCE
Run the VM Settings utility for Unified Intelligence Center
Validate deployment
Upgrade Unified Intelligence Center
Upgrade Unified Communications Manager and run VM Settings Utility for Communications Manager
Upgrade Cisco Finesse
Perform upgrade
Before You Begin
You must perform the upgrade on the primary Finesse node first, and then on the secondary Finesse node.
Procedure
Step 1
Perform a DRS
backup on the primary Finesse server. To access the DRS application, direct
your browser to https://IP address of Finesse server:8443/drf. For more information,
see the online help provided with the DRS application.
Important:
If a problem
occurs with the upgrade and you need to roll back to the previous version, you
need the DRS backup to restore your system. If you do not use the DRS backup to
restore your system, replication to the second Finesse node breaks and cannot
be repaired.
Step 2
Save your
current layout configuration. Sign in to the Administration Console on the
primary Finesse node (http://IP address or hostname of primary Finesse server/cfadmin).
Copy the layout XML file from the Manage Desktop Layout gadget on the Desktop
Settings tab and save it as a text file on your local system.
Note
If you are
currently running the default layout, the layout automatically upgrades to the
new layout. If you decide to use the layout from the previous version, you can
copy and paste to the Manage Desktop Layout gadget after the upgrade is
complete.
Upgrade Finesse
from DVD/CD
Procedure
Step 1
SSH to your
Finesse system and log in with the platform administration account.
Step 2
From the CLI,
run the command
utils system
upgrade initiate.
Step 3
Choose Local DVD/CD. Follow the
instructions provided by the
utils
system upgrade initiate command.
Step 4
Mount the ISO image.
Step 5
At the
Automatically switch versions if the upgrade is successful prompt, type
yes to upgrade and switch version.
Step 6
After the
upgrade is complete, unmount the ISO: disconnect the CD/DVD drive by unmounting the ISO.
Sign in to the
Finesse Agent Desktop to verify that the upgrade was successful (http://IP address or hostname of
Finesse server).
Note
After
Finesse restarts, wait approximately 20 minutes before you attempt to sign in
to the desktop.
Step 9
Repeat for the
secondary Finesse server.
What to Do Next
If you want to
restore a previous layout for the desktop, sign in to the Administration
Console on the primary Finesse node. Copy and paste your saved layout XML into
the Manage Desktop Layout gadget.
Upgrade Finesse from
a remote file system
Procedure
Step 1
SSH to your
Finesse system and log in with the platform administration account.
Step 2
From the CLI,
run the command
utils system
upgrade initiate.
Step 3
Choose SFTP or FTP.
Step 4
Follow the
instructions provided by the
utils
system upgrade initiate command.
Step 5
Provide the
location and credentials for the remote site.
Step 6
At the
Automatically switch versions if the upgrade is successful prompt, type
yes to upgrade and switch version.
Sign in to the
Finesse Agent Desktop to verify that the upgrade was successful (http://IP address or hostname of
Finesse server).
Note
After Finesse
restarts, wait approximately 20 minutes before you attempt to sign in to the
desktop.
Step 9
Repeat for the
secondary Finesse server.
Upgrade Customer Voice Portal and CVP Reporting
Pre-upgrade tasks
Procedure
Step 1
Close all programs.
Step 2
Stop any third-party services and applications that are running on the server.
Step 3
Back up C:\Cisco\CVP for all CVP components except the Operations Console.
Step 4
Back up the Operations Console as follows:
Log in to
Operations Console.
On the
Operations Console page, click
System > Export System
Configuration > Export.
Manually copy the sip.properties file.
(CVP Operations Console cannot export the sip.properties file.)
Save the
CVP-OpsConsole-Backup.zip file.
Save the
exported configuration and custom files on network storage media or a portable
storage media.
Step 5
Back up the log files in the following directories:
<CVP_HOME>\logs
<CVP_HOME>\lVXMLServer\logs
<CVP_HOME>\applications\<app_name>\logs
Upgrade
Upgrade CVP
Operations Console
The default media
files are overwritten during the Unified CVP 10.0(1) upgrade. Customized media
files, such as whisper announcements and agent greetings, are not overwritten;
they retain the format they had in Release 9.0(1).
Procedure
Step 1
To retain the
default media file format for Unified CVP 10.0(1), which is U-Law, skip Step 2
and proceed to Step 3.
Step 2
To convert the
format of the media files from 9.0 U-LAW or 9.0 A-LAW to 10.0 A-LAW:
Navigate
to the
C:\Cisco\CVP\conf location.
In the
cvp_pkgs.properties file, add the
cvp-pkgs.PromptEncodeFormatALaw = 1 property at line 7 to
enable the A-Law flag.
Note
Ensure
that you leave a space before and after the "=" sign.
Step 3
From the
CVP\Installer_Windows folder of the Unified CVP
10.0(1) installation DVD, run
setup.exe.
When you upgrade the
CVP/VXML server, you must also upgrade Call Studio to the same version.
Procedure
Step 1
From the
CVP\Installer_Windows folder of the new release of Unified CVP installation
DVD, run
setup.exe.
Follow
the prompts as the installer guides you through the upgrade process.
Log in to the
Operations Console and select
Bulk
Administration > File Transfer > Scripts and
Media.
Use the Cisco
IOS CLI command
call
application voice load <service_Name> to load the gateway
download transferred files into the Cisco IOS memory for each CVP service.
Restore any
backed-up third-party libraries.
Re-license CVP
Servers with a license for the new version.
Obtain and apply
upgrade license
The CVP server and the CVP Reporting Server require an updated
license. The Operations Console runs without requiring a license.
To upgrade software from Release 9.x to Release 10.0(1), enter your
contract number into the Cisco Product Upgrade Tool (PUT):
http://tools.cisco.com/gct/Upgrade/jsp/index.jsp. If there is an
entitlement to upgrade, the tool returns a Product Authorization Key (PAK), if
not the tool displays the option to purchase a PAK.
Your new license is sent to you by email.
Save it locally so that you can transfer it using the Operations
Console.
Procedure
Step 1
In the
Operation Console, go to
Bulk
Administration > File Transfer > Licenses.
Step 2
In the
Device
Association panel, select the device type from the drop-down list.
For example select Unified CVP Reporting Server or CVP Call Server.
Step 3
Move the objects
you want to license from
Available to
Selected.
Step 4
In the Licenses
Files panel, select
Select
new file and then browse to the location where you saved the
upgrade license.
Step 5
Click
Transfer.
Upgrade Reporting
Server
Before You Begin
Back up the
Informix database.
Run
C:\Cisco\CVP\bin\cvpbackup.bat. This backs up the database to
E:\cvp-db-backup\cvp-backup-data.gz.
Turn off the
scheduled purge.
To do this, go to
Start > Administrative
Tools > Task Scheduler. Select all the
CVP-related tasks, right-click and choose
Disable.
Ensure that
Reporting Server is not part of any domain and is part of a workgroup. Add it
to the domain after the upgrade, if necessary.
Procedure
Step 1
From the
CVP\Installer_Windows folder of the new release of
Unified CVP installation DVD, run
setup.exe.
The installer
guides you through the upgrade process.
Step 2
On the
password screen, enter the password, and click
Upgrade.
Make a note of
the password that you create during installation. This password is required
when you log in to Reporting Server for configuration.
Step 3
Restart the
Server.
Step 4
Restore the
backed-up database to the upgraded Reporting Server.
Copy the new
image from the remote TFTP server into flash memory, making sure that you
specify your own TFTP server's IP address and Cisco IOS filename.
Step 2
Verify that the new image was downloaded.
Step 3
Boot using the
new image. Update the gateway config to boot using the new version.
Upgrade Unified Contact Center Data Server and Call Server
Pre-upgrade tasks
Disable
configuration changes
Procedure
To disable
configuration changes during the upgrade, set the following registry key to 1
on the Side A Call Router:
HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\ICM\<instance
name>\Router A\Router\CurrentVersion\Configuration\Global\DBMaintenance.
Identify
passwords
The workflow for
validating Packaged CCE PCCE-PAC-M1 and building the system inventory requires
you to enter the usernames and passwords indicated below.
VMHost for Side
A
VMHost for Side
B
AXL for Cisco
Unified Communications Manager
CVP CLI for
Cisco Customer Voice Portal (by default, this is wsmadmin)
Diagnostic
Framework Portico for Cisco Contact Center Enterprise (must be the same on Side
A and Side B Call Servers and Data Servers)
Download the Enhanced Database Migration Tool
EDMT is a wizard application used to upgrade the Unified CCE database. You run this tool when you upgrade the database on the Side A and Side B Data Servers and on any external AW-HDS-DDS servers.
In the Downloads Home > Products table, select Products > Customer Collaboraton > Contact Center > Cisco Unified Contact Center Enterprise.
Step 6
In the Select a Software type page, select Cisco Enhanced Data Migration Tool Software Releases and navigate to the current release.
Step 7
Select the EDMT zip file. Then click Download.
Step 8
Download the file to the Unified CCE Data Server on Side A.
Step 9
Repeat to download the EDMT file to the Unified CCE Data Server on Side B and to any external AW-HDS-DDS servers.
Upgrade Side A
Stop Services on
Side A Data Server and Call Server
Before you begin the
upgrade, click the
Unified CCE Service Control icon from the
desktops. Stop all services on both the Side A Call Server and the Side A Data
Server and change to Startup to Manual.
Upgrade Data Server
databases
Procedure
Step 1
Use the
Microsoft SQL backup and restore utility to create a backup copy of the Logger
database.
(Optional) To
apply any Maintenance Releases, click
Browse and navigate to the Maintenance Release
software. Click
Next.
Step 4
Click
OK on any informational messages that display.
Step 5
If you have a
patch installed, click
Yes allow setup to remove it as part of the upgrade.
Step 6
Reboot the
server only if you are not upgrading CTI OS Server. If you are upgrading CTI OS
Server, reboot after both the Unified CCE and CT IOS Server upgrades are
complete.
Step 7
Run the utility to update the VMware settings (see Upgrade VMware Settings Utility)
only if you are not upgrading CTI OS Server. If you are upgrading CTI OS
Server, run the tools after both the Unified CCE and CT IOS Server upgrades are
complete.
Run Setup for CTI OS
Server
This step is
required only if CTI OS is installed.
(Optional) To
apply any Maintenance Releases, click
Browse and navigate to the Maintenance Release
software. Click
Next.
Step 4
Click
OK on any informational messages that display.
Step 5
If you have a
patch installed, click
Yes allow setup to remove it as part of the upgrade.
Step 6
Reboot the
server only if you are not upgrading CTI OS Server. If you are upgrading CTI OS
Server, reboot after both the Unified CCE and CT IOS Server upgrades are
complete.
Step 7
Run the utility to update the VMware settings (see Upgrade VMware Settings Utility)
only if you are not upgrading CTI OS Server. If you are upgrading CTI OS
Server, run the tools after both the Unified CCE and CT IOS Server upgrades are
complete.
Run Setup for CTI OS
Server
This step is
required only if CTI OS is installed.
(Optional) To
apply any Maintenance Releases, click
Browse and navigate to the Maintenance Release
software. Click
Next.
Step 4
(Optional)
Select
SQL
Server 2008 Security Hardening and click
Next.
Step 5
Click
OK on any informational messages that display.
Step 6
If you have a
patch installed, click
Yes to allow setup to remove it as part of the
upgrade.
Step 7
Click
Install.
Step 8
Reboot when
the upgrade is complete.
Step 9
Manually
restart services.
Post-upgrade tasks
Re-enable configuration changes
Perform this step on one side only. It is automatically replicated to the other side.
Procedure
Step 1
To enable configuration changes during the upgrade, set the following registry key to 0 on the Side A Call Routers: HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\ICM\<instance name>\Router<A\Router\CurrentVersion\Configuration\Global\DBMaintenance
Step 2
Confirm that configuration changes are enabled by attempting to save a configuration change.
The configuration change should be successful.
Set Services to
Automatic
Repeat the following procedure on the Side A Call Server, Side A Data
Server, Side B Call Server, and Side B Data Server, and on the external
AW-HDS-DDS machines if you have them.
Procedure
Step 1
Click
Unified
CCE Service Control.
Step 2
On the
ICM/CCE/CCH Service Control dialog box, click each service and changes the
startup to Automatic.
Run the utility to update Cisco Unified Intelligence Center
Before you validate and before you upgrade Cisco Unified Intelligence Center, you must run the utility to update the VMware settings. See
Upgrade VMware Settings Utility.
Validate system
and build system inventory
Procedure
Step 1
On the Data Server, navigate to https:<Data Server IP Address>/cceadmin.
Step 2
Click
System > Deployment.
The Configure
Deployment page shows errors that the VM host information is missing. This is
expected.
Step 3
Enter fields
for the IP address and the Username and Password for the VMware hosts for Side
A and Side B. Then click
Next.
Step 4
On the Specify
Side A CM Information dialog box:
For an
on-box Unified Communications Manager, select Unified CM Publisher from the
drop-down menu. Then enter the AXL Username and Password for that VM.
For an
external Unified Communications Manager deployment, enter the Unified CM
Publisher Name and IP address. Then enter the AXL Username and Password.
Step 5
On the Specify
CVP Ops Console Server Information dialog, enter the CLI Username and Password
for the Web Services manager. Then click
Next.
Step 6
At the Specify
Unified CCE Data Server Information page, enter the Username and Password for
the Unified CCE Diagnostic Framework Service. Then click
Next.
The Usernames and Passwords must be the same for the Side A Call
Server, Side A Data Server, Side B Call Server, and Side B Data Server.
This opens a
Congratulations screen.
Step 7
Click
Finish.
This opens the
System Inventory page—an interactive, visual display of your system where you
can monitor system health, add external servers, and update VM information.
Upgrade Unified Intelligence Center
Upgrade
About
Upgrades
The upgrade takes
less than one hour, and you can install upgrade software on your server while
the system continues to operate.
Before starting the
software upgrade, back up your system data using the Disaster Recovery system
application.
To access the DRS application, direct your browser to https://IP address of Intelligence
Center:8443/drf. For more information, see the online help provided with
the DRS application.
Upgrade and restart
the Controller node first. Then upgrade and restart the members. All nodes must
be on the same version of Unified Intelligence Center.
Your configuration
information migrates automatically to the upgraded version in the active
partition.
Note
Existing customers using VMware EXSi 4.x should first migrate to VMWare EXSi 5.x before upgrading to Unified Intelligence Center 10.0(1).
Repeat for the
subscriber on Side A and the subscriber on Side B.
Upgrade JTAPI on
the Call Server
If you upgrade
Unified Communications Manager, you must also upgrade the JTAPI client that
resides on the Side A and Side B Call Servers.
You install the
new JTAPI client using the Unified Communications Manager Administration
application.
Procedure
Step 1
Uninstall the old JTAPI client from each Call Server:
Stop PG1A/PG1B.
Go to
Control
Panel > Programs.
Uninstall the JTAPI client, following all prompts.
Step 2
To launch the
Unified Communications Manager Administration application, enter the following
URL in a Web browser on each Call Server:
https://<Unified Communications Manager machine
name>/ccmadmin.
Step 3
Enter the
username and password that you created when you installed and configured
Unified Communications Manager.
Step 4
Select
Application > Plug-ins.
Step 5
Click
Find to see the list of applications.
Step 6
Click the
download link next to Cisco JTAPI 32-bit client for Windows.
Step 7
Choose
Run
this program from its current location. Click
OK.
Step 8
If a Security
Warning box appears, click
Yes to install.
Step 9
When asked for the Cisco TFTP Server IP Address, enter the IP address of the Unified Communications Manager. Click Next.
Step 10
Choose
Next
or
Continue through the remaining setup windows. Accept
the default installation path.
From the
command line, run java -jar UpgradeVMwareSettings-10.0.jar
Step 3
Enter the IP
address of the Side A or Side B ESXi host.
Step 4
Enter the
username and password for root-level access to the ESXi host. This displays a
list of all VMs on that host.
You see a summary of all Virtual Machines, listed by number, with a message that indicates if and what the tool needs to fix.
Step 5
Enter the
number of the server you want to update. You must update one VM at a time. The results
of the conversion process appear on the screen and are stored in the results directory in the
vmwareConversion.log.
Step 6
If you are updating a Windows server, enter the username and password of the VM.
Step 7
After running the update on the Call Server or Data Server, ensure that the network binding order is correct.
If the tool was unable to set the correct binding order, this message will appear on the console and in the log: The Utility is unable to fix the binding order for the network. See the procedure on binding order in Configure network adapters for Call Server and Data Server.