Cisco Cisco IP Contact Center Release 4.6.2 Prospecto

Descargar
Página de 428
 
11-13
Cisco Unified Contact Center Enterprise 7.5 SRND
Chapter 11      Sizing Cisco Unified Communications Manager Servers
Upgrading Unified CM
Step 4
Fail over the primary subscribers to their backups, and stop the Cisco CallManager service on the 
primaries. All users are on primaries and are moved to backup subscribers when the Cisco CallManager 
service is stopped. CTI Manager is also stopped, causing the Peripheral Gateway (PG) to switch sides 
and inducing a brief outage for agents on that particular node. 
Step 5
Upgrade the primaries, and then re-enable the Cisco CallManager service.
With this upgrade method, there is no period (except for the failover period) when devices are registered 
to subscriber servers that are running different versions of the Unified CM software. This factor can be 
important, because the Intra-Cluster Communication Signaling (ICCS) protocol that communicates 
between subscribers can detect a different software version and shut down communications to that 
subscriber.
The 2:1 redundancy scheme allows for fewer servers in a cluster, but it can potentially result in an outage 
during upgrades. This is not a recommended scheme for Unified CCE deployments, although it is 
supported if it is a customer requirement and if possible outage of call processing is not a concern to the 
customer.
The 2:1 redundancy scheme enables you to upgrade the cluster using the following method. If the Cisco 
CallManager service does not run on the publisher database server, upgrade the servers in the following 
order:
Step 1
Upgrade the publisher database server.
Step 2
Upgrade the Cisco TFTP server if it exists separately from the publisher database server.
Step 3
Upgrade servers that have services related only to Unified CM (music on hold, Cisco IP Media 
Streaming Application, and so forth) running on them. Make sure that you upgrade only one server at a 
time. Make sure that the Cisco CallManager service does not run on these servers.
Step 4
Upgrade each backup server, one server at a time.
Note
Cisco does not recommend that you oversubscribe the backup server or servers during the 
upgrade. The number of agent phones registered to the backup server during the upgrade should 
not exceed the maximum capacity indicated by the Cisco Unified CM Capacity Tool or the 
Unified Communications Sizing Tool. Perform the upgrade during off-peak hours when the call 
volume is low.
Step 5
Upgrade each primary server that has the Cisco CallManager service running on it. Remember to 
upgrade one server at a time. During the upgrade of the second primary subscriber, there will be some 
outage for users and agents subscribed on that server, until the server is upgraded. Similarly, when you 
upgrade the fourth primary subscriber, there will be some outage for users and agents subscribed on that 
server, until the server is upgraded.