3-2
Install, Upgrade, and Maintenance Guide for Cisco Unity Connection Release 10.x
Chapter3 Upgrading CiscoUnity Connection
Upgrade Types
Table3-1 Upgrade Matrix for Unity Connection
Upgrade Type Upgrade Path Description
Service Update (SU) Examples of supported paths:
•10.5.x/10.5.xSUx1 to
10.5.xSUx2
•8.6.x/8.6.xSUx1 to 8.6.xSUx2
•SU is installed on the inactive
partition to which you can switch
later on.
•ISO images are non-bootable
images not meant for installation.
Refresh Upgrade (RU) 8.5 or earlier to 10.x or later •If the RHEL version of the Unity
Connection operating system
changes during an upgrade, it is
referred to as a Refresh Upgrade
(RU).
•You need the following COP files
before performing this upgrade:
–
ciscocm.refresh_upgrade.cop
–
ciscocm.version3-keys.cop
•The new version is installed on
the inactive partition. You should
perform automatic switch
version during RU for successful
upgrade.
9.x.x or earlier to 10.x or later •You need the following COP file
before performing this upgrade:
–
ciscocm.version3-keys.cop
•The new version is installed on
the inactive partition. You should
perform automatic switch
version during RU for successful
upgrade.
Level 2 (L2) Examples of supported paths:
•10.0.x to 10.5.y
•10.5.x to 10.5.y
•9.x to 9.y
•If the RHEL version of the Unity
Connection operating system do
not change during an upgrade, it
is referred to as an Level 2 (L2)
upgrade.
•The new version is installed on
the inactive partition to which
you can switch later on.
COP file, for more
information, see the
Applying COP file
from a Network
Location, page 3-9
section.
Fix for the same version •COP files are installed on the
active partition and you cannot
uninstall them. Contact Cisco
TAC to uninstall COP files.