Cisco Cisco E-Mail Manager Unity Integration Option Guida All'Installazione
2-5
Cisco ICM Software Upgrade Migration Guide, Release 6.0(0)
Chapter 2 ICR/ICM Upgrade Planning
Upgrade Planning
Schedule of Upgrade Activities
Due to the complexity of an ICR/ICM production system, it is recommended you
create a detailed schedule of upgrade activities. This allows your Project Manager
to maintain the status of each machine upgrade. It also helps to use a chart
indicating all of the ICR/ICM nodes to be upgraded and their upgrade status.
create a detailed schedule of upgrade activities. This allows your Project Manager
to maintain the status of each machine upgrade. It also helps to use a chart
indicating all of the ICR/ICM nodes to be upgraded and their upgrade status.
Upgrades are usually performed during off-peak hours. Keep in mind that you
may require more than one upgrade window. Normally, an initial maintenance
window is established to get the ICR/ICM Central Controller and critical (key)
AWs upgraded first. The remaining AWs and PGs are then scheduled as early as
maintenance windows allow.
may require more than one upgrade window. Normally, an initial maintenance
window is established to get the ICR/ICM Central Controller and critical (key)
AWs upgraded first. The remaining AWs and PGs are then scheduled as early as
maintenance windows allow.
Note
Ensure your AWs have been upgraded to the same software version before
bringing them online.
bringing them online.
Definition of Upgrade Steps
The upgrade migration of an ICR/ICM system involves numerous steps. From
your initial software load, you must install/upgrade the operating system, the ICM
software (and options), the database software, and any required third party
software.
your initial software load, you must install/upgrade the operating system, the ICM
software (and options), the database software, and any required third party
software.
Be aware that, for a period of time during the upgrade migration, the ICR/ICM
system runs in a non-fault tolerant mode. In addition, network default routing
takes place when both sides of the Central Controller are “stopped” during the
cross over (see
system runs in a non-fault tolerant mode. In addition, network default routing
takes place when both sides of the Central Controller are “stopped” during the
cross over (see
).
Testing must take place when the side A Central Controller is upgraded and
running. The upgrade team must then come to consensus on the success of the
testing and make a “go” or “no go” decision to proceed with upgrading the side B
Central Controller.
running. The upgrade team must then come to consensus on the success of the
testing and make a “go” or “no go” decision to proceed with upgrading the side B
Central Controller.
If critical problems are encountered after upgrading side A, the upgrade team
could decide to restore the side A Central Controller to the old/prior release.
could decide to restore the side A Central Controller to the old/prior release.