Cisco Cisco IP Contact Center Release 4.6.1 デザインガイド
11-11
Cisco Unified Contact Center Enterprise 7.0, 7.1, and 7.2 SRND
OL-8669-16
Chapter 11 Sizing Cisco Unified Communications Manager Servers
Upgrading Unified CM
For additional information on general call processing topics such as secondary TFTP servers and
gatekeeper considerations, refer to the Cisco Unified Communications Solution Reference Network
Design (SRND) guide, available at
gatekeeper considerations, refer to the Cisco Unified Communications Solution Reference Network
Design (SRND) guide, available at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_implementation_design_guides
_list.html
_list.html
Upgrading Unified CM
The 1:1 redundancy scheme allows upgrades with only the failover periods impacting the cluster. The
1:1 redundancy scheme enables you to upgrade the cluster using the following method:
1:1 redundancy scheme enables you to upgrade the cluster using the following method:
Step 1
Upgrade the publisher server.
Step 2
Upgrade dedicated TFTP and music-on-hold (MoH) servers.
Step 3
Upgrade the backup subscribers one at a time. This step will affect some users if 50/50 load balancing
is implemented.
is implemented.
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.
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.
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.
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:
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.
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.