INDEX
conventions, documentation
A
adding server to create a cluster
-ix
converting publisher to single server without a
cluster 11-3
11-1
associated components on which IP address of server must
be changed 12-2
D
DNS settings, using CLI commands to change
C
documentation conventions
15-1
-ix
changing
DNS settings by using CLI commands
15-1
IP address for publisher defined by hostname
12-7
IP address for publisher defined by IP address
12-10
E
effects of reverting to version on inactive partition
4-1, 4-2
IP address for single server defined by hostname (no
cluster) 12-3
IP address for single server defined by IP address (no
cluster) 12-5
G
IP address for subscriber defined by hostname
gateway server, reverting to version on inactive
partition 4-5
IP address for subscriber defined by IP address
language settings
12-13
12-15
9-7
Cisco voicemail organization, reverting gateway server to
version on inactive partition 4-5
H
Cisco voicemail organization, reverting member server to
version on inactive partition 4-4
hard disks
CLI commands, using to change DNS settings
replacing in publisher and subscriber servers
15-1
replacing in publisher server
cluster
adding server to create
10-2
replacing in single server without Connection
cluster 10-1
11-1
changing the SMTP domain
10-8
replacing in subscriber server
14-4
hostname, determining whether servers are defined
by 12-1
replacing publisher and subscriber servers, or hard
disks 10-8
replacing publisher server or hard disks
replacing subscriber server or hard disks
10-5
10-2
10-5
reverting servers to version on inactive partition
4-3
COBRAS
for migrating data from Cisco Unity 4.0(5) or later to
Connection 8.x by using a flash cutover 6-2
I
IP addresses
changing for publisher defined by hostname
changing for publisher defined by IP address
12-7
12-10
Upgrade Guide for Cisco Unity Connection Release 9.x
IN-1
Index
changing for single server defined by hostname (no
cluster) 12-3
replacing along with subscriber server, or hard
disks 10-8
changing for single server defined by IP address (no
cluster) 12-5
reverting to version on inactive partition
changing for subscriber defined by hostname
12-13
changing for subscriber defined by IP address
changing on associated components
12-15
12-2
R
removing language files
determining whether servers are defined by
4-2
12-1
9-7
renaming
publisher server (task list)
14-4
subscriber server (task list)
L
14-7
replacing
languages
publisher and subscriber servers, or hard disks
adding to a Connection cluster (task list)
9-2
publisher server or hard disks
adding to a Connection server (no cluster) (task
list) 9-1
changing settings
removing files
10-2
single server or hard disks without Connection
cluster 10-1
9-7
subscriber server or hard disks
9-7
10-8
10-5
reverting
Connection software to version on inactive partition,
about 4-1
M
effects of
4-1, 4-2
member server, reverting to version on inactive
partition 4-4
gateway server in a Cisco voicemail organization to
version on inactive partition 4-5
migrating
member server in a Cisco voicemail organization to
version on inactive partition 4-4
from a Connection physical server to a Connection 8.x
virtual machine (task list) 8-1
server, or publisher server in a cluster to version on
inactive partition 4-2
from Cisco Unity 4.0(5) or later to Connection 8.x by
using a flash cutover (task list) 6-4
servers in a cluster to version on inactive
partition 4-3
from Cisco Unity to Connection 8.x by gradually
moving data (task list) 7-4
from Connection 1.x to 8.x (task list)
5-1
S
Migration Export tool
for migrating data from Cisco Unity 4.x or later to
Connection 8.x by using a flash cutover 6-2
servers
adding to create a cluster
11-1
associated components on which IP address must be
changed 12-2
P
changing IP address for publisher defined by
hostname 12-7
publisher server
converting to single server without a cluster
renaming (task list)
replacing
11-3
14-4
10-2
Upgrade Guide for Cisco Unity Connection Release 9.x
IN-2
changing IP address for publisher defined by IP
address 12-10
changing IP address for single defined by hostname
(no cluster) 12-3
Index
changing IP address for single server defined by IP
address (no cluster) 12-5
for renaming subscriber server
for replacing single server or hard disks without
Connection cluster 10-1
changing IP address for subscriber defined by
hostname 12-13
for reverting servers in a cluster to version on inactive
partition 4-3
changing IP address for subscriber defined by IP
address 12-15
for upgrading Connection 7.x software to shipping 8.x
version 1-2, 2-4, 3-7, 3-12, 3-16
converting publisher to single server without a
cluster 11-3
for upgrading Connection 7.x software to shipping 8.x
version (no cluster) 1-2, 2-3, 3-6, 3-16
determining whether server is defined by hostname or
IP address 12-1
renaming publisher (task list)
tools for migrating
14-7
replacing publisher and subscriber, or hard disks
replacing publisher or hard disks
from Cisco Unity 4.0(5) or later to Connection 8.x by
using a flash cutover, about 6-2
10-8
10-2
replacing single without Connection cluster
replacing subscriber or hard disks
10-1
10-5
U
reverting to version on inactive partition in a
cluster 4-2
upgrading
SMTP domain
about the process
changing for a cluster
14-4
Connection 7.x software to shipping 8.x version (task
list) 1-2, 2-4, 3-7, 3-12, 3-16
subscriber server
renaming (task list)
2-1, 3-2
Connection 7.x software to shipping 8.x version, no
cluster (task list) 1-2, 2-3, 3-6, 3-16
software, about reverting to version on inactive
partition 4-1
replacing
for upgrading Connection 7.x software to shipping 8.x
version in a Connection cluster 3-11
14-4
renaming subscriber (task list)
14-7
Connection 7.x software to shipping 8.x version in a
Connection cluster (task list) 3-11
14-7
10-5
replacing along with publisher server, or hard
disks 10-8
T
task lists
for adding languages to a Connection cluster
9-2
for adding languages to a Connection server (no
cluster) 9-1
for migrating from a Connection physical server to a
Connection 8.x virtual machine 8-1
for migrating from Cisco Unity 4.0(5) or later to
Connection 8.x by using a flash cutover 6-4
for migrating from Cisco Unity to Connection 8.x by
gradually moving data 7-4
for migrating from Connection 1.x to 8.x
for renaming publisher server
5-1
14-4
Upgrade Guide for Cisco Unity Connection Release 9.x
IN-3
Index
Upgrade Guide for Cisco Unity Connection Release 9.x
IN-4
Preface
This preface contains the following sections:
•
Audience and Use, page ix
•
Documentation Conventions, page ix
•
Cisco Unity Connection Documentation, page x
•
Obtaining Documentation and Submitting a Service Request, page x
•
Cisco Product Security Overview, page xi
Audience and Use
The Upgrade Guide for Cisco Unity Connection is intended for system administrators and technicians
who handle upgrades and changes to the Cisco Unity Connection system configuration.
The Upgrade Guide for Cisco Unity Connection focuses on information and procedures necessary for
changing the current configuration of the system—that is the hardware and software arrangements that
define what Cisco Unity Connection is and what it does—and for upgrading the Connection software to
newer versions. The guide does not include information on changing Cisco Unity Connection data (for
example, user templates and call handlers).
Documentation Conventions
Table 1
Conventions in the Upgrade Guide for Cisco Unity Connection
Convention
Description
boldfaced text
Boldfaced text is used for:
<>
(angle brackets)
•
Key and button names. (Example: Select OK.)
•
Information that you enter. (Example: Enter Administrator
in the User Name box.)
Angle brackets are used around parameters for which you supply
a value. (Example: In the Command Prompt window, enter ping
<IP address>.)
Upgrade Guide for Cisco Unity Connection Release 9.x
ix
Preface
Table 1
Conventions in the Upgrade Guide for Cisco Unity Connection (continued)
Convention
Description
-
Hyphens separate keys that must be pressed simultaneously.
(Example: Press Ctrl-Alt-Delete.)
(hyphen)
>
(right angle bracket)
A right angle bracket is used to separate selections that you make
on menus. (Example: On the Windows Start menu, select
Settings > Control Panel > Phone and Modem Options.)
The Upgrade Guide for Cisco Unity Connection also uses the following conventions:
Note
Caution
Warning
Means reader take note. Notes contain helpful suggestions or references to material not covered in the
document.
Means reader be careful. In this situation, you might do something that could result in equipment damage
or loss of data.
Means reader be warned. In this situation, you might perform an action that could result in bodily
injury.
(For translations of safety warnings listed in this guide, see Regulatory Compliance and Safety
Information for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/regulatory/compliance/ucwarns.html.)
Cisco Unity Connection Documentation
For descriptions and URLs of Cisco Unity Connection documentation on Cisco.com, see the
Documentation Guide for Cisco Unity Connection Release 9.x. The document is shipped with
Cisco Unity Connection and is available at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/roadmap/9xcucdg.html.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional
information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and
revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed
and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free
service and Cisco currently supports RSS Version 2.0.
Upgrade Guide for Cisco Unity Connection Release 9.x
x
Preface
Cisco Product Security Overview
This product contains cryptographic features and is subject to United States and local country laws
governing import, export, transfer and use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption. Importers, exporters, distributors
and users are responsible for compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable to comply with U.S. and local
laws, return this product immediately
Further information regarding U.S. export regulations may be found at
http://www.access.gpo.gov/bis/ear/ear_data.html.
Upgrade Guide for Cisco Unity Connection Release 9.x
xi
Preface
Upgrade Guide for Cisco Unity Connection Release 9.x
xii
CH A P T E R
1
Upgrading Cisco Unity Connection SRSV 9.1
Version
This chapter contains the following sections:
•
About Upgrades to Unity Connection SRSV 9.1, page 1-1
•
Status of Unity Connection Features During the Upgrade to Unity Connection SRSV 9.1, page 1-1
•
Task List for Upgrading to Unity Connection SRSV 9.1 Version, page 1-2
•
Upgrading Unity Connection SRSV 9.1 Software to the Shipping Unity Connection SRSV 9.1
Version from a Local DVD, page 1-3
•
Upgrading Unity Connection SRSV 9.1 Software to the Shipping Unity Connection SRSV 9.1
Version from a Network Location, page 1-4
About Upgrades to Unity Connection SRSV 9.1
At the start of the upgrade, you choose whether to restart to the inactive partition. After the upgrade is
completed:
Note
•
If you choose to restart, the Unity Connection SRSV automatically restarts, running the upgraded
version of Unity Connection SRSV.
•
If you choose not to restart, you must manually switch to the upgraded version.
The following considerations about upgrading a Unity Connection SRSV to version 9.1:
•
If you have never upgraded the Unity Connection SRSV before, the upgrade copies the new version
to an empty partition.
•
Upgrading to Unity Connection SRSV 9.1 requires approximately four hours.
•
Switching to the upgraded software requires approximately two hours.
Status of Unity Connection Features During the Upgrade to
Unity Connection SRSV 9.1
During an upgrade to Unity Connection SRSV 9.1, Unity Connection is completely disabled for the
entire duration of the upgrade.
Upgrade Guide for Cisco Unity Connection Release 9.x
1-1
Chapter 1
Upgrading Cisco Unity Connection SRSV 9.1 Version
Task List for Upgrading to Unity Connection SRSV 9.1 Version
Task List for Upgrading to Unity Connection SRSV 9.1 Version
Revised March 14, 2013
Do the following tasks to upgrade an existing Unity Connection SRSV 9.1 to the shipping
Unity Connection SRSV 9.1 version when Unity Connection cluster is not configured.
1.
If you are upgrading Unity Connection SRSV on a Cisco MCS 7825-H3 server or the equivalent HP
DL320G5: Confirm that you have a 128 GB or larger USB flash drive or external hard disk.
During the upgrade, disk drives in the Unity Connection server are converted from hardware-based
RAID to software-based RAID. Before the RAID conversion, the USB drive is reformatted, and data
and voice messages on the Unity Connection server are copied to the drive. After the RAID
reconfiguration, data and voice messages are copied back to the disk drives in the Unity Connection
server.
Caution
Note
Do not use a USB drive that contains data that you want to keep. During the upgrade, the USB
drive is reformatted, and all existing data on the drive is destroyed.
2.
Review the list of features that are disabled or that have limited functionality during the upgrade.
During an upgrade to Unity Connection SRSV 9.1, Unity Connection is completely disabled for the
entire duration of the upgrade.
3.
If you are upgrading from Unity Connection 9.0 to Unity Connection 9.1: Run the CLI command
run cuc preupgrade test to verify the prerequisites before running the upgrade.
4.
See the applicable version of Release Notes for Cisco Unity Connection for any additional
information on upgrading to the shipping version. In particular, note the items in the “Installation
and Upgrade Information” section. Release notes are available at
http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html.
5.
If you do not have a database backup before replacing the hard disks or the server: Back up the
server by using the Disaster Recovery System. For more information, see the applicable Disaster
Recovery System Administration Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
6.
Upgrade the Unity Connection SRSV software. See the applicable section:
•
Upgrading Unity Connection SRSV 9.1 Software to the Shipping Unity Connection SRSV 9.1
Version from a Local DVD, page 1-3
•
Upgrading Unity Connection SRSV 9.1 Software to the Shipping Unity Connection SRSV 9.1
Version from a Network Location, page 1-4
If you have the Japanese locale already installed on your Unity Connection server, make sure to uninstall
uc-locale-ja_JP-9.1.0.1-xx.cop.sgn, the default Japanese cop file before upgrading to Unity Connection
SRSV server. After the Unity Connection SRSV server is installed, you can install
uc-locale-SRSV-ja_JP-9.1.0.1-xx.cop.sgn, the SRSV specific Japanese cop file to have the Japanese
locale.
7.
Switch to the upgraded software version of the Unity Connection SRSV. See the “Switching to the
Upgraded Version of Unity Connection 9.x Software” section on page 3-29
Upgrade Guide for Cisco Unity Connection Release 9.x
1-2
Chapter 1
Upgrading Cisco Unity Connection SRSV 9.1 Version
Upgrading Unity Connection SRSV 9.1 Software to the Shipping Unity Connection SRSV 9.1 Version from a Local DVD
Upgrading Unity Connection SRSV 9.1 Software to the Shipping
Unity Connection SRSV 9.1 Version from a Local DVD
Revised March 5, 2013
To upgrade Unity Connection SRSV from a local DVD, you can do either of the following:
Warning
Tip
•
Use a DVD shipped from Cisco.
•
Download a signed .iso file from Cisco.com, and burn a disc image of the downloaded software.
Burning a disc image extracts the files from the .iso file that you downloaded and writes them to a
DVD.
Be aware that when you mount an ISO file through the VM console, VMware does not eject the disc
at the end of the install process.
Always mount your DVD ISO file from the Edit Settings menu in VMware.
To follow the upgrade process through the CLI interface, see the utils system upgrade command at the
Command Line Interface Reference Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
To Upgrade to the Unity Connection SRSV 9.1 Version from a Local DVD
Step 1
Insert the DVD that contains Unity Connection SRSV ISO file into the disc drive on the
Unity Connection SRSV server.
Step 2
Sign in to Cisco Unified Operating System Administration.
Step 3
From the Software Upgrades menu, select Install/Upgrade.
Step 4
On the Software Installation/Upgrade page, in the Source field, select DVD/CD.
Step 5
In the Directory field, enter a forward slash (/).
Step 6
Select Next.
Step 7
Select the upgrade version that you want to install, and select Next. The upgrade file is copied to the
hard disk on the Unity Connection SRSVserver. When the file is copied, a screen displays the checksum
value.
Step 8
Verify the checksum.
Step 9
On the next page, monitor the progress of the upgrade.
If you lose your Unity Connection SRSV server connection with the remote server or close your browser
during this step, you may see the warning below when you try to view the Software
Installation/Upgrade page again.
Warning
Another session is installing software, click Assume Control to take over the installation.
To continue monitoring the upgrade, select Assume Control.
You can also monitor the upgrade by using the Real-Time Monitoring Tool.
Step 10
Select Next.
Upgrade Guide for Cisco Unity Connection Release 9.x
1-3
Chapter 1 Upgrading Cisco Unity Connection SRSV 9.1 Version
Upgrading Unity Connection SRSV 9.1 Software to the Shipping Unity Connection SRSV 9.1 Version from a Network
Note
•
For without a Unity Connection cluster, you can select either the manual switch version or the
automatic switch version option.
•
For a Unity Connection cluster, you need to select the manual switch version option,
During the initial phase of the upgrade, the Installation Log text box in Cisco Unified Operating System
Administration is updated with information on the progress of the upgrade, but updates stop after the
server automatically restarts for the first time. To determine when the upgrade is complete, view the
console for the Unity Connection SRSV: the console screen displays a message indicating that the
installation is complete, and the login prompt for the command-line interface appears.
Step 11
To verify the success of the upgrade, run the CLI command show cuc version. The upgrade succeeded
if the active partition has the upgraded version and the inactive partition has the old version.
Upgrading Unity Connection SRSV 9.1 Software to the Shipping
Unity Connection SRSV 9.1 Version from a Network Location
To upgrade Unity Connection SRSV version from a network location, you must download a signed .iso
file from Cisco.com, and copy the .iso file to an FTP or SFTP server. Unity Connection SRSV does not
allow you to upgrade by copying either the contents of a DVD shipped from Cisco or the extracted
contents of a downloaded .iso file to an FTP or SFTP server. This helps prevent someone from attempting
to upgrade by using software that has been tampered with.
To follow the upgrade process through the CLI interface, see the utils system upgrade command at the
Command Line Interface Reference Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
To Upgrade to the Unity Connection SRSV 9.1 Version from a Network Location
Step 1
Copy the upgrade file to a folder on an FTP or SFTP server that the Unity Connection SRSV server can
access.
Step 2
Sign in to Cisco Unified Operating System Administration.
Step 3
From the Software Upgrades menu, select Install/Upgrade.
Step 4
On the Software Installation/Upgrade page, in the Source field, select Remote Filesystem.
Step 5
In the Directory field, enter the path to the folder that contains the upgrade file.
If the upgrade file is located on a Linux or Unix server, you must enter a forward slash (/) at the beginning
of the folder path. (For example, if the upgrade file is in the upgrade folder, you must enter /upgrade.)
If the upgrade file is located on a Windows server, you must use the applicable syntax for an FTP or
SFTP server such as:
•
The path must begin with a forward slash (/) and contain forward slashes throughout instead of
backward slashes (\).
•
The path must start from the FTP or SFTP root folder on the server and must not include a Windows
absolute path, which starts with a drive letter (for example, C:).
Step 6
In the Server field, enter the server name or IP address.
Step 7
In the User Name field, enter the alias that will be used to sign in to the remote server.
Upgrade Guide for Cisco Unity Connection Release 9.x
1-4
Chapter 1
Upgrading Cisco Unity Connection SRSV 9.1 Version
Upgrading Unity Connection SRSV 9.1 Software to the Shipping Unity Connection SRSV 9.1 Version from a Network
Step 8
In the User Password field, enter the password that will be used further to sign in to the remote server.
Step 9
In the Transfer Protocol field, select the applicable transfer protocol.
Step 10
Select Next.
Step 11
Select the upgrade version that you want to install and select Next. The upgrade file is copied to the hard
disk on the Unity Connection SRSV server. When the file is copied, a screen displays the checksum
value.
Step 12
Verify the checksum.
Step 13
On the next page, monitor the progress of the upgrade.
If you lose your Unity Connection SRSV server connection with the remote server or close your browser
during this step, you may see the warning below when you try to view the Software Installation/Upgrade
page again.
Warning
Another session is installing software, click Assume Control to take over the installation.
To continue monitoring the upgrade, select Assume Control.
You can also monitor the upgrade by using the Real-Time Monitoring Tool.
Step 14
Note
Select Next.
•
For without a Unity Connection cluster, you can select either the manual switch version or the
automatic switch version option.
•
For a Unity Connection cluster, you need to select the manual switch version option,
During the initial phase of the upgrade, the Installation Log text box in Cisco Unified Operating System
Administration is updated with information on the progress of the upgrade, but updates stop after the
server automatically restarts for the first time. To determine when the upgrade is complete, view the
console for the Unity Connection SRSV: the console screen displays a message indicating that the
installation is complete, and the login prompt for the command-line interface appears.
Step 15
To verify the success of the upgrade, run the CLI command show cuc version. The upgrade succeeded
if the active partition has the upgraded version and the inactive partition has the old version.
Upgrade Guide for Cisco Unity Connection Release 9.x
1-5
Chapter 1 Upgrading Cisco Unity Connection SRSV 9.1 Version
Upgrading Unity Connection SRSV 9.1 Software to the Shipping Unity Connection SRSV 9.1 Version from a Network
Upgrade Guide for Cisco Unity Connection Release 9.x
1-6
CH A P T E R
2
Upgrading Cisco Unity Connection 9.0 to the
Shipping Cisco Unity Connection 9.1 Version
This chapter contains the following sections:
•
About Upgrades to Unity Connection 9.1, page 2-1
•
Status of Unity Connection Features During an Upgrade from Unity Connection 9.0 to
Unity Connection 9.1, page 2-2
•
Features that You Must Reconfigure When You Upgrade from Unity Connection 9.0, page 2-3
•
Task List for Upgrading Unity Connection 9.0 Software to the Shipping 9.1 Version Without a
Unity Connection Cluster, page 2-3
•
Task List for Upgrading Unity Connection 9.0 Software to the Shipping 9.1 Version in a
Unity Connection Cluster, page 2-5
•
Installing a Memory Upgrade or Replacing All Hard Disks to Support Unity Connection 9.1
(Selected Servers Only), page 2-9
•
Upgrading Unity Connection 9.0 Software to the Shipping 9.1 Version from a Local DVD,
page 2-12
•
Upgrading Unity Connection 9.0 Software to the Shipping 9.1 Version from a Network Location,
page 2-13
About Upgrades to Unity Connection 9.1
During the upgrade process, you choose whether to restart to the inactive partition after completing the
upgrade sucessfully. If you choose to restart, after completing the upgrade process, Unity Connection
automatically restarts running the upgraded version of Unity Connection. If you choose not to restart,
you must manually switch to the upgraded version after the upgrade process is completed.
The following considerations about upgrading a Unity Connection server to version 9.1:
•
Note
If you have never upgraded Unity Connection before, the upgrade copies the new version to an
empty partition.
To migrate from a physical to virtual server or from virtual to virtual server, make sure the server
requirements are met for Unity Connection 9.x, as mentioned in:
http://docwiki.cisco.com/wiki/Ongoing_Virtualization_Operations_and_Maintenance#Upgrading_the_
UC_applications.
Upgrade Guide for Cisco Unity Connection Release 9.x
2-1
Chapter 2 Upgrading Cisco Unity Connection 9.0 to the Shipping Cisco Unity Connection 9.1 Version
Status of Unity Connection Features During an Upgrade from Unity Connection 9.0 to Unity Connection 9.1
•
If you have upgraded the Unity Connection server before, the upgrade copies the new version to the
inactive partition, which usually contains a version of Unity Connection older than the version that
is running on the active partition. (If you previously upgraded to a later version and then reverted to
the older version, the inactive partition includes a version of Unity Connection later than the version
that is currently running.) The software that was on the inactive partition before you started the
upgrade is overwritten.
•
Depending on your current version, you may be required to upgrade twice to reach the desired
version. In that case, the current version is no longer available when the upgrade is complete because
the partition that contains the current version will be overwritten by the second upgrade.
•
Installing the software upgrade requires approximately two hours for each server. When upgrading
a Connection cluster, an upgrade requires approximately four hours.
•
Switching to the upgraded software requires a few minutes.
Status of Unity Connection Features During an Upgrade from
Unity Connection 9.0 to Unity Connection 9.1
During an upgrade from Unity Connection 9.0 to Unity Connection 9.1, if you do not have a cluster,
Unity Connection is completely disabled for the entire duration of the upgrade.
If you are upgrading a cluster, the upgrade starts on the publisher server. Unity Connection functionality
on the publisher server is completely disabled for the entire duration of the upgrade. Note the following
about the functionality that is available on the subscriber server while the publisher server is being
upgraded:
•
If the phone system is routing calls to the subscriber server, outside callers and Unity Connection
users can leave voice messages, but the messages are not immediately delivered to user mailboxes.
•
Unity Connection users can use the telephone user interface (touchtone conversation) to listen to
messages that are left before you start the upgrade. However, users cannot listen to messages that
are left during the upgrade, and Unity Connection will not always retain the status of messages. For
example, if a user plays a voice message during the upgrade, the message may be marked as new
again after the upgrade. If a user deletes a message, the message may reappear after the upgrade.
•
Unity Connection users cannot access Unity Connection using graphical user interfaces, for
example, ViewMail for Outlook, Web Inbox, or IMAP email applications.
•
If Unity Connection users use the touchtone conversation to change their user preferences or other
settings during the upgrade, their changes will probably be lost. (There are brief periods during the
upgrade when changes are saved, but identifying those periods is difficult at best.)
•
Cisco Unified Operating System Administration is available, but other administration user
interfaces, for example, Unity Connection Administration and Cisco Unity Connection
Serviceability, are not available. In addition, custom administration interfaces that were developed
by using the Unity Connection administration API are also not available.
•
Intrasite and intersite networking is disabled for the duration of the upgrade. Directory changes
made on other nodes in the network are not replicated to the server or cluster that you are upgrading
until after the upgrade is complete.
When the upgrade of the publisher server is complete, full functionality is restored on the publisher
server.
When you start the upgrade on the subscriber server in a cluster:
Upgrade Guide for Cisco Unity Connection Release 9.x
2-2
Chapter 2
Upgrading Cisco Unity Connection 9.0 to the Shipping Cisco Unity Connection 9.1 Version
Features that You Must Reconfigure When You Upgrade from Unity Connection 9.0
•
Messages that were left on the subscriber server are copied to the publisher server, and the publisher
server begins to deliver the messages to user mailboxes.
•
Unity Connection functionality on the subscriber server is completely disabled for the entire
duration of the upgrade.
While the subscriber server is being upgraded, messages that are left on the publisher server are
delivered to user mailboxes on the publisher server. When the upgrade of the subscriber server is
complete, the messages are replicated to the subscriber server and are delivered to user mailboxes on the
subscriber server. If single inbox is configured, messages are synchronized to Exchange after they are
delivered to user mailboxes. If a large number of messages were left during the upgrade, there may be a
significant delay before message delivery, replication, and synchronization with Exchange.
Features that You Must Reconfigure When You Upgrade from
Unity Connection 9.0
Unity Connection 9.1 included enhancements to the following features, which are now among the
features in Unity Connection unified messaging:
•
Accessing Exchange email by using text to speech.
•
Accessing Exchange calendars by phone, which allows you to hear a list of upcoming meetings,
send a message to the meeting organizer or the meeting participants, and so on.
•
Importing Exchange contacts, which can be used in Unity Connection personal call transfer rules
and when users place outgoing calls by using voice commands.
If you are upgrading from Unity Connection 9.0 and if Unity Connection is accessing Exchange email,
calendars, or contacts, the features stop working until you reconfigure them. The task list tells you when
in the upgrade process to reconfigure these features.
Task List for Upgrading Unity Connection 9.0 Software to the
Shipping 9.1 Version Without a Unity Connection Cluster
Do the following tasks to upgrade an existing Unity Connection 9.0 server to the shipping 9.1 version
when no Unity Connection cluster is configured.
1.
If you are upgrading Unity Connection 9.0 on a Cisco MCS 7825-H3 server or the equivalent HP
DL320G5: Confirm that you have a 128 GB or larger USB flash drive or external hard disk.
During the upgrade, disk drives in the Unity Connection server are converted from hardware-based
RAID to software-based RAID. Before the RAID conversion, the USB drive is reformatted, and data
and voice messages on the Unity Connection server are copied to the drive. After the RAID
reconfiguration, data and voice messages are copied back to the disk drives in the Unity Connection
server.
Caution
Do not use a USB drive that contains data that you want to keep. During the upgrade, the USB
drive is reformatted, and all existing data on the drive is destroyed.
Upgrade Guide for Cisco Unity Connection Release 9.x
2-3
Chapter 2 Upgrading Cisco Unity Connection 9.0 to the Shipping Cisco Unity Connection 9.1 Version
Task List for Upgrading Unity Connection 9.0 Software to the Shipping 9.1 Version Without a Unity Connection Cluster
2.
Review the list of features that are disabled or that have limited functionality during the upgrade.
See the “Status of Unity Connection Features During an Upgrade from Unity Connection 9.0 to
Unity Connection 9.1” section on page 2-2.
3.
Review the list of features that stop working until you reconfigure them. See the “Features that You
Must Reconfigure When You Upgrade from Unity Connection 9.0” section on page 2-3.
4.
If you are upgrading from Unity Connection 9.0 to Unity Connection 9.1: Run the CLI command
run cuc preupgrade test to verify the prerequisites before running the upgrade.
5.
See the applicable version of Release Notes for Cisco Unity Connection for any additional
information on upgrading to the shipping version. In particular, note the items in the “Installation
and Upgrade Information” section. Release notes are available at
http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html.
6.
Obtain the license files for the upgrade to Unity Connection 9.1. Do not install them now; you do so
later in the upgrade process. See the “Managing Licenses in Cisco Unity Connection 9.x” chapter
of the System Administration Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/guide/9xcucsagx
.html.
7.
If the Unity Connection server has languages other than English-United States installed and you
want to continue using the languages: Download the applicable Unity Connection 9.1 language
files. See the “Downloading Unity Connection 9.x Language Files” section on page 9-3.
Caution
When languages other than English-United States are installed and in use on the
Unity Connection server, you must install the Unity Connection 9.1 versions of the same
languages later during the upgrade. Otherwise, the Unity Connection conversation will not
function properly for all users.
8.
If you do not have a backup from replacing hard disks or replacing the server: Back up the server
by using the Disaster Recovery System. For more information, see the applicable Disaster Recovery
System Administration Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
9.
If you are upgrading during nonbusiness hours: Run the CLI command utils iothrottle disable to
speed up the upgrade.
In an effort to prevent upgrades from adversely affecting system performance during business hours,
the upgrade process is throttled and may take several hours to complete. If you are upgrading during
a maintenance window, you can speed up the upgrade by disabling the throttling. This decreases the
time required for the upgrade to complete but adversely affects Unity Connection performance. For
more information, see the applicable Command Line Interface Reference Guide for Cisco Unified
Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
10. Upgrade the Unity Connection software. See the applicable section:
•
Upgrading Unity Connection 9.0 Software to the Shipping 9.1 Version from a Local DVD,
page 2-12
•
Upgrading Unity Connection 9.0 Software to the Shipping 9.1 Version from a Network
Location, page 2-13
11. If you disabled the upgrade throttle in Task 9.: Run the CLI command utils iothrottle enable to
re-enable the throttle. For more information, see the applicable Command Line Interface Reference
Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
Upgrade Guide for Cisco Unity Connection Release 9.x
2-4
Chapter 2
Upgrading Cisco Unity Connection 9.0 to the Shipping Cisco Unity Connection 9.1 Version
Task List for Upgrading Unity Connection 9.0 Software to the Shipping 9.1 Version in a Unity Connection Cluster
12. Switch to the upgraded software on the Unity Connection server. See the “Switching to the
Upgraded Version of Unity Connection 9.x Software” section on page 3-29.
13. If the Unity Connection server has languages other than English-United States installed, and you
want to continue using the languages: See the “Installing Unity Connection 9.x Language Files”
section on page 9-4.
If you are installing Japanese and you want Cisco Unity Connection Administration to be localized,
you must also install the Cisco Unified Communications Manager Japanese user locale. See the
“Locale Installation” section in the “Software Upgrades” chapter of the applicable Cisco Unified
Communications Operating System Administration Guide at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
If you are installing other languages and you want the Cisco Personal Communications Assistant to
be localized, you must also install the corresponding Cisco Unified Communications Manager user
locales. See the “Locale Installation” section in the “Software Upgrades” chapter of the applicable
Cisco Unified Communications Operating System Administration Guide at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
14. If you are upgrading from Unity Connection 9.0 to the shipping Unity Connection 9.1 version, and
if any of the following are true: Configure unified messaging, or review and update unified
messaging settings, as applicable.
– You were using text to speech to access Exchange email before the upgrade.
– You were accessing Exchange calendars by phone before the upgrade.
– You were using Exchange contacts for personal call transfer rules or voice commands before
the upgrade.
– You were accessing MeetingPlace calendars before the upgrade.
– You want to synchronize Unity Connection and Exchange mailboxes (single inbox).
For more information, see the applicable chapters in the Unified Messaging Guide for Cisco Unity
Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/unified_messaging/guide/9xcuc
umgx.html.
15. If you configured single inbox in Task and you want full single-inbox functionality: Do the following
tasks:
a. If Outlook on user workstations is currently configured to access Unity Connection voice
messages via IMAP, delete the IMAP profile from Outlook.
b. Install or upgrade to Cisco Unity Connection ViewMail for Microsoft Outlook Release 9.x on
user workstations, and configure ViewMail to access Unity Connection voice messages in
Exchange
Task List for Upgrading Unity Connection 9.0 Software to the
Shipping 9.1 Version in a Unity Connection Cluster
Revised December 13, 2013
As the upgrade software is installed, the publisher and subscriber servers continue answering calls and
replication occurs. After the upgrade is complete, you switch the two servers, one at a time, to the
upgraded software.
Upgrade Guide for Cisco Unity Connection Release 9.x
2-5
Chapter 2 Upgrading Cisco Unity Connection 9.0 to the Shipping Cisco Unity Connection 9.1 Version
Task List for Upgrading Unity Connection 9.0 Software to the Shipping 9.1 Version in a Unity Connection Cluster
Note
Note
The following details about how Unity Connection functions during the switch:
•
When you switch the publisher server to the upgraded software, the subscriber server answers all
calls, but replication does not occur and messages may not be available.
•
When you switch the subscriber server to the upgraded software, the publisher server answers all
calls, but replication does not occur and messages may not be available.
•
About 15 minutes after both servers are switched to the upgraded software, both servers answer
calls, replication resumes, and messages are available.
The following considerations about the upgrade process:
•
Messages that are recorded while switching to the upgraded software are not replicated. This means
that, depending on the Unity Connection server that is accessed, a user may briefly not be able to
retrieve new messages. After the upgrade process is complete, messages are replicated. When
replication is complete, all messages are available regardless of which Unity Connection server is
accessed.
•
MWIs and notifications may not be sent. MWIs and notifications synchronize only after the upgrade
process is complete.
To follow the upgrade process through the CLI interface, see the utils system upgrade command at the
Command Line Interface Reference Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
Do the following tasks to upgrade the publisher and subscriber servers in a Unity Connection 9.0 cluster
to the shipping Unity Connection 9.1 version.
1.
If you are upgrading Unity Connection 9.0 on a Cisco MCS 7825-H3 server or the equivalent HP
DL320G5: Confirm that you have a 128 GB or larger USB flash drive or external hard disk.
During the upgrade, disk drives in the Unity Connection server are converted from hardware-based
RAID to software-based RAID. Before the RAID conversion, the USB drive is reformatted, and data
and voice messages on the Unity Connection server are copied to the drive. After the RAID
reconfiguration, data and voice messages are copied back to the disk drives in the Unity Connection
server.
Caution
Note
Do not use a USB drive that contains data that you want to keep. During the upgrade, the USB
drive is reformatted, and all existing data on the drive is destroyed.
2.
If you are upgrading to Unity Connection 9.1: Confirm the status of publisher and subscriber servers
as active. To confirm the server status, navigate to Cisco Unity Connection Serviceability> Tools>
Cluster Management. In addition, you need to confirm the running state of database replication,
run the CLI command show cuc cluster status. For more information, see the applicable section
in the Command Line Interface Reference Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html
•
The status of publisher server should be primary and subscriber server should be secondary.
•
You should always upgrade the publisher server first, and then the subscriber server.
3.
Review the list of features that are disabled or that have limited functionality during the upgrade.
See the “Status of Unity Connection Features During an Upgrade from Unity Connection 9.0 to
Unity Connection 9.1” section on page 2-2.
Upgrade Guide for Cisco Unity Connection Release 9.x
2-6
Chapter 2
Upgrading Cisco Unity Connection 9.0 to the Shipping Cisco Unity Connection 9.1 Version
Task List for Upgrading Unity Connection 9.0 Software to the Shipping 9.1 Version in a Unity Connection Cluster
4.
Review the list of features that stop working until you reconfigure them. See the “Features that You
Must Reconfigure When You Upgrade from Unity Connection 9.0” section on page 2-3.
5.
If you are upgrading from Unity Connection 9.0 to Unity Connection 9.1: Run the CLI command
run cuc preupgrade test to verify the prerequisites before running the upgrade.
6.
See the applicable version of Release Notes for Cisco Unity Connection for any additional
information on upgrading to the shipping version. In particular, note the items in the “Installation
and Upgrade Information” section. Release notes are available at
http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html.
7.
If the Unity Connection server has languages other than English-United States installed and you
want to continue using the languages: Download the applicable Unity Connection 9.1 language
files. See the “Downloading Unity Connection 9.x Language Files” section on page 9-3.
Caution
If languages other than English-United States are installed and in use on the Unity Connection
server, you must install the Unity Connection 9.1 versions of the same languages later during
the upgrade. Otherwise, the Unity Connection conversation will not function properly for all
users.
8.
If you are upgrading from Unity Connection 9.1 and you are adding memory to the current
Unity Connection server: See the “Installing a Memory Upgrade or Replacing All Hard Disks to
Support Unity Connection 9.1 (Selected Servers Only)” section on page 2-9.
9.
If you do not have a database backup befre replacing the hard disks or the server: Back up the
publisher server by using the Disaster Recovery System. For more information, see the applicable
Disaster Recovery System Administration Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
10. If you are upgrading during nonbusiness hours: On the publisher server, run the CLI command utils
iothrottle disable to speed up the upgrade.
In an effort to prevent upgrades from adversely affecting system performance during business hours,
the upgrade process is throttled and may take several hours to complete. If you are upgrading during
a maintenance window, you can speed up the upgrade by disabling the throttling. This decreases the
time required for the upgrade to complete but adversely affects Unity Connection performance. For
more information, see the applicable Command Line Interface Reference Guide for Cisco Unified
Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
Caution
You cannot disable throttling while an upgrade is running. If you decide to disable throttling
after you start an upgrade, you must stop the upgrade, disable throttling, and restart the
upgrade from the beginning.
11. Upgrade the Unity Connection software on the publisher server. See the applicable section:
•
Upgrading Unity Connection 9.0 Software to the Shipping 9.1 Version from a Local DVD,
page 2-12
•
Upgrading Unity Connection 9.0 Software to the Shipping 9.1 Version from a Network
Location, page 2-13
Caution
Do not restart the publisher server and do not switch to the upgraded software during this task.
Otherwise, the Unity Connection cluster will not function correctly.
Upgrade Guide for Cisco Unity Connection Release 9.x
2-7
Chapter 2 Upgrading Cisco Unity Connection 9.0 to the Shipping Cisco Unity Connection 9.1 Version
Task List for Upgrading Unity Connection 9.0 Software to the Shipping 9.1 Version in a Unity Connection Cluster
If the phone system is routing calls to the subscriber server, outside callers and Unity Connection
users can leave voice messages, but the messages are not immediately delivered to user mailboxes.
12. If you are upgrading during nonbusiness hours: On the subscriber server, run the CLI command utils
iothrottle disable to speed up the upgrade.
13. On the subscriber server, confirm that the publisher server has Primary status and that the subscriber
server has Secondary status. For instructions, see the “Administering a Cisco Unity Connection 9.x
Cluster” chapter of the Cluster Configuration and Administration Guide for Cisco Unity Connection
at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/cluster_administration/guide/9.h
tml.
14. Confirm that the publisher server is taking calls and delivering voice messages to users.
15. Upgrade the Unity Connection software on the subscriber server. See the applicable section:
•
Upgrading Unity Connection 9.0 Software to the Shipping 9.1 Version from a Local DVD,
page 2-12
•
Upgrading Unity Connection 9.0 Software to the Shipping 9.1 Version from a Network
Location, page 2-13
Caution
Do not restart the subscriber server and do not switch to the upgraded software during this
task. Otherwise, the Unity Connection cluster will not function correctly.
If the phone system is routing calls to the publisher server, outside callers and Unity Connection
users can leave voice messages. Messages are immediately delivered to user mailboxes.
16. Switch to the upgraded software on the publisher server. See the “Switching to the Upgraded Version
of Unity Connection 9.x Software” section on page 3-29.
17. On the publisher server wait for the services to start and then switch on the subscriber server. See
the “Switching to the Upgraded Version of Unity Connection 9.x Software” section on page 3-29.
18. On the publisher server, confirm that the publisher server has Primary status and that the subscriber
server has Secondary status. For instructions, see the “Administering a Cisco Unity Connection 9.x
Cluster” chapter of the Cluster Configuration and Administration Guide for Cisco Unity Connection
at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/cluster_administration/guide/9x
cuccagx.html.
19. Switch to the upgraded software on the subsubcriber server. See the “Switching to the Upgraded
Version of Unity Connection 9.x Software” section on page 3-29.
20. On the subscriber server, confirm that the publisher server has Primary status and that the subscriber
server has Secondary status. For instructions, see the “Administering a Cisco Unity Connection 9.x
Cluster” chapter of the Cluster Configuration and Administration Guide for Cisco Unity Connection
at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/cluster_administration/guide/9x
cuccagx.html.
21. Install Unity Connection 9.1 languages obtained in Task 7., if applicable. See the “Installing Unity
Connection 9.x Language Files” section on page 9-4.
Install languages on the publisher server first, then on the subscriber server.
Upgrade Guide for Cisco Unity Connection Release 9.x
2-8
Chapter 2
Upgrading Cisco Unity Connection 9.0 to the Shipping Cisco Unity Connection 9.1 Version
Installing a Memory Upgrade or Replacing All Hard Disks to Support Unity Connection 9.1 (Selected Servers Only)
If you are installing Japanese and you want Cisco Unity Connection Administration to be localized,
you must also install the Cisco Unified Communications Manager Japanese locale. See the “Locale
Installation” section in the “Software Upgrades” chapter of the applicable Cisco Unified
Communications Operating System Administration Guide at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
If you are installing other languages and you want the Cisco Personal Communications Assistant to
be localized, you must also install the corresponding Cisco Unified Communications Manager
locales. See the “Locale Installation” section in the “Software Upgrades” chapter of the applicable
Cisco Unified Communications Operating System Administration Guide at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
22. If you are upgrading from Unity Connection 9.0 to the shipping Unity Connection 9.1 version, and
if any of the following are true: Configure unified messaging, or review and update unified
messaging settings, as applicable.
– You were using text to speech to access Exchange email before the upgrade.
– You were accessing Exchange calendars by phone before the upgrade.
– You were using Exchange contacts for personal call transfer rules or voice commands before
the upgrade.
– You were accessing MeetingPlace calendars before the upgrade.
– You want to synchronize Unity Connection and Exchange mailboxes (single inbox).
For more information, see the applicable chapters in the Unified Messaging Guide for Cisco Unity
Connection Release 9.0 at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/unified_messaging/guide/9xcuc
umgx.html.
23. If you configured single inbox in Task 22. and you want full single-inbox functionality: Do the
following tasks:
a. If Outlook on user workstations is currently configured to access Unity Connection voice
messages via IMAP, delete the IMAP profile from Outlook.
b. Install or upgrade to Cisco Unity Connection ViewMail for Microsoft Outlook Release 9.0 on
user workstations, and configure ViewMail to access Unity Connection voice messages in
Exchange.
Installing a Memory Upgrade or Replacing All Hard Disks to
Support Unity Connection 9.1 (Selected Servers Only)
Note
If you are upgrading a server that does not require a memory upgrade or a hard-disk replacement, skip
this section.
For information on your Unity Connection server, see the applicable server-specific table in the
Cisco Unity Connection 9.<x> Supported Platforms List at
http://www.cisco.com/en/US/products/ps6509/products_data_sheets_list.html.
Warning
Before working on a system that has an on/off switch, turn OFF the power and unplug the power cord.
Statement 1
Upgrade Guide for Cisco Unity Connection Release 9.x
2-9
Chapter 2 Upgrading Cisco Unity Connection 9.0 to the Shipping Cisco Unity Connection 9.1 Version
Installing a Memory Upgrade or Replacing All Hard Disks to Support Unity Connection 9.1 (Selected Servers Only)
Warning
Before opening the chassis, disconnect the telephone-network cables to avoid contact with
telephone-network voltages. Statement 2
Warning
This equipment is to be installed and maintained by service personnel only as defined by AS/NZS 3260
Clause 1.2.14.3 Service Personnel. Statement 88
Warning
During this procedure, wear grounding wrist straps to avoid ESD damage to the card. Do not directly
touch the backplane with your hand or any metal tool, or you could shock yourself. Statement 94
Warning
The safety cover is an integral part of the product. Do not operate the unit without the safety cover
installed. Operating the unit without the cover in place will invalidate the safety approvals and pose
a risk of fire and electrical hazards. Statement 117
Warning
Do not work on the system or connect or disconnect cables during periods of lightning activity.
Statement 1001
Warning
Read the installation instructions before connecting the system to the power source. Statement 1004
Warning
To prevent bodily injury when mounting or servicing this unit in a rack, you must take special
precautions to ensure that the system remains stable. The following guidelines are provided to ensure
your safety:
• This unit should be mounted at the bottom of the rack if it is the only unit in the rack.
• When mounting this unit in a partially filled rack, load the rack from the bottom to the top with the
heaviest component at the bottom of the rack.
• If the rack is provided with stabilizing devices, install the stabilizers before mounting or servicing
the unit in the rack. Statement 1006
Warning
There is the danger of explosion if the battery is replaced incorrectly. Replace the battery only with
the same or equivalent type recommended by the manufacturer. Dispose of used batteries according
to the manufacturer’s instructions. Statement 1015
Warning
This unit is intended for installation in restricted access areas. A restricted access area can be
accessed only through the use of a special tool, lock and key, or other means of security. Statement
1017
Warning
To avoid electric shock, do not connect safety extra-low voltage (SELV) circuits to telephone-network
voltage (TNV) circuits. LAN ports contain SELV circuits, and WAN ports contain TNV circuits. Some
LAN and WAN ports both use RJ-45 connectors. Use caution when connecting cables. Statement 1021
Upgrade Guide for Cisco Unity Connection Release 9.x
2-10
Chapter 2
Upgrading Cisco Unity Connection 9.0 to the Shipping Cisco Unity Connection 9.1 Version
Installing a Memory Upgrade or Replacing All Hard Disks to Support Unity Connection 9.1 (Selected Servers Only)
Warning
To reduce the risk of fire, use only No. 26 AWG or larger telecommunication line cord. Statement 1023
Warning
This equipment must be grounded. Never defeat the ground conductor or operate the equipment in the
absence of a suitably installed ground conductor. Contact the appropriate electrical inspection
authority or an electrician if you are uncertain that suitable grounding is available. Statement 1024
Warning
Blank faceplates and cover panels serve three important functions: they prevent exposure to
hazardous voltages and currents inside the chassis; they contain electromagnetic interference (EMI)
that might disrupt other equipment; and they direct the flow of cooling air through the chassis. Do not
operate the system unless all cards, faceplates, front covers, and rear covers are in place. Statement
1029
Warning
Only trained and qualified personnel should be allowed to install, replace, or service this equipment.
Statement 1030
Warning
Ultimate disposal of this product should be handled according to all national laws and regulations.
Statement 1040
(For translations of the preceding safety warnings, see Regulatory Compliance and Safety Information
for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/regulatory/compliance/ucwarns.html.)
To Install a Memory Upgrade or Replace All Hard Disks to Support Unity Connection 9.1 (Selected Servers Only)
Step 1
Remove the cover.
Step 2
If you are not installing a memory upgrade, skip to Step 3.
Install the memory modules in the applicable slots or locations, depending on the server model, as
documented in the Cisco Unity Connection 9.<x> Supported Platforms List at
http://www.cisco.com/en/US/products/ps6509/products_data_sheets_list.html.
Caution
Step 3
If you install new memory modules in the wrong slots, the server and operating system may
not recognize that they have been installed, and Cisco Unity Connection performance may
suffer.
If you are not replacing hard disks, skip to Step 4.
Replace all of the hard disks in the server.
Upgrade Guide for Cisco Unity Connection Release 9.x
2-11
Chapter 2 Upgrading Cisco Unity Connection 9.0 to the Shipping Cisco Unity Connection 9.1 Version
Upgrading Unity Connection 9.0 Software to the Shipping 9.1 Version from a Local DVD
Caution
Step 4
You must remove existing hard disks and install exactly as many hard disks as you remove, or
Cisco Unity Connection installation will fail.
a.
Make note of the current locations of the hard disks in the server, including which hard disk is in
which hard disk slot. If the replacement fails and you want to revert to the current configuration, you
must put the existing hard disks back into their current locations.
b.
Remove the drive trays from the server.
c.
Remove the old hard disks from the drive trays.
d.
Insert the new hard disks into the drive trays.
e.
Reinstall the drive trays in the locations that you made note of in Step a.
Reattach the cover.
Upgrading Unity Connection 9.0 Software to the Shipping 9.1
Version from a Local DVD
Revised March 5, 2013
To upgrade Unity Connection from a local DVD, you can do either of the following:
Warning
Tip
•
Use a DVD shipped from Cisco.
•
Download a signed .iso file from Cisco.com, and burn a disc image of the downloaded software.
Burning a disc image extracts the files from the .iso file that you downloaded and writes them to a
DVD.
Unity ConnectionBe aware that when you mount an ISO file through the VM console, VMware does
not eject the disc at the end of the install process.
Always mount your DVD ISO file from the Edit Settings menu in VMware.
To follow the upgrade process through the CLI interface, see the utils system upgrade command at the
Command Line Interface Reference Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
Caution
If you are upgrading a cluster, do not start the upgrade on the subscriber server until after the upgrade
of the publisher server is complete, or all Unity Connection functionality on both servers will be disabled
until the upgrade of the publisher server completes. In addition, the upgrade of the subscriber server will
fail, and you will have to upgrade the subscriber server again.
To Upgrade Unity Connection 9.0 Software to the Shipping 9.1 Version from a Local DVD
Step 1
Insert the DVD that contains Unity Connection into the disc drive on the Cisco Unity Connection server.
Step 2
Sign in to Cisco Unified Operating System Administration.
Upgrade Guide for Cisco Unity Connection Release 9.x
2-12
Chapter 2
Upgrading Cisco Unity Connection 9.0 to the Shipping Cisco Unity Connection 9.1 Version
Upgrading Unity Connection 9.0 Software to the Shipping 9.1 Version from a Network Location
If you are upgrading the subscriber server in a Unity Connection cluster, you can only access Cisco
Unified Operating System Administration by browsing to:
http://<Unity Connection_servername>/cmplatform
Step 3
From the Software Upgrades menu, select Install/Upgrade.
Step 4
On the Software Installation/Upgrade page, in the Source field, select DVD/CD.
Step 5
In the Directory field, enter a forward slash (/).
Step 6
Select Next.
Step 7
Select the upgrade version that you want to install, and select Next. The upgrade file is copied to the
hard disk on the Unity Connection server. When the file is copied, a screen displays the checksum value.
Step 8
Verify the checksum.
Step 9
On the next page, monitor the progress of the upgrade.
If you lose your connection with the remote server or close your browser during this step, you may see
the following message when you try to view the Software Installation/Upgrade page again:
Warning: Another session is installing software, click Assume Control to take over the installation.
To continue monitoring the upgrade, select Assume Control.
You can also monitor the upgrade by using the Real-Time Monitoring Tool.
Step 10
Note
Select Next.
•
For without a Unity Connection cluster, you can select either the manual switch version or the
automatic switch version option.
•
For a Unity Connection cluster, you need to select the manual switch version option,
During the initial phase of the upgrade, the Installation Log text box in Cisco Unified Operating System
Administration is updated with information on the progress of the upgrade, but updates stop after the
server automatically restarts for the first time. To determine when the upgrade is complete, view the
console for the Unity Connection server: the console screen displays a message indicating that the
installation is complete, and the login prompt for the command-line interface appears.
Step 11
To verify the success of the upgrade, run the CLI command show cuc version. The upgrade succeeded
if the active partition has the upgraded version and the inactive partition has the old version.
Upgrading Unity Connection 9.0 Software to the Shipping 9.1
Version from a Network Location
To upgrade Unity Connection from a network location, you must download a signed .iso file from
Cisco.com, and copy the .iso file to an FTP or SFTP server. Unity Connection does not allow you to
upgrade by copying either the contents of a DVD shipped from Cisco or the extracted contents of a
downloaded .iso file to an FTP or SFTP server. This helps prevent someone from attempting to upgrade
by using software that has been tampered with.
Upgrade Guide for Cisco Unity Connection Release 9.x
2-13
Chapter 2 Upgrading Cisco Unity Connection 9.0 to the Shipping Cisco Unity Connection 9.1 Version
Upgrading Unity Connection 9.0 Software to the Shipping 9.1 Version from a Network Location
To follow the upgrade process through the CLI interface, see the utils system upgrade command at the
Command Line Interface Reference Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
Caution
If you are upgrading a cluster, do not start the upgrade on the subscriber server until after the upgrade
of the publisher server is complete, or all Unity Connection functionality on both servers will be disabled
until the upgrade of the publisher server completes. In addition, the upgrade of the subscriber server will
fail, and you will have to upgrade the subscriber server again.
To Upgrade Unity Connection 9.0 Software to the Shipping 9.1 Version from a Network Location
Step 1
Copy the upgrade file to a folder on an FTP or SFTP server that the Cisco Unity Connection server can
access.
Step 2
Sign in to Cisco Unified Operating System Administration.
If you are upgrading the subscriber server in a Unity Connection cluster, you can only access Cisco
Unified Operating System Administration by browsing to:
http://<Unity Connection_servername>/cmplatform
Step 3
From the Software Upgrades menu, select Install/Upgrade.
Step 4
On the Software Installation/Upgrade page, in the Source field, select Remote Filesystem.
Step 5
In the Directory field, enter the path to the folder that contains the upgrade file.
If the upgrade file is located on a Linux or Unix server, you must enter a forward slash (/) at the beginning
of the folder path. (For example, if the upgrade file is in the upgrade folder, you must enter /upgrade.)
If the upgrade file is located on a Windows server, you must use the applicable syntax for an FTP or
SFTP server such as:
•
The path must begin with a forward slash (/) and contain forward slashes throughout instead of
backward slashes (\).
•
The path must start from the FTP or SFTP root folder on the server and must not include a Windows
absolute path, which starts with a drive letter (for example, C:).
Step 6
In the Server field, enter the server name or IP address.
Step 7
In the User Name field, enter the alias that will be used to sign in to the remote server.
Step 8
In the User Password field, enter the password that will be used to sign in to the remote server.
Step 9
In the Transfer Protocol field, select the applicable transfer protocol.
Step 10
Select Next.
Step 11
Select the upgrade version that you want to install and select Next. The upgrade file is copied to the hard
disk on the Unity Connection server. When the file is copied, a screen displays the checksum value.
Step 12
Verify the checksum.
Step 13
On the next page, monitor the progress of the upgrade.
If you lose your connection with the remote server or close your browser during this step, you may see
the following message when you try to view the Software Installation/Upgrade page again:
Warning: Another session is installing software, click Assume Control to take over the installation.
To continue monitoring the upgrade, select Assume Control.
You can also monitor the upgrade by using the Real-Time Monitoring Tool.
Upgrade Guide for Cisco Unity Connection Release 9.x
2-14
Chapter 2
Upgrading Cisco Unity Connection 9.0 to the Shipping Cisco Unity Connection 9.1 Version
Upgrading Unity Connection 9.0 Software to the Shipping 9.1 Version from a Network Location
Step 14
Note
Select Next.
•
For without a Unity Connection cluster, you can select either the manual switch version or the
automatic switch version option.
•
For a Unity Connection cluster, you need to select the manual switch version option,
During the initial phase of the upgrade, the Installation Log text box in Cisco Unified Operating System
Administration is updated with information on the progress of the upgrade, but updates stop after the
server automatically restarts for the first time. To determine when the upgrade is complete, view the
console for the Unity Connection server: the console screen displays a message indicating that the
installation is complete, and the login prompt for the command-line interface appears.
Step 15
To verify the success of the upgrade, run the CLI command show cuc version. The upgrade succeeded
if the active partition has the upgraded version and the inactive partition has the old version.
Upgrade Guide for Cisco Unity Connection Release 9.x
2-15
Chapter 2 Upgrading Cisco Unity Connection 9.0 to the Shipping Cisco Unity Connection 9.1 Version
Upgrading Unity Connection 9.0 Software to the Shipping 9.1 Version from a Network Location
Upgrade Guide for Cisco Unity Connection Release 9.x
2-16
CH A P T E R
3
Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or
8.6 to the Shipping 9.x Version
This chapter contains the following sections:
•
About Upgrades to Unity Connection 9.x, page 3-2
•
Status of Unity Connection Features During an Upgrade from Unity Connection 7.x, 8.0, or 8.5 to
Unity Connection 9.x, page 3-2
•
Features that You Must Reconfigure When You Upgrade to Unity Connection 9.x, page 3-3
•
Duration of an Upgrade Unity Connection 7.x, 8.0, or 8.5 to Unity Connection 9.x, page 3-4
•
Migrating Licenses to Cisco Unity Connection Surviable Remote Site VoiceMail 9.x, page 3-4
•
Task List for Upgrading Unity Connection 7.x, 8.0, or 8.5 Software to the Shipping 9.x Version
Without a Unity Connection Cluster, page 3-6
•
Task List for Upgrading Unity Connection 7.x, 8.0, or 8.5 Software to the Shipping 9.x Version in
a Unity Connection Cluster, page 3-11
•
Task List for Upgrading Unity Connection 8.6 Software to the Shipping 9.x Version Without a
Unity Connection Cluster, page 3-16
•
Task List for Upgrading Unity Connection 8.6 Software to the Shipping 9.x Version in a Unity
Connection Cluster, page 3-18
•
Installing a Memory Upgrade or Replacing All Hard Disks to Support Unity Connection 9.x
(Selected Servers Only), page 3-22
•
Installing the Cisco Option Package that Is Required to Upgrade from Unity Connection 7.x, 8.0, or
8.5 to the Shipping 9.x Version, page 3-25
•
Upgrading Unity Connection 7.x, 8.0, 8.5, or 8.6 Software to the Shipping 9.x Version from a Local
DVD, page 3-27
•
Upgrading Unity Connection 7.x, 8.0, 8.5, or 8.6 Software to the Shipping 9.x Version from a
Network Location, page 3-28
•
Switching to the Upgraded Version of Unity Connection 9.x Software, page 3-29
Upgrade Guide for Cisco Unity Connection Release 9.x
3-1
Chapter 3
Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
About Upgrades to Unity Connection 9.x
About Upgrades to Unity Connection 9.x
The following points should be considered when upgrading from Unity Connection 7.x, 8.0, or 8.5 to version 9.x:
•
If you have never upgraded the Unity Connection server before, the upgrade copies the new version
to an empty partition.
•
If you have upgraded the Unity Connection server before, the upgrade copies the new version to the
inactive partition, which usually contains a version of Unity Connection older than the version that
is running on the active partition. (If you previously upgraded to a later version and then reverted to
the older version, the inactive partition includes a version of Unity Connection later than the version
that is currently running.) The software that was on the inactive partition before you started the
upgrade is overwritten.
•
Depending on your current version, you may be required to upgrade twice to reach the desired
version. In that case, the current version is no longer available when the upgrade is complete because
the partition that contains the current version will be overwritten by the second upgrade.
•
If you are upgrading a Cisco MCS 7825-H3 server (or the equivalent HP DL320G5), Unity
Connection must reformat the hard disk to convert from hardware-based RAID to software-based
RAID. When the upgrade is complete, only the latest version of Unity Connection will be available
on the hard disk.
•
While upgrading an MCS 7825-H3 or HP DL320G5 server, Unity Connection saves data and voice
messages to an external drive. You must have a 128 GB or larger USB flash drive or external hard
disk to perform the upgrade for these servers.
The following points should be considered when upgrading from Unity Connection 8.6 to version 9.x:
•
If you have never upgraded the Unity Connection server before, the upgrade copies the new version
to an empty partition.
•
If you have upgraded the Unity Connection server before, the upgrade copies the new version to the
inactive partition, which usually contains a version of Unity Connection older than the version that
is running on the active partition. (If you previously upgraded to a later version and then reverted to
the older version, the inactive partition includes a version of Unity Connection later than the version
that is currently running.) The software that was on the inactive partition before you started the
upgrade is overwritten.
•
Depending on your current version, you may be required to upgrade twice to reach the desired
version. In that case, the current version is no longer available when the upgrade is complete because
the partition that contains the current version will be overwritten by the second upgrade.
•
Upgrading a Connection cluster, an upgrade requires approximately four hours.
•
Depending on the data size, switching to the upgraded software may requires some time.
Status of Unity Connection Features During an Upgrade from
Unity Connection 7.x, 8.0, or 8.5 to Unity Connection 9.x
During an upgrade from Unity Connection 7.x, 8.0, or 8.5 to Unity Connection 9.x, if you do not have a
cluster, Unity Connection is completely disabled for the entire duration of the upgrade.
Upgrade Guide for Cisco Unity Connection Release 9.x
3-2
Chapter 3
Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Features that You Must Reconfigure When You Upgrade to Unity Connection 9.x
If you are upgrading a cluster, the upgrade starts on the publisher server. Unity Connection functionality
on the publisher server is completely disabled for the entire duration of the upgrade. Note the following
about the functionality that is available on the subscriber server while the publisher server is being
upgraded:
•
If the phone system is routing calls to the subscriber server, outside callers and Unity Connection
users can leave voice messages, but the messages are not immediately delivered to user mailboxes.
•
Unity Connection users can use the telephone user interface (touchtone conversation ) to listen to
messages that are left before you start the upgrade. However, users cannot listen to messages that
are left during the upgrade, and Unity Connection will not always retain the status of messages. For
example, if a user plays a voice message during the upgrade, the message may be marked as new
again after the upgrade. If a user deletes a message, the message may reappear after the upgrade.
•
Unity Connection users cannot access Unity Connection using graphical user interfaces, for
example, ViewMail for Outlook, Web Inbox, or IMAP email applications.
•
If Unity Connection users use the touchtone conversation to change their user preferences or other
settings during the upgrade, their changes will probably be lost. (There are brief periods during the
upgrade when changes are saved, but identifying those periods is difficult at best.)
•
Cisco Unified Operating System Administration is available, but other administration user
interfaces, for example, Connection Administration and Cisco Unity Connection Serviceability, are
not available. In addition, custom administration interfaces that were developed by using the Unity
Connection administration API are also not available.
•
Intrasite and intersite networking is disabled for the duration of the upgrade. Directory changes
made on other nodes in the network are not replicated to the server or cluster that you are upgrading
until after the upgrade is complete.
When the upgrade of the publisher server is complete, full functionality is restored on the publisher
server.
When you start the upgrade on the subscriber server in a cluster:
•
Messages that were left on the subscriber server are copied to the publisher server, and the publisher
server begins to deliver the messages to user mailboxes.
•
Unity Connection functionality on the subscriber server is completely disabled for the entire
duration of the upgrade.
While the subscriber server is being upgraded, messages that are left on the publisher server are
delivered to user mailboxes on the publisher server. When the upgrade of the subscriber server is
complete, the messages are replicated to the subscriber server and are delivered to user mailboxes on the
subscriber server. If single inbox is configured, messages are synchronized to Exchange after they are
delivered to user mailboxes. If a large number of messages were left during the upgrade, there may be a
significant delay before message delivery, replication, and synchronization with Exchange.
Features that You Must Reconfigure When You Upgrade to Unity
Connection 9.x
Unity Connection 8.5 included enhancements to the following features, which are now among the
features in Unity Connection unified messaging:
•
Accessing Exchange email by using text to speech.
•
Accessing Exchange calendars by phone, which allows you to hear a list of upcoming meetings,
send a message to the meeting organizer or the meeting participants, and so on.
Upgrade Guide for Cisco Unity Connection Release 9.x
3-3
Chapter 3 Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Duration of an Upgrade Unity Connection 7.x, 8.0, or 8.5 to Unity Connection 9.x
•
Importing Exchange contacts, which can be used in Unity Connection personal call transfer rules
and when users place outgoing calls by using voice commands.
If you are upgrading from Unity Connection 8.0 or earlier and if Unity Connection is accessing
Exchange email, calendars, or contacts, the features stop working until you reconfigure them. The task
list tells you when in the upgrade process to reconfigure these features.
Duration of an Upgrade Unity Connection 7.x, 8.0, or 8.5 to Unity
Connection 9.x
Part of an upgrade to Unity Connection 9.x is a major upgrade to the Linux operating system on the Unity
Connection server, which significantly slows the upgrade process. Under ideal conditions, upgrading a
non-clustered Unity Connection server will take four hours or longer. Under less than ideal conditions,
for example, if you are upgrading from a network drive over a slow network connection, an upgrade
could take several hours longer. Upgrading both servers in a cluster will take roughly twice as long as
upgrading a non-clustered server.
In addition, if you are upgrading Unity Connection on a Cisco MCS 7825-H3 server (or the equivalent
HP DL320G5), the upgrade also converts from hardware-based RAID to software-based RAID, which
requires copying Unity Connection data and voice messages to an external drive. Under ideal conditions,
upgrading a non-clustered 7825-H3 server will take six hours or longer, and upgrading a cluster that
includes two 7825-H3 servers will take roughly twice that long.
You can reduce the duration of an upgrade by having users delete old voice messages and empty their
Unity Connection deleted items folder a few days before you start the upgrade. Deleting voice messages
reduces the duration of all upgrades by at least a little bit because it reduces the amount of data that is
exported. Deleting messages potentially has a much larger effect on the MCS 7825-H3 and
HP DL320G5 servers because the messages themselves are being exported, not just data about the
messages.
Note
By default, when users delete Unity Connection voice messages, the messages are moved to the Unity
Connection deleted items folder, which is also exported during the upgrade. (Messages are moved to the
deleted items folder regardless of how the users deleted the messages, for example, the telephone user
interface, the Cisco Unity Inbox, or an email application when IMAP access to Unity Connection is
configured.) If Unity Connection is configured to move deleted messages to the deleted items folder,
users must delete messages and also empty their Unity Connection deleted items folder to reduce the
number of messages that are exported during the upgrade.
Migrating Licenses to Cisco Unity Connection Surviable Remote
Site VoiceMail 9.x
You need to upgrade licenses while migrating from Cisco Unity or from the earlier versions of Cisco
Unity Connection to Connection 9.x. For more information, see the following sections:
•
Migrating Licenses from Cisco Unity to Cisco Unity Connection Surviable Remote Site VoiceMail
9.x
•
Migrating Licenses from Cisco Unity Unity Connection 7.x or 8.x to Unity Connection 9.x
Upgrade Guide for Cisco Unity Connection Release 9.x
3-4
Chapter 3
Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Migrating Licenses to Cisco Unity Connection Surviable Remote Site VoiceMail 9.x
Migrating Licenses from Cisco Unity to Cisco Unity Connection Surviable
Remote Site VoiceMail 9.x
Migrating licenses from Cisco Unity to Cisco Unity Connection Surviable Remote Site VoiceMail 9.x
involves exporting of legacy license information from Cisco Unity and importing the exported data to
Unity Connection 9.x. The legacy license information from Cisco Unity is exported to the computer
through the export tool of COBRAS. For more information on COBRAS export tool, refer to
http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html link. The exported
data is further imported in Connection 9.x and is stored in Unity Connection 9.x database.
After the completion of importing of legacy license information, Unity Connection 9.x needs to be
configured and synchronized with the ELM server. For more information, refer to the ELM User Guide
at
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/elmuserguide/9_0_1/CUCM_BK_E596FD72
_00_enterprise-license-manager-user-90.html.
Once synchronization is done at ELM server, the legacy license information from Unity Connection 9.x
is sent to the ELM server for migration. Now, you can migrate licenses through the ELM server. For more
information in migrating licenses through the ELM server, refer to the "Migrate licenses using Upgrade
Licenses wizard" section of ELM User Guide.
Migrating Licenses from Cisco Unity Unity Connection 7.x or 8.x to Unity
Connection 9.x
Revised September 18, 2012
You can use either of the following methods to migrate licenses from Cisco Unity Connection Surviable
Remote Site VoiceMail 7.x or 8.x to Connection 9.x:
•
Using COBRAS tool
•
Using Upgrade Process
Using COBRAS Tool
You can use COBRAS tool to migrate licenses from Cisco Unity Connection Surviable Remote Site
VoiceMail 7.x or 8.x to Unity Connection 9.x.
Caution
You must install all provided licenses on Cisco Unity Connection 8.6(2) and earlier releases before you
export the data as only installed license data will be migrated.
Steps for migrating licenses from Cisco Unity Connection 8.6(2) and earlier release to Cisco Unity Connection 9.x
Step 1
Start the COBRAS export tool.
Step 2
Navigate to License Details for Migration to Connection 9.x and later field under Backup Options
tab. Select the License Details for migration to Connection 9.x and later check box on Backup
Options tab for exporting the legacy license data from Cisco Unity. A pop up appears.
Step 3
Enter the CLI credentials and click ok.
Step 4
Browse to the backup location for exporting the legacy license data under select Backup Destination tab.
Upgrade Guide for Cisco Unity Connection Release 9.x
3-5
Chapter 3 Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Task List for Upgrading Unity Connection 7.x, 8.0, or 8.5 Software to the Shipping 9.x Version Without a Unity Connection
Step 5
Note
Click on the Export Data tab to export the legacy license data.
Similarly, you can use COBRAS import tool to import the backup to Unity Connection 9.x. When the
backup data is imported in Unity Connection 9.x, the legacy license information is stored in Unity
Connection 9.x database. For more information on COBRAS tools, refer to
http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html link.
After the completion of uploading of legacy license information, Unity Connection 9.x needs to be
configured and synchronized with the ELM server. For more information, refer to the ELM User Guide
at
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/elmuserguide/9_0_1/CUCM_BK_E596FD72
_00_enterprise-license-manager-user-90.html.
Once synchronization is done at ELM server, the legacy license information from Unity Connection 9.x
is sent to the ELM server for migration. Now, you can migrate licenses through the ELM server. For more
information in migrating licenses through the ELM server, refer to the "Migrate licenses using Upgrade
Licenses wizard" section of ELM user guide.
Using Upgrade Process
If you are upgrading from Cisco Unity Connection Surviable Remote Site VoiceMail 7.x or 8.x to Unity
Connection 9.x., during the upgrade, the legacy license information of the previous version is uploaded
to Unity Connection 9.x database. After the completion of upgrade process, Unity Connection 9.x needs
to be configured and synchronized with the ELM server. For more information, refer to the ELM User
Guide at
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/elmuserguide/9_0_1/CUCM_BK_E596FD72
_00_enterprise-license-manager-user-90.html.
Once Unity Connection 9.x is configured with the ELM server, the legacy information is sent to the ELM
server. Now, you can migrate licenses through the ELM server. For more information in migrating
licenses through the ELM server, refer to the "Migrate licenses using Upgrade Licenses wizard" section
of ELM user guide.
Warning
You must install all pre 9.x licenses to pre 9.x Cisco Unity Connection Surviable Remote Site
VoiceMail and Cisco Unity before you upgrade to Cisco Unity Connection Surviable Remote Site
VoiceMail release 9.x as only the installed license informtation is considered as legacy license data
to migrate licenses. After you upgrade to Release 9.x, you can not apply pre 9.x licenses to Cisco Unity
Connection Surviable Remote Site VoiceMail 9.x and you can not apply them using the Enterprise
License Manager.
Task List for Upgrading Unity Connection 7.x, 8.0, or 8.5 Software
to the Shipping 9.x Version Without a Unity Connection Cluster
Do the following tasks to upgrade an existing Unity Connection 7.x, 8.0, or 8.5 server to the shipping
9.x version when no Unity Connection cluster is configured.
1.
If you are upgrading Unity Connection on a Cisco MCS 7825-H3 server or the equivalent HP
DL320G5: Confirm that you have a 128 GB or larger USB flash drive or external hard disk.
Upgrade Guide for Cisco Unity Connection Release 9.x
3-6
Chapter 3
Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Task List for Upgrading Unity Connection 7.x, 8.0, or 8.5 Software to the Shipping 9.x Version Without a Unity
During the upgrade, disk drives in the Unity Connection server are converted from hardware-based
RAID to software-based RAID. Before the RAID conversion, the USB drive is reformatted, and data
and voice messages on the Unity Connection server are copied to the drive. After the RAID
reconfiguration, data and voice messages are copied back to the disk drives in the Unity Connection
server.
Caution
Do not use a USB drive that contains data that you want to keep. During the upgrade, the USB
drive is reformatted, and all existing data on the drive is destroyed.
2.
Review the list of features that are disabled or that have limited functionality during the upgrade.
See the “Status of Unity Connection Features During an Upgrade from Unity Connection 7.x, 8.0,
or 8.5 to Unity Connection 9.x” section on page 3-2.
3.
Review the list of features that stop working until you reconfigure them. See the “Features that You
Must Reconfigure When You Upgrade to Unity Connection 9.x” section on page 3-3.
4.
Review the applicable Cisco Unity Connection Surviable Remote Site VoiceMail 9.<x> Supported
Platforms List to determine:
•
Whether the current Unity Connection server is supported for Unity Connection 9.x.
•
If the current Unity Connection server is supported, whether it requires replacement hard disks.
•
If the current Unity Connection server is supported, whether it requires additional memory.
The document is available at
http://www.cisco.com/en/US/products/ps6509/products_data_sheets_list.html.
If the server is no longer supported, replace it before you obtain the replacement license files for the
new server.
If you are also migrating Unity Connection from a physical server to a virtual machine, migrate to
the virtual machine and obtain the replacement license files for the virtual machine before you
upgrade.
Warning
5.
See the applicable version of Release Notes for Cisco Unity Connection for any additional
information on upgrading to the shipping version. In particular, note the items in the “Installation
and Upgrade Information” section. Release notes are available at
http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html.
6.
Install the licenses on the existing Unity Connection server before you upgrade to Connection 9.x
server. While upgrade, the legacy license information is uploaded in Unity Connection database. See
the “Migrating Licenses to Cisco Unity Connection Surviable Remote Site VoiceMail 9.x” section.
For more information on Cisco Unity Connection Surviable Remote Site VoiceMail 9.x Licenses,
see the “Managing Licenses in Cisco Unity Connection Surviable Remote Site VoiceMail” chapter
of the System Administration Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/guide/9xcucsagx
.html.
You must install all valid pre 9.x licenses to pre 9.x Cisco Unity Connection Surviable Remote Site
VoiceMail and Cisco Unity before you upgrade to Cisco Unity Connection Surviable Remote Site
VoiceMail release 9.x as only the installed license informtation is considered as legacy license data
to migrate licenses. After you upgrade to Release 9.x, you can not apply pre 9.x licenses to Cisco Unity
Connection Surviable Remote Site VoiceMail 9.x and you can not apply them using the Enterprise
License Manager.
7.
Confirm that you have the software required for the upgrade. Note the following:
Upgrade Guide for Cisco Unity Connection Release 9.x
3-7
Chapter 3 Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Task List for Upgrading Unity Connection 7.x, 8.0, or 8.5 Software to the Shipping 9.x Version Without a Unity Connection
•
You must download the ciscocm.refresh_upgrade.cop (Cisco Option Package) file from
Cisco.com. The .cop file patches your current version of Unity Connection, which is required
before you can upgrade to Unity Connection 9.x. For information on downloading the .cop file
from Cisco.com, see the “Installation and Upgrade Information” section of the applicable
Release Notes for Cisco Unity Connection at
http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html.
•
If you are replacing the Unity Connection server and the server is currently running Unity
Connection 7.0(1) through 7.1(2), you will also need Unity Connection 7.1(3) software.
However, not all Unity Connection 7.x versions earlier than 7.1(3) can be directly upgraded to
Unity Connection 7.1(3), so you may also need software for an intermediate version that can be
upgraded directly to Unity Connection 7.1(3). For information on supported upgrades, see the
“Supported Cisco Unified Communications Manager Upgrades” section of Cisco Unified
Communications Manager Software Compatibility Matrix at
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html.
For 7.x and later versions, Cisco Unified CM and Cisco Unity Connection Surviable Remote
Site VoiceMail version numbers are identical.
Note
Unity Connection 7.1(3) software is required for two reasons. First, some older servers are not
supported for use with Unity Connection 8.x, and an attempt to install or upgrade to Unity
Connection 8.x on these older servers will fail. In addition, Unity Connection software earlier
than version 7.1(3) does not include the drivers required by the new servers. This means you
cannot install Unity Connection earlier than version 7.1(3) on a new server, move data to the
new server by using the Disaster Recovery System, and then upgrade the new server to Unity
Connection 9.x.
•
If you are replacing the Unity Connection server or replacing hard disks in the server, you must
order physical DVDs because the software that you download from Cisco.com cannot be used
for a new install.
•
If you are not replacing the server or replacing hard disks in the server, you can download the
software for the upgrade from Cisco.com. For information on downloading the software from
Cisco.com, see the “Installation and Upgrade Information” section of the applicable Release
Notes for Cisco Unity Connection at
http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html.
If you are not replacing the server or the hard disks in the server, you may still need software
for an upgrade to an intermediate version before you can upgrade to Unity Connection 9.x. For
information on supported upgrades, see the “Supported Cisco Unified Communications
Manager Upgrades” section of Cisco Unified Communications Manager Software Compatibility
Matrix at
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html.
8.
If the Unity Connection server has languages other than English-United States installed and you
want to continue using the languages: Download the applicable Unity Connection 9.x language
files. See the “Downloading Connection 9.x Language Files” section on page 3-1.
Caution
When languages other than English-United States are installed and in use on the Unity
Connection server, you must install the Unity Connection 9.x versions of the same languages
after the upgrade. Otherwise, the Unity Connection conversation will not function properly
for all users.
Upgrade Guide for Cisco Unity Connection Release 9.x
3-8
Chapter 3
Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Task List for Upgrading Unity Connection 7.x, 8.0, or 8.5 Software to the Shipping 9.x Version Without a Unity
9.
Warning
If an intermediate upgrade is required as described in Task 7.: Upgrade Unity Connection as
necessary. For information on how to upgrade from Unity Connection 7.x to a later version of Unity
Connection 7.x, see the “Upgrading Cisco Unity Connection Surviable Remote Site VoiceMail 7.x
to the Shipping 7.x Version” chapter in the Upgrade Guide for Cisco Unity Connection Release 7.x
at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrugx.html.
Do not install the Unity Connection 9.x license files on the Unity Connection 7.x server.
Caution
If the intermediate upgrade includes a major-version upgrade (for example, from 2.x to 7.x),
you must complete the upgrade to Unity Connection 9.x before Unity Connection will
function again. If you want 2.x license data to be sent to 9.x as legacy license information, you
must obtain and install upgrade licenses for the intermediate upgrade.
10. If you are upgrading from Unity Connection 7.x, you are using the current server for Unity
Connection 9.x, and you are replacing hard disks and/or adding memory:
a. Back up the server by using the Disaster Recovery System. You will use this backup to restore
data on the replacement hard disks. For more information, see the Disaster Recovery System
Administration Guide for Cisco Unity Connection Release 7.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/drs_administration/guide/7x
cucdrsag.html.
b. Replace the hard disks and/or add memory. See the “Installing a Memory Upgrade or Replacing
All Hard Disks to Support Unity Connection 9.x (Selected Servers Only)” section on page 3-22.
c. Reinstall the version of Unity Connection that was installed when you backed up the server in
Task 10.a. See the Installation Guide for Cisco Unity Connection Release 7.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/installation/guide/7xcucigx.
html.
d. Restore data on the server by using the DRS backup that you made in Task 10.a.
e. Skip to Task 13.
11. If you are upgrading from Unity Connection 7.x and replacing the Unity Connection server: Replace
the server. See the “Replacing a Single 7.x Server Without a Unity Connection Cluster” section in
the “Replacing Cisco Unity Connection Surviable Remote Site VoiceMail 7.x Servers” chapter in
the Upgrade Guide for Cisco Unity Connection Release 7.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrugx.html.
12. If you do not have a backup from replacing hard disks or replacing the server: Back up the server
by using the Disaster Recovery System. For more information, see the applicable Disaster Recovery
System Administration Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
Caution
If you are upgrading Unity Connection on a Cisco MCS 7825-H3 server or the equivalent
HP DL320G5, you cannot use the revert feature to revert to a previous version after you have
upgraded to Unity Connection 9.x. If you want to revert to a previous version, you must install
that version and then restore data from a DRS backup.
Upgrade Guide for Cisco Unity Connection Release 9.x
3-9
Chapter 3 Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Task List for Upgrading Unity Connection 7.x, 8.0, or 8.5 Software to the Shipping 9.x Version Without a Unity Connection
13. On the Unity Connection server, install the Cisco Option Package that is required for the upgrade to
Unity Connection 9.x. (This is the Cisco Option Package that you downloaded in Task 7.) See the
“Installing the Cisco Option Package that Is Required to Upgrade from Unity Connection 7.x, 8.0,
or 8.5 to the Shipping 9.x Version” section on page 3-25.
14. If Unity Connection is running on a Cisco MCS 7825-H3 server or HP DL320G5 server: Connect a
128-GB or larger USB flash drive or external hard disk to the Unity Connection server.
Caution
Do not use a USB drive that contains data that you want to keep. During the upgrade, the USB
drive is reformatted, and all existing data on the drive is destroyed.
15. Install Unity Connection 9.x languages, if applicable. See the “Installing Connection 9.x Language
Files” section on page 3-2.
If you are installing Japanese and you want Cisco Unity Connection Administration to be localized,
you must also install the Cisco Unified Communications Manager Japanese user locale. See the
“Locale Installation” section in the “Software Upgrades” chapter of the applicable Cisco Unified
Communications Operating System Administration Guide at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
If you are installing other languages and you want the Cisco Personal Communications Assistant to
be localized, you must also install the corresponding Cisco Unified Communications Manager user
locales. See the “Locale Installation” section in the “Software Upgrades” chapter of the applicable
Cisco Unified Communications Operating System Administration Guide at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
16. Upgrade the Unity Connection software. See the applicable section:
•
Upgrading Unity Connection 7.x, 8.0, 8.5, or 8.6 Software to the Shipping 9.x Version from a
Local DVD, page 3-27
•
Upgrading Unity Connection 7.x, 8.0, 8.5, or 8.6 Software to the Shipping 9.x Version from a
Network Location, page 3-28
17. If you are upgrading from Unity Connection 7.x or 8.0 to Unity Connection 9.x or later, and if any
of the following are true: Configure unified messaging, or review and update unified messaging
settings, as applicable.
– You were using text to speech to access Exchange email before the upgrade.
– You were accessing Exchange calendars by phone before the upgrade.
– You were using Exchange contacts for personal call transfer rules or voice commands before
the upgrade.
– You were accessing MeetingPlace calendars before the upgrade.
– You want to synchronize Unity Connection and Exchange mailboxes (single inbox).
For more information, see the applicable chapters in the Unified Messaging Guide for Cisco Unity
Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/unified_messaging/guide/9xcuc
umgx.html.
Note the following:
– External services in Unity Connection 7.x or 8.0 are converted to unified messaging services.
The unified messaging services are enabled, but the default settings may not be the ideal settings
for your Active Directory and Exchange configuration.
Upgrade Guide for Cisco Unity Connection Release 9.x
3-10
Chapter 3
Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Task List for Upgrading Unity Connection 7.x, 8.0, or 8.5 Software to the Shipping 9.x Version in a Unity Connection
– Unity Connection 8.5 no longer uses user passwords that are stored in the Unity Connection
database to access Exchange. Instead, Unity Connection accesses Exchange through one or
more unified messaging accounts that you create in Active Directory.
18. If you configured single inbox in Task 17. and you want full single-inbox functionality: Do the
following tasks:
a. If Outlook on user workstations is currently configured to access Unity Connection voice
messages via IMAP, delete the IMAP profile from Outlook.
b. Install or upgrade to Cisco Unity Connection ViewMail for Microsoft Outlook Release 8.5 on
user workstations, and configure ViewMail to access Unity Connection voice messages in
Exchange.
Task List for Upgrading Unity Connection 7.x, 8.0, or 8.5 Software
to the Shipping 9.x Version in a Unity Connection Cluster
Do the following tasks to upgrade the publisher and subscriber servers in a Unity Connection 7.x, 8.0,
or 8.5 cluster to the shipping Unity Connection 9.x version.
1.
If one or both of the servers in the Unity Connection cluster are Cisco MCS 7825-H3 servers or the
equivalent HP DL320G5: Confirm that you have a 128 GB or larger USB flash drive or external hard
disk.
During the upgrade, disk drives in MCS 7825-H3 or HP DL320 G5 servers are converted from
hardware-based RAID to software-based RAID. Before the RAID conversion, the USB drive is
reformatted, and data and voice messages on the Unity Connection server are copied to the drive.
After the RAID reconfiguration, data and voice messages are copied back to the disk drives in the
Unity Connection server.
Caution
2.
Do not use a USB drive that contains data that you want to keep. During the upgrade, the USB
drive is reformatted, and all existing data on the drive is destroyed.
If you are upgrading to Unity Connection 9.x: Confirm the status of publisher and subscriber servers
as active. To confirm the server status, navigate to Cisco Unity Connection Serviceability> Tools>
Cluster Management. In addition, you need to confirm the running state of database replication, run
the CLI command show cuc cluster status. For more information, see the applicable section in
the Command Line Interface Reference Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html
Note the following:
– The status of publisher server should be primary and subscriber server should be secondary.
– You should always upgrade the publisher server first, and then the subscriber server.
3.
Review the list of features that are disabled or that have limited functionality during the upgrade.
See the “Status of Unity Connection Features During an Upgrade from Unity Connection 7.x, 8.0,
or 8.5 to Unity Connection 9.x” section on page 3-2.
4.
Review the list of features that stop working until you reconfigure them. See the “Features that You
Must Reconfigure When You Upgrade to Unity Connection 9.x” section on page 3-3.
5.
Review the Cisco Unity Connection Surviable Remote Site VoiceMail 9.x Supported Platforms List
to determine:
Upgrade Guide for Cisco Unity Connection Release 9.x
3-11
Chapter 3 Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Task List for Upgrading Unity Connection 7.x, 8.0, or 8.5 Software to the Shipping 9.x Version in a Unity Connection
•
Whether the current Unity Connection server is supported for Unity Connection 9.x.
•
If the current Unity Connection servers are supported, whether they require replacement hard
disks.
•
If the current Unity Connection servers are supported, whether you are adding a feature that
requires additional memory.
The document is available at
http://www.cisco.com/en/US/products/ps6509/products_data_sheets_list.html.
If the servers are no longer supported, replace them before you obtain license files, which are tied
to the MAC address of the server.
Warning
6.
See the applicable version of Release Notes for Cisco Unity Connection for any additional
information on upgrading to the shipping version. In particular, note the items in the “Installation
and Upgrade Information” section. Release notes are available at
http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html.
7.
Install the licenses on the existing Unity Connection server to upgrade on Connection 9.x server.
While upgrade, the legacy license information is uploaded in Unity Connection database. See the
“Migrating Licenses to Cisco Unity Connection Surviable Remote Site VoiceMail 9.x” section. For
more information on Cisco Unity Connection Surviable Remote Site VoiceMail 9.x Licenses, see
the “Managing Licenses in Cisco Unity Connection Surviable Remote Site VoiceMail” chapter of
the System Administration Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/guide/9xcucsagx
.html.
You must install all pre 9.x licenses to pre 9.x Cisco Unity Connection Surviable Remote Site
VoiceMail and Cisco Unity before you upgrade to Cisco Unity Connection Surviable Remote Site
VoiceMail release 9.x as only the installed license informtation is considered as legacy license data
to migrate licenses. After you upgrade to Release 9.x, you can not apply pre 9.x licenses to Cisco Unity
Connection Surviable Remote Site VoiceMail 9.x and you can not apply them using the Enterprise
License Manager.
8.
Note
Confirm that you have the software required for the upgrade. Note the following:
•
You must download the ciscocm.refresh_upgrade.cop (Cisco Option Package) file from
Cisco.com. For information on downloading the .cop file from Cisco.com, see the “Installation
and Upgrade Information” section of the applicable Release Notes for Cisco Unity Connection
at http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html.
•
If you are replacing Unity Connection servers and the servers are currently running Unity
Connection 7.0(1) through 7.1(2), you will also need Unity Connection 7.1(3) software.
However, not all Unity Connection 7.x versions earlier than 7.1(3) can be directly upgraded to
Unity Connection 7.1(3), so you may also need software for an intermediate version that can be
upgraded directly to Unity Connection 7.1(3). For information on supported upgrades, see the
“Supported Cisco Unified Communications Manager Upgrades” section of Cisco Unified
Communications Manager Software Compatibility Matrix at
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html.
For 7.x and later versions, Cisco Unified CM and Cisco Unity Connection Surviable Remote
Site VoiceMail version numbers are identical.
Upgrade Guide for Cisco Unity Connection Release 9.x
3-12
Chapter 3
Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Task List for Upgrading Unity Connection 7.x, 8.0, or 8.5 Software to the Shipping 9.x Version in a Unity Connection
Unity Connection 7.1(3) and Unity Connection 7.1(5) softwares are required for two reasons.
First, some older servers are not supported for use with Unity Connection 8.x, and an attempt
to install or upgrade to Unity Connection 8.x on these older servers will fail. In addition, Unity
Connection software earlier than version 7.1(3) does not include the drivers required by the new
servers. This prevents you from installing Unity Connection earlier than version 7.1(3) on a new
server, moving data to the new server by using the Disaster Recovery System, and then
upgrading the new server to Unity Connection 9.x.
9.
•
If you are replacing the Unity Connection server or replacing hard disks in the server, you must
order physical DVDs because the software that you download from Cisco.com cannot be used
for a new install.
•
If you are not replacing the server or replacing hard disks in the server, you can download the
software for the upgrade from Cisco.com. For information on downloading the software from
Cisco.com, see the “Installation and Upgrade Information” section of the applicable Release
Notes for Cisco Unity Connection at
http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html.
•
If you are not replacing the servers, you may still need software for an upgrade to an
intermediate version before you can upgrade to Unity Connection 9.x. For information on
supported upgrades, see the “Supported Cisco Unified Communications Manager Upgrades”
section of Cisco Unified Communications Manager Software Compatibility Matrix at
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html.
If the Unity Connection server has languages other than English-United States installed and you
want to continue using the languages: Download the applicable Unity Connection 9.x language
files. See the “Downloading Connection 9.x Language Files” section on page 3-1.
Caution
If languages other than English-United States are installed and in use on the Unity Connection
server, you must install the Unity Connection 9.x versions of the same languages after the
upgrade. Otherwise, the Unity Connection conversation will not function properly for all
users.
10. If an intermediate upgrade is required as described in Task 8.: Upgrade Unity Connection as
necessary. For information on how to upgrade from Unity Connection 7.x to a later version of Unity
Connection 7.x, see the “Upgrading Cisco Unity Connection Surviable Remote Site VoiceMail 7.x
to the Shipping 7.x Version” chapter in the Upgrade Guide for Cisco Unity Connection Release 7.x
at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrugx.html.
Do not install the Unity Connection 8.x license files on the Unity Connection 7.x servers.
Caution
If the intermediate upgrade includes a major-version upgrade (for example, from 2.x to 7.x),
you must complete the upgrade to Unity Connection 9.x before Unity Connection will
function again. When you integrate with the ELM server to obtain license files for the
upgrade, Cisco sends you only 9.x license files, which cannot be used on intermediate
versions.
11. If you are upgrading from Unity Connection 7.x, you are using the current servers for Unity
Connection 9.x, and you are either replacing one or both servers or replacing hard disks in one or
both servers: Replace the servers or replace hard disks in the servers. See the applicable section in
the “Replacing Cisco Unity Connection Surviable Remote Site VoiceMail 7.x Servers or Hard
Disks” chapter of the Upgrade Guide for Cisco Unity Connection Release 7.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrugx.html.
Upgrade Guide for Cisco Unity Connection Release 9.x
3-13
Chapter 3 Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Task List for Upgrading Unity Connection 7.x, 8.0, or 8.5 Software to the Shipping 9.x Version in a Unity Connection
Caution
If you are replacing hard disks, do not use the “Installing a Memory Upgrade or Replacing All
Hard Disks to Support Unity Connection 9.x (Selected Servers Only)” section on page 3-22
of this chapter, which does not account for issues related to a cluster.
12. If you are upgrading from Unity Connection 7.x and you are adding memory to the current Unity
Connection server: See the “Installing a Memory Upgrade or Replacing All Hard Disks to Support
Unity Connection 9.x (Selected Servers Only)” section on page 3-22.
13. If you do not have a backup from replacing hard disks or replacing the server: Back up the publisher
server by using the Disaster Recovery System. For more information, see the applicable Disaster
Recovery System Administration Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
Caution
If you are upgrading Unity Connection on Cisco MCS 7825-H3 servers or the equivalent
HP DL320G5, you cannot use the revert feature to revert to a previous version after you have
upgraded to Unity Connection 9.x. If you want to revert to a previous version, you must install
that version and then restore data from a DRS backup.
14. Install the a.cop file on both Publisher and Subscriber before upgrading to Connection 9.x. (This is
the Cisco Option Package that you downloaded in Task 8.). The .cop file patches your current
version of Unity Connection, which is required before you can upgrade to Unity Connection 9.x.
See the “Installing the Cisco Option Package that Is Required to Upgrade from Unity
Connection 7.x, 8.0, or 8.5 to the Shipping 9.x Version” section on page 3-25.
15. If the publisher server is a Cisco MCS 7825-H3 server or HP DL320G5 server: Connect a 128-GB
or larger USB flash drive or external hard disk to the publisher server.
Caution
Do not use a USB drive that contains data that you want to keep. During the upgrade, the USB
drive is reformatted, and all existing data on the drive is destroyed.
16. Upgrade the Unity Connection software on the publisher server. See the applicable section:
•
Upgrading Unity Connection 7.x, 8.0, 8.5, or 8.6 Software to the Shipping 9.x Version from a
Local DVD, page 3-27
•
Upgrading Unity Connection 7.x, 8.0, 8.5, or 8.6 Software to the Shipping 9.x Version from a
Network Location, page 3-28
Caution
Do not start the upgrade on the subscriber server until the upgrade of the publisher server is
complete, or all Unity Connection functionality on both servers will be disabled until the
upgrade of the publisher server completes. In addition, the upgrade of the subscriber server
will fail, and you will have to upgrade the subscriber server again.
If the phone system is routing calls to the subscriber server, outside callers and Unity Connection
users can leave voice messages, but the messages are not immediately delivered to user mailboxes.
17. If the subscriber server is a Cisco MCS 7825-H3 server or HP DL320G5 server: Connect a 128-GB
or larger USB flash drive or external hard disk to the subscriber server.
If the publisher server was a Cisco MCS 7825-H3 server or HP DL320G5 server, you can use the
same drive that you connected to the publisher server in Task 15.
Upgrade Guide for Cisco Unity Connection Release 9.x
3-14
Chapter 3
Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Task List for Upgrading Unity Connection 7.x, 8.0, or 8.5 Software to the Shipping 9.x Version in a Unity Connection
18. Confirm that the publisher server is taking calls and delivering voice messages to users.
19. On the subscriber server, install the Cisco Option Package that is required for the upgrade to Unity
Connection 9.x. (This is the Cisco Option Package that you downloaded in Task 8.) See the
“Installing the Cisco Option Package that Is Required to Upgrade from Unity Connection 7.x, 8.0,
or 8.5 to the Shipping 9.x Version” section on page 3-25.
20. Upgrade the Unity Connection software on the subscriber server. See the applicable section:
•
Upgrading Unity Connection 7.x, 8.0, 8.5, or 8.6 Software to the Shipping 9.x Version from a
Local DVD, page 3-27
•
Upgrading Unity Connection 7.x, 8.0, 8.5, or 8.6 Software to the Shipping 9.x Version from a
Network Location, page 3-28
If the phone system is routing calls to the publisher server, outside callers and Unity Connection
users can leave voice messages. Messages are immediately delivered to user mailboxes.
Caution
If you are upgrading Unity Connection on Cisco MCS 7825-H3 servers or the equivalent
HP DL320G5, you cannot use the revert feature to revert to a previous version after you have
upgraded to Unity Connection 9.x. If you want to revert to a previous version, you must
reinstall that version.
21. Install Unity Connection 9.x languages, if applicable. See the “Installing Connection 9.x Language
Files” section on page 3-2.
Install languages on the publisher server first, then on the subscriber server.
If you are installing Japanese and you want Cisco Unity Connection Administration to be localized,
you must also install the Cisco Unified Communications Manager Japanese locale. See the “Locale
Installation” section in the “Software Upgrades” chapter of the applicable Cisco Unified
Communications Operating System Administration Guide at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
If you are installing other languages and you want the Cisco Personal Communications Assistant to
be localized, you must also install the corresponding Cisco Unified Communications Manager
locales. See the “Locale Installation” section in the “Software Upgrades” chapter of the applicable
Cisco Unified Communications Operating System Administration Guide at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
22. If you are upgrading from Unity Connection 7.x or 8.0 to Unity Connection 9.x, and if any of the
following are true: Configure unified messaging, or review and update unified messaging settings,
as applicable.
– You were using text to speech to access Exchange email before the upgrade.
– You were accessing Exchange calendars by phone before the upgrade.
– You were using Exchange contacts for personal call transfer rules or voice commands before
the upgrade.
– You were accessing MeetingPlace calendars before the upgrade.
– You want to synchronize Unity Connection and Exchange mailboxes (single inbox).
For more information, see the applicable chapters in the Unified Messaging Guide for Cisco Unity
Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/unified_messaging/guide/9xcuc
umgx.html.
Note the following:
Upgrade Guide for Cisco Unity Connection Release 9.x
3-15
Chapter 3 Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Task List for Upgrading Unity Connection 8.6 Software to the Shipping 9.x Version Without a Unity Connection Cluster
– External services in Unity Connection 7.x or 8.0 are converted to unified messaging services.
The unified messaging services are enabled, but the default settings may not be the ideal settings
for your Active Directory and Exchange configuration.
– Unity Connection 8.5 no longer uses user passwords that are stored in the Unity Connection
database to access Exchange. Instead, Unity Connection accesses Exchange through one or
more unified messaging accounts that you create in Active Directory.
23. If you configured single inbox in Task 22. and you want full single-inbox functionality: Do the
following tasks:
a. If Outlook on user workstations is currently configured to access Unity Connection voice
messages via IMAP, delete the IMAP profile from Outlook.
b. Install or upgrade to Cisco Unity Connection ViewMail for Microsoft Outlook Release 8.5 on
user workstations, and configure ViewMail to access Unity Connection voice messages in
Exchange.
Task List for Upgrading Unity Connection 8.6 Software to the
Shipping 9.x Version Without a Unity Connection Cluster
Do the following tasks to upgrade an existing Unity Connection 8.6 server to the shipping 9.x version
when no Unity Connection cluster is configured.
Warning
1.
Review the list of features that are disabled or that have limited functionality during the upgrade.
See the “Status of Unity Connection Features During an Upgrade from Unity Connection 7.x, 8.0,
or 8.5 to Unity Connection 9.x” section on page 3-2.
2.
Review the list of features that stop working until you reconfigure them. See the “Features that You
Must Reconfigure When You Upgrade to Unity Connection 9.x” section on page 3-3.
3.
See the applicable version of Release Notes for Cisco Unity Connection for any additional
information on upgrading to the shipping version. In particular, note the items in the “Installation
and Upgrade Information” section. Release notes are available at
http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html.
4.
Install the licenses on the existing Unity Connection server to upgrade on Connection 9.x server.
While upgrade, the legacy license information is uploaded in Unity Connection database. See the
“Migrating Licenses to Cisco Unity Connection Surviable Remote Site VoiceMail 9.x” section. For
more information on Cisco Unity Connection Surviable Remote Site VoiceMail 9.x Licenses, see
the “Managing Licenses in Cisco Unity Connection Surviable Remote Site VoiceMail” chapter of
the System Administration Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/guide/9xcucsagx
.html.
You must install all pre 9.x licenses to pre 9.x Cisco Unity Connection Surviable Remote Site
VoiceMail and Cisco Unity before you upgrade to Cisco Unity Connection Surviable Remote Site
VoiceMail release 9.x as only the installed license informtation is considered as legacy license data
to migrate licenses. After you upgrade to Release 9.x, you can not apply pre 9.x licenses to Cisco Unity
Connection Surviable Remote Site VoiceMail 9.x and you can not apply them using the Enterprise
License Manager.
Upgrade Guide for Cisco Unity Connection Release 9.x
3-16
Chapter 3
Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Task List for Upgrading Unity Connection 8.6 Software to the Shipping 9.x Version Without a Unity Connection Cluster
5.
If the Unity Connection server has languages other than English-United States installed and you
want to continue using the languages: Download the applicable Unity Connection 9.x language
files. See the “Downloading Connection 9.x Language Files” section on page 3-1.
Caution
When languages other than English-United States are installed and in use on the Unity
Connection server, you must install the Unity Connection 9.x versions of the same languages
after the upgrade. Otherwise, the Unity Connection conversation will not function properly
for all users.
6.
If you do not have a backup from replacing hard disks or replacing the server: Back up the server
by using the Disaster Recovery System. For more information, see the applicable Disaster Recovery
System Administration Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
7.
If you are upgrading during nonbusiness hours: Run the CLI command utils iothrottle disable to
speed up the upgrade.
In an effort to prevent upgrades from adversely affecting system performance during business hours,
the upgrade process is throttled and may take several hours to complete. If you are upgrading during
a maintenance window, you can speed up the upgrade by disabling the throttling. This decreases the
time required for the upgrade to complete but adversely affects Unity Connection performance. For
more information, see the applicable Command Line Interface Reference Guide for Cisco Unified
Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
8.
9.
Note
Upgrade the Unity Connection software. See the applicable section:
•
Upgrading Unity Connection 7.x, 8.0, 8.5, or 8.6 Software to the Shipping 9.x Version from a
Local DVD, page 3-27
•
Upgrading Unity Connection 7.x, 8.0, 8.5, or 8.6 Software to the Shipping 9.x Version from a
Network Location, page 3-28
(Optional) If you want to install Cisco Unity Connection Surviable Remote Site VoiceMail (SRSV):
run the CLI command utlis cuc activate CUSRSV.
After you have installed Cisco Unity Connection SRSV, all the data running in the previous
version will not be upgraded to the newer version.
10. If you disabled the upgrade throttle in Task 7.: Run the CLI command utils iothrottle enable to
re-enable the throttle. For more information, see the applicable Command Line Interface Reference
Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
11. If the Connection server has languages other than English-United States installed, and you want to
continue using the languages: See the “Installing Connection 9.x Language Files” section on
page 3-2.
If you are installing Japanese and you want Cisco Unity Connection Administration to be localized,
you must also install the Cisco Unified Communications Manager Japanese user locale. See the
“Locale Installation” section in the “Software Upgrades” chapter of the applicable Cisco Unified
Communications Operating System Administration Guide at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
Upgrade Guide for Cisco Unity Connection Release 9.x
3-17
Chapter 3 Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Task List for Upgrading Unity Connection 8.6 Software to the Shipping 9.x Version in a Unity Connection Cluster
If you are installing other languages and you want the Cisco Personal Communications Assistant to
be localized, you must also install the corresponding Cisco Unified Communications Manager user
locales. See the “Locale Installation” section in the “Software Upgrades” chapter of the applicable
Cisco Unified Communications Operating System Administration Guide at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
12. If you are upgrading from Unity Connection 8.6 to the shipping Unity Connection 9.x version, and
if any of the following are true: Configure unified messaging, or review and update unified
messaging settings, as applicable.
– You were using text to speech to access Exchange email before the upgrade.
– You were accessing Exchange calendars by phone before the upgrade.
– You were using Exchange contacts for personal call transfer rules or voice commands before
the upgrade.
– You were accessing MeetingPlace calendars before the upgrade.
– You want to synchronize Unity Connection and Exchange mailboxes (single inbox).
For more information, see the applicable chapters in the Unified Messaging Guide for Cisco Unity
Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/unified_messaging/guide/9xcuc
umgx.html.
13. If you configured single inbox in Task 11. and you want full single-inbox functionality: Do the
following tasks:
a. If Outlook on user workstations is currently configured to access Unity Connection voice
messages via IMAP, delete the IMAP profile from Outlook.
b. Install or upgrade to Cisco Unity Connection ViewMail for Microsoft Outlook Release 8.5 on
user workstations, and configure ViewMail to access Unity Connection voice messages in
Exchange.
Task List for Upgrading Unity Connection 8.6 Software to the
Shipping 9.x Version in a Unity Connection Cluster
Revised December 13, 2013
As the upgrade software is installed, the publisher and subscriber servers continue answering calls and
replication occurs. After the upgrade is complete, you switch the two servers, one at a time, to the
upgraded software.
Note the following details about how Unity Connection functions during the switch:
•
When you switch the publisher server to the upgraded software, the subscriber server answers all
calls, but replication does not occur and messages may not be available.
•
When you switch the subscriber server to the upgraded software, the publisher server answers all
calls, but replication does not occur and messages may not be available.
•
About 15 minutes after both servers are switched to the upgraded software, both servers answer
calls, replication resumes, and messages are available.
Upgrade Guide for Cisco Unity Connection Release 9.x
3-18
Chapter 3
Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Task List for Upgrading Unity Connection 8.6 Software to the Shipping 9.x Version in a Unity Connection Cluster
Note the following considerations about the upgrade process:
•
Messages that are recorded while switching to the upgraded software are not replicated. This means
that, depending on the Connection server that is accessed, a user may briefly not be able to retrieve
new messages. After the upgrade process is complete, messages are replicated. When replication is
complete, all messages are available regardless of which Unity Connection server is accessed.
•
MWIs and notifications may not be sent. MWIs and notifications synchronize only after the upgrade
process is complete.
•
A Unity Connection cluster cannot be converted to Cisco Unity Connection Surviable Remote Site
VoiceMail (SRSV).
To follow the upgrade process through the CLI interface, see the utils system upgrade command at the
Command Line Interface Reference Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
Do the following tasks to upgrade the publisher and subscriber servers in a Unity Connection 8.6 cluster
to the shipping Unity Connection 9.x version.
1.
If you are upgrading to Unity Connection 9.x: Confirm the status of publisher and subscriber servers
as active. To confirm the server status, navigate to Cisco Unity Connection Serviceability> Tools>
Cluster Management. In addition, you need to confirm the running state of database replication,
run the CLI command show cuc cluster status. For more information, see the applicable section
in the Command Line Interface Reference Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html
Note the following:
– The status of publisher server should be primary and subscriber server should be secondary.
– You should always upgrade the publisher server first, and then the subscriber server.
– You should never go for the automatic upgrade option.
2.
Review the list of features that are disabled or that have limited functionality during the upgrade.
See the “Status of Unity Connection Features During an Upgrade from Unity Connection 7.x, 8.0,
or 8.5 to Unity Connection 9.x” section on page 3-2.
3.
Review the list of features that stop working until you reconfigure them. See the “Features that You
Must Reconfigure When You Upgrade to Unity Connection 9.x” section on page 3-3.
4.
See the applicable version of Release Notes for Cisco Unity Connection for any additional
information on upgrading to the shipping version. In particular, note the items in the “Installation
and Upgrade Information” section. Release notes are available at
http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html.
5.
If the Unity Connection server has languages other than English-United States installed and you
want to continue using the languages: Download the applicable Unity Connection 9.x language
files. See the “Downloading Connection 9.x Language Files” section on page 3-1.
Caution
6.
If languages other than English-United States are installed and in use on the Unity Connection
server, you must install the Unity Connection 9.x versions of the same languages after the
upgrade. Otherwise, the Unity Connection conversation will not function properly for all
users.
If you are upgrading from Unity Connection 8.6 and you are adding memory to the current Unity
Connection server: See the “Installing a Memory Upgrade or Replacing All Hard Disks to Support
Unity Connection 9.x (Selected Servers Only)” section on page 3-22.
Upgrade Guide for Cisco Unity Connection Release 9.x
3-19
Chapter 3 Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Task List for Upgrading Unity Connection 8.6 Software to the Shipping 9.x Version in a Unity Connection Cluster
7.
If you do not have a database backup before replacing the hard disks or the server: Back up the
publisher server by using the Disaster Recovery System. For more information, see the applicable
Disaster Recovery System Administration Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
8.
If you are upgrading during nonbusiness hours: On the publisher server, run the CLI command utils
iothrottle disable to speed up the upgrade.
In an effort to prevent upgrades from adversely affecting system performance during business hours,
the upgrade process is throttled and may take several hours to complete. If you are upgrading during
a maintenance window, you can speed up the upgrade by disabling the throttling. This decreases the
time required for the upgrade to complete but adversely affects Unity Connection performance. For
more information, see the applicable Command Line Interface Reference Guide for Cisco Unified
Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
Caution
9.
You cannot disable throttling while an upgrade is running. If you decide to disable throttling
after you start an upgrade, you must stop the upgrade, disable throttling, and restart the
upgrade from the beginning.
Upgrade the Unity Connection software on the publisher server. See the applicable section:
•
Upgrading Unity Connection 7.x, 8.0, 8.5, or 8.6 Software to the Shipping 9.x Version from a
Local DVD, page 3-27
•
Upgrading Unity Connection 7.x, 8.0, 8.5, or 8.6 Software to the Shipping 9.x Version from a
Network Location, page 3-28
Caution
Do not restart the publisher server and do not switch to the upgraded software during this task.
Otherwise, the Unity Connection cluster will not function correctly.
If the phone system is routing calls to the subscriber server, outside callers and Unity Connection
users can leave voice messages, but the messages are not immediately delivered to user mailboxes.
10. If you are upgrading during nonbusiness hours: On the subscriber server, run the CLI command utils
iothrottle disable to speed up the upgrade.
11. On the subscriber server, confirm that the publisher server has Primary status and that the subscriber
server has Secondary status. For instructions, see the “Administering a Cisco Unity Connection
Surviable Remote Site VoiceMail 9.x Cluster” chapter of the Cluster Configuration and
Administration Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/cluster_administration/guide/9x
cuccagx.html.
12. Confirm that the publisher server is taking calls and delivering voice messages to users.
13. Upgrade the Unity Connection software on the subscriber server. See the applicable section:
•
Upgrading Unity Connection 7.x, 8.0, 8.5, or 8.6 Software to the Shipping 9.x Version from a
Local DVD, page 3-27
•
Upgrading Unity Connection 7.x, 8.0, 8.5, or 8.6 Software to the Shipping 9.x Version from a
Network Location, page 3-28
Upgrade Guide for Cisco Unity Connection Release 9.x
3-20
Chapter 3
Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Task List for Upgrading Unity Connection 8.6 Software to the Shipping 9.x Version in a Unity Connection Cluster
Caution
Do not restart the subscriber server and do not switch to the upgraded software during this
task. Otherwise, the Unity Connection cluster will not function correctly.
If the phone system is routing calls to the publisher server, outside callers and Unity Connection
users can leave voice messages. Messages are immediately delivered to user mailboxes.
14. Switch to the upgraded software on the publisher server and then to the subscriber server. See the
“Switching to the Upgraded Version of Unity Connection 9.x Software” section on page 3-29.
15. About 15 minutes after you complete Task 14., on the publisher server, confirm that the publisher
server has Primary status and that the subscriber server has Secondary status. For instructions, see
the “Administering a Cisco Unity Connection Surviable Remote Site VoiceMail 9.x Cluster” chapter
of the Cluster Configuration and Administration Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/cluster_administration/guide/9x
cuccagx.html.
16. On the subscriber server, confirm that the publisher server has Primary status and that the subscriber
server has Secondary status. For instructions, see the “Administering a Cisco Unity Connection
Surviable Remote Site VoiceMail 9.x Cluster” chapter of the Cluster Configuration and
Administration Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/cluster_administration/guide/9x
cuccagx.html.
17. Install Unity Connection 9.x languages obtained in Task 5. , if applicable. See the “Installing
Connection 9.x Language Files” section on page 3-2.
Install languages on the publisher server first, then on the subscriber server.
If you are installing Japanese and you want Cisco Unity Connection Administration to be localized,
you must also install the Cisco Unified Communications Manager Japanese locale. See the “Locale
Installation” section in the “Software Upgrades” chapter of the applicable Cisco Unified
Communications Operating System Administration Guide at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
If you are installing other languages and you want the Cisco Personal Communications Assistant to
be localized, you must also install the corresponding Cisco Unified Communications Manager
locales. See the “Locale Installation” section in the “Software Upgrades” chapter of the applicable
Cisco Unified Communications Operating System Administration Guide at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
18. If you are upgrading from Unity Connection 8.6 to the shipping Unity Connection 9.x version, and
if any of the following are true: Configure unified messaging, or review and update unified
messaging settings, as applicable.
– You were using text to speech to access Exchange email before the upgrade.
– You were accessing Exchange calendars by phone before the upgrade.
– You were using Exchange contacts for personal call transfer rules or voice commands before
the upgrade.
– You were accessing MeetingPlace calendars before the upgrade.
– You want to synchronize Unity Connection and Exchange mailboxes (single inbox).
For more information, see the applicable chapters in the Unified Messaging Guide for Cisco Unity
Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/unified_messaging/guide/9xcuc
umgx.html.
Upgrade Guide for Cisco Unity Connection Release 9.x
3-21
Chapter 3 Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Installing a Memory Upgrade or Replacing All Hard Disks to Support Unity Connection 9.x (Selected Servers Only)
19. If you configured single inbox in Task 18. and you want full single-inbox functionality: Do the
following tasks:
a. If Outlook on user workstations is currently configured to access Unity Connection voice
messages via IMAP, delete the IMAP profile from Outlook.
b. Install or upgrade to Cisco Unity Connection ViewMail for Microsoft Outlook Release 8.5 on
user workstations, and configure ViewMail to access Unity Connection voice messages in
Exchange.
Installing a Memory Upgrade or Replacing All Hard Disks to
Support Unity Connection 9.x (Selected Servers Only)
Note
If you are upgrading a server that does not require a memory upgrade or a hard-disk replacement, skip
this section.
Some servers that are running Cisco Unity Connection Surviable Remote Site VoiceMail 7.x and are
qualified for use with Unity Connection 9.x require a hard-disk replacement to support Unity Connection
9.x. In addition, some servers require additional memory if you are going to add selected features (for
example, intrasite or intersite networking) to the upgraded server.
For information on your Unity Connection server, see the applicable server-specific table in the
Cisco Unity Connection Surviable Remote Site VoiceMail 9.<x> Supported Platforms List at
http://www.cisco.com/en/US/products/ps6509/products_data_sheets_list.html.
Warning
Before working on a system that has an on/off switch, turn OFF the power and unplug the power cord.
Statement 1
Warning
Before opening the chassis, disconnect the telephone-network cables to avoid contact with
telephone-network voltages. Statement 2
Warning
This equipment is to be installed and maintained by service personnel only as defined by AS/NZS 3260
Clause 1.2.14.3 Service Personnel. Statement 88
Warning
During this procedure, wear grounding wrist straps to avoid ESD damage to the card. Do not directly
touch the backplane with your hand or any metal tool, or you could shock yourself. Statement 94
Warning
The safety cover is an integral part of the product. Do not operate the unit without the safety cover
installed. Operating the unit without the cover in place will invalidate the safety approvals and pose
a risk of fire and electrical hazards. Statement 117
Upgrade Guide for Cisco Unity Connection Release 9.x
3-22
Chapter 3
Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Installing a Memory Upgrade or Replacing All Hard Disks to Support Unity Connection 9.x (Selected Servers Only)
Warning
Do not work on the system or connect or disconnect cables during periods of lightning activity.
Statement 1001
Warning
Read the installation instructions before connecting the system to the power source. Statement 1004
Warning
To prevent bodily injury when mounting or servicing this unit in a rack, you must take special
precautions to ensure that the system remains stable. The following guidelines are provided to ensure
your safety:
• This unit should be mounted at the bottom of the rack if it is the only unit in the rack.
• When mounting this unit in a partially filled rack, load the rack from the bottom to the top with the
heaviest component at the bottom of the rack.
• If the rack is provided with stabilizing devices, install the stabilizers before mounting or servicing
the unit in the rack. Statement 1006
Warning
There is the danger of explosion if the battery is replaced incorrectly. Replace the battery only with
the same or equivalent type recommended by the manufacturer. Dispose of used batteries according
to the manufacturer’s instructions. Statement 1015
Warning
This unit is intended for installation in restricted access areas. A restricted access area can be
accessed only through the use of a special tool, lock and key, or other means of security. Statement
1017
Warning
To avoid electric shock, do not connect safety extra-low voltage (SELV) circuits to telephone-network
voltage (TNV) circuits. LAN ports contain SELV circuits, and WAN ports contain TNV circuits. Some
LAN and WAN ports both use RJ-45 connectors. Use caution when connecting cables. Statement 1021
Warning
To reduce the risk of fire, use only No. 26 AWG or larger telecommunication line cord. Statement 1023
Warning
This equipment must be grounded. Never defeat the ground conductor or operate the equipment in the
absence of a suitably installed ground conductor. Contact the appropriate electrical inspection
authority or an electrician if you are uncertain that suitable grounding is available. Statement 1024
Warning
Blank faceplates and cover panels serve three important functions: they prevent exposure to
hazardous voltages and currents inside the chassis; they contain electromagnetic interference (EMI)
that might disrupt other equipment; and they direct the flow of cooling air through the chassis. Do not
operate the system unless all cards, faceplates, front covers, and rear covers are in place. Statement
1029
Upgrade Guide for Cisco Unity Connection Release 9.x
3-23
Chapter 3 Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Installing a Memory Upgrade or Replacing All Hard Disks to Support Unity Connection 9.x (Selected Servers Only)
Warning
Only trained and qualified personnel should be allowed to install, replace, or service this equipment.
Statement 1030
Warning
Ultimate disposal of this product should be handled according to all national laws and regulations.
Statement 1040
(For translations of the preceding safety warnings, see Regulatory Compliance and Safety Information
for Cisco Unity Connection Surviable Remote Site VoiceMail at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/regulatory/compliance/ucwarns.html.)
To Install a Memory Upgrade or Replace All Hard Disks to Support Unity Connection 9.x (Selected Servers Only)
Step 1
Remove the cover.
Step 2
If you are not installing a memory upgrade, skip to Step 3.
Install the memory modules in the applicable slots or locations, depending on the server model, as
documented in the Cisco Unity Connection Surviable Remote Site VoiceMail 9.<x> Supported Platforms
List at http://www.cisco.com/en/US/products/ps6509/products_data_sheets_list.html.
Caution
Step 3
If you install new memory modules in the wrong slots, the server and operating system may
not recognize that they have been installed, and Cisco Unity Connection Surviable Remote
Site VoiceMail performance may suffer.
If you are not replacing hard disks, skip to Step 4.
Replace all of the hard disks in the server.
Caution
Step 4
You must remove existing hard disks and install exactly as many hard disks as you remove, or
Cisco Unity Connection Surviable Remote Site VoiceMail installation will fail.
a.
Make note of the current locations of the hard disks in the server, including which hard disk is in
which hard disk slot. If the replacement fails and you want to revert to the current configuration, you
must put the existing hard disks back into their current locations.
b.
Remove the drive trays from the server.
c.
Remove the old hard disks from the drive trays.
d.
Insert the new hard disks into the drive trays.
e.
Reinstall the drive trays in the locations that you made note of in Step a.
Reattach the cover.
Upgrade Guide for Cisco Unity Connection Release 9.x
3-24
Chapter 3
Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Installing the Cisco Option Package that Is Required to Upgrade from Unity Connection 7.x, 8.0, or 8.5 to the Shipping
Installing the Cisco Option Package that Is Required to Upgrade
from Unity Connection 7.x, 8.0, or 8.5 to the Shipping 9.x Version
Note
Installing the Cisco Option Package will temporarily affect access to Unity Connection administration
applications and to the command-line interface.
Do the applicable procedure:
•
To Install, from a Local DVD, the Cisco Option Package that Is Required to Upgrade from Unity
Connection 7.x, 8.0, or 8.5 to the Shipping 9.x Version, page 3-25
•
To Install, from a Network Location, the Cisco Option Package that Is Required to Upgrade from
Unity Connection 7.x, 8.0, or 8.5 to the Shipping 9.x Version, page 3-26
To Install, from a Local DVD, the Cisco Option Package that Is Required to Upgrade from Unity Connection 7.x, 8.0,
or 8.5 to the Shipping 9.x Version
Step 1
Insert the DVD that contains the Cisco Option Package (.cop) file into the disc drive on the Cisco Unity
Connection Surviable Remote Site VoiceMail server.
Step 2
Sign in to Cisco Unified Operating System Administration.
If you are upgrading the subscriber server in a Unity Connection cluster, you can only access Cisco
Unified Operating System Administration by browsing to:
http://<Unity Connection_servername>/cmplatform
Step 3
From the Software Upgrades menu, select Install/Upgrade.
Step 4
On the Software Installation/Upgrade page, in the Source field, select DVD/CD.
Step 5
In the Directory field, enter a forward slash (/).
Step 6
Select Next.
Step 7
Choose the software that you want to install, and select Next.
The .cop file is copied to the hard disk on Unity Connection server. When the file is copied, a screen
displays the checksum value.
Step 8
Verify the checksum.
Step 9
Select Next to begin the installation.
During the installation, the value of the Status field is Running. When the installation is complete, the
value of the Status field changes to Complete.
Note the following:
– All command-line interface sessions are terminated automatically.
– The Cisco Tomcat Service can take several minutes to restart automatically.
Step 10
Logout from the Cisco Unified Operating System Administration application to reflect the successful
installation of the .cop file.
Upgrade Guide for Cisco Unity Connection Release 9.x
3-25
Chapter 3 Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Installing the Cisco Option Package that Is Required to Upgrade from Unity Connection 7.x, 8.0, or 8.5 to the Shipping
Step 11
Confirm the running state of Cisco Tomcat Service, run the CLI command utils service list. For more
information, see the applicable section in the Command Line Interface Reference Guide for Cisco
Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html
To Install, from a Network Location, the Cisco Option Package that Is Required to Upgrade from Unity Connection
7.x, 8.0, or 8.5 to the Shipping 9.x Version
Step 1
Copy the Cisco Option Package (.cop) file on an FTP or SFTP server that the Cisco Unity Connection
Surviable Remote Site VoiceMail server can access.
Step 2
Sign in to Cisco Unified Operating System Administration.
If you are upgrading the subscriber server in a Unity Connection cluster, you can only access Cisco
Unified Operating System Administration by browsing to:
http://<Unity Connection_servername>/cmplatform
Step 3
From the Software Upgrades menu, select Install/Upgrade.
Step 4
On the Software Installation/Upgrade page, in the Source field, select Remote Filesystem.
Step 5
In the Directory field, enter the path to the folder that contains the .cop file.
If the .cop file is located on a Linux or Unix server, you must enter a forward slash (/) at the beginning
of the folder path. (For example, if the .cop file is in the cop folder, you must enter /cop.)
If the .cop file is located on a Windows server, you must use the applicable syntax for an FTP or SFTP
server such as:
•
The path must begin with a forward slash (/) and contain forward slashes throughout instead of
backward slashes (\).
•
The path must start from the FTP or SFTP root folder on the server and must not include a Windows
absolute path, which starts with a drive letter (for example, C:).
Step 6
In the Server field, enter the server name or IP address.
Step 7
In the User Name field, enter the alias that will be used to sign in to the remote server.
Step 8
In the User Password field, enter the password that will be used to sign in to the remote server.
Step 9
In the Transfer Protocol field, select the applicable transfer protocol.
Step 10
Select Next.
Step 11
Choose the software that you want to install, and select Next.
The .cop file is copied to the hard disk on Unity Connection server. When the file is copied, a screen
displays the checksum value.
Step 12
Verify the checksum.
Step 13
Select Next to begin the installation.
During the installation, the value of the Status field is Running. When the installation is complete, the
value of the Status field changes to Complete.
Note the following:
– All command-line interface sessions are terminated automatically.
– The Cisco Tomcat Service can take several minutes to restart automatically.
Upgrade Guide for Cisco Unity Connection Release 9.x
3-26
Chapter 3
Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Upgrading Unity Connection 7.x, 8.0, 8.5, or 8.6 Software to the Shipping 9.x Version from a Local DVD
Step 14
Logout from the Cisco Unified Operating System Administration application to reflect the successful
installation of the .cop file.
Step 15
Confirm the running state of Cisco Tomcat Service, run the CLI command utils service list. For more
information, see the applicable section in the Command Line Interface Reference Guide for Cisco
Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html
Upgrading Unity Connection 7.x, 8.0, 8.5, or 8.6 Software to the
Shipping 9.x Version from a Local DVD
Revised March 5, 2013
To upgrade Unity Connection from a local DVD, you can do either of the following:
Warning
Tip
Caution
•
Use a DVD shipped from Cisco.
•
Download a signed .iso file from Cisco.com, and burn a disc image of the downloaded software.
Burning a disc image extracts the files from the .iso file that you downloaded and writes them to a
DVD.
Unity ConnectionBe aware that when you mount an ISO file through the VM console, VMware does
not eject the disc at the end of the install process.
Always mount your DVD ISO file from the Edit Settings menu in VMware.
If you are upgrading a cluster, do not start the upgrade on the subscriber server until after the upgrade
of the publisher server is complete, or all Unity Connection functionality on both servers will be disabled
until the upgrade of the publisher server completes. In addition, the upgrade of the subscriber server will
fail, and you will have to upgrade the subscriber server again.
To Upgrade Unity Connection 7.x, 8.0, 8.5, or 8.6 Software to the Shipping 9.x Version from a Local DVD
Step 1
Insert the DVD that contains Unity Connection into the disc drive on the Cisco Unity Connection
Surviable Remote Site VoiceMail server.
Step 2
Sign in to Cisco Unified Operating System Administration.
If you are upgrading the subscriber server in a Unity Connection cluster, you can only access Cisco
Unified Operating System Administration by browsing to:
http://<Unity Connection_servername>/cmplatform
Step 3
From the Software Upgrades menu, select Install/Upgrade.
Step 4
On the Software Installation/Upgrade page, in the Source field, select DVD/CD.
Step 5
In the Directory field, enter a forward slash (/).
Step 6
Select Next.
Upgrade Guide for Cisco Unity Connection Release 9.x
3-27
Chapter 3 Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Upgrading Unity Connection 7.x, 8.0, 8.5, or 8.6 Software to the Shipping 9.x Version from a Network Location
Step 7
Select the upgrade version that you want to install, and select Next. The upgrade file is copied to the
hard disk on the Unity Connection server. When the file is copied, a screen displays the checksum value.
Step 8
Verify the checksum.
Step 9
On the next page, monitor the progress of the upgrade.
If you lose your connection with the remote server or close your browser during this step, you may see
the following message when you try to view the Software Installation/Upgrade page again:
Warning: Another session is installing software, click Assume Control to take over the installation.
To continue monitoring the upgrade, select Assume Control.
You can also monitor the upgrade by using the Real-Time Monitoring Tool.
Step 10
Select Next.
During the initial phase of the upgrade, the Installation Log text box in Cisco Unified Operating System
Administration is updated with information on the progress of the upgrade, but updates stop after the
server automatically restarts for the first time. To determine when the upgrade is complete, view the
console for the Unity Connection server: the console screen displays a message indicating that the
installation is complete, and the login prompt for the command-line interface appears.
Step 11
To verify the success of the upgrade, run the CLI command show cuc version. The upgrade succeeded
if the active partition has the upgraded version and the inactive partition has the old version.
Upgrading Unity Connection 7.x, 8.0, 8.5, or 8.6 Software to the
Shipping 9.x Version from a Network Location
To upgrade Unity Connection from a network location, you must download a signed .iso file from
Cisco.com, and copy the .iso file to an FTP or SFTP server. Unity Connection does not allow you to
upgrade by copying either the contents of a DVD shipped from Cisco or the extracted contents of a
downloaded .iso file to an FTP or SFTP server. This helps prevent someone from attempting to upgrade
by using software that has been tampered with.
Caution
If you are upgrading a cluster, do not start the upgrade on the subscriber server until after the upgrade
of the publisher server is complete, or all Unity Connection functionality on both servers will be disabled
until the upgrade of the publisher server completes. In addition, the upgrade of the subscriber server will
fail, and you will have to upgrade the subscriber server again.
To Upgrade Unity Connection 7.x, 8.0, 8.5, or 8.6 Software to the Shipping 9.x Version from a Network Location
Step 1
Copy the upgrade file to a folder on an FTP or SFTP server that the Cisco Unity Connection Surviable
Remote Site VoiceMail server can access.
Step 2
Sign in to Cisco Unified Operating System Administration.
If you are upgrading the subscriber server in a Unity Connection cluster, you can only access Cisco
Unified Operating System Administration by browsing to:
http://<Unity Connection_servername>/cmplatform
Step 3
From the Software Upgrades menu, select Install/Upgrade.
Upgrade Guide for Cisco Unity Connection Release 9.x
3-28
Chapter 3
Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
Switching to the Upgraded Version of Unity Connection 9.x Software
Step 4
On the Software Installation/Upgrade page, in the Source field, select Remote Filesystem.
Step 5
In the Directory field, enter the path to the folder that contains the upgrade file.
If the upgrade file is located on a Linux or Unix server, you must enter a forward slash (/) at the beginning
of the folder path. (For example, if the upgrade file is in the upgrade folder, you must enter /upgrade.)
If the upgrade file is located on a Windows server, you must use the applicable syntax for an FTP or
SFTP server such as:
•
The path must begin with a forward slash (/) and contain forward slashes throughout instead of
backward slashes (\).
•
The path must start from the FTP or SFTP root folder on the server and must not include a Windows
absolute path, which starts with a drive letter (for example, C:).
Step 6
In the Server field, enter the server name or IP address.
Step 7
In the User Name field, enter the alias that will be used to sign in to the remote server.
Step 8
In the User Password field, enter the password that will be used to sign in to the remote server.
Step 9
In the Transfer Protocol field, select the applicable transfer protocol.
Step 10
Select Next.
Step 11
Select the upgrade version that you want to install and select Next. The upgrade file is copied to the hard
disk on the Unity Connection server. When the file is copied, a screen displays the checksum value.
Step 12
Verify the checksum.
Step 13
On the next page, monitor the progress of the upgrade.
If you lose your connection with the remote server or close your browser during this step, you may see
the following message when you try to view the Software Installation/Upgrade page again:
Warning: Another session is installing software, click Assume Control to take over the installation.
To continue monitoring the upgrade, select Assume Control.
You can also monitor the upgrade by using the Real-Time Monitoring Tool.
Step 14
Select Next.
During the initial phase of the upgrade, the Installation Log text box in Cisco Unified Operating System
Administration is updated with information on the progress of the upgrade, but updates stop after the
server automatically restarts for the first time. To determine when the upgrade is complete, view the
console for the Unity Connection server: the console screen displays a message indicating that the
installation is complete, and the login prompt for the command-line interface appears.
Step 15
To verify the success of the upgrade, run the CLI command show cuc version. The upgrade succeeded
if the active partition has the upgraded version and the inactive partition has the old version.
Switching to the Upgraded Version of Unity Connection 9.x
Software
If you chose not to automatically switch to the upgraded partition at the end of the upgrade, do the
following procedure when you are ready to switch partitions.
Upgrade Guide for Cisco Unity Connection Release 9.x
3-29
Chapter 3
Switching to the Upgraded Version of Unity Connection 9.x Software
Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version
To Switch to the Upgraded Version of Unity Connection 9.x Software
Step 1
If you do not have a recent backup, back up the server by using the Disaster Recovery System. For more
information, see the Disaster Recovery System Administration Guide for Cisco Unity Connection
Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/drs_administration/guide/9xcucdrsa
g.html.
Step 2
Sign in to Cisco Unified Operating System Administration.
Step 3
From the Settings menu, select Version.
Step 4
On the Version Settings page, select Switch Versions, and the following occurs:
•
Unity Connection services are stopped.
•
Data from the partition where the older version is installed is copied to the partition where the newer
version is installed. Note that messages are stored in a common partition, so they are not copied.
•
The Unity Connection server restarts and switches to the newer version.
Note
You can check the status of the installation of the upgrade software by using the CLI command
show cuc version. The upgrade is complete when the inactive partition has the upgraded
software and the active partition has the old software.
Upgrade Guide for Cisco Unity Connection Release 9.x
3-30
CH A P T E R
4
Reverting Cisco Unity Connection 9.x Servers to
the Version on the Inactive Partition
This chapter contains the following sections:
•
About Reverting from Unity Connection 9.x to the Version on the Inactive Partition, page 4-1
•
Reverting a Unity Connection 9.x Server to the Version on the Inactive Partition, page 4-2
•
Reverting the Servers in a Unity Connection 9.x Cluster to the Version on the Inactive Partition,
page 4-3
•
Reverting a Unity Connection 9.x Member Server in a Cisco Voicemail Organization to the Version
on the Inactive Partition, page 4-4
•
Reverting a Unity Connection 9.x Site Gateway Server in a Cisco Voicemail Organization to the
Version on the Inactive Partition, page 4-5
About Reverting from Unity Connection 9.x to the Version on the
Inactive Partition
•
Reverting from Unity Connection 9.0 to Unity Connection 8.6, page 4-1
•
Reverting from Unity Connection 9.0 to Unity Connection 8.5 and Earlier, page 4-2
After upgrading, you can revert to the software version that was running before the upgrade by switching
to the software version on the inactive partition.
Caution
If you revert to the version on the inactive partition, you cannot later switch to the newest version.
Instead, you must reinstall the upgrade as documented in this guide.
Reverting from Unity Connection 9.0 to Unity Connection 8.6
Note the following effects on data and messages of reverting to the version on the inactive partition:
•
Users that were added after you upgraded to the new version will no longer exist after you revert to
the version on the inactive partition. You will have to add the new users again.
•
All messages are preserved. However, users that were added after the upgrade no longer exist, so
their messages are orphaned. These messages are moved to the undeliverable messages folder.
Upgrade Guide for Cisco Unity Connection Release 9.x
4-1
Chapter 4 Reverting Cisco Unity Connection 9.x Servers to the Version on the Inactive Partition
Reverting a Unity Connection 9.x Server to the Version on the Inactive Partition
•
If you moved mailboxes from one mailbox store to another after upgrading, those mailboxes will be
moved back to the mailbox stores they were in before the upgrade.
•
If you created mailbox stores after upgrading, the new mailbox stores will be deleted.
•
The future delivery folder is created the first time a users marks a message for future delivery. If you
revert to a version that supports future delivery but the future delivery folder had not yet been created
for the user, messages in the future delivery folder for the new version are moved to the
undeliverable messages folder.
Reverting from Unity Connection 9.0 to Unity Connection 8.5 and Earlier
Note the following effects on data and messages of reverting to the version on the inactive partition:
Note
•
No voice messages will be left after reverting to Unity Connection 8.6.
•
No administrator settings will be left after reverting to Unity Connection 8.6.
If you are upgrading Unity Connection on a MCS 7825-H3 server or the equivalent HP DL320G5, you
cannot use the revert feature to revert to a previous version after you have upgraded to Unity Connection
9.0. If you want to revert to a previous version, you must install that version and then restore the data
from a DRS backup.
Reverting a Unity Connection 9.x Server to the Version on the
Inactive Partition
Use the procedure in this section only if the server is not in a cluster, is not a member server in a Unity
Connection site, and is not a gateway server between Unity Connection sites or between a Unity
Connection site and a Cisco Unity site.
Caution
Do not revert to the version on the inactive partition during regular business hours unless doing so is
necessary. Reverting causes the Unity Connection server to restart, and Unity Connection will not
function for about 15 minutes, until the restart completes.
To Revert a Unity Connection 9.x Server to the Version on the Inactive Partition
Step 1
Sign in to Cisco Unified Operating System Administration.
Step 2
From the Settings menu, select Version.
The Version Settings window displays.
Step 3
Select the Switch Versions button.
After you confirm that you want to restart the system, the system restarts, which might take up to 15
minutes.
Step 4
Confirm that the version switch was successful:
a.
Sign in to Cisco Unified Operating System Administration.
b.
From the Settings menu, select Version. The Version Settings window displays.
Upgrade Guide for Cisco Unity Connection Release 9.x
4-2
Chapter 4
Reverting Cisco Unity Connection 9.x Servers to the Version on the Inactive Partition
Reverting the Servers in a Unity Connection 9.x Cluster to the Version on the Inactive Partition
c.
Confirm that the correct product version is now running on the active partition.
d.
Confirm that all activated services are running.
e.
Sign in to Cisco Unity Connection Administration.
f.
Confirm that the configuration data exists.
Reverting the Servers in a Unity Connection 9.x Cluster to the
Version on the Inactive Partition
To revert the servers in a Unity Connection cluster to the version on the inactive partition, do the
following three procedures.
Use the procedure in this section only if the server is not a member server in a Unity Connection site,
and is not a gateway server between Unity Connection sites or between a Unity Connection site and a
Cisco Unity site.
Caution
You must revert both servers and reset database replication, or the cluster will not function properly.
Caution
Do not revert to the version on the inactive partition during regular business hours unless doing so is
necessary. Reverting causes the Unity Connection server to restart, and Unity Connection will not
function for about 15 minutes, until the restart completes. In addition, voice messages left on the
subscriber server while you are reverting the publisher server will be lost.
To Revert the Publisher Server in a Unity Connection Cluster to the Version on the Inactive Partition
Step 1
Sign in to Cisco Unified Operating System Administration.
Step 2
From the Settings menu, select Version.
The Version Settings window displays.
Step 3
Select the Switch Versions button.
After you confirm that you want to restart the system, the system restarts, which might take up to 15
minutes.
Step 4
Confirm that the version switch was successful:
a.
Sign in to Cisco Unified Operating System Administration.
b.
From the Settings menu, select Version. The Version Settings window displays.
c.
Confirm that the correct product version is now running on the active partition.
d.
Confirm that all activated services are running.
e.
Sign in to Cisco Unity Connection Administration.
f.
Confirm that the configuration data exists.
Upgrade Guide for Cisco Unity Connection Release 9.x
4-3
Chapter 4 Reverting Cisco Unity Connection 9.x Servers to the Version on the Inactive Partition
Reverting a Unity Connection 9.x Member Server in a Cisco Voicemail Organization to the Version on the Inactive
To Revert the Subscriber Server in a Unity Connection 9.x Cluster to the Version on the Inactive Partition
Step 1
Sign in to Cisco Unified Operating System Administration.
Step 2
From the Settings menu, select Version. The Version Settings window displays.
Step 3
Select the Switch Versions button.
After you confirm that you want to restart the system, the system restarts, which might take up to 15
minutes.
Step 4
Confirm that the version switch was successful:
a.
Sign in to Cisco Unified Operating System Administration on the subscriber server.
b.
From the Settings menu, select Version. The Version Settings window displays.
c.
Confirm that the correct version is now running on the active partition.
d.
Confirm that all activated services are running.
Reverting a Unity Connection 9.x Member Server in a Cisco
Voicemail Organization to the Version on the Inactive Partition
If an intersite link is configured between a Cisco Unity Connection site and a Cisco Unity site or
between two Unity Connection sites, do the following tasks to revert a Unity Connection member server
or cluster in a site to the version of Unity Connection on the inactive partition.
Caution
Do not revert to the version on the inactive partition during regular business hours unless doing so is
necessary. Reverting causes the Unity Connection server to restart, and Unity Connection will not
function for about 15 minutes, until the restart completes.
1.
If you added this server to the Unity Connection site before you upgraded to the version on the active
partition, skip to Task 2. You do not need to remove this member server from the site before you
revert.
If you added this server to the Unity Connection site after you upgraded to the version on the active
partition, remove this member server from the site. If a cluster is configured, do the task on the
publisher server. For more information, see the “Removing a Location From a Cisco Unity
Connection Site” section in the “Making Changes to the Networking Configuration in Cisco Unity
Connection 9.x” chapter of the Networking Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/networking/guide/9xcucnetx.ht
ml.
2.
If no cluster is configured, revert the server. See the “Reverting a Unity Connection 9.x Server to
the Version on the Inactive Partition” section on page 4-2.
If a cluster is configured, revert both servers, and reset database replication. See the “Reverting the
Servers in a Unity Connection 9.x Cluster to the Version on the Inactive Partition” section on
page 4-3.
3.
If you removed the server from a Unity Connection site in Task 1., if the version you reverted to
supports networking, and if you still want the server to be part of a Cisco voicemail organization,
set up networking again. See the “Setting Up Networking Between Cisco Unity Connection 9.x
Upgrade Guide for Cisco Unity Connection Release 9.x
4-4
Chapter 4
Reverting Cisco Unity Connection 9.x Servers to the Version on the Inactive Partition
Reverting a Unity Connection 9.x Site Gateway Server in a Cisco Voicemail Organization to the Version on the Inactive
Servers” chapter of the Networking Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/networking/guide/9xcucnetx.ht
ml.
Reverting a Unity Connection 9.x Site Gateway Server in a Cisco
Voicemail Organization to the Version on the Inactive Partition
If an intersite link is configured between a Cisco Unity Connection site and a Cisco Unity site or
between two Unity Connection sites, do the following tasks to revert a Unity Connection site gateway
server or cluster to the version of Unity Connection on the inactive partition.
Caution
Do not revert to the version on the inactive partition during regular business hours unless doing so is
necessary. Reverting causes the Unity Connection server to restart, and Unity Connection will not
function for about 15 minutes, until the restart completes.
1.
If you configured an intersite link before you upgraded to the version on the active partition, skip to
Task 4. You do not need to remove the gateway server from the Unity Connection site before you
revert.
If you configured an intersite link after you upgraded to the version on the active partition, and if
the Unity Connection site gateway is the link to another Unity Connection site, remove the intersite
link between the two Unity Connection sites. If a cluster is configured, do the task on the publisher
server. For more information, see the “Removing an Intersite Link Between Two Cisco Unity
Connection Sites” section in the “Making Changes to the Networking Configuration in Cisco Unity
Connection 9.x” chapter of the Networking Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/networking/guide/9xcucnetx.ht
ml.
If you configured an intersite link after you upgraded to the version on the active partition, and if
the Unity Connection site gateway is the link to a Cisco Unity site, remove the intersite link between
the Unity Connection site and the Cisco Unity site. If a cluster is configured, do the task on the
publisher server. For more information, see the “Removing an Intersite Link Between a Cisco Unity
Connection Site and a Cisco Unity Site” section in the “Making Changes to the Networking
Configuration in Cisco Unity Connection 9.x” chapter of the Networking Guide for Cisco Unity
Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/networking/guide/9xcucnetx.ht
ml.
2.
If you removed an intersite link in Task 1., in Connection Administration, on the Tools > Task
Management page, change the schedule for the Remove Objects Associated With Deleted Remote
Sites task to run in a few minutes. (By default, this task runs every day at 10 pm.)
3.
If you removed an intersite link in Task 1., watch the progress of the task in two locations:
– On the Task Definition Basics page for the Remove Objects Associated With Deleted Remote
Sites task, where errors, if any, are displayed.
– On the Intersite Links page (Networking > Links > Intersite Links in
Connection Administration). When the link disappears from this page, the task is complete, and
the server is no longer a bridgehead server.
Upgrade Guide for Cisco Unity Connection Release 9.x
4-5
Chapter 4 Reverting Cisco Unity Connection 9.x Servers to the Version on the Inactive Partition
Reverting a Unity Connection 9.x Site Gateway Server in a Cisco Voicemail Organization to the Version on the Inactive
Caution
4.
Do not continue reverting the server until the task is complete.
If you added this server to the Unity Connection site before you upgraded to the version on the active
partition, skip to Task 5. You do not need to remove this member server from the site before you
revert.
If you added this server to the Unity Connection site after you upgraded to the version on the active
partition, remove this member server from the site. If a cluster is configured, do the task on the
publisher server. For more information, see the “Removing a Location From a Cisco Unity
Connection Site” section in the “Making Changes to the Networking Configuration in Cisco Unity
Connection 9.x” chapter of the Networking Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/networking/guide/9xcucnetx.ht
ml.
5.
If no cluster is configured, revert the server. See the “Reverting a Unity Connection 9.x Server to
the Version on the Inactive Partition” section on page 4-2.
If a cluster is configured, revert both servers, and reset database replication. See the “Reverting the
Servers in a Unity Connection 9.x Cluster to the Version on the Inactive Partition” section on
page 4-3.
6.
If you removed an intersite link in Task 1. or removed the server from a Unity Connection site in
Task 4., if the version you reverted to supports networking, and if you still want the server to be part
of a Cisco voicemail organization, set up networking again. See the applicable chapter in the
Networking Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/networking/guide/9xcucnetx.ht
ml.
Upgrade Guide for Cisco Unity Connection Release 9.x
4-6
CH A P T E R
5
Migrating from Cisco Unity Connection 1.x to
Version 9.x
This chapter contains the following sections:
•
Task List for Migrating from Unity Connection 1.x to Version 9.x, page 5-1
•
Installing a Memory Upgrade or Replacing All Hard Disks to Support Unity Connection 9.x
(Selected Servers Only), page 5-5
•
Preparing to Create User Accounts by Using Multiple Unity Connection 9.x Templates, page 5-7
Task List for Migrating from Unity Connection 1.x to Version 9.x
Use the following high-level task list to migrate to Unity Connection 9.x correctly. The tasks reference
detailed instructions in this guide and in other Unity Connection documentation as noted. Follow the
documentation for a successful migration.
Note the following:
•
If you want to reuse the licenses of Unity Connection 1.x on Unity Connection 9.x, see the Reusing
Unity Connection Licenses section.
•
If you want to use new licenses for Unity Connection 9.x, see the Using New Unity Connection
Licenses section.
Reusing Unity Connection Licenses
If you want to reuse Unity Connection licenses you need to first migrate from Unity Connection 1.x to
Unity Connection 8.x and then migrate from Unity Connection 8.x to Unity Connection 9.x.
Migrating from Unity Connection 1.x to Unity Connection 8.x
1.
If you are reusing the current Unity Connection server rather than installing a new server, review the
applicable Cisco Unity Connection 8.<x> Supported Platforms List to determine whether the server
requires replacement hard disks or additional RAM. The document is available at
http://www.cisco.com/en/US/products/ps6509/products_data_sheets_list.html.
Upgrade Guide for Cisco Unity Connection Release 9.x
5-1
Chapter 5
Migrating from Cisco Unity Connection 1.x to Version 9.x
Task List for Migrating from Unity Connection 1.x to Version 9.x
2.
If the Unity Connection server is running version 1.1: Upgrade to version 1.2. For more information,
see the “Upgrading Cisco Unity Connection or Voice-Recognition Software to the Shipping
Version” chapter of the Cisco Unity Connection Reconfiguration and Upgrade Guide, Release 1.x
at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/1x/installation/guide/inst.html.
3.
Obtain a Unity Connection upgrade license, which enables Unity Connection 8.x and is required for
Unity Connection-specific features.
See the “Managing Licenses in Cisco Unity Connection 8.x” chapter of the System Administration
Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/administration/guide/8xcucsagx
.html.
4.
Review the “Requirements for Migrating from Cisco Unity Connection 1.x to Version 8.x” section
of System Requirements for Cisco Unity Connection Release 8.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/requirements/8xcucsysreqs.html
.
5.
See the applicable version of Release Notes for Cisco Unity Connection for additional information
on upgrading to the shipping version. In particular, note the items in the “Installation and Upgrade
Information” section. Release notes are available at
http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html.
6.
Download the following tools:
•
Unity Connection 1.x Disaster Recovery tools, available at
http://www.ciscounitytools.com/Applications/CxN/DIRT/DIRT.html.
•
COBRAS, available at
http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html.
7.
Install the tools that you downloaded in Task 6.
8.
Back up the server by using the Unity Connection 1.x Disaster Recovery tools. This backup will not
be used to restore data on the Unity Connection 9.x system; we recommend it only so that you can
revert to Unity Connection 1.2 if necessary.
Note
9.
The Unity Connection 1.x Disaster Recovery tools are different from the Disaster Recovery
System available with Unity Connection 2.x and later.
Use COBRAS to export Unity Connection data and messages. For more information, see COBRAS
Help at http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html.
10. If additional memory or replacement hard disks are required: Add memory or replace hard disks.
See the “Installing a Memory Upgrade or Replacing All Hard Disks to Support Unity Connection
9.x (Selected Servers Only)” section on page 5-5 of this guide.
11. Install and begin configuring Unity Connection 8.x. See Part 1 through Part 3 in the “Task List for
Installing a Cisco Unity Connection 8.x System (Without a Connection Cluster)” in the “Overview
of Mandatory Tasks for Installing a Cisco Unity Connection 8.x System” chapter of the Installation
Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/installation/guide/8xcucigx.html
.
12. Populate the system with user and call management data. See the following documentation:
– COBRAS Help at
http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html.
Upgrade Guide for Cisco Unity Connection Release 9.x
5-2
Chapter 5
Migrating from Cisco Unity Connection 1.x to Version 9.x
Task List for Migrating from Unity Connection 1.x to Version 9.x
– “Part 4: Populating the System with User and Call Management Data” in the “Task List for
Installing a Cisco Unity Connection 8.x System (Without a Connection Cluster)” in the
“Overview of Mandatory Tasks for Installing a Cisco Unity Connection 8.x System” chapter of
the Installation Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/installation/guide/8xcucigx.
html. Skip tasks for data that will be imported.
13. Finish configuring Unity Connection 8.x. See Part 5 through Part 9 in the “Task List for Installing
a Cisco Unity Connection 9.x System (Without a Connection Cluster)” in the “Overview of
Mandatory Tasks for Installing a Cisco Unity Connection 8.x System” chapter of the Installation
Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/installation/guide/8xcucigx.html
.
Migrating from Unity Connection 8.x to Unity Connection 9.x
To migrate from Unity Connection 8.x to Unity Connection 9.x, see the “Upgrading Cisco Unity
Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version” chapter.
Using New Unity Connection Licenses
If you want to directly migrate to Unity Connection 9.x without reusing licenses, see the Migrating from
Unity Connection 1.x to Unity Connection 9.x section.Unity Connection.
Migrating from Unity Connection 1.x to Unity Connection 9.x
1.
If you are reusing the current Unity Connection server rather than installing a new server, review the
applicable Cisco Unity Connection 9.<x> Supported Platforms List to determine whether the server
requires replacement hard disks or additional RAM. The document is available at
http://www.cisco.com/en/US/products/ps6509/products_data_sheets_list.html.
2.
If the Unity Connection server is running version 1.1: Upgrade to version 1.2. For more information,
see the “Upgrading Cisco Unity Connection or Voice-Recognition Software to the Shipping
Version” chapter of the Cisco Unity Connection Reconfiguration and Upgrade Guide, Release 1.x
at http://www.cisco.com/en/US/docs/voice_ip_comm/connection/1x/installation/guide/inst.html
3.
Review the “Requirements for Migrating from Cisco Unity Connection 1.x to Version 9.x” section
of System Requirements for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/requirements/9xcucsysreqs.html
.
4.
See the applicable version of Release Notes for Cisco Unity Connection for additional information
on upgrading to the shipping version. In particular, note the items in the “Installation and Upgrade
Information” section. Release notes are available at
http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html.
5.
Download the following tools:
6.
•
Unity Connection 1.x Disaster Recovery tools, available at
http://www.ciscounitytools.com/Applications/CxN/DIRT/DIRT.html.
•
COBRAS, available at
http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html.
Install the tools that you downloaded in Task 6.
Upgrade Guide for Cisco Unity Connection Release 9.x
5-3
Chapter 5
Migrating from Cisco Unity Connection 1.x to Version 9.x
Task List for Migrating from Unity Connection 1.x to Version 9.x
7.
Note
Back up the server by using the Unity Connection 1.x Disaster Recovery tools. This backup will not
be used to restore data on the Unity Connection 9.x system; we recommend it only so that you can
revert to Unity Connection 1.2 if necessary.
The Unity Connection 1.x Disaster Recovery tools are different from the Disaster Recovery
System available with Unity Connection 2.x and later.
8.
Use COBRAS to export Unity Connection data and messages. For more information, see COBRAS
Help at http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html.
9.
If additional memory or replacement hard disks are required: Add memory or replace hard disks.
See the “Installing a Memory Upgrade or Replacing All Hard Disks to Support Unity Connection
9.x (Selected Servers Only)” section on page 5-5 of this guide.
10. Install and begin configuring Unity Connection 9.x. See Part 1 through Part 3 in the “Task List for
Installing a Cisco Unity Connection 9.x System (Without a Connection Cluster)” in the “Overview
of Mandatory Tasks for Installing a Cisco Unity Connection 9.x System” chapter of the Installation
Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/installation/guide/9xcucigx.html
.
11. Populate the system with user and call management data. See the following documentation:
– COBRAS Help at
http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html.
12. “Part 4: Populating the System with User and Call Management Data” in the “Task List for Installing
a Cisco Unity Connection 9.x System (Without a Connection Cluster)” in the “Overview of
Mandatory Tasks for Installing a Cisco Unity Connection 9.x System” chapter of the Installation
Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/installation/guide/9xcucigx.html
. Skip tasks for data that will be imported.
13. Finish configuring Unity Connection 9.x. See Part 5 through Part 9 in the “Task List for Installing
a Cisco Unity Connection 9.x System (Without a Connection Cluster)” in the “Overview of
Mandatory Tasks for Installing a Cisco Unity Connection 9.x System” chapter of the Installation
Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/installation/guide/9xcucigx.html
.
14. Obtain and intsall the licenses in the ELM server. For details on obtaining and installing the licenses
in the ELM server, see the "New License Fulfillment" section in the ELM user guide at
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/elmuserguide/9_0_1/CUCM_BK_E596F
D72_00_enterprise-license-manager-user-90.html. For more information on Cisco Unity
Connection 9.0 Licenses, see the “Managing Licenses in Cisco Unity Connection” chapter of the
System Administration Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/guide/9xcucsagx
.html.
Upgrade Guide for Cisco Unity Connection Release 9.x
5-4
Chapter 5
Migrating from Cisco Unity Connection 1.x to Version 9.x
Installing a Memory Upgrade or Replacing All Hard Disks to Support Unity Connection 9.x (Selected Servers Only)
Installing a Memory Upgrade or Replacing All Hard Disks to
Support Unity Connection 9.x (Selected Servers Only)
Note
If you are upgrading a server that does not require a memory upgrade or a hard-disk replacement, skip
this section.
Some servers that are qualified for use with Cisco Unity Connection require:
•
A memory upgrade to run Unity Connection 9.x in any configuration.
•
A memory upgrade to support a specified number of Unity Connection users when both voice
recognition and intrasite or intersite networking are configured.
•
A hard-disk replacement to support a Unity Connection cluster.
See the applicable server-specific table in the Cisco Unity Connection 9.<x> Supported Platforms List
at http://www.cisco.com/en/US/products/ps6509/products_data_sheets_list.html.
Warning
Before working on a system that has an on/off switch, turn OFF the power and unplug the power cord.
Statement 1
Warning
Before opening the chassis, disconnect the telephone-network cables to avoid contact with
telephone-network voltages. Statement 2
Warning
This equipment is to be installed and maintained by service personnel only as defined by AS/NZS 3260
Clause 1.2.14.3 Service Personnel. Statement 88
Warning
During this procedure, wear grounding wrist straps to avoid ESD damage to the card. Do not directly
touch the backplane with your hand or any metal tool, or you could shock yourself. Statement 94
Warning
The safety cover is an integral part of the product. Do not operate the unit without the safety cover
installed. Operating the unit without the cover in place will invalidate the safety approvals and pose
a risk of fire and electrical hazards. Statement 117
Warning
Do not work on the system or connect or disconnect cables during periods of lightning activity.
Statement 1001
Warning
Read the installation instructions before connecting the system to the power source. Statement 1004
Upgrade Guide for Cisco Unity Connection Release 9.x
5-5
Chapter 5 Migrating from Cisco Unity Connection 1.x to Version 9.x
Installing a Memory Upgrade or Replacing All Hard Disks to Support Unity Connection 9.x (Selected Servers Only)
Warning
To prevent bodily injury when mounting or servicing this unit in a rack, you must take special
precautions to ensure that the system remains stable. The following guidelines are provided to ensure
your safety:
• This unit should be mounted at the bottom of the rack if it is the only unit in the rack.
• When mounting this unit in a partially filled rack, load the rack from the bottom to the top with the
heaviest component at the bottom of the rack.
• If the rack is provided with stabilizing devices, install the stabilizers before mounting or servicing
the unit in the rack. Statement 1006
Warning
There is the danger of explosion if the battery is replaced incorrectly. Replace the battery only with
the same or equivalent type recommended by the manufacturer. Dispose of used batteries according
to the manufacturer’s instructions. Statement 1015
Warning
This unit is intended for installation in restricted access areas. A restricted access area can be
accessed only through the use of a special tool, lock and key, or other means of security. Statement
1017
Warning
To avoid electric shock, do not connect safety extra-low voltage (SELV) circuits to telephone-network
voltage (TNV) circuits. LAN ports contain SELV circuits, and WAN ports contain TNV circuits. Some
LAN and WAN ports both use RJ-45 connectors. Use caution when connecting cables. Statement 1021
Warning
To reduce the risk of fire, use only No. 26 AWG or larger telecommunication line cord. Statement 1023
Warning
This equipment must be grounded. Never defeat the ground conductor or operate the equipment in the
absence of a suitably installed ground conductor. Contact the appropriate electrical inspection
authority or an electrician if you are uncertain that suitable grounding is available. Statement 1024
Warning
Blank faceplates and cover panels serve three important functions: they prevent exposure to
hazardous voltages and currents inside the chassis; they contain electromagnetic interference (EMI)
that might disrupt other equipment; and they direct the flow of cooling air through the chassis. Do not
operate the system unless all cards, faceplates, front covers, and rear covers are in place. Statement
1029
Warning
Only trained and qualified personnel should be allowed to install, replace, or service this equipment.
Statement 1030
Warning
Ultimate disposal of this product should be handled according to all national laws and regulations.
Statement 1040
Upgrade Guide for Cisco Unity Connection Release 9.x
5-6
Chapter 5
Migrating from Cisco Unity Connection 1.x to Version 9.x
Preparing to Create User Accounts by Using Multiple Unity Connection 9.x Templates
(For translations of the preceding safety warnings, see Regulatory Compliance and Safety Information
for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/regulatory/compliance/ucwarns.html.)
To Install a Memory Upgrade or Replace All Hard Disks to Support Unity Connection 9.x (Selected Servers Only)
Step 1
Remove the cover.
Step 2
If you are not installing a memory upgrade, skip to Step 3.
Install the memory modules in the applicable slots or locations, depending on the server model, as
documented in the Cisco Unity Connection 9.<x> Supported Platforms List at
http://www.cisco.com/en/US/products/ps6509/products_data_sheets_list.html.
Caution
Step 3
If you install new memory modules in the wrong slots, the server and operating system may
not recognize that they have been installed, and Cisco Unity Connection performance may
suffer.
If you are not replacing hard disks, skip to Step 4.
Caution
You must remove existing hard disks and install exactly as many hard disks as you remove, or
Cisco Unity Connection installation will fail.
Replace the hard disks:
Step 4
a.
Make note of the current locations of the hard disks in the server, including which hard disk is in
which hard disk slot. If the replacement fails and you want to revert to the current configuration, you
must put the existing hard disks back into their current locations.
b.
Remove the drive trays from the server.
c.
Remove the old hard disks from the drive trays.
d.
Insert the new hard disks into the drive trays.
e.
Reinstall the drive trays in the locations that you made note of in Step a.
Reattach the cover.
Preparing to Create User Accounts by Using Multiple Unity
Connection 9.x Templates
The utility that exports user data from Unity Connection 1.x creates one CSV file with data for all users,
and the utility that imports this data into Unity Connection 9.x creates all of the new user accounts by
using the same template. If you want to create user accounts by using two or more templates, you may
want to split the CSV file into one file per template. (Depending on how you want to split users among
templates, it might be faster to create all user accounts with the same template and then update user
settings individually.)
Upgrade Guide for Cisco Unity Connection Release 9.x
5-7
Chapter 5
Preparing to Create User Accounts by Using Multiple Unity Connection 9.x Templates
Migrating from Cisco Unity Connection 1.x to Version 9.x
To Prepare Multiple CSV Files for Creating User Accounts by Using Multiple Unity Connection 9.x Templates
Step 1
In the location to which you exported Unity Connection 1.x data, create a subfolder for each template
that you want to use. Give each subfolder the same name as the corresponding template.
Step 2
Copy the CSV file to each subfolder. Use the same filename as the original CSV file, or the import will
fail.
Step 3
Copy all of the recorded-name WAV files from the location to which you exported Unity Connection 1.x
data to each subfolder that you created in Step 1. Filenames are in the format
<user_alias>_VOICE_NAME.wav.
When you import user data from a CSV file, the corresponding recorded-name WAV files are also
imported. The import utility looks for these files only in the folder that contains the CSV file from which
you are importing.
Step 4
Open the CSV file in each subfolder, and delete the rows for the users who you do not want to import by
using the corresponding template.
For example, if you were editing the CSV file in a SalesStaffTemplate folder, you would delete all of the
rows for all of the users who you do not want to create by using the SalesStaffTemplate.
Upgrade Guide for Cisco Unity Connection Release 9.x
5-8
CH A P T E R
6
Migrating from Cisco Unity 4.x and Later to
Cisco Unity Connection 9.x by Using a Flash
Cutover
This chapter contains the following sections:
•
Overview of a Flash Cutover from Cisco Unity to Unity Connection 9.x, page 6-1
•
Task List for Migrating from Cisco Unity 4.0(3) or Later to Unity Connection 9.x by Using a Flash
Cutover, page 6-4
•
Installing a Memory Upgrade or Replacing All Hard Disks to Support Unity Connection 9.x
(Selected Servers Only), page 6-7
•
Preparing to Create User Accounts by Using Multiple Unity Connection 9.x Templates, page 6-9
•
Importing User Data and Messages into Unity Connection 9.x by Using COBRAS, page 6-10
•
Importing User Data and Messages into Unity Connection 9.x by Using the Cisco Unity to
Connection Migration Export Tool, page 6-10
Overview of a Flash Cutover from Cisco Unity to Unity
Connection 9.x
See the following sections:
•
About the Tools Used for Migrating from Cisco Unity 4.0(3) or Later to Unity Connection 9.x by
Using a Flash Cutover, page 6-2
•
How Migrated Messages Can Exceed Available Disk Space on the Unity Connection 9.x Server,
page 6-2
•
About the Behavior of Mailbox Synchronization If You Migrate Messages, page 6-3
•
Removing Cisco Unity Data from Active Directory, page 6-3
Upgrade Guide for Cisco Unity Connection Release 9.x
6-1
Chapter 6 Migrating from Cisco Unity 4.x and Later to Cisco Unity Connection 9.x by Using a Flash Cutover
Overview of a Flash Cutover from Cisco Unity to Unity Connection 9.x
About the Tools Used for Migrating from Cisco Unity 4.0(3) or Later to Unity
Connection 9.x by Using a Flash Cutover
To migrate user data and, optionally, voice messages from a Cisco Unity 4.0(3) or later system to Unity
Connection 9.x, you must export the data and messages from the Cisco Unity system by using either
COBRAS (Cisco Objected Backup and Restore Application Suite) or the Cisco Unity 4.x to Unity
Connection 2.x Migration Export Tool.
COBRAS
COBRAS exports more data than the Cisco Unity to Unity Connection Migration Export tool. In
addition, COBRAS does not require a server running a secure shell (SSH) server application, as the
Cisco Unity to Unity Connection Migration Export Tool does.
COBRAS and COBRAS help are available at
http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html.
Cisco Unity to Unity Connection Migration Export Tool
The main use for the Cisco Unity to Unity Connection Migration Export Tool is as a backup migration
method in case you encounter problems with COBRAS. However, it requires a server running a secure
shell (SSH) server application to import Cisco Unity 4.0(5) and later data and messages. Configuring an
SSH server application can be a complicated and time-consuming process.
The Migration Export tool and Help for the tool are available at
http://www.ciscounitytools.com/Applications/CxN/UnityToConnectionMigrationExport/UnityToConn
ectionMigrationExport.html.
How Migrated Messages Can Exceed Available Disk Space on the Unity
Connection 9.x Server
We discourage migrating messages from Cisco Unity to Unity Connection because you can easily fill the
hard disk on the Unity Connection server with messages migrated from Cisco Unity. Like Exchange,
Unity Connection supports single-instance messaging, meaning that when a message is sent to a
distribution list, only one copy is stored. However, COBRAS cannot retain single-instance messaging
for a migration, so for every message sent to a distribution list and migrated to Unity Connection, the
Unity Connection database contains one copy of the message for each recipient. For example, if you send
a Cisco Unity voice message to a distribution list that has 10 members and then migrate that message to
Unity Connection, the Unity Connection database will contain 10 copies of the message.
To complicate matters further, there is no way to estimate the total size of all voice messages when
messages to distribution lists are expanded from single-instance messaging. As a result, you can easily
fill the hard disk on the Unity Connection server with migrated messages.
Instead of migrating messages, we recommend that you leave the Cisco Unity servers running for a few
weeks so users can continue to access messages that were left before the migration.
COBRAS never migrates secure messages, faxes, or receipts.
Upgrade Guide for Cisco Unity Connection Release 9.x
6-2
Chapter 6
Migrating from Cisco Unity 4.x and Later to Cisco Unity Connection 9.x by Using a Flash Cutover
Overview of a Flash Cutover from Cisco Unity to Unity Connection 9.x
About the Behavior of Mailbox Synchronization If You Migrate Messages
As noted in the “How Migrated Messages Can Exceed Available Disk Space on the Unity Connection 9.x
Server” section on page 6-2, we discourage migrating messages. However, if you must migrate messages
from Cisco Unity to Unity Connection 8.5 or later, and if you configure Unity Connection and Exchange
mailbox synchronization (single inbox), note the following:
•
Migrated messages will appear in the Unity Connection mailbox and in the Exchange mailbox for
each user.
•
COBRAS retains the read/unread status of the migrated messages. If a user played a message in
Cisco Unity before the message was migrated, the message will be read both in Unity Connection
and in the Exchange mailbox.
•
If you migrate messages for the same Cisco Unity subscriber more than once, the corresponding
Unity Connection user will have one more copy of each migrated message in Unity Connection and
in Exchange for each additional migration attempt.
If the Cisco Unity server is configured as unified messaging, we further discourage migrating messages
because of the following behaviors.
•
Two copies of migrated messages will appear in the Exchange mailbox for each user: the original
message and the migrated message that is synchronized into the Exchange mailbox when single
inbox is configured.
•
If a user uses Outlook to play the original message in Exchange (the copy that Cisco Unity put into
Exchange when the message was received), the message will remain unread in Unity Connection,
and the message waiting indicator will remain on. This only happens with migrated messages.
Playing the migrated message (the copy that was synchronized into the Exchange mailbox by the
single inbox feature) or playing messages that are received after the migration will turn off the
message waiting indicator on the new extension as appropriate.
In only one configuration must you migrate messages: you configured secure messaging for Cisco Unity
subscribers, and you want the corresponding Unity Connection users to be able to use Cisco Unity
Connection ViewMail for Microsoft Outlook to play messages from the Cisco Unity server after the
migration. In this configuration, you must also upgrade to Cisco Unity Connection ViewMail for
Microsoft Outlook version 8.5 because Cisco Unity ViewMail version 8.0 cannot access secure
messages in Unity Connection, and Cisco Unity Connection ViewMail for Microsoft Outlook version
8.5 cannot access secure messages in Cisco Unity.
Removing Cisco Unity Data from Active Directory
Depending on the Cisco Unity configuration, after the migration is complete, you may want to remove
Cisco Unity–specific attributes from Active Directory accounts or delete the Active Directory accounts
by using the Uninstall Unity tool, the Bulk Subscriber Delete tool, or both. Regardless of the method you
use for removing Cisco Unity–specific attributes or removing Active Directory accounts, after you
migrate Cisco Unity data to Unity Connection, you should still run Uninstall Unity on the server to
remove Cisco Unity objects from Active Directory.
In a flash cutover migration and a Unified Messaging configuration, use the Uninstall Unity utility to
remove Cisco Unity–specific attributes from Active Directory accounts. The tool removes Cisco Unity
attributes from Active Directory accounts for all of the Cisco Unity subscribers who are homed on the
current server.
Upgrade Guide for Cisco Unity Connection Release 9.x
6-3
Chapter 6 Migrating from Cisco Unity 4.x and Later to Cisco Unity Connection 9.x by Using a Flash Cutover
Task List for Migrating from Cisco Unity 4.0(3) or Later to Unity Connection 9.x by Using a Flash Cutover
In a Voice Messaging configuration for which you created duplicate Active Directory accounts in the
corporate forest for Cisco Unity subscribers, you will probably want to remove the Active Directory
accounts, not just Cisco Unity–specific attributes. To remove Active Directory accounts, you must use
the Bulk Subscriber Delete tool in Tools Depot.
In a Voice Messaging configuration for which you created a separate forest, removing Active Directory
attributes and accounts is unnecessary if you are going to reinstall the operating system on the
Cisco Unity servers and on the domain controllers and global catalog servers.
Task List for Migrating from Cisco Unity 4.0(3) or Later to Unity
Connection 9.x by Using a Flash Cutover
Use the following high-level task list to migrate to Unity Connection 9.x correctly. The tasks reference
detailed instructions in this guide and in other Unity Connection documentation as noted. Follow the
documentation for a successful migration.
Note
For information on migrating from Cisco Unity to Unity Connection by gradually moving data, see the
“Migrating from Cisco Unity to Cisco Unity Connection 9.x by Gradually Moving Data” chapter.
1.
If you are reusing the current Cisco Unity server rather than installing a new server, review the
applicable Cisco Unity Connection 9.<x> Supported Platforms List to determine whether the server
requires replacement hard disks or additional RAM. The document is available at
http://www.cisco.com/en/US/products/ps6509/products_data_sheets_list.html.
2.
Obtain and intsall the licenses in the ELM server. For details on obtaining and installing the licenses
in the ELM server, see the "New License Fulfillment" section in the ELM user guide at
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/elmuserguide/9_0_1/CUCM_BK_E596F
D72_00_enterprise-license-manager-user-90.html. For more information on Cisco Unity
Connection 9.0 Licenses, see the “Managing Licenses in Cisco Unity Connection” chapter of the
System Administration Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/guide/9xcucsagx
.html.
3.
Review the “Requirements for Migrating from Cisco Unity 4.0(3) or Later to Cisco Unity
Connection Version 9.x” section of System Requirements for Cisco Unity Connection 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/requirements/9xcucsysreqs.html
.
4.
See the applicable version of Release Notes for Cisco Unity Connection for additional information
on the shipping version of Cisco Unity Connection. In particular, note the items in the section
“Installation and Upgrade Information.” Release notes are available at
http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html.
5.
If the Cisco Unity server is running version 4.0(1) through 4.0(4): Download the software for
upgrading to Cisco Unity 4.0(3) or later. For more information, see the section on downloading
software in the applicable release notes at
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.
6.
Download the following tools:
•
The Cisco Unity Disaster Recovery tools, available at
http://www.ciscounitytools.com/Applications/Unity/DIRT/DIRT.html.
Upgrade Guide for Cisco Unity Connection Release 9.x
6-4
Chapter 6
Migrating from Cisco Unity 4.x and Later to Cisco Unity Connection 9.x by Using a Flash Cutover
Task List for Migrating from Cisco Unity 4.0(3) or Later to Unity Connection 9.x by Using a Flash Cutover
7.
•
COBRAS, available at
http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html.
•
Optional: The Cisco Unity to Unity Connection Migration Export tool,
http://www.ciscounitytools.com/Applications/CxN/UnityToConnectionMigrationExport/Unity
ToConnectionMigrationExport.html.
•
If Cisco Unity attributes and objects are stored in the corporate directory: The Uninstall Unity
tool, http://ciscounitytools.com/Applications/Unity/UninstallUnity/UninstallUnity.html.
Install the tools that you downloaded in Step 6.
When Cisco Unity failover is configured:
– Install the Cisco Unity Disaster Recovery Backup tool on the secondary server.
– Install all other tools on the active server, regardless of whether the active server is the primary
or secondary server.
8.
Back up the server by using the Cisco Unity Disaster Recovery tools. This backup will not be used
to restore data on the Unity Connection 9.x system; we recommend it only so you can revert to
Cisco Unity if necessary.
9.
If you want to use the Migration Export tool, and if you do not already have a secure shell (SSH)
server application installed on a server that is accessible to the Cisco Unity server: Install an SSH
server application. The migration tool that imports Cisco Unity data into Unity Connection 9.x uses
SSH to access the exported user data and messages.
Only OpenSSH for Windows was tested, and customers have reported problems migrating using
other SSH applications.
Note
10. Optional: Use the Cisco Unity to Unity Connection Migration Export tool to export Cisco Unity
data and messages. You will use the data exported by this tool only if COBRAS fails for some
reason. For more information, see Help for the tool at
http://www.ciscounitytools.com/Applications/CxN/UnityToConnectionMigrationExport/UnityToC
onnectionMigrationExport.html.
If you have a secure shell (SSH) server application installed on a server that is accessible to the
Cisco Unity server, export to the SSH server. If you do not have an SSH server, you can export data
to any network location. You can set up an SSH server later if necessary.
11. If the Cisco Unity server is running version 4.0(1) through 4.0(4): Upgrade to Cisco Unity 4.0(3) or
later. For more information, see the following documentation:
•
The release notes for the applicable version of Cisco Unity at
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_notes_list.html.
•
The applicable upgrade chapter in the applicable Reconfiguration and Upgrade Guide at
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.
12. Use COBRAS to export Cisco Unity data and, optionally, messages. For more information, see Help
for the tool at http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html.
If you are configuring single inbox, and if Cisco Unity is configured as unified messaging, so Unity
Connection voice messages that are synchronized to Exchange will be saved in the same mailbox
that Cisco Unity voice messages are stored in now, we recommend that you select the Include
Corporate Email Addresses from Backup for New User Creation checkbox in COBRAS. When
you restore Cisco Unity data on the Unity Connection server, the Exchange email addresses
Upgrade Guide for Cisco Unity Connection Release 9.x
6-5
Chapter 6 Migrating from Cisco Unity 4.x and Later to Cisco Unity Connection 9.x by Using a Flash Cutover
Task List for Migrating from Cisco Unity 4.0(3) or Later to Unity Connection 9.x by Using a Flash Cutover
associated with Cisco Unity users will be saved in the Corporate Email Address field on the User
Basics page in Cisco Unity Connection Administration. This will simplify configuration of single
inbox later in the migration process.
13. If additional memory or replacement hard disks are required: Add memory or replace hard disks.
See the “Installing a Memory Upgrade or Replacing All Hard Disks to Support Unity Connection
9.x (Selected Servers Only)” section on page 6-7.
14. Install and begin configuring Unity Connection 9.x. See Part 1 through Part 3 in the “Task List for
Installing a Cisco Unity Connection 9.x System (Without a Connection Cluster)” in the “Overview
of Mandatory Tasks for Installing a Cisco Unity Connection 9.x System” chapter of the Installation
Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/installation/guide/9xcucigx.html
.
15. Restore Cisco Unity data on the Unity Connection server by using COBRAS. See the following
documentation:
•
The “Importing User Data and Messages into Unity Connection 9.x by Using COBRAS” section
on page 6-10 of this guide.
•
“Part 4: Populating the System with User and Call Management Data” in the “Task List for
Installing a Cisco Unity Connection 9.x System (Without a Connection Cluster)” in the
“Overview of Mandatory Tasks for Installing a Cisco Unity Connection 9.x System” chapter of
the Installation Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/installation/guide/9xcucigx.
html.
If you need to instead restore data by using the Migration Import tool, see the following
documentation:
•
“Part 4: Populating the System with User and Call Management Data” in the “Task List for
Installing a Cisco Unity Connection 9.x System (Without a Connection Cluster)” in the
“Overview of Mandatory Tasks for Installing a Cisco Unity Connection 9.x System” chapter of
the Installation Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/installation/guide/9xcucigx.
html.
•
Preparing to Create User Accounts by Using Multiple Unity Connection 9.x Templates,
page 6-9
•
Importing User Data and Messages into Unity Connection 9.x by Using the Cisco Unity to
Connection Migration Export Tool, page 6-10
16. Finish configuring Unity Connection 9.x. See Part 5 through Part 9 in the “Task List for Installing
a Cisco Unity Connection 9.x System (Without a Connection Cluster)” in the “Overview of
Mandatory Tasks for Installing a Cisco Unity Connection 9.x System” chapter of the Installation
Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/installation/guide/9xcucigx.html
.
17. Test Unity Connection to confirm that the migration was successful.
18. If Cisco Unity attributes and objects are in the corporate directory: Uninstall Cisco Unity, which
removes Cisco Unity attributes and objects from Active Directory. For more information, see the
“Removing Cisco Unity Data from Active Directory” section on page 6-3.
Upgrade Guide for Cisco Unity Connection Release 9.x
6-6
Chapter 6
Migrating from Cisco Unity 4.x and Later to Cisco Unity Connection 9.x by Using a Flash Cutover
Installing a Memory Upgrade or Replacing All Hard Disks to Support Unity Connection 9.x (Selected Servers Only)
Installing a Memory Upgrade or Replacing All Hard Disks to
Support Unity Connection 9.x (Selected Servers Only)
Note
If you are upgrading a server that does not require a memory upgrade or a hard-disk replacement, skip
this section.
Some servers that are qualified for use with Cisco Unity Connection require a memory upgrade or a
hard-disk replacement, either to support Unity Connection 9.x or to support Unity Connection 9.x
features.
See the applicable server-specific table in the Cisco Unity Connection 9.<x> Supported Platforms List
at http://www.cisco.com/en/US/products/ps6509/products_data_sheets_list.html.
Warning
Before working on a system that has an on/off switch, turn OFF the power and unplug the power cord.
Statement 1
Warning
Before opening the chassis, disconnect the telephone-network cables to avoid contact with
telephone-network voltages. Statement 2
Warning
This equipment is to be installed and maintained by service personnel only as defined by AS/NZS 3260
Clause 1.2.14.3 Service Personnel. Statement 88
Warning
During this procedure, wear grounding wrist straps to avoid ESD damage to the card. Do not directly
touch the backplane with your hand or any metal tool, or you could shock yourself. Statement 94
Warning
The safety cover is an integral part of the product. Do not operate the unit without the safety cover
installed. Operating the unit without the cover in place will invalidate the safety approvals and pose
a risk of fire and electrical hazards. Statement 117
Warning
Do not work on the system or connect or disconnect cables during periods of lightning activity.
Statement 1001
Warning
Read the installation instructions before connecting the system to the power source. Statement 1004
Warning
To prevent bodily injury when mounting or servicing this unit in a rack, you must take special
precautions to ensure that the system remains stable. The following guidelines are provided to ensure
your safety:
• This unit should be mounted at the bottom of the rack if it is the only unit in the rack.
• When mounting this unit in a partially filled rack, load the rack from the bottom to the top with the
Upgrade Guide for Cisco Unity Connection Release 9.x
6-7
Chapter 6 Migrating from Cisco Unity 4.x and Later to Cisco Unity Connection 9.x by Using a Flash Cutover
Installing a Memory Upgrade or Replacing All Hard Disks to Support Unity Connection 9.x (Selected Servers Only)
heaviest component at the bottom of the rack.
• If the rack is provided with stabilizing devices, install the stabilizers before mounting or servicing
the unit in the rack. Statement 1006
Warning
There is the danger of explosion if the battery is replaced incorrectly. Replace the battery only with
the same or equivalent type recommended by the manufacturer. Dispose of used batteries according
to the manufacturer’s instructions. Statement 1015
Warning
This unit is intended for installation in restricted access areas. A restricted access area can be
accessed only through the use of a special tool, lock and key, or other means of security. Statement
1017
Warning
To avoid electric shock, do not connect safety extra-low voltage (SELV) circuits to telephone-network
voltage (TNV) circuits. LAN ports contain SELV circuits, and WAN ports contain TNV circuits. Some
LAN and WAN ports both use RJ-45 connectors. Use caution when connecting cables. Statement 1021
Warning
To reduce the risk of fire, use only No. 26 AWG or larger telecommunication line cord. Statement 1023
Warning
This equipment must be grounded. Never defeat the ground conductor or operate the equipment in the
absence of a suitably installed ground conductor. Contact the appropriate electrical inspection
authority or an electrician if you are uncertain that suitable grounding is available. Statement 1024
Warning
Blank faceplates and cover panels serve three important functions: they prevent exposure to
hazardous voltages and currents inside the chassis; they contain electromagnetic interference (EMI)
that might disrupt other equipment; and they direct the flow of cooling air through the chassis. Do not
operate the system unless all cards, faceplates, front covers, and rear covers are in place. Statement
1029
Warning
Only trained and qualified personnel should be allowed to install, replace, or service this equipment.
Statement 1030
Warning
Ultimate disposal of this product should be handled according to all national laws and regulations.
Statement 1040
(For translations of the preceding safety warnings, see Regulatory Compliance and Safety Information
for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/regulatory/compliance/ucwarns.html.)
To Install a Memory Upgrade or Replace All Hard Disks to Support Unity Connection 9.x (Selected Servers Only)
Step 1
Remove the cover.
Upgrade Guide for Cisco Unity Connection Release 9.x
6-8
Chapter 6
Migrating from Cisco Unity 4.x and Later to Cisco Unity Connection 9.x by Using a Flash Cutover
Preparing to Create User Accounts by Using Multiple Unity Connection 9.x Templates
Step 2
If you are not installing a memory upgrade, skip to Step 3.
Install the memory modules in the applicable slots or locations, depending on the server model, as
documented in the Cisco Unity Connection 9.<x> Supported Platforms List at
http://www.cisco.com/en/US/products/ps6509/products_data_sheets_list.html.
Caution
Step 3
If you install new memory modules in the wrong slots, the server and operating system may
not recognize that they have been installed, and Cisco Unity Connection performance may
suffer.
If you are not replacing hard disks, skip to Step 4.
Caution
You must remove existing hard disks and install exactly as many hard disks as you remove, or
Cisco Unity Connection installation will fail.
Replace the hard disks:
Step 4
a.
Make note of the current locations of the hard disks in the server, including which hard disk is in
which hard disk slot. If the replacement fails and you want to revert to the current configuration, you
must put the existing hard disks back into their current locations.
b.
Remove the drive trays from the server.
c.
Remove the old hard disks from the drive trays.
d.
Insert the new hard disks into the drive trays.
e.
Reinstall the drive trays in the locations that you made note of in Step a.
Reattach the cover.
Preparing to Create User Accounts by Using Multiple Unity
Connection 9.x Templates
The utility that exports user data from Cisco Unity 4.0(5) and later creates one CSV file with data for all
users, and the utility that imports this data into Unity Connection 9.x creates all of the new user accounts
by using the same template. If you want to create user accounts by using two or more templates, you may
want to split the CSV file into one file per template. (Depending on how you want to split users among
templates, it might be faster to create all user accounts with the same template and then update user
settings individually.)
To Prepare Multiple CSV Files for Creating User Accounts by Using Multiple Unity Connection 9.x Templates
Step 1
In the location to which you exported Cisco Unity 4.0(5) and later data, create a subfolder for each
template that you want to use. Give each subfolder the same name as the corresponding template.
Step 2
Copy the CSV file to each subfolder. Use the same filename as the original CSV file, or the import will
fail.
Upgrade Guide for Cisco Unity Connection Release 9.x
6-9
Chapter 6 Migrating from Cisco Unity 4.x and Later to Cisco Unity Connection 9.x by Using a Flash Cutover
Importing User Data and Messages into Unity Connection 9.x by Using COBRAS
Step 3
Copy all of the recorded-name WAV files from the location to which you exported Cisco Unity 4.0(5)
and later data to each subfolder that you created in Step 1. Filenames are in the format
<user_alias>_VOICE_NAME.wav.
When you import user data from a CSV file, the corresponding recorded-name WAV files are also
imported. The import utility looks for these files only in the folder that contains the CSV file from which
you are importing.
Step 4
Open the CSV file in each subfolder, and delete the rows for the users who you do not want to import by
using the corresponding template.
For example, if you were editing the CSV file in a SalesStaffTemplate folder, you would delete all of the
rows for all of the users who you do not want to create by using the SalesStaffTemplate.
Importing User Data and Messages into Unity Connection 9.x by
Using COBRAS
For extensive information on importing user data and, optionally, messages into Unity Connection, see
the COBRAS Help at http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html.
Importing User Data and Messages into Unity Connection 9.x by
Using the Cisco Unity to Connection Migration Export Tool
Note
If you exported data by using the COBRAS tool, see COBRAS Help
(http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html) for information on
importing data and messages.
If you exported both user data and messages, you must import user data before you import messages.
Caution
Passwords for Cisco Unity web applications cannot be exported because they are stored in Active
Directory. When you create new user accounts by importing data, every account will get the same
password, which is the password in the template that you specify when you import data.
When you import user data into Cisco Unity Connection 9.x, the Migrate Users utility does not confirm
that passwords meet the password requirements specified by Unity Connection credential policies. The
first time users sign in to Unity Connection 9.x by phone or sign in to a web tool, they are prompted to
change the password. Credential policies will enforce password requirements. If the user data you import
contains any blank passwords, those new user accounts will be created with the default password of the
chosen template.
This section contains two procedures, one for importing user data and the other for importing messages.
Upgrade Guide for Cisco Unity Connection Release 9.x
6-10
Chapter 6
Migrating from Cisco Unity 4.x and Later to Cisco Unity Connection 9.x by Using a Flash Cutover
Importing User Data and Messages into Unity Connection 9.x by Using the Cisco Unity to Connection Migration Export
To Import User Data into Unity Connection 9.x by Using the Cisco Unity to Connection Migration Export Tool
Step 1
In Cisco Unity Connection Administration, expand Tools, expand Migration Utilities, and select
Migrate Users.
Step 2
In the Server Name or IP Address field, enter the name or the IP address of the SSH server to which
you copied Cisco Unity user data.
Step 3
In the Path Name field, enter the path to the folder that contains the user data that you want to import.
The format of the path depends on how you configured the SSH server application for access to that
folder.
Step 4
In the User Name and Password fields, enter the account name and password for an account that has
the permissions required to access the server and files to which you exported the data.
Step 5
For User Template, select the template whose settings you want to apply to all of the users you are
creating with the imported data.
Step 6
In the Failed Objects Filename field, enter the filename for the log file. Connection will save information
in the specified file about users whose data could not be imported.
Step 7
Select Submit.
When the import is finished, the Status displays “Bulk Administration Tool completed,” as well as the
number of users for which the import process succeeded and the number for which it failed.
Step 8
If the import failed for any users, review the file that you specified in Step 6 for information on which
user accounts could not be created, and correct the errors as applicable.
You can ignore errors for accounts that are common to all versions of Unity Connection, for example,
Operator and UndeliverableMessagesMailbox.
If the import failed for only a few accounts, it may be faster to create the missing accounts manually in
Cisco Unity Connection Administration.
Caution
Step 9
If you create accounts manually and you want to import messages that you exported from
Cisco Unity, you must give each account the exact alias and SMTP address that the
corresponding Cisco Unity account had. If you give the new account a different alias and/or
SMTP address, Unity Connection 9.x will not be able to associate the imported messages with
the new accounts.
Correct user data that could not be imported and reimport it, if applicable:
a.
Save the log file locally. This file, which contains only rows for the users who could not be imported,
is the file you specified in the Failed Objects Filename field in Step 6.
b.
Correct data in the log file.
c.
Change the name of the log file to match the name of the CSV file that you imported from,
UnityMigrationOutput.csv.
d.
Copy the renamed log file into the folder that contains the CSV file that you imported from, and
overwrite the original CSV file.
e.
Repeat Step 2 through Step 8 until all of the accounts are successfully imported.
Caution
If you exported messages as well as user data, you must successfully create all user accounts
before you import messages, or the message import will fail.
Upgrade Guide for Cisco Unity Connection Release 9.x
6-11
Chapter 6 Migrating from Cisco Unity 4.x and Later to Cisco Unity Connection 9.x by Using a Flash Cutover
Importing User Data and Messages into Unity Connection 9.x by Using the Cisco Unity to Connection Migration Export
Step 10
If you created more than one CSV file so that you could import by using more than one template, repeat
Step 2 through Step 8 for each of the remaining CSV files that you created in the “To Prepare Multiple
CSV Files for Creating User Accounts by Using Multiple Unity Connection 9.x Templates” procedure
on page 6-9.
To Import Messages into Unity Connection 9.x by Using the Cisco Unity to Connection Migration Export Tool
Step 1
In Cisco Unity Connection Administration, expand Tools, expand Migration Utilities, and select
Migrate Messages.
Step 2
In the Server Name or IP Address field, enter the name or the IP address of the SSH server to which
you exported Cisco Unity user data and messages.
Step 3
In the Path Name field, enter the path to the folder that contains the messages that you want to import.
The format of the path depends on how you configured the SSH server application for access to that
folder.
Step 4
In the User Name and Password fields, enter the account name and password for an account that has
the permissions required to access the server and files to which you exported the data.
Step 5
Select Submit.
When the import is finished, the Status displays “Bulk Administration Tool completed,” as well as the
number of messages migrated.
Upgrade Guide for Cisco Unity Connection Release 9.x
6-12
CH A P T E R
7
Migrating from Cisco Unity to Cisco Unity
Connection 9.x by Gradually Moving Data
This chapter contains the following sections:
•
Overview of a Gradual Migration from Cisco Unity to Cisco Unity Connection 9.x, page 7-1
•
Task List for Migrating from Cisco Unity to Unity Connection 9.x by Gradually Moving Data,
page 7-4
Overview of a Gradual Migration from Cisco Unity to Cisco Unity
Connection 9.x
Before you begin to gradually migrate users and other data from Cisco Unity to Cisco Unity Connection,
familiarize yourself with the following conceptual and procedural documentation related to the
migration:
•
Documentation on setting up Unity Connection networking. See the following chapters of the
Networking Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/networking/guide/9xcucnetx.ht
ml:
– “Overview of Networking Concepts in Cisco Unity Connection 9.x”
– “Setting Up Networking Between Cisco Unity and Cisco Unity Connection 9.x Servers”
•
Documentation on the Cisco Unified Backup and Restore Application Suite (COBRAS), which you
use to migrate data. See:
– COBRAS Help at
http://www.ciscounitytools.com/Applications/General/COBRAS/Help/COBRAS.htm.
– Training videos for using COBRAS Help, also at
http://www.ciscounitytools.com/Applications/General/COBRAS/Help/COBRAS.htm.
See the following sections:
•
Gradual Migrations vs. Flash-Cutover Migrations, page 7-2
•
How Migrated Messages Can Exceed Available Disk Space on the Unity Connection 9.x Server,
page 7-2
•
About the Behavior of Mailbox Synchronization If You Migrate Messages (Unity Connection 9.x),
page 7-2
Upgrade Guide for Cisco Unity Connection Release 9.x
7-1
Chapter 7 Migrating from Cisco Unity to Cisco Unity Connection 9.x by Gradually Moving Data
Overview of a Gradual Migration from Cisco Unity to Cisco Unity Connection 9.x
•
How the Migration Affects Cisco Unity Subscribers, page 7-3
•
Copying Cisco Unity Public Distribution Lists to Unity Connection, page 7-4
•
Removing Cisco Unity Data from Active Directory, page 7-4
Gradual Migrations vs. Flash-Cutover Migrations
Gradually migrating users and other data is a complex, time-consuming process. Unless a gradual
migration is a non-negotiable requirement, we recommend that you consider a flash-cutover migration,
as documented in the “Migrating from Cisco Unity 4.x and Later to Cisco Unity Connection 9.x by
Using a Flash Cutover” chapter.
How Migrated Messages Can Exceed Available Disk Space on the Unity
Connection 9.x Server
We discourage migrating messages from Cisco Unity to Unity Connection. Like Exchange, Unity
Connection supports single-instance messaging, meaning that when a message is sent to a distribution
list, only one copy is stored. However, COBRAS cannot retain single-instance messaging for a
migration, so for every message sent to a distribution list and migrated to Unity Connection, the Unity
Connection database contains one copy of the message for each recipient. For example, if you send a
Cisco Unity voice message to a distribution list that has 10 members and then migrate that message to
Unity Connection, the Unity Connection database will contain 10 copies of the message.
To complicate matters further, there is no way to estimate the total size of all voice messages when
messages to distribution lists are expanded from single-instance messaging. As a result, you can easily
fill the hard disk on the Unity Connection server with migrated messages.
COBRAS never migrates secure messages, faxes, or receipts.
When Unity Connection networking is configured and you run COBRAS Import for Unity Connection
7.x and Later, COBRAS starts automatically in Hot Mode, the mode for gradually migrating Cisco Unity
subscribers to Unity Connection. Hot Mode does not include an option to migrate messages. If you want
to migrate messages, you must:
a. Run COBRAS export to export the messages from Cisco Unity before you migrate Cisco Unity
subscribers to Unity Connection.
b. Run COBRAS import to import messages into Unity Connection after you migrate subscribers.
The task list indicates when to perform these steps, if applicable.
About the Behavior of Mailbox Synchronization If You Migrate Messages (Unity
Connection 9.x)
As noted in the “How Migrated Messages Can Exceed Available Disk Space on the Unity Connection 9.x
Server” section on page 7-2, we discourage migrating messages. However, if you must migrate messages
from Cisco Unity to Unity Connection 8.5 or later, and if you configure Unity Connection and Exchange
mailbox synchronization (single inbox), note the following:
•
Migrated messages will appear in the Unity Connection mailbox and in the Exchange mailbox for
each user.
Upgrade Guide for Cisco Unity Connection Release 9.x
7-2
Chapter 7
Migrating from Cisco Unity to Cisco Unity Connection 9.x by Gradually Moving Data
Overview of a Gradual Migration from Cisco Unity to Cisco Unity Connection 9.x
•
COBRAS retains the read/unread status of the migrated messages. If a user played a message in
Cisco Unity before the message was migrated, the message will be read both in Unity Connection
and in the Exchange mailbox.
•
If you migrate messages for the same Cisco Unity subscriber more than once, the corresponding
Unity Connection user will have one more copy of each migrated message in Unity Connection and
in Exchange for each additional migration attempt.
If the Cisco Unity server is configured as unified messaging, we further discourage migrating messages
because of the following behaviors.
•
Two copies of migrated messages will appear in the Exchange mailbox for each user: the original
message and the migrated message that is synchronized into the Exchange mailbox when single
inbox is configured.
•
If a user uses Outlook to play the original message in Exchange (the copy that Cisco Unity put into
Exchange when the message was received), the message will remain unread in Unity Connection,
and the message waiting indicator will remain on. This only happens with migrated messages.
Playing the migrated message (the copy that was synchronized into the Exchange mailbox by the
single inbox feature) or playing messages that are received after the migration will turn off the
message waiting indicator on the new extension as appropriate.
In only one configuration must you migrate messages: you configured secure messaging for Cisco Unity
subscribers, and you want the corresponding Unity Connection users to be able to use Cisco Unity
Connection ViewMail for Microsoft Outlook to play messages from the Cisco Unity server after the
migration. In this configuration, you must also upgrade to Cisco Unity Connection ViewMail for
Microsoft Outlook version 8.5 because Cisco Unity ViewMail version 8.0 cannot access secure
messages in Unity Connection, and Cisco Unity Connection ViewMail for Microsoft Outlook version
8.5 cannot access secure messages in Cisco Unity.
How the Migration Affects Cisco Unity Subscribers
As Cisco Unity subscribers are migrated to Unity Connection, their primary extensions are prefixed with
an alphabetical string. This has the following effects:
•
The migrated subscribers can no longer call the old pilot number to access their old Cisco Unity
voice messages because their extension is now associated with their Unity Connection mailbox.
•
To allow migrated users to access their Cisco Unity voice messages using the telephone user
interface, you must configure a new pilot number and create a Direct Calls routing rule that routes
calls to the Sign-In Archived Mailbox conversation. This conversation allows users to access
messages on the Cisco Unity server by entering their old Cisco Unity primary extension.
For more information, see the “About the Behavior of Mailbox Synchronization If You Migrate
Messages (Unity Connection 9.x)” section on page 7-2.
•
The migrated subscribers are no longer listed in the Cisco Unity directory.
•
Subscribers who have not been migrated can no longer send messages to the Cisco Unity mailbox
of subscribers who have been migrated.
•
Cisco Unity notification devices (for example, message waiting indicators) are disabled for
migrated subscribers.
•
Alternate extensions for migrated subscribers are deleted.
Upgrade Guide for Cisco Unity Connection Release 9.x
7-3
Chapter 7 Migrating from Cisco Unity to Cisco Unity Connection 9.x by Gradually Moving Data
Task List for Migrating from Cisco Unity to Unity Connection 9.x by Gradually Moving Data
Copying Cisco Unity Public Distribution Lists to Unity Connection
You can copy Cisco Unity public distribution lists to Unity Connection by using the Public Distribution
List Builder for Unity on the CiscoUnityTools.com website. For more information, see the Help for the
tool and the training video at
http://www.ciscounitytools.com/Applications/Unity/PublicDistributionListBuilder/PublicDistributionL
istBuilder.html.
Removing Cisco Unity Data from Active Directory
Depending on the Cisco Unity configuration, after the migration is complete, you may want to remove
Cisco Unity–specific attributes from Active Directory accounts or delete the Active Directory accounts
by using the Uninstall Unity tool, the Bulk Subscriber Delete tool, or both. Regardless of the method you
use for removing Cisco Unity–specific attributes or removing Active Directory accounts, after you
migrate the last Cisco Unity subscriber from a given Cisco Unity server to Unity Connection, you should
still run Uninstall Unity on the server to remove Cisco Unity objects from Active Directory.
In a Unified Messaging configuration, you can remove Cisco Unity–specific attributes from Active
Directory accounts by using either the Bulk Subscriber Delete tool in Tools Depot or by using the
Uninstall Unity utility. Bulk Subscriber Delete is useful if you want to remove attributes as you migrate
subscribers. Uninstall Unity cannot be used until you have migrated all subscribers because you cannot
select the subscribers for which attributes are removed from Cisco Unity; the tool removes Cisco Unity
attributes from Active Directory accounts for all of the Cisco Unity subscribers who are homed on the
current server.
In a Voice Messaging configuration for which you created duplicate Active Directory accounts in the
corporate forest for Cisco Unity subscribers, you will probably want to remove the Active Directory
accounts, not just Cisco Unity–specific attributes. To remove Active Directory accounts, you must use
the Bulk Subscriber Delete tool.
In a Voice Messaging configuration for which you created a separate forest, removing Active Directory
attributes and accounts is unnecessary if you are going to reinstall the operating system on the
Cisco Unity servers and on the domain controllers and global catalog servers.
Task List for Migrating from Cisco Unity to Unity Connection 9.x
by Gradually Moving Data
Use the following high-level task list to gradually migrate to Unity Connection 9.x correctly. The tasks
reference detailed instructions in this guide and in other Unity Connection documentation as noted.
Follow the documentation for a successful migration.
1.
Review the “Requirements for Migrating from Cisco Unity to Cisco Unity Connection Version 9.x”
section of System Requirements for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/requirements/9xcucsysreqs.html
.
2.
Prepare the Cisco Unity servers for the migration:
a. Upgrade one or more Cisco Unity servers to Cisco Unity 9.x as necessary to satisfy the
requirements listed in the System Requirements for Cisco Unity Connection Release 9.x.
b. Install the engineering specials that allow gradual migration of Cisco Unity 5.x or 7.x servers
in a Unity Connection networking site, if applicable.
Upgrade Guide for Cisco Unity Connection Release 9.x
7-4
Chapter 7
Migrating from Cisco Unity to Cisco Unity Connection 9.x by Gradually Moving Data
Task List for Migrating from Cisco Unity to Unity Connection 9.x by Gradually Moving Data
3.
Obtain and intsall the licenses in the ELM server. For details on obtaining and installing the licenses
in the ELM server, see the "New License Fulfillment" section in the ELM user guide at
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/elmuserguide/9_0_1/CUCM_BK_E596F
D72_00_enterprise-license-manager-user-90.html For more information on Cisco Unity
Connection 9.0 Licenses, see the “Managing Licenses in Cisco Unity Connection” chapter of the
System Administration Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/guide/9xcucsagx
.html.
4.
Install one or more Unity Connection 9.x servers, if applicable, and upgrade all existing Unity
Connection servers, if any, to version 8.x. For information on:
– Installing new Unity Connection 9.x servers, see the Installation Guide for Cisco Unity
Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/installation/guide/9xcucigx.
html.
– Upgrading from Unity Connection 7.x to 9.x, see the “Upgrading Cisco Unity Connection 7.x,
8.0, 8.5, or 8.6 to the Shipping 9.x Version” chapter.
5.
See the applicable version of Release Notes for Cisco Unity Connection for additional information
on the shipping version of Cisco Unity Connection. In particular, note the items in the section
“Installation and Upgrade Information.” Release notes are available at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/release/notes/701cucrn.html.
6.
Download the following tools:
– The Cisco Unity Disaster Recovery Backup tool, available at
http://www.ciscounitytools.com/App_DisasterRecoveryTools.htm.
– The COBRAS Import for Unity Connection 7.x and Later tool, available at
http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html.
– If you want to migrate voice messages from Cisco Unity to Unity Connection: The COBRAS
Export for Unity tool, available at
http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html.
Note
The COBRAS page at CiscoUnityTools.com includes several versions of COBRAS. Take
care to download the correct versions.
– If you want to remove subscriber data from the Cisco Unity database and attributes for
Cisco Unity subscribers from Active Directory as you migrate subscribers: The Bulk Subscriber
Delete tool, available at
http://www.ciscounitytools.com/Applications/Unity/BulkSubscriberDelete403/BulkSubscriber
Delete403.html.
– If Cisco Unity attributes and objects are stored in the corporate directory: The Uninstall Unity
tool, available at
http://www.ciscounitytools.com/Applications/Unity/UninstallUnity/UninstallUnity.html.
7.
On the first Cisco Unity server, install the tools that you downloaded in Step 6., including COBRAS
Import for Unity Connection 7.x.
When Cisco Unity failover is configured:
– Install the Cisco Unity Disaster Recovery Backup tool on the secondary server.
– Install all other tools on the active server, regardless of whether the active server is the primary
or secondary server.
Upgrade Guide for Cisco Unity Connection Release 9.x
7-5
Chapter 7 Migrating from Cisco Unity to Cisco Unity Connection 9.x by Gradually Moving Data
Task List for Migrating from Cisco Unity to Unity Connection 9.x by Gradually Moving Data
8.
Set up Unity Connection networking. For more information, see the “Setting Up Networking
Between Cisco Unity and Cisco Unity Connection 9.x Servers” chapter of the Networking Guide for
Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/networking/guide/9xcucnetx.ht
ml.
9.
Confirm that the Cisco Unity server that you are migrating to Unity Connection can ping the
Cisco Unity site gateway to the Unity Connection site.
10. Back up the Cisco Unity server by using the Cisco Unity Disaster Recovery tools. This backup will
not be used to migrate data to the Unity Connection 8.x system; we recommend it only so you can
revert to Cisco Unity if necessary.
11. If you want to migrate voice messages from Cisco Unity to Unity Connection: Export data and voice
messages by using COBRAS Export for Unity.
Caution
We discourage migrating voice messages. For more information, see the “Overview of a
Gradual Migration from Cisco Unity to Cisco Unity Connection 9.x” section on page 7-1.
12. If you do not to migrate voice messages from Cisco Unity to Unity Connection: Configure access for
migrated users to their old voice messages on the Cisco Unity server:
a. On the phone system, set up a new voicemail pilot number that calls Cisco Unity.
b. In Cisco Unity Administrator, in the Direct Calls call routing table, add a direct routing rule to
the top of the routing table. Configure the new routing rule to respond to calls from the pilot
number that you set up in Task 12.a., and route calls to the Sign-In Archived Mailbox
conversation, which gives migrated users access to their old Cisco Unity mailbox. The
conversation prompts callers to enter their Cisco Unity primary extension and PIN.
Alternate extensions are all deleted when a subscriber is migrated, so subscribers cannot use
alternate extensions to access archived mailboxes.
13. Give the following information to the Cisco Unity subscribers you are about to migrate:
– Accessing their new voice messages in Unity Connection.
– If you do not to migrate voice messages from Cisco Unity to Unity Connection: Accessing their
old Cisco Unity voice messages by using the pilot number that you set up in Task 12.a.
14. Use COBRAS to migrate Cisco Unity subscribers to Unity Connection.
If you are configuring single inbox, and if Cisco Unity is configured as unified messaging, so Unity
Connection voice messages that are synchronized to Exchange will be saved in the same mailbox
that Cisco Unity voice messages are stored in now, we recommend that you select the Include
Corporate Email Addresses from Backup for New User Creation checkbox in COBRAS. When
you restore Cisco Unity data on the Unity Connection server, the Exchange email addresses
associated with Cisco Unity users will be saved in the Corporate Email Address field on the User
Basics page in Cisco Unity Connection Administration. This will simplify configuration of single
inbox later in the migration process.
For more information, see Help for the tool at
http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html.
Upgrade Guide for Cisco Unity Connection Release 9.x
7-6
Chapter 7
Migrating from Cisco Unity to Cisco Unity Connection 9.x by Gradually Moving Data
Task List for Migrating from Cisco Unity to Unity Connection 9.x by Gradually Moving Data
Caution
Do not migrate subscribers during normal business hours. Cisco Unity subscribers who are
being migrated to Unity Connection can access neither their archived messages in Cisco Unity
nor their new messages in Unity Connection while they are being migrated. In addition, even
after they have been migrated, they cannot access new messages until you have reconfigured
their phone or the phone system as explained in Task 15.
15. Reconfigure the phone or the phone system to:
– Route calls to Unity Connection when the extension for the user is busy or the user does not
answer.
– Route calls to Unity Connection when the user presses the Messages button, if applicable.
16. Wait for information on all of the migrated subscribers to replicate:
– Cisco Unity subscribers that have been migrated to Unity Connection no longer appear in
Cisco Unity Administrator.
– In Connection Administration, users that have been migrated from Cisco Unity appear as
regular users. (Before the migration starts, they appear as contacts. While the migration is
occurring, they appear both as contacts and as users.)
17. If you want to migrate voice messages from Cisco Unity to Unity Connection:
a. Install COBRAS Import for Unity Connection 7.x and later on a Windows computer other than
the Cisco Unity server. COBRAS Import can be run from the Cisco Unity server, but it runs
better on a computer on which Cisco Security Agent for Cisco Unity is not running.
b. Run COBRAS Import to import voice messages into Unity Connection for the migrated users.
For more information, see Help for the tool at
http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html.
18. Optionally, remove migrated Cisco Unity subscribers by using the Bulk Subscriber Delete tool in
the Administration Tools folder in Tools Depot. Bulk Subscriber Delete removes selected
subscribers from the Cisco Unity database and lets you choose one of the following options:
– Remove Cisco Unity-specific properties for the selected subscribers from Active Directory.
– Remove Active Directory account and the Exchange mailbox for the selected subscribers.
For more information, see:
– Help for the tool at
http://www.ciscounitytools.com/Applications/Unity/BulkSubscriberDelete403/BulkSubscriber
Delete403.html.
– The “Removing Cisco Unity Data from Active Directory” section on page 7-4.
19. Repeat Task 13. through Task 18. to migrate the remaining Cisco Unity subscribers on this server to
Unity Connection.
20. If Cisco Unity attributes and objects are in the corporate directory: Uninstall Cisco Unity, which
removes Cisco Unity attributes and objects from Active Directory. For more information, see the
“Removing Cisco Unity Data from Active Directory” section on page 7-4.
21. Repeat Task 7. through Task 20. to migrate subscribers on the remaining Cisco Unity servers to
Unity Connection.
Upgrade Guide for Cisco Unity Connection Release 9.x
7-7
Chapter 7 Migrating from Cisco Unity to Cisco Unity Connection 9.x by Gradually Moving Data
Task List for Migrating from Cisco Unity to Unity Connection 9.x by Gradually Moving Data
Upgrade Guide for Cisco Unity Connection Release 9.x
7-8
CH A P T E R
8
Migrating from a Cisco Unity Connection
Physical Servers to a Unity Connection 9.x Virtual
Machine
This chapter contains the following sections:
•
Task List for Migrating from a Unity Connection Standalone Physical Server to a Unity Connection
9.x Virtual Machine, page 8-1
•
Replacing the Publisher and Subscriber Servers or the Hard Disks in Both Servers in a Unity
Connection 9.x Cluster, page 10-8, page 8-4
•
Changing the Boot Order of the Unity Connection 9.x Virtual Machine, page 8-4
Task List for Migrating from a Unity Connection Standalone
Physical Server to a Unity Connection 9.x Virtual Machine
Revised June 26, 2013
1. Review the section “Requirements for Installing Cisco Unity Connection 9.x on a Virtual Machine”
in System Requirements for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/requirements/9xcucsysreqs.html
.
2.
In the Cisco Unity Connection 9.x Supported Platforms List, in the table of virtualization
specifications, determine which VMware configuration you want to deploy on the Unity Connection
server, based on the maximum number of ports and the maximum number of users. Then make note
of the VMware OVA template that corresponds with that configuration. The document is available
at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/supported_platforms/9xcucspl.h
tml.
3.
Optional: Download the VMware OVA template that you identified in Task 2. See the “Installing
Cisco Unity Connection for the First Time on a Virtual Machine” section in the applicable Release
Notes for Cisco Unity Connection at
http://www.cisco.com/en/US/products/ps6509/prod_release_notes_list.html.
You can also manually configure a virtual machine; if you prefer that option, you do not need the
OVA template.
Upgrade Guide for Cisco Unity Connection Release 9.x
8-1
Chapter 8 Migrating from a Cisco Unity Connection Physical Servers to a Unity Connection 9.x Virtual Machine
Task List for Migrating from a Unity Connection Standalone Physical Server to a Unity Connection 9.x Virtual Machine
Information on downloading a VMware OVA template appears in the Release Notes for
Cisco Unity Connection for versions 9.x and later.
Note
4.
If the Unity Connection physical server is running version 7.1(3), or version 8.0(2) or later: Skip to
Task 5.
If the Unity Connection physical server is running version 8.0(1): Upgrade to Unity Connection 9.x:
See the “Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version”
chapter of this guide.
If the Unity Connection physical server is running version 7.1(2) or earlier: Upgrade to Unity
Connection 7.1(3). See the applicable chapter in the Upgrade Guide for Cisco Unity Connection
Release 7.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/upgrade/guide/7xcucrugx.html.
(You upgrade to version 9.x in a later task.)
Caution
Running Unity Connection 7.1(3) in a virtual environment for any longer than is required for
the migration is not supported.
5.
Provision the physical host where the Unity Connection virtual machine will run, according to the
“Requirements for Installing a Cisco Unity Connection 9.x Virtual Machine” section in System
Requirements for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/requirements/9xcucsysreqs.html
.
6.
If you downloaded the VMware OVA template in Task 3.: Deploy the template, which creates a
virtual machine and configures it.
If you did not download the VMware OVA template in Task 3.: Create a virtual machine for the Unity
Connection server, and configure the virtual machine hardware properties to match the settings in
the “Requirements for Installing a Cisco Unity Connection 9.x Virtual Machine” section in System
Requirements for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/requirements/9xcucsysreqs.html
.
7.
If the physical server has more total available disk space than the virtual machine: Change the
VMware virtual machine hardware configuration so the Unity Connection virtual machine has as
much as or more total available disk space than the physical server.
Total available disk space is the amount of disk space usable by Unity Connection after accounting
for the RAID configuration. (For example, two 146-GB hard disks configured as RAID 1 provide
only 146 GB of total available disk space.)
8.
In the VMware vSphere Client, configure the virtual disks that are assigned to the Unity Connection
virtual machine in independent-persistent mode. This provides the best storage performance.
9.
On the virtual machine, change the BIOS setting so the virtual machine boots first from the DVD
virtual device, then from the virtual hard disk. See the “Changing the Boot Order of the Unity
Connection 9.x Virtual Machine” section on page 8-4.
10. Back up the Unity Connection physical server by using the Disaster Recovery System. For more
information, see the applicable Disaster Recovery System Administration Guide for Cisco Unity
Connection at http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
Upgrade Guide for Cisco Unity Connection Release 9.x
8-2
Chapter 8
Migrating from a Cisco Unity Connection Physical Servers to a Unity Connection 9.x Virtual Machine
Task List for Migrating from a Unity Connection Standalone Physical Server to a Unity Connection 9.x Virtual Machine
11. Shut down the Unity Connection physical server by using the CLI command utils system shutdown.
For more information, see the applicable Command Line Interface Reference Guide for Cisco
Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
12. On the virtual machine, install the exact version of Unity Connection that is installed on the physical
server, including engineering specials, if any. See the Installation Guide for Cisco Unity Connection
Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/installation/guide/9xcucigx.html
.
The following two installation settings must be the same on the Unity Connection virtual machine
as on the Unity Connection physical server, or using the Disaster Recovery System to transfer data
from the physical server to the virtual machine will fail:
•
Hostname of the server
•
IP address of the server
We recommend that you enter settings that are unlikely to change for the foreseeable future:
•
Time zone
•
NTP server
•
NIC speed and duplex settings
•
DHCP settings
•
Primary DNS settings
•
SMTP hostname
•
X.509 Certificate information (Organization, Unit, Location, State, and Country)
You must give the Unity Connection virtual machine the same hostname as the Unity Connection
physical server so you can restore data. After you have restored data, you may change the hostname
and/or IP address of the Unity Connection virtual machine.
13. Restore data on the Unity Connection virtual machine by using the backup that you made in Task 10.
14. Optional: Change the hostname of the Unity Connection virtual machine. See the “Renaming
Cisco Unity Connection 9.x Servers” chapter of this guide.
15. If you installed Unity Connection 7.1(3) on the virtual machine: Upgrade to version 9.x or later. See
the “Upgrading Cisco Unity Connection 7.x, 8.0, 8.5, or 8.6 to the Shipping 9.x Version” chapter of
this guide.
16. Post installation, if you have installed Unity Connection on a virtual machine with 1v CPU and upto
4 GB RAM, make sure to install the ciscocm.cuc_license_patch.sgn COP file. For more information
on the specific Unity Connection version for which you need to install the COP file, see the Readme
file available at the Download Software page. To download the cop file, sign in to a computer with
a high-speed Internet connection, and go to the Voice and Unified Communications Downloads page
at http://www.cisco.com/cisco/software/navigator.html?mdfid=280082558.
Note
To access the software download page, you must be signed in to Cisco.com as a registered user.
Upgrade Guide for Cisco Unity Connection Release 9.x
8-3
Chapter 8 Migrating from a Cisco Unity Connection Physical Servers to a Unity Connection 9.x Virtual Machine
Replacing the Publisher and Subscriber Servers or the Hard Disks in Both Servers in a Unity Connection 9.x Cluster,
Replacing the Publisher and Subscriber Servers or the Hard
Disks in Both Servers in a Unity Connection 9.x Cluster, page
10-8
To replace the Publisher and Subscriber servers or the Hard Disk in both the servers in a cluster, see the
following section Replacing the Publisher and Subscriber Servers or the Hard Disks in Both Servers in
a Unity Connection 9.x Cluster, page 10-8
Changing the Boot Order of the Unity Connection 9.x Virtual
Machine
Do the procedure in this section to change the BIOS setting so the virtual machine boots first from the
DVD virtual device, then from the virtual hard disk.
To Change the Boot Order of the Unity Connection 9.x Virtual Machine
Step 1
In VMware vSphere Client, power off the virtual machine on which you deployed the OVA template.
Step 2
In the left pane of vSphere Client, right-click the name of the virtual machine, and select Edit Settings.
Step 3
In the Virtual Machine Properties dialog box, select the Options tab.
Step 4
In the Settings column, under Advanced, select Boot Options.
Step 5
Under Force BIOS Setup, check the The Next Time the Virtual Machine Boots, Force Entry into the
BIOS Setup Screen check box.
Step 6
Select OK to close the Virtual Machine Properties dialog box.
Step 7
Power on the virtual machine. The virtual machine boots into the BIOS menu.
Step 8
Navigate to the Boot menu, and change the boot device order so the CD-ROM device is listed first and
the Hard Drive device is listed second.
Step 9
Save the change, and exit BIOS setup.
Upgrade Guide for Cisco Unity Connection Release 9.x
8-4
CH A P T E R
9
Adding or Removing Cisco Unity Connection 9.x
Languages
This chapter contains the following sections:
•
Task List for Adding Languages to a Unity Connection 9.x Server (No Unity Connection Cluster),
page 9-1
•
Task List for Adding Languages to a Unity Connection 9.x Cluster, page 9-2
•
Downloading Unity Connection 9.x Language Files, page 9-3
•
Installing Unity Connection 9.x Language Files, page 9-4
•
Changing Unity Connection 9.x Language Settings, page 9-7
•
Removing Unity Connection 9.x Language Files, page 9-7
Task List for Adding Languages to a Unity Connection 9.x Server
(No Unity Connection Cluster)
Note
Languages are not licensed, and Unity Connection 9.x does not enforce a limit on the number of
languages you can install and use. However, the more languages you install, the less hard-disk space is
available for storing voice messages. In the Cisco Unity Connection 9.x Supported Platforms List
(http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/supported_platforms/9xcucspl.html
), information on the number of minutes of storage available on each server assumes that you have
installed no more than five languages.
Do the following tasks to download and install languages in addition to English-United States on a Unity
Connection server that is not part of a Unity Connection cluster.
1.
Download the Unity Connection languages that you want to install. See the “Downloading Unity
Connection 9.x Language Files” section on page 9-3.
2.
Install the Unity Connection languages that you downloaded in Task 1. See the “Installing Unity
Connection 9.x Language Files” section on page 9-4.
Upgrade Guide for Cisco Unity Connection Release 9.x
9-1
Chapter 9
Adding or Removing Cisco Unity Connection 9.x Languages
Task List for Adding Languages to a Unity Connection 9.x Cluster
3.
If you are using Japanese because you want Cisco Unity Connection Administration to be localized:
Download and install the Cisco Unified Communications Manager Japanese locale. See the “Locale
Installation” section in the “Software Upgrades” chapter of the applicable Cisco Unified
Communications Operating System Administration Guide at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
4.
If you are using additional languages because you want the Cisco Personal Communications
Assistant to be localized: Download and install the corresponding Cisco Unified Communications
Manager locales. See the “Locale Installation” section in the “Software Upgrades” chapter of the
Cisco Unified Communications Operating System Administration Guide at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
5.
Change language settings in Cisco Unity Connection Administration, as applicable. See the
“Changing Unity Connection 9.x Language Settings” section on page 9-7.
Task List for Adding Languages to a Unity Connection 9.x Cluster
Note
Languages are not licensed, and Unity Connection 9.x does not enforce a limit on the number of
languages you can install and use. However, the more languages you install, the less hard-disk space is
available for storing voice messages. In the Cisco Unity Connection 9.x Supported Platforms List
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/supported_platforms/9xcucspl.html,
information on the number of minutes of storage available on each server assumes that you have installed
no more than five languages. Modified this task list for CPCA in 8.6(2), PY, 8/10/11.
Do the following tasks to download and install languages in addition to English-United States on both
servers in a Unity Connection cluster.
1.
Download the Unity Connection languages that you want to install. See the “Downloading Unity
Connection 9.x Language Files” section on page 9-3.
2.
Change the subscriber server to Primary status (if it does not have Primary status already). The
publisher server must have Secondary status in order to install the Unity Connection languages. See
the “To Manually Change an 9.x Server from Secondary Status to Primary Status” procedure in the
“Manually Changing 9.x Server Status” section in the “Administering a Cisco Unity Connection 9.x
Cluster” chapter of the Cluster Configuration and Administration Guide for Cisco Unity Connection
at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/cluster_administration/guide/9x
cuccagx.html.
3.
On the publisher server, install the Unity Connection languages that you downloaded in Task 1. See
the “Installing Unity Connection 9.x Language Files” section on page 9-4.
4.
If you are using Japanese because you want Cisco Unity Connection Administration to be localized:
Download and install the Cisco Unified Communications Manager Japanese locale on the publisher
server. See the “Locale Installation” section in the “Software Upgrades” chapter of the applicable
Cisco Unified Communications Operating System Administration Guide at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
5.
If you are using additional languages because you want the Cisco Personal Communications
Assistant to be localized: Download and install the corresponding Cisco Unity Connection locales
on the publisher server.
Upgrade Guide for Cisco Unity Connection Release 9.x
9-2
Chapter 9
Adding or Removing Cisco Unity Connection 9.x Languages
Downloading Unity Connection 9.x Language Files
6.
Change the publisher server to Primary status. See the “To Manually Change an 9.x Server from
Secondary Status to Primary Status” procedure in the “Manually Changing 9.x Server Status”
section in the “Administering a Cisco Unity Connection 9.x Cluster” chapter of the Cluster
Configuration and Administration Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/cluster_administration/guide/9x
cuccagx.html.
7.
On the subscriber server, install the same Unity Connection languages that you installed in Task 3.
8.
If you are using Japanese because you want Cisco Unity Connection Administration to be localized:
On the subscriber server, install the Cisco Unified Communications Manager Japanese locale that
you installed in Task 4.
9.
If you are using additional languages because you want the Cisco Personal Communications
Assistant to be localized: On the subscriber server, install the same Cisco Unified Communications
Manager locales that you installed in Task 5.
10. Change language settings in Cisco Unity Connection Administration, as applicable. See the
“Changing Unity Connection 9.x Language Settings” section on page 9-7.
Downloading Unity Connection 9.x Language Files
RTo Download Unity Connection 9.x Language Files
Step 1
On a computer with a high-speed Internet connection, go to the Voice and Unified Communications
Downloads page at http://tools.cisco.com/support/downloads/pub/Redirect.x?mdfid=278875240.
Note
To access the software download page, you must be signed in to Cisco.com as a registered user.
Step 2
In the tree control on the Downloads page, expand Unified Communications Applications > Voicemail
and Unified Messaging > Cisco Unity Connection, and select the applicable Unity Connection
version.
Step 3
On the Select a Software Type page, select Cisco Unity Connection Locale Installer.
Step 4
On the Select a Release page, select the applicable Unity Connection version. The download links for
languages appear on the right side of the page.
Step 5
Confirm that the computer you are using has sufficient hard-disk space for the downloaded files. (The
download file sizes appear below the download links.)
The filename for each language is uc-locale-<two-letter language abbreviation>_<two-letter country
abbreviation>-<version>.cop.sgn. (The full name of each language also appears on the page.)
Step 6
Select the name of a file to download.
Step 7
On the Download Image page, make note of the MD5 value.
Step 8
Follow the on-screen prompts to complete the download.
Step 9
Repeat Step 6 through Step 8 for each additional Connection language that you want to install.
Step 10
For each downloaded file, use a checksum generator to confirm that the MD5 checksum matches the
checksum that is listed on Cisco.com. If the values do not match, the downloaded file is damaged.
Upgrade Guide for Cisco Unity Connection Release 9.x
9-3
Chapter 9
Adding or Removing Cisco Unity Connection 9.x Languages
Installing Unity Connection 9.x Language Files
Caution
Do not attempt to use a damaged file to install software or the results will be unpredictable.
If the MD5 values do not match, download the file again until the value for the downloaded
file matches the value listed on Cisco.com.
Free checksum tools are available on the Internet—for example, the Microsoft File Checksum Integrity
Verifier utility. The utility is described in Microsoft Knowledge Base article 841290, Availability and
Description of the File Checksum Integrity Verifier Utility. The KB article also includes a link for
downloading the utility.
Step 11
Step 12
Either copy the downloaded files to an FTP or SFTP server, or burn the files to CDs or DVDs. If you
burn discs of the files, note the following considerations:
•
Use the Joliet file system, which accommodates filenames up to 64 characters long.
•
If the disc-burning application that you are using includes an option to verify the contents of the
burned disc, select that option. This causes the application to compare the contents of the burned
disc with the source files.
•
Label the discs “Cisco Unity Connection <version> Languages.”
Delete the downloaded files to free disk space.
Installing Unity Connection 9.x Language Files
You can install language files by using a CD or DVD in the Unity Connection server, or by accessing the
files on a remote source. See the applicable section:
•
Installing Unity Connection 9.x Language Files from a Disc, page 9-4
•
Installing Unity Connection 9.x Language Files from a Network Location or from a Remote Server,
page 9-5
Installing Unity Connection 9.x Language Files from a Disc
To Install Unity Connection 9.x Language Files from a Disc
Step 1
Stop the Connection Conversation Manager and Connection Mixer services:
a.
Start Cisco Unity Connection Serviceability.
b.
From the Tools menu, select Service Management.
c.
Under Critical Services, in the Connection Conversation Manager row, select Stop.
d.
Wait for the service to stop.
e.
Also under Critical Services, in the Connection Mixer row, select Stop.
f.
Wait for the service to stop.
Step 2
Insert the Languages disc in the disc drive.
Step 3
Sign in to Cisco Unified Operating System Administration.
Upgrade Guide for Cisco Unity Connection Release 9.x
9-4
Chapter 9
Adding or Removing Cisco Unity Connection 9.x Languages
Installing Unity Connection 9.x Language Files
Step 4
From the Software Upgrades menu, select Install/Upgrade. The Software Installation/Upgrade window
appears.
Step 5
In the Source list, select DVD/CD.
Step 6
In the Directory field, enter the path to the folder that contains the language file on the CD or DVD.
If the language file is in the root folder or if you created an ISO image DVD, enter a slash (/) in the
Directory field.
Step 7
To continue the language installation process, select Next.
Step 8
Select the language that you want to install, and select Next.
Step 9
Monitor the progress of the download.
Step 10
If you want to install another language: Select Install Another, and repeat Step 4 through Step 9.
If you are finished installing languages: Restart services:
Note
a.
Start Cisco Unity Connection Serviceability.
b.
From the Tools menu, select Service Management.
c.
Under Critical Services, in the Connection Conversation Manager row, select Start.
d.
Wait for the service to start.
e.
Also under Critical Services, in the Connection Mixer row, select Start.
f.
Wait for the service to start.
g.
If you installed Japanese: Run the CLI command utils service restart Cisco Tomcat to restart the
Tomcat service.
Make sure that the multilingual .cop files are installed on the exact specific CUC build that they were
created for. Applying incorrect .cop files for your specific version results in an unexpected behavior of
the user conversations.
Installing Unity Connection 9.x Language Files from a Network Location or from
a Remote Server
During this procedure, do not use the web browser controls (for example, Refresh/Reload) while
accessing Cisco Unified Operating System Administration. Instead, use the navigation controls in the
administration interface.
To Install Unity Connection 9.x Language Files from a Network Location or from a Remote Server
Step 1
Stop the Connection Conversation Manager and Connection Mixer services:
a.
Start Cisco Unity Connection Serviceability.
b.
From the Tools menu, select Service Management.
c.
Under Critical Services, in the Connection Conversation Manager row, select Stop.
d.
Wait for the service to stop.
e.
Also under Critical Services, in the Connection Mixer row, select Stop.
Upgrade Guide for Cisco Unity Connection Release 9.x
9-5
Chapter 9
Adding or Removing Cisco Unity Connection 9.x Languages
Installing Unity Connection 9.x Language Files
f.
Wait for the service to stop.
Sign in to Cisco Unified Operating System Administration.
Step 2
From the Software Upgrades menu, select Install/Upgrade. The Software Installation/Upgrade window
appears.
Step 3
In the Source list, select Remote Filesystem.
Step 4
In the Directory field, enter the path to the folder that contains the language file on the remote system.
If the language file is located on a Linux or Unix server, you must enter a forward slash at the beginning
of the folder path. (For example, if the language file is in the languages folder, you must enter
/languages.)
If the language file is located on a Windows server, remember that you are connecting to an FTP or SFTP
server, so use the appropriate syntax:
•
Begin the path with a forward slash (/) and use forward slashes throughout the path.
•
The path must start from the FTP or SFTP root folder on the server, so you cannot enter a Windows
absolute path, which starts with a drive letter (for example, C:).
Step 5
In the Server field, enter the server name or IP address.
Step 6
In the User Name field, enter your user name on the remote server.
Step 7
In the User Password field, enter your password on the remote server.
Step 8
In the Transfer Protocol list, select the applicable option.
Step 9
Select Next.
Step 10
Select the language that you want to install, and select Next.
Step 11
Monitor the progress of the download.
If you lose your connection with the server or close your browser during the installation process, you
may see the following message when you try to access the Software Upgrades menu again:
Warning: Another session is installing software, click Assume Control to take over the installation.
If you are sure you want to take over the session, select Assume Control.
If Assume Control does not display, you can also monitor the language installation with the Real-Time
Monitoring Tool.
Step 12
If you want to install another language,: Select Install Another, and repeat Step 2 through Step 11.
If you are finished installing languages: Restart services:
a.
Start Cisco Unity Connection Serviceability.
b.
From the Tools menu, select Service Management.
c.
Under Critical Services, in the Connection Conversation Manager row, select Start.
d.
Wait for the service to start.
e.
Also under Critical Services, in the Connection Mixer row, select Start.
f.
Wait for the service to start.
g.
If you installed Japanese: Run the CLI command utils service restart Cisco Tomcat to restart the
Tomcat service.
Upgrade Guide for Cisco Unity Connection Release 9.x
9-6
Chapter 9
Adding or Removing Cisco Unity Connection 9.x Languages
Changing Unity Connection 9.x Language Settings
Note
Make sure that the multilingual .cop files are installed on the exact specific CUC build that they were
created for. Applying incorrect .cop files for your specific version results in an unexpected behavior of
the user conversations.
Changing Unity Connection 9.x Language Settings
Table 9-1 lists the documentation that provides information and procedures for changing language
settings.
Table 9-1
Documentation for Changing Unity Connection 9.x Language Settings
Language Settings
Documentation
System prompts for all users
The “Language of System Prompts” section in the “Changing Conversation Settings
for All Users in Cisco Unity Connection 9.x” chapter of the System Administration
Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/gu
ide/9xcucsag130.html
System prompts for templates,
or for one or more individual users
The “Phone Language That Users and Callers Hear” section in the “Setting Up
Features and Functionality That Are Controlled by User Account Settings in
Cisco Unity Connection 9.x” chapter of the User Moves, Adds, and Changes Guide
for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/user_mac/guide/9
xcucmacx.html.
Call handlers
The “Changing Phone Language Settings” section in the “Managing Call Handlers in
Cisco Unity Connection 9.x” chapter of the System Administration Guide for
Cisco Unity Connection.
Directory handlers
The “Changing Phone Language Settings” section in the “Managing Directory
Handlers in Cisco Unity Connection 9.x” chapter of the System Administration Guide
for Cisco Unity Connection.
Interview handlers
The “Changing Phone Language Settings” section in the “Managing Interview
Handlers in Cisco Unity Connection 9.x” chapter of the System Administration Guide
for Cisco Unity Connection.
Call routing tables
The “Changing Phone Language Settings” section in the “Managing Call Routing
Tables in Cisco Unity Connection 9.x” chapter of the System Administration Guide
for Cisco Unity Connection.
Removing Unity Connection 9.x Language Files
Revised October 31, 2012
To Remove a Unity Connection 9.x Language File
Step 1
Sign in to the command-line interface as a platform administrator.
Upgrade Guide for Cisco Unity Connection Release 9.x
9-7
Chapter 9
Adding or Removing Cisco Unity Connection 9.x Languages
Removing Unity Connection 9.x Language Files
Note
Make sure to stop Connection Conversation Manager and Connection Mixer services before uninstalling
the languages
Step 2
Run the CLI command show cuc locales to display a list of installed language files.
Step 3
In the command results, find the language that you want to remove, and note the value of the Locale
column for the language.
Step 4
Run the CLI command delete cuc locale <code> to remove the language, where <code> is the value of
the Locale column that you found in Step 3.
When the command completes, the following information appears:
<code> uninstalled
Upgrade Guide for Cisco Unity Connection Release 9.x
9-8
CH A P T E R
10
Replacing Cisco Unity Connection 9.x Servers or
Hard Disks
This chapter contains the following sections:
•
Replacing a Single Unity Connection 9.x Server or the Hard Disks in a Single Server Without a
Unity Connection Cluster, page 10-2
•
Replacing a Publisher Server or the Hard Disks in a Publisher Server in a Unity Connection 9.x
Cluster, page 10-2
•
Replacing a Subscriber Server or the Hard Disks in a Subscriber Server in a Unity Connection 9.x
Cluster, page 10-5
•
Replacing the Publisher and Subscriber Servers or the Hard Disks in Both Servers in a Unity
Connection 9.x Cluster, page 10-8
•
Replacing a Unity Connection 9.x Site Gateway in a Cisco Voicemail Organization, page 10-15
•
Installing Replacement Hard Disks in a Unity Connection 9.x Server, page 10-16
Note
If you are replacing a physical server with a virtual machine, see the “Migrating from a Cisco Unity
Connection Physical Servers to a Unity Connection 9.x Virtual Machine” instead.
Note
After upgrading, you need to re-install the corresponding multilingual.cop file for the language other
than English (United States). Please see “Installing Additional Languages on the Cisco Unity
Connection 9.x Server” chapter of the Installation Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/9x/installation/guide/9xcucigx/9xcu
cig030.html
Note
If RAID mirroring is already configured with Unity Connection and at least one of the hard disk is
functional, then you need not to install a replacement publisher server. To perform failed RAID disk
replacement, see the information at
http://www.cisco.com/c/en/us/support/docs/unified-communications/mcs-7835-i3/117568-problemsolu
tion-CUC-00.html.
Upgrade Guide for Cisco Unity Connection Release 9.x
10-1
Chapter 10 Replacing Cisco Unity Connection 9.x Servers or Hard Disks
Replacing a Single Unity Connection 9.x Server or the Hard Disks in a Single Server Without a Unity Connection Cluster
Replacing a Single Unity Connection 9.x Server or the Hard
Disks in a Single Server Without a Unity Connection Cluster
Use the high-level task list in this section to correctly replace a single Unity Connection 9.x server or to
correctly replace the hard disks in a single Unity Connection 9.x server.
Note
Do the same tasks if intrasite networking is configured. After data is restored, intrasite networking
automatically starts working again.
1.
If you are replacing the server, not just replacing hard disks in the subscriber server, use the Disaster
Recovery System to back up the Unity Connection server. See the Disaster Recovery System
Administration Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/drs_administration/guide/9xcuc
drsag.html.
2.
Shut down the server.
3.
If you are replacing the server, disconnect the network cable from the old server and connect it to
the new server.
If you are replacing hard disks, do the procedure in the “Installing Replacement Hard Disks in a
Unity Connection 9.x Server” section on page 10-16.
4.
Reinstall Unity Connection. See “Part 1: Installing and Configuring the Cisco Unity Connection
Server” in the “Task List for Installing a Cisco Unity Connection 9.x System (Without a Connection
Cluster)” in the “Overview of Mandatory Tasks for Installing a Cisco Unity Connection 9.x System”
chapter of the Installation Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/installation/guide/9xcucigx.html
.
When you reinstall Unity Connection, note the following:
– You must install the same software and ES version that was previously installed on the server,
or the Disaster Recovery System restore will fail.
– You must specify the same hostname and IP address as the previous values, or the Disaster
Recovery System restore will fail.
5.
Use the Disaster Recovery System to restore data. See the Disaster Recovery System Administration
Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/drs_administration/guide/9xcuc
drsag.html.
Replacing a Publisher Server or the Hard Disks in a Publisher
Server in a Unity Connection 9.x Cluster
You can replace the publisher server or replace the hard disks in the publisher server in a Unity
Connection cluster without replacing the subscriber server. During the time that the publisher server is
not functioning, the subscriber server handles all functions for the Unity Connection cluster to avoid loss
of service to the system.
Upgrade Guide for Cisco Unity Connection Release 9.x
10-2
Chapter 10
Replacing Cisco Unity Connection 9.x Servers or Hard Disks
Replacing a Publisher Server or the Hard Disks in a Publisher Server in a Unity Connection 9.x Cluster
When replacing either the server or the hard disks in the server, you must install a replacement publisher
server; you cannot convert the subscriber server into the publisher server. (Replacing hard disks requires
that you reinstall all software on the server, so you effectively have a replacement server.) On the
replacement publisher server, you configure a new Unity Connection cluster. When you connect the
subscriber server to the new Unity Connection cluster, the subscriber server replicates its data to the
replacement publisher server without loss of service to the system. When the replacement publisher
server has Primary or Secondary status, it begins to handle calls again.
Do the applicable procedures in this section in the order listed.
To Remove the Cluster from the Unity Connection Site (Only When Intrasite Networking Is Configured)
If you are using intrasite networking, remove the server from the Unity Connection site. For instructions,
see the “Making Changes to the Networking Configuration in Cisco Unity Connection 9.x” chapter of
the Networking Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/networking/guide/9xcucnetx.html.
To Manually Change the Subscriber Server to Primary Status
Step 1
Sign in to Cisco Unity Connection Serviceability.
Step 2
On the Tools menu, select Cluster Management.
Step 3
On the Cluster Management page, under Server Manager, locate the subscriber server.
Step 4
If the subscriber server has Primary status, skip the remaining steps in this procedure and skip to the next
procedure.
If the subscriber server has Secondary status, skip to Step 5.
If the subscriber has Deactivated status, change the status to Secondary:
a.
In the Change Server Status column for the subscriber server, select Activate.
b.
When prompted to confirm changing the server status, select OK.
c.
Confirm that the Server Status column indicates that the subscriber server now has Secondary status.
Step 5
In the Change Server Status column for the subscriber server, select Make Primary.
Step 6
When prompted to confirm changing the server status, select OK.
The Server Status column displays the changed status when the change is complete.
Note
The publisher server will automatically change to Secondary status.
To Manually Change the Publisher Server from Secondary Status to Deactivated Status
Step 1
Sign in to the Real-Time Monitoring Tool (RTMT).
Step 2
On the Cisco Unity Connection menu, select Port Monitor. The Port Monitor tool appears in the right
pane.
Step 3
In the Node field, select the publisher server.
Upgrade Guide for Cisco Unity Connection Release 9.x
10-3
Chapter 10 Replacing Cisco Unity Connection 9.x Servers or Hard Disks
Replacing a Publisher Server or the Hard Disks in a Publisher Server in a Unity Connection 9.x Cluster
Step 4
In the right pane, select Start Polling.
Step 5
Note whether any voice messaging ports are currently handling calls for the server.
Step 6
Return to the Cluster Management page of Cisco Unity Connection Serviceability.
Step 7
If no voice messaging ports are currently handling calls for the publisher server, skip to Step 8.
If there are voice messaging ports that are currently handling calls for the publisher server, on the Cluster
Management page, under Change Port Status, select Stop Taking Calls for the publisher server, then
wait until RTMT shows that all ports for the publisher server are idle.
Step 8
Under Server Manager, in the Change Server Status column for the publisher server, select Deactivate.
Step 9
When prompted to confirm changing the server status, select OK.
The Server Status column displays the changed server status when the change is complete.
To Install the Replacement Publisher Server or Hard Disks
Step 1
Shut down the publisher server.
On the subscriber server, in Cisco Unity Connection Serviceability, on the Cluster Management page,
the Server Status column shows the publisher server has Not Functioning status.
Step 2
If you are replacing the publisher server, disconnect the network cable from the old publisher server and
connect it to the new publisher server.
If you are replacing hard disks, do the procedure in the “Installing Replacement Hard Disks in a Unity
Connection 9.x Server” section on page 10-16.
Step 3
Reinstall Unity Connection. Follow the instructions in “Part 1: Installing and Configuring the
Cisco Unity Connection Server” in the “Task List for Installing a Cisco Unity Connection 9.x System
(Without a Unity Connection Cluster)” in the “Overview of Mandatory Tasks for Installing a Cisco Unity
Connection 9.x System” chapter of the Installation Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/installation/guide/9xcucigx.html.
When you reinstall Unity Connection, note the following:
•
You must install the same software and ES version that is installed on the subscriber server.
Otherwise, the Unity Connection cluster may not function correctly.
•
You must specify the same hostname as the publisher server that you are replacing. Otherwise, the
Unity Connection cluster will not function.
•
You must specify the same security password as the publisher server that you are replacing, which
also matches the security password for the subscriber server. Otherwise, the Unity Connection
cluster will not function. If you do not know the security password, you can change it on the
subscriber server before you install the publisher server by using the CLI command set password
user. For more information, see the applicable version of the Command Line Interface Reference
Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
To Configure the Cluster on the Replacement Publisher Server
Step 1
Sign in to Cisco Unity Connection Administration on the publisher server.
Step 2
In Cisco Unity Connection Administration, expand System Settings, then select Cluster.
Upgrade Guide for Cisco Unity Connection Release 9.x
10-4
Chapter 10
Replacing Cisco Unity Connection 9.x Servers or Hard Disks
Replacing a Subscriber Server or the Hard Disks in a Subscriber Server in a Unity Connection 9.x Cluster
Step 3
On the Find and List Servers page, select Add New.
Step 4
On the New Server Configuration page, in the Hostname/IP Address field, enter the hostname or IP
address of the subscriber server.
Step 5
In the Description field, enter a description for the subscriber server.
Step 6
Select Save.
Step 7
Sign out of Cisco Unity Connection Administration.
To Connect the Subscriber Server to the New Unity Connection Cluster, and Replicate Data and Messages to the
Publisher Server
Step 1
Sign in to the command-line interface (CLI) for the subscriber server.
Step 2
Run the CLI command utils cuc cluster renegotiate.
Note
Step 3
When the CLI command completes, the publisher server automatically restarts.
Run the CLI command show cuc cluster status on the subscriber server to confirm that the new Unity
Connection cluster has been configured correctly.
To Re-add the Cluster to the Unity Connection Site (Only When Intrasite Networking Is Configured)
If you are using intrasite networking, re-add the cluster to the Unity Connection site. For instructions,
see the “Making Changes to the Networking Configuration in Cisco Unity Connection 9.x” chapter of
the Networking Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/networking/guide/9xcucnetx.html.
Replacing a Subscriber Server or the Hard Disks in a Subscriber
Server in a Unity Connection 9.x Cluster
You can replace the subscriber server or replace hard disks in the subscriber server in a Unity Connection
cluster. During the time that the subscriber server is not functioning, the publisher server will handle all
functions for the Unity Connection cluster to avoid loss of service to the system.
When replacing either the server or the hard disks in the server, you remove the subscriber server from
the Unity Connection cluster and add the replacement subscriber server. (Replacing hard disks requires
that you reinstall all software on the server, so you effectively have a replacement server.) After you
install the replacement subscriber server, the publisher server replicates its data to the replacement
subscriber server without loss of service to the system. When the replacement subscriber server has
Primary or Secondary status, it begins to handle calls again.
Do the applicable procedures in this section in the order listed.
Upgrade Guide for Cisco Unity Connection Release 9.x
10-5
Chapter 10 Replacing Cisco Unity Connection 9.x Servers or Hard Disks
Replacing a Subscriber Server or the Hard Disks in a Subscriber Server in a Unity Connection 9.x Cluster
To Manually Change the Publisher Server to Primary Status
Step 1
Sign in to Cisco Unity Connection Serviceability.
Step 2
On the Tools menu, select Cluster Management.
Step 3
On the Cluster Management page, under Server Manager, locate the publisher server.
Step 4
If the publisher server has Primary status, skip the remaining steps in this procedure and skip to the next
procedure.
If the publisher server has Secondary status, skip to Step 5.
If the publisher has Deactivated status, change the status to Secondary:
a.
In the Change Server Status column for the publisher server, select Activate.
b.
When prompted to confirm changing the server status, select OK.
c.
Confirm that the Server Status column indicates that the publisher server now has Secondary status.
Step 5
In the Change Server Status column for the publisher server, select Make Primary.
Step 6
When prompted to confirm changing the server status, select OK.
The Server Status column displays the changed status when the change is complete.
Note
The subscriber server automatically changes to Secondary status.
To Manually Change the Subscriber Server from Secondary Status to Deactivated Status
Step 1
Sign in to the Real-Time Monitoring Tool (RTMT).
Step 2
On the Cisco Unity Connection menu, select Port Monitor. The Port Monitor tool appears in the right
pane.
Step 3
In the Node field, select the subscriber server.
Step 4
In the right pane, select Start Polling.
Step 5
Note whether any voice messaging ports are currently handling calls for the server.
Step 6
Return to the Cluster Management page of Cisco Unity Connection Serviceability.
Step 7
If no voice messaging ports are currently handling calls for the server, skip to Step 8.
If there are voice messaging ports that are currently handling calls for the subscriber server, on the
Cluster Management page, under Change Port Status, select Stop Taking Calls for the subscriber server,
then wait until RTMT shows that all ports for the server are idle.
Step 8
Under Server Manager, in the Change Server Status column for the subscriber server, select Deactivate.
Step 9
When prompted to confirm changing server status, select OK.
The Server Status column displays the changed server status when the change is complete.
To Install the Replacement Subscriber Server or Hard Disks
Step 1
Shut down the subscriber server.
Upgrade Guide for Cisco Unity Connection Release 9.x
10-6
Chapter 10
Replacing Cisco Unity Connection 9.x Servers or Hard Disks
Replacing a Subscriber Server or the Hard Disks in a Subscriber Server in a Unity Connection 9.x Cluster
On the publisher server, in Cisco Unity Connection Serviceability, on the Cluster Management page, the
Server Status column shows the subscriber server has Not Functioning status.
Step 2
If you are replacing the subscriber server, disconnect the network cable from the old subscriber server
and connect it to the new subscriber server.
If you are replacing hard disks, do the procedure in the “Installing Replacement Hard Disks in a Unity
Connection 9.x Server” section on page 10-16.
Step 3
Follow the instructions in “Part 3: Configuring the Cluster, and Installing and Configuring the Subscriber
Unity Connection Server” in the “Task List for Installing a Cisco Unity Connection 9.x system with a
Unity Connection Cluster Configured” in the “Overview of Mandatory Tasks for Installing a Cisco Unity
Connection 9.x System” chapter of the Installation Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/installation/guide/9xcucigx.html.
When you reinstall Unity Connection, note the following:
•
You must install the same software and ES version that is installed on the publisher server.
Otherwise, the Unity Connection cluster may not function correctly.
•
You must specify the same security password as the subscriber server that you are replacing, which
also matches the security password for the publisher server. Otherwise, the Unity Connection cluster
will not function. If you do not know the security password, you can change it on the publisher
server before you install the subscriber server by using the CLI command set password user. For
more information, see the applicable version of the Command Line Interface Reference Guide for
Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
To Change the Hostname or IP Address for the Subscriber Server in Connection Administration on the Publisher
Server (Only If You Changed the Hostname or IP Address of the Subscriber Server)
Step 1
If the replacement subscriber server will have the same hostname or IP address as the subscriber server
that you removed, skip the remaining steps in this procedure and go to the next procedure.
If the replacement subscriber server will have a different hostname or IP address, sign in to Cisco Unity
Connection Administration on the publisher server.
Step 2
In Cisco Unity Connection Administration, expand System Settings, then select Cluster.
Step 3
On the Find and List Servers page, select Find to display all servers in the cluster.
Step 4
Check the check box in front of the subscriber server and select Delete Selected.
Step 5
When prompted to confirm deleting the server, select OK.
Step 6
Select Add New.
Step 7
On the New Server Configuration page, in the Hostname/IP Address field, enter the hostname or IP
address of the replacement server.
Step 8
In the Description field, enter Server 2 or another description for the server.
Step 9
Select Save.
Step 10
Sign out of Cisco Unity Connection Administration.
Upgrade Guide for Cisco Unity Connection Release 9.x
10-7
Chapter 10 Replacing Cisco Unity Connection 9.x Servers or Hard Disks
Replacing the Publisher and Subscriber Servers or the Hard Disks in Both Servers in a Unity Connection 9.x Cluster
To Confirm That the Unity Connection Cluster Is Configured
Step 1
Sign in to the command-line interface (CLI) for the subscriber server.
Step 2
Run the CLI command show cuc cluster status.
Replacing the Publisher and Subscriber Servers or the Hard
Disks in Both Servers in a Unity Connection 9.x Cluster
See the applicable section:
•
When Both Original Unity Connection 9.x Servers Are Available and Functioning, page 10-8
•
When Neither of the Original Unity Connection 9.x Servers Is Functioning, page 10-13
When Both Original Unity Connection 9.x Servers Are Available and
Functioning
When both the publisher and subscriber servers in the Unity Connection cluster are available and
functioning, you can replace both servers or replace the hard disks in both servers by completing the
process in stages:
•
While you are replacing one server, the other server will handle all functions for the Unity
Connection cluster to avoid loss of service to the system.
•
After each replacement server is installed, the other server replicates data to the replacement server.
Do the applicable procedures in this section in the order listed.
To Remove the Cluster from the Unity Connection Site (Only When Intrasite Networking Is Configured)
If you are using intrasite networking, remove the cluster from the Unity Connection site. For
instructions, see the “Making Changes to the Networking Configuration in Cisco Unity Connection 9.x”
chapter of the Networking Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/networking/guide/9xcucnetx.html.
To Manually Change the Publisher Server to Primary Status
Step 1
Sign in to Cisco Unity Connection Serviceability.
Step 2
On the Tools menu, select Cluster Management.
Step 3
On the Cluster Management page, under Server Manager, locate the publisher server.
Step 4
If the publisher server has Primary status, skip the remaining steps in this procedure and skip to the next
procedure.
If the publisher server has Secondary status, skip to Step 5.
Upgrade Guide for Cisco Unity Connection Release 9.x
10-8
Chapter 10
Replacing Cisco Unity Connection 9.x Servers or Hard Disks
Replacing the Publisher and Subscriber Servers or the Hard Disks in Both Servers in a Unity Connection 9.x Cluster
If the publisher has Deactivated status, change the status to Secondary:
a.
In the Change Server Status column for the publisher server, select Activate.
b.
When prompted to confirm changing the server status, select OK.
c.
Confirm that the Server Status column indicates that the publisher server now has Secondary status.
Step 5
In the Change Server Status column for the publisher server, select Make Primary.
Step 6
When prompted to confirm changing the server status, select OK.
The Server Status column displays the changed status when the change is complete.
Note
The subscriber server automatically changes to Secondary status.
To Manually Change a Subscriber Server from Secondary Status to Deactivated Status
Step 1
Sign in to the Real-Time Monitoring Tool (RTMT).
Step 2
On the Cisco Unity Connection menu, select Port Monitor. The Port Monitor tool appears in the right
pane.
Step 3
In the Node field, select the subscriber server.
Step 4
In the right pane, select Start Polling.
Step 5
Note whether any voice messaging ports are currently handling calls for the server.
Step 6
Return to the Cluster Management page of Cisco Unity Connection Serviceability.
Step 7
If no voice messaging ports are currently handling calls for the server, continue to Step 8.
If there are voice messaging ports that are currently handling calls for the subscriber server, on the
Cluster Management page, under Change Port Status, select Stop Taking Calls for the subscriber server,
then wait until RTMT shows that all ports for the server are idle.
Step 8
Under Server Manager, in the Change Server Status column for the subscriber server, select Deactivate.
Step 9
When prompted to confirm changing server status, select OK.
The Server Status column displays the changed server status when the change is complete.
To Install the Replacement Subscriber Server or Hard Disks
Step 1
Shut down the subscriber server.
On the publisher server, in Cisco Unity Connection Serviceability, on the Cluster Management page, the
Server Status column shows the subscriber server has Not Functioning status.
Step 2
If you are replacing the subscriber server, disconnect the network cable from the old subscriber server
and connect it to the new subscriber server.
If you are replacing hard disks, do the procedure in the “Installing Replacement Hard Disks in a Unity
Connection 9.x Server” section on page 10-16.
Upgrade Guide for Cisco Unity Connection Release 9.x
10-9
Chapter 10 Replacing Cisco Unity Connection 9.x Servers or Hard Disks
Replacing the Publisher and Subscriber Servers or the Hard Disks in Both Servers in a Unity Connection 9.x Cluster
Step 3
Follow the instructions in “Part 3: Configuring the Cluster, and Installing and Configuring the Subscriber
Unity Connection Server” in the “Task List for Installing a Cisco Unity Connection 9.x system with a
Unity Connection Cluster Configured” in the “Overview of Mandatory Tasks for Installing a Cisco Unity
Connection 9.x System” chapter of the Installation Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/installation/guide/9xcucigx.html.
When you reinstall Unity Connection, note the following:
•
You must install the same software and ES version that is installed on the publisher server.
Otherwise, the Unity Connection cluster may not function correctly.
•
You must specify the same security password as the subscriber server that you are replacing, which
also matches the security password for the publisher server. Otherwise, the Unity Connection cluster
will not function. If you do not know the security password, you can change it on the publisher
server before you install the subscriber server by using the CLI command set password user. For
more information, see the applicable version of the Command Line Interface Reference Guide for
Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
To Change the Hostname or IP Address for the Subscriber Server in Connection Administration on the Publisher
Server (Only If You Changed the Hostname or IP Address of the Subscriber Server)
Step 1
When you reinstalled Unity Connection, if you specified the same hostname and IP address as those for
the subscriber server that you removed, skip this procedure and go to the next procedure.
If the replacement subscriber server has a different hostname or IP address, sign in to Cisco Unity
Connection Administration on the publisher server.
Step 2
In Cisco Unity Connection Administration, expand System Settings, then select Cluster.
Step 3
On the Find and List Servers page, select Find to display all servers in the cluster.
Step 4
Check the check box in front of the subscriber server and select Delete Selected.
Step 5
When prompted to confirm deleting the server, select OK.
Step 6
Select Add New.
Step 7
On the New Server Configuration page, in the Hostname/IP Address field, enter the hostname or IP
address of the replacement server.
Step 8
In the Description field, enter Server 2 or another description for the server.
Step 9
Select Save.
Step 10
Sign out of Cisco Unity Connection Administration.
To Confirm That the Unity Connection Cluster Is Configured with the Replacement Subscriber Server
Step 1
Sign in to the command-line interface (CLI) for the subscriber server.
Step 2
Run the CLI command show cuc cluster status.
Upgrade Guide for Cisco Unity Connection Release 9.x
10-10
Chapter 10
Replacing Cisco Unity Connection 9.x Servers or Hard Disks
Replacing the Publisher and Subscriber Servers or the Hard Disks in Both Servers in a Unity Connection 9.x Cluster
To Manually Change the Subscriber Server to Primary Status
Step 1
Sign in to Cisco Unity Connection Serviceability.
Step 2
On the Tools menu, select Cluster Management.
Step 3
On the Cluster Management page, under Server Manager, locate the subscriber server.
Step 4
If the subscriber server has Primary status, skip the remaining steps in this procedure and continue to the
next procedure. If the subscriber server has Secondary status, in the Change Server Status column for
the subscriber server, select Make Primary.
Step 5
When prompted to confirm changing the server status, select OK.
The Server Status column displays the changed status when the change is complete.
Note
The publisher server will automatically change to Secondary status.
To Manually Change the Publisher Server from Secondary Status to Deactivated Status
Step 1
Sign in to the Real-Time Monitoring Tool (RTMT).
Step 2
On the Cisco Unity Connection menu, select Port Monitor. The Port Monitor tool appears in the right
pane.
Step 3
In the Node field, select the publisher server.
Step 4
In the right pane, select Start Polling.
Step 5
Note whether any voice messaging ports are currently handling calls for the server.
Step 6
Return to the Cluster Management page of Cisco Unity Connection Serviceability.
Step 7
If no voice messaging ports are currently handling calls for the publisher server, skip to Step 8.
If there are voice messaging ports that are currently handling calls for the publisher server, on the Cluster
Management page, under Change Port Status, select Stop Taking Calls for the publisher server, then
wait until RTMT shows that all ports for the publisher server are idle.
Step 8
Under Server Manager, in the Change Server Status column for the publisher server, select Deactivate.
Step 9
When prompted to confirm changing the server status, select OK.
The Server Status column displays the changed server status when the change is complete.
To Install the Replacement Publisher Server or Hard Disks
Step 1
Shut down the publisher server.
On the Cluster Management page, the Server Status column shows the publisher server has Not
Functioning status.
Step 2
If you are replacing the publisher server, disconnect the network cable from the old publisher server and
connect it to the new publisher server.
If you are replacing hard disks, do the procedure in the “Installing Replacement Hard Disks in a Unity
Connection 9.x Server” section on page 10-16.
Upgrade Guide for Cisco Unity Connection Release 9.x
10-11
Chapter 10 Replacing Cisco Unity Connection 9.x Servers or Hard Disks
Replacing the Publisher and Subscriber Servers or the Hard Disks in Both Servers in a Unity Connection 9.x Cluster
Step 3
Reinstall Unity Connection. Follow the instructions in “Part 1: Installing and Configuring the
Cisco Unity Connection Server” in the “Task List for Installing a Cisco Unity Connection 9.x System
(Without a Unity Connection Cluster)” in the “Overview of Mandatory Tasks for Installing a Cisco Unity
Connection 9.x System” chapter of the Installation Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/installation/guide/9xcucigx.html.
When you reinstall Unity Connection, note the following:
•
You must install the same software and ES version that is installed on the subscriber server.
Otherwise, the Unity Connection cluster may not function correctly.
•
You must specify the same hostname as the publisher server that you are replacing. Otherwise, the
Unity Connection cluster will not function.
•
You must specify the same security password as the publisher server that you are replacing, which
also matches the security password for the subscriber server. Otherwise, the Unity Connection
cluster will not function. If you do not know the security password, you can change it on the
subscriber server before you install the publisher server by using the CLI command set password
user. For more information, see the applicable version of the Command Line Interface Reference
Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
To Configure the Cluster on the Replacement Publisher Server
Step 1
Sign in to Cisco Unity Connection Administration on the publisher server.
Step 2
In Cisco Unity Connection Administration, expand System Settings, then select Cluster.
Step 3
On the Find and List Servers page, select Add New.
Step 4
On the New Server Configuration page, in the Hostname/IP Address field, enter the hostname or IP
address of the subscriber server.
Step 5
In the Description field, enter Server 2 or another description for the server.
Step 6
Select Save.
Step 7
Sign out of Cisco Unity Connection Administration.
To Connect the Subscriber Server to the New Unity Connection Cluster, and Replicate Data and Messages to the
Publisher Server
Step 1
Sign in to the command-line interface (CLI) for the subscriber server.
Step 2
Run the CLI command utils cuc cluster renegotiate.
Note
Step 3
When the CLI command completes, the publisher server automatically restarts.
Run the CLI command show cuc cluster status to confirm that the new Unity Connection cluster has
been configured correctly.
Upgrade Guide for Cisco Unity Connection Release 9.x
10-12
Chapter 10
Replacing Cisco Unity Connection 9.x Servers or Hard Disks
Replacing the Publisher and Subscriber Servers or the Hard Disks in Both Servers in a Unity Connection 9.x Cluster
To Re-add the Cluster to the Unity Connection Site (Only When Intrasite Networking Is Configured)
If you are using intrasite networking, re-add the cluster to the Unity Connection site. For instructions,
see the “Making Changes to the Networking Configuration in Cisco Unity Connection 9.x” chapter of
the Networking Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/networking/guide/9xcucnetx.html.
When Neither of the Original Unity Connection 9.x Servers Is Functioning
When neither the publisher nor the subscriber server in the Unity Connection cluster is functioning, and
when you have a Disaster Recovery System backup from which you can restore the Unity Connection
data, you can replace both servers or replace the hard disks in both servers at the same time. During this
process, the Unity Connection cluster is not able to answer calls.
You install the replacement publisher server and restore the backed-up Unity Connection data by using
Disaster Recovery System. Then you install the replacement subscriber server and force Unity
Connection to copy the data from the publisher server to the subscriber server. When the copying is
complete, replication will resume between the two servers. When the replacement servers have Primary
or Secondary status, they will handle calls.
Do the applicable procedures in this section in the order listed.
Note
Pre-configured backup devices must be created before restoring Connection server.
To Install the Replacement Publisher Server or Hard Disks
Step 1
Shut down the publisher server.
Step 2
If you are replacing the publisher server, disconnect the network cable from the old publisher server and
connect it to the new publisher server.
If you are replacing hard disks, do the procedure in the “Installing Replacement Hard Disks in a Unity
Connection 9.x Server” section on page 10-16.
Step 3
Reinstall Unity Connection. Follow the instructions in “Part 1: Installing and Configuring the
Cisco Unity Connection Server” in the “Task List for Installing a Cisco Unity Connection 9.x System
(Without a Unity Connection Cluster)” in the “Overview of Mandatory Tasks for Installing a Cisco Unity
Connection 9.x System” chapter of the Installation Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/installation/guide/9xcucigx.html.
When you reinstall Unity Connection, note the following:
•
You must install the same software and ES version that was installed on the previous publisher
server, or the Disaster Recovery System restore will fail.
•
You must specify the same hostname and IP address as the values on the previous publisher server,
or the Disaster Recovery System restore will fail.
Upgrade Guide for Cisco Unity Connection Release 9.x
10-13
Chapter 10 Replacing Cisco Unity Connection 9.x Servers or Hard Disks
Replacing the Publisher and Subscriber Servers or the Hard Disks in Both Servers in a Unity Connection 9.x Cluster
To Restore the Backed-up Data to the Replacement Publisher Server or Hard Disks
Step 1
Sign in to Disaster Recovery System.
Step 2
On the Restore menu, select Restore Wizard.
Step 3
On the Step 1 Restore—Choose Backup Device page, in the Device Name field, select the name of the
backup device from which you want to restore and select Next.
Step 4
On the Step 2 Restore—Choose the Backup Tar File page, in Select Backup File field, select the backup
file that you want to restore and select Next.
Note
Step 5
In the Step 3 Restore—Select the Type of Restore page, under Special Features, check the check boxes
for the features that you want to restore and select Next.
Note
Step 6
Only the features that were backed up to the file that you chose will appear on the page.
In the Step 4 Restore—Final Warning for Restore page, in the Select the Server field, select the publisher
server and select Restore.
Caution
Note
Step 7
The backup filename indicates the date and time that the system created the backup file.
The publisher server must have the same IP address and hostname as the server from which
Disaster Recovery System backed up the data. Otherwise, Disaster Recovery System Disaster
Recovery System will not restore the data.
During the restore process, do not perform any tasks with Connection Administration.
When the restore status indicates 100 percent, restart the publisher server.
To Install the Replacement Subscriber Server or Hard Disks
Step 1
Shut down the subscriber server.
Step 2
If you are replacing the subscriber server, disconnect the network cable from the old subscriber server
and connect it to the new subscriber server.
If you are replacing hard disks, do the procedure in the “Installing Replacement Hard Disks in a Unity
Connection 9.x Server” section on page 10-16.
Step 3
Reinstall Unity Connection. Follow the instructions in “Part 3: Configuring the Cluster, and Installing
and Configuring the Subscriber Unity Connection Server” in the “Task List for Installing a Cisco Unity
Connection 9.x system with a Unity Connection Cluster Configured” in the “Overview of Mandatory
Tasks for Installing a Cisco Unity Connection 9.x System” chapter of the Installation Guide for
Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/installation/guide/9xcucigx.html.
When you reinstall Unity Connection, note the following:
Upgrade Guide for Cisco Unity Connection Release 9.x
10-14
Chapter 10
Replacing Cisco Unity Connection 9.x Servers or Hard Disks
Replacing a Unity Connection 9.x Site Gateway in a Cisco Voicemail Organization
•
You must install the same software and ES version that is installed on the publisher server.
Otherwise, the Unity Connection cluster may not function correctly.
•
You must specify the same security password as the security password for the publisher server.
Otherwise, the Unity Connection cluster will not function. If you do not know the security password,
you can change it on the publisher server before you install the subscriber server by using the CLI
command set password user. For more information, see the applicable version of the Command
Line Interface Reference Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
To Copy the Data from the Publisher Server to the Subscriber Server
Step 1
Sign in to the command-line interface (CLI) for the subscriber server.
Step 2
Run the CLI command utils cuc cluster overwritedb to force Unity Connection to copy data from the
publisher server to the subscriber server:
Step 3
Run the CLI command show cuc cluster status to confirm that the new Unity Connection cluster has
been configured correctly on the subscriber server.
Step 4
Sign in to the CLI for the publisher server.
Step 5
Run the CLI command show cuc cluster status to confirm that the new Unity Connection cluster has
been configured correctly on the publisher server.
To Synchronize MWIs for Each Phone System
Step 1
During off-peak hours, sign in to either server in the Unity Connection cluster.
Step 2
In Connection Administration, expand Telephony Integrations, then select Phone System.
Step 3
On the Search Phone Systems page, select the name of the first phone system.
Step 4
On the Phone System Basics page, under Messaging Waiting Indicators, select Run.
Step 5
Select Next.
Step 6
Repeat Step 4 and Step 5 for the remaining phone systems.
Replacing a Unity Connection 9.x Site Gateway in a Cisco
Voicemail Organization
For information on replacing a Unity Connection site gateway when Connection networking is
configured, see the “Making Changes to a Unity Connection Site Gateway” section in the“Making
Changes to the Networking Configuration in Cisco Unity Connection 9.x” chapter of the Networking
Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/networking/guide/9xcucnetx.html.
Upgrade Guide for Cisco Unity Connection Release 9.x
10-15
Chapter 10
Replacing Cisco Unity Connection 9.x Servers or Hard Disks
Installing Replacement Hard Disks in a Unity Connection 9.x Server
Installing Replacement Hard Disks in a Unity Connection 9.x
Server
Use the procedure in this section to replace all hard disks in the server with blank disks as part of an
installation or upgrade.
Caution
Do not replace hard disks in the Unity Connection server with disks that contain data, even if the
replacement disks were originally disks in the same RAID in the same server.
Caution
The procedure in this section is just one part of the process of replacing hard disks in a Unity Connection
server. When replacing hard disks in a Unity Connection server, refer to the applicable task list earlier
in this chapter, or Unity Connection may not function correctly.
Warning
Before working on a system that has an on/off switch, turn OFF the power and unplug the power cord.
Statement 1
Warning
Before opening the chassis, disconnect the telephone-network cables to avoid contact with
telephone-network voltages. Statement 2
Warning
This equipment is to be installed and maintained by service personnel only as defined by AS/NZS 3260
Clause 1.2.14.3 Service Personnel. Statement 88
Warning
During this procedure, wear grounding wrist straps to avoid ESD damage to the card. Do not directly
touch the backplane with your hand or any metal tool, or you could shock yourself. Statement 94
Warning
The safety cover is an integral part of the product. Do not operate the unit without the safety cover
installed. Operating the unit without the cover in place will invalidate the safety approvals and pose
a risk of fire and electrical hazards. Statement 117
Warning
Do not work on the system or connect or disconnect cables during periods of lightning activity.
Statement 1001
Warning
Read the installation instructions before connecting the system to the power source. Statement 1004
Warning
To prevent bodily injury when mounting or servicing this unit in a rack, you must take special
precautions to ensure that the system remains stable. The following guidelines are provided to ensure
your safety:
Upgrade Guide for Cisco Unity Connection Release 9.x
10-16
Chapter 10
Replacing Cisco Unity Connection 9.x Servers or Hard Disks
Installing Replacement Hard Disks in a Unity Connection 9.x Server
• This unit should be mounted at the bottom of the rack if it is the only unit in the rack.
• When mounting this unit in a partially filled rack, load the rack from the bottom to the top with the
heaviest component at the bottom of the rack.
• If the rack is provided with stabilizing devices, install the stabilizers before mounting or servicing
the unit in the rack. Statement 1006
Warning
There is the danger of explosion if the battery is replaced incorrectly. Replace the battery only with
the same or equivalent type recommended by the manufacturer. Dispose of used batteries according
to the manufacturer’s instructions. Statement 1015
Warning
This unit is intended for installation in restricted access areas. A restricted access area can be
accessed only through the use of a special tool, lock and key, or other means of security. Statement
1017
Warning
To avoid electric shock, do not connect safety extra-low voltage (SELV) circuits to telephone-network
voltage (TNV) circuits. LAN ports contain SELV circuits, and WAN ports contain TNV circuits. Some
LAN and WAN ports both use RJ-45 connectors. Use caution when connecting cables. Statement 1021
Warning
To reduce the risk of fire, use only No. 26 AWG or larger telecommunication line cord. Statement 1023
Warning
This equipment must be grounded. Never defeat the ground conductor or operate the equipment in the
absence of a suitably installed ground conductor. Contact the appropriate electrical inspection
authority or an electrician if you are uncertain that suitable grounding is available. Statement 1024
Warning
Blank faceplates and cover panels serve three important functions: they prevent exposure to
hazardous voltages and currents inside the chassis; they contain electromagnetic interference (EMI)
that might disrupt other equipment; and they direct the flow of cooling air through the chassis. Do not
operate the system unless all cards, faceplates, front covers, and rear covers are in place. Statement
1029
Warning
Only trained and qualified personnel should be allowed to install, replace, or service this equipment.
Statement 1030
Warning
Ultimate disposal of this product should be handled according to all national laws and regulations.
Statement 1040
(For translations of the preceding safety warnings, see Regulatory Compliance and Safety Information
for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/regulatory/compliance/ucwarns.html.)
Upgrade Guide for Cisco Unity Connection Release 9.x
10-17
Chapter 10
Replacing Cisco Unity Connection 9.x Servers or Hard Disks
Installing Replacement Hard Disks in a Unity Connection 9.x Server
To Install Replacement Hard Disks in a Unity Connection 9.x Server
Step 1
Remove the cover.
Step 2
Replace all of the hard disks in the server:
Caution
Step 3
If you are replacing hard disks as part of a Unity Connection installation or upgrade, you must
remove all existing hard disks and install exactly as many hard disks as you remove, or the
Unity Connection installation or upgrade will fail.
a.
Make note of the current locations of the hard disks in the server, including which hard disk is in
which hard disk slot. If the replacement fails and you want to revert to the current configuration, you
must put the existing hard disks back into their current locations.
b.
Remove the drive trays from the server.
c.
Remove the old hard disks from the drive trays.
d.
Insert the new hard disks into the drive trays.
e.
Reinstall the drive trays in the locations that you made note of in Step a.
Reattach the cover.
Upgrade Guide for Cisco Unity Connection Release 9.x
10-18
CH A P T E R
11
Creating or Changing a Cisco Unity Connection
9.x Cluster
This chapter contains the following sections:
•
Adding an 9.x Server to Create a Unity Connection Cluster, page 11-1
•
Converting an 9.x Publisher Server to a Single Server Without a Unity Connection Cluster,
page 11-3
Adding an 9.x Server to Create a Unity Connection Cluster
When you have a single Unity Connection 9.x server, you can add a subscriber server and create a Unity
Connection cluster.
Do the three procedures in this section in the order listed.
•
To install the subscriber server
•
To configure the phone system for the Unity Connection cluster
•
To configure Cisco Unity Connection for the cluster
To Install the Subscriber Server
Follow the instructions in “Part 3: Configuring the Cluster, and Installing and Configuring the Subscriber
Unity Connection Server” in the “Task List for Installing a Cisco Unity Connection 9.x System with a
Unity Connection Cluster Configured” in the “Overview of Mandatory Tasks for Installing a Cisco Unity
Connection 9.x System” chapter of the Installation Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/installation/guide/9xcucigx.html.
Caution
Both Unity Connection servers must have the same software and ES versions installed.
Otherwise, the Unity Connection cluster may not function correctly.
Upgrade Guide for Cisco Unity Connection Release 9.x
11-1
Chapter 11
Creating or Changing a Cisco Unity Connection 9.x Cluster
Adding an 9.x Server to Create a Unity Connection Cluster
To Configure the Phone System for the Unity Connection Cluster
See the applicable documentation, depending on the phone system integration type:
Integration by Skinny Client Control Protocol (SCCP) with Cisco Unified Communications
Manager
a.
To add the ports on the phone system that will connect to the subscriber server, see the “Adding Ports
to an Existing Cisco Voice-Mail Server” section in the “Cisco Voicemail Port Wizard” chapter of the
applicable Cisco Unified Communications Manager Administration Guide at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
b.
To set the Distribution Algorithm field to Top Down for the line group of the answering voicemail
ports, see the “Configuring a Line Group” section in the “Line Group Configuration” chapter of the
applicable Cisco Unified Communications Manager Administration Guide at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
Integration by Skinny Client Control Protocol (SCCP) with Cisco Unified Communications
Manager Express
To add the ports on the phone system that will connect to the subscriber server, see the “How to
Configure Voice-Mail Integration” section in the “Integrating Voicemail” chapter of the Cisco Unified
Communications Manager Express System Administrator Guide at
http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_installation_and_configuration_g
uides_list.html.
Integration through a SIP trunk with Cisco Unified Communications Manager
See the “Programming the Cisco Unified Communications Manager Phone System for Integrating with
Cisco Unity Connection” section of the Cisco Unified Communications Manager SIP Trunk Integration
Guide for Cisco Unity Connection 9.x at
http://www.cisco.com/en/US/products/ps6509/products_installation_and_configuration_guide.
Integration through a SIP trunk with Cisco Unified Communications Manager Express
See the “Programming the Cisco Unified Communications Manager Express Phone System for
Integrating with Cisco Unity Connection” section of the Cisco Unified Communications Manager
Express SIP Trunk Integration Guide for Cisco Unity Connection 9.x at
http://www.cisco.com/en/US/products/ps6509/products_installation_and_configuration_guides_list.ht
ml.
Integration through PIMG/TIMG units
See the “Setting Up the PIMG Units” or “Setting Up the TIMG Units” section of the applicable
Cisco Unity Connection integration guide at
http://www.cisco.com/en/US/products/ps6509/products_installation_and_configuration_guides_list.ht
ml.
Other integrations that use SIP
See the “Programming the <Phone System>” section of the applicable Cisco Unity Connection
integration guide at
http://www.cisco.com/en/US/products/ps6509/products_installation_and_configuration_guides_list.ht
ml.
Upgrade Guide for Cisco Unity Connection Release 9.x
11-2
Chapter 11
Creating or Changing a Cisco Unity Connection 9.x Cluster
Converting an 9.x Publisher Server to a Single Server Without a Unity Connection Cluster
To Configure Cisco Unity Connection for the Cluster
See the applicable documentation, depending on the phone system integration:
Cisco Unified CM and Cisco Unified CM Express integrations
To add voice messaging ports to the applicable port group on the publisher server, see the “Managing
Ports” section in the “Managing the Phone System Integrations” chapter of the System Administration
Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/guide/9xcucsagx.htm
l.
Note
The total number of ports on the Unity Connection server must not exceed the number of ports
enabled by the Cisco Unity Connection license.
All phone system integrations except for PIMG/TIMG integrations
To configure the ports on the publisher server, see the “Creating the Integration with the <Phone
System>” section of the applicable Cisco Unity Connection integration guide at
http://www.cisco.com/en/US/products/ps6509/products_installation_and_configuration_guides_list.ht
ml.
Converting an 9.x Publisher Server to a Single Server Without a
Unity Connection Cluster
You can remove the subscriber server from a Unity Connection cluster so that you undo the Unity
Connection cluster. The publisher server becomes a single server without a Unity Connection cluster,
and the subscriber server is removed from the network.
Note
•
To use the subscriber server as a single server without a Unity Connection cluster, you must reinstall
Unity Connection on the server.
•
You cannot remove the publisher server from a Unity Connection cluster
Do the five procedures in this section in the order listed.
To Manually Change the Publisher Server to Primary Status
Step 1
Sign in to Cisco Unity Connection Serviceability.
Step 2
On the Tools menu, select Cluster Management.
Step 3
On the Cluster Management page, under Server Manager, locate the publisher server.
Step 4
If the publisher server has Primary status, skip the remaining steps in this procedure and skip to the next
procedure.
If the publisher server has Secondary status, skip to Step 5.
Upgrade Guide for Cisco Unity Connection Release 9.x
11-3
Chapter 11
Converting an 9.x Publisher Server to a Single Server Without a Unity Connection Cluster
Creating or Changing a Cisco Unity Connection 9.x Cluster
If the publisher has Deactivated status, change the status to Secondary:
a.
In the Change Server Status column for the publisher server, select Activate.
b.
When prompted to confirm changing the server status, select OK.
c.
Confirm that the Server Status column indicates that the publisher server now has Secondary status.
Step 5
In the Change Server Status column for the publisher server, select Make Primary.
Step 6
When prompted to confirm changing the server status, select OK.
The Server Status column displays the changed status when the change is complete.
Note
The subscriber server will automatically change to Secondary status.
To Manually Change the Subscriber Server from Secondary Status to Deactivated Status
Step 1
Sign in to the Real-Time Monitoring Tool (RTMT).
Step 2
On the Cisco Unity Connection menu, select Port Monitor. The Port Monitor tool appears in the right
pane.
Step 3
In the Node field, select the subscriber server.
Step 4
In the right pane, select Start Polling.
Step 5
Note whether any voice messaging ports are currently handling calls for the server.
Step 6
If no voice messaging ports are currently handling calls for the server, skip to Step 7.
If there are voice messaging ports that are currently handling calls for the server, in Cisco Unity
Connection Serviceability, on the Cluster Management page, under Change Port Status, select Stop
Taking Calls for the subscriber server, then wait until RTMT shows that all ports for the subscriber
server are idle.
Step 7
In Cisco Unity Connection Serviceability, on the Cluster Management page, under Server Manager, in
the Change Server Status column for the subscriber server, select Deactivate.
Step 8
When prompted to confirm changing server status, select OK.
The Server Status column displays the changed status for the subscriber server when the change is
complete.
To Remove the Subscriber Server from the Environment
Step 1
Shut down the subscriber server.
The Server Status column shows the subscriber server has Not Functioning status.
Step 2
Disconnect the network cable from the subscriber server.
The subscriber server can be removed from the environment.
Upgrade Guide for Cisco Unity Connection Release 9.x
11-4
Chapter 11
Creating or Changing a Cisco Unity Connection 9.x Cluster
Converting an 9.x Publisher Server to a Single Server Without a Unity Connection Cluster
To Remove the Subscriber Server from the Cluster
Step 1
On the publisher server, sign in to Cisco Unity Connection Administration.
Step 2
In Cisco Unity Connection Administration, expand System Settings, then select Cluster.
Step 3
On the Find and List Servers page, select Find to display all servers in the cluster.
Step 4
Check the check box in front of the name for the subscriber server and select Delete Selected.
Step 5
When prompted to confirm deleting the server, select OK.
To Ensure That All Calls Go to the Remaining Unity Connection Server
See the applicable documentation, depending on the phone system integration type:
Integration by Skinny Client Control Protocol (SCCP) with Cisco Unified Communications
Manager
a.
To delete the ports on the phone system that connected to the subscriber server, see the Cisco Unified
Communications Manager Administration Guide at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
b.
Configure the hunt group for the voicemail ports on the phone system to send calls only to the
remaining server (the publisher).
Integration by Skinny Client Control Protocol (SCCP) with Cisco Unified Communications
Manager Express
a.
To delete the ports on the phone system that connected to the subscriber server, see the Cisco Unified
Communications Manager Express System Administration Guide at
http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_installation_and_configuratio
n_guides_list.html.
b.
Configure the hunt group for the voicemail ports on the phone system to send calls only to the
remaining server (the publisher).
Integration through a SIP trunk with Cisco Unified Communications Manager
To configure the hunt group for the voicemail ports on the phone system to send calls only to the
remaining server (the publisher), see the Cisco Unified Communications Manager Administration Guide
at http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
Integration through a SIP trunk with Cisco Unified Communications Manager Express
To configure the hunt group for the voicemail ports on the phone system to send calls only to the
remaining server (the publisher), see the Cisco Unified Communications Manager Express System
Administration Guide at
http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_installation_and_configuration_g
uides_list.html.
Integration through PIMG/TIMG units
To configure the PIMG/TIMG units to send all calls to the remaining server (the publisher), see the
“Setting Up the PIMG Units” or “Setting Up the TIMG Units” section of the applicable Cisco Unity
Connection integration guide at
http://www.cisco.com/en/US/products/ps6509/products_installation_and_configuration_guides_list.ht
ml.
Upgrade Guide for Cisco Unity Connection Release 9.x
11-5
Chapter 11
Converting an 9.x Publisher Server to a Single Server Without a Unity Connection Cluster
Creating or Changing a Cisco Unity Connection 9.x Cluster
Other Integrations That Use SIP
To configure the hunt group for the voicemail ports on the phone system to send calls only to the
remaining server (the publisher), see the phone system documentation.
Upgrade Guide for Cisco Unity Connection Release 9.x
11-6
CH A P T E R
12
Changing the IP Addresses of Cisco Unity
Connection 9.x Servers
This chapter contains the following sections:
•
Determining Whether a Unity Connection 9.x Server is Defined by a Hostname or an IP Address,
page 12-1
•
Associated Components on Which the IP Address of a Unity Connection 9.x Server Must Be
Changed, page 12-2
•
Changing the IP Address of a Single 9.x Server that is Defined by a Hostname (No Unity Connection
Cluster), page 12-3
•
Changing the IP Address of a Single 9.x Server that is Defined by an IP Address (No Unity
Connection Cluster), page 12-5
•
Changing the IP Address of a Unity Connection 9.x Publisher Server that is Defined by a Hostname,
page 12-7
•
Changing the IP Address of a Unity Connection 9.x Publisher Server That Is Defined by an IP
Address, page 12-10
•
Changing the IP Address of a Unity Connection 9.x Subscriber Server that is Defined by a
Hostname, page 12-13
•
Changing the IP Address of a Unity Connection 9.x Subscriber Server that is Defined by an IP
Address, page 12-15
•
Changing the IP Address of a Unity Connection 9.x Site Gateway in a Cisco Voicemail
Organization, page 12-17
Determining Whether a Unity Connection 9.x Server is Defined
by a Hostname or an IP Address
The procedure you use to change the IP address of a Unity Connection server depends on whether the
server is defined by a hostname or by an IP address.
To Determine Whether a Unity Connection 9.x Server Is Defined by a Hostname or an IP Address
Step 1
On the server whose IP address you want to change, sign in to Cisco Unity Connection Administration.
Step 2
Expand System Settings, and select Cluster.
Upgrade Guide for Cisco Unity Connection Release 9.x
12-1
Chapter 12 Changing the IP Addresses of Cisco Unity Connection 9.x Servers
Associated Components on Which the IP Address of a Unity Connection 9.x Server Must Be Changed
You go to the Cluster page even when no cluster is configured.
Step 3
Select Find to display a list of servers in the cluster.
Step 4
For the server whose IP address you want to change, if the value of the Hostname/IP Address column is
a hostname, the server is defined by a hostname.
If the value of the Hostname/IP Address column is an IP address, the server is defined by an IP address.
Associated Components on Which the IP Address of a Unity
Connection 9.x Server Must Be Changed
When you change the IP address of the Unity Connection server, you must also make the same change
on all associated components that reference the Unity Connection server by IP address:
•
Bookmarks on client computers to the following web applications:
– Cisco Personal Communications Assistant
– Cisco Unity Connection Administration
– Real-Time Monitoring Tool
•
Cisco Fax Server
•
Cisco Unified Application Environment
•
Cisco Unified Mobile Advantage
•
Cisco Unified Presence
•
Cisco Unified Personal Communicator
•
Cisco Unity Connection ViewMail for Microsoft Outlook
•
IMAP email clients that access Unity Connection
•
Phone systems and related components:
– Cisco EGW 2200
– Cisco ISR voice gateway
– Cisco SIP Proxy Server
– Cisco Unified Communications Manager
– Cisco Unified Communications Manager Express
– PIMG/TIMG units
•
RSS readers
•
SMTP smart host
•
Voice-messaging systems with which Unity Connection is integrated via VPIM, including:
– Cisco Unity
– Cisco Unity Express
Upgrade Guide for Cisco Unity Connection Release 9.x
12-2
Chapter 12
Changing the IP Addresses of Cisco Unity Connection 9.x Servers
Changing the IP Address of a Single 9.x Server that is Defined by a Hostname (No Unity Connection Cluster)
Changing the IP Address of a Single 9.x Server that is Defined by
a Hostname (No Unity Connection Cluster)
Caution
Do not change the IP address of a Unity Connection server during business hours. The server must be
restarted for changes to take effect.
If the Unity Connection server is configured to get an IP address from a DHCP server, you cannot
manually change the IP address of the server using Unity Connection processes. Instead, you must do
one of the following:
•
Change DHCP/DNS settings, and restart the Unity Connection server by running the CLI command
utils system restart.
•
Disable DHCP on the Unity Connection server by running the CLI command set network dhcp, and
then manually change the IP address by doing the following procedure.
For more information on the CLI commands, see the applicable version of the Command Line Interface
Reference Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
To Change the IP Address of a Single 9.x Server That Is Defined by a Hostname (No Unity Connection Cluster)
Step 1
Review the list of associated components on which you also need to change the IP address of the Unity
Connection server if those components reference Unity Connection by IP address. See the “Associated
Components on Which the IP Address of a Unity Connection 9.x Server Must Be Changed” section on
page 12-2.
Caution
Step 2
If associated components reference the Unity Connection server by IP address and if you do
not change the IP address as applicable, the components will no longer be able to access the
Unity Connection server.
In the Real-Time Monitoring Tool (RTMT) confirm that the server is running and available:
a.
Using the RTMT, sign in to the server.
b.
In the left pane, under Tools, select Alert Central.
c.
In the right pane, on the System tab, if ServerDown is black, skip to Step 3.
If ServerDown is red, right-click ServerDown, and select Alert Details. Resolve the problem before
continuing.
Step 3
Step 4
Sign in to Cisco Unified Serviceability, and check the status of the server:
a.
From the Tools menu, select Cluster Management.
b.
In the Server Status column, confirm that the value for the current server is Primary. If the Server
Status column has any other value, resolve the problem before continuing.
Check network connectivity and DNS server configuration by running the following CLI command:
Upgrade Guide for Cisco Unity Connection Release 9.x
12-3
Chapter 12 Changing the IP Addresses of Cisco Unity Connection 9.x Servers
Changing the IP Address of a Single 9.x Server that is Defined by a Hostname (No Unity Connection Cluster)
admin: utils diagnose module validate_network
Log file: /var/log/active/platform/log/diag1.log
Starting diagnostic test(s)
===========================
test - validate_network
: Passed
Diagnostics Completed
admin:
Step 5
Back up the server by using the Disaster Recovery System. See the Disaster Recovery System
Administration Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/drs_administration/guide/9xcucdrsa
g.html.
Step 6
If intrasite networking is configured, remove the server from the Unity Connection site. For instructions,
see the “Making Changes to the Networking Configuration in Cisco Unity Connection 9.x” chapter of
the Networking Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/networking/guide/9xcucnetx.html.
Caution
Readding a server to a Unity Connection site can be a time-consuming process. Ensure that
you thoroughly understand the work required to readd a server to a site before you continue
with this procedure.
Step 7
On a DNS server, change the DNS record of the server to the new IP address. Update both the
forward (A) and reverse (PTR) records.
Step 8
Change the IP address of the server and, if applicable, the default gateway:
Step 9
a.
Sign in to Cisco Unified Operating System Administration.
b.
From the Settings menu, select IP > Ethernet.
c.
Under Port Information, change the value of the IP Address field and, if applicable, the Subnet Mask
field.
d.
If you are moving the server to a different subnet that requires a new default gateway address, under
Gateway Information, change the value of the Default Gateway field.
e.
Select Save, and the system restarts.
In the RTMT, confirm that the server is running and available:
a.
Using the RTMT, sign in to the server.
b.
In the left pane, under Tools, select Alert Central.
c.
In the right pane, on the System tab, if ServerDown is black, skip to Step 10.
If ServerDown is red, right-click ServerDown, and select Alert Details. Resolve the problem before
continuing.
Step 10
Update RTMT custom alerts and saved profiles.
•
RTMT custom alerts that are derived from performance counters include the hard-coded server IP
address. You must delete and reconfigure the custom alerts.
Upgrade Guide for Cisco Unity Connection Release 9.x
12-4
Chapter 12
Changing the IP Addresses of Cisco Unity Connection 9.x Servers
Changing the IP Address of a Single 9.x Server that is Defined by an IP Address (No Unity Connection Cluster)
•
RTMT saved profiles that have performance counters include the hard-coded server IP address. You
must delete and readd the counters and then save the profiles to update them to the new IP address.
Step 11
Check associated components and change configurations as required. (Consult documentation for the
affected products to determine how to make the required changes.) See the “Associated Components on
Which the IP Address of a Unity Connection 9.x Server Must Be Changed” section on page 12-2.
Step 12
If the server was part of a Unity Connection site before you changed the IP address, readd the server to
the site. For instructions, see the “Making Changes to the Networking Configuration in Cisco Unity
Connection 9.x” chapter of the Networking Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/networking/guide/9xcucnetx.html.
Step 13
Back up the server by using the Disaster Recovery System. See the Disaster Recovery System
Administration Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/drs_administration/guide/9xcucdrsa
g.html.
Changing the IP Address of a Single 9.x Server that is Defined by
an IP Address (No Unity Connection Cluster)
Caution
Do not change the IP address of a Unity Connection server during business hours. The server must be
restarted for changes to take effect.
If the Unity Connection server is configured to get an IP address from a DHCP server, you cannot
manually change the IP address of the server using Unity Connection processes. Instead, you must do
one of the following:
•
Change DHCP/DNS settings, and restart the Unity Connection server by running the CLI command
utils system restart.
•
Disable DHCP on the Unity Connection server by running the CLI command set network dhcp, and
then manually change the IP address by doing the following procedure.
For more information on the CLI commands, see the applicable version of the Command Line Interface
Reference Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
To Change the IP Address of a Single 9.x Server That Is Defined by an IP Address (No Unity Connection Cluster)
Step 1
Review the list of associated components on which you also need to change the IP address of the Unity
Connection server if those components reference Unity Connection by IP address. See the “Associated
Components on Which the IP Address of a Unity Connection 9.x Server Must Be Changed” section on
page 12-2.
Caution
If associated components reference the Unity Connection server by IP address and if you do
not change the IP address as applicable, the components will no longer be able to access the
Unity Connection server.
Upgrade Guide for Cisco Unity Connection Release 9.x
12-5
Chapter 12 Changing the IP Addresses of Cisco Unity Connection 9.x Servers
Changing the IP Address of a Single 9.x Server that is Defined by an IP Address (No Unity Connection Cluster)
Step 2
In the Real-Time Monitoring Tool (RTMT) confirm that the server is running and available:
a.
Using the RTMT, sign in to the server.
b.
In the left pane, under Tools, select Alert Central.
c.
In the right pane, on the System tab, if ServerDown is black, skip to Step 3.
If ServerDown is red, right-click ServerDown, and select Alert Details. Resolve the problem before
continuing.
Step 3
Step 4
Sign in to Cisco Unified Serviceability, and check the status of the server:
a.
From the Tools menu, select Cluster Management.
b.
In the Server Status column, confirm that the value for the current server is Primary. If the Server
Status column has any other value, resolve the problem before continuing.
Check network connectivity and DNS server configuration by running the following CLI command:
admin: utils diagnose module validate_network
Log file: /var/log/active/platform/log/diag1.log
Starting diagnostic test(s)
===========================
test - validate_network
: Passed
Diagnostics Completed
admin:
Step 5
Back up the server by using the Disaster Recovery System. See the Disaster Recovery System
Administration Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/drs_administration/guide/9xcucdrsa
g.html.
Step 6
If intrasite networking is configured, remove the server from the Unity Connection site. For instructions,
see the “Making Changes to the Networking Configuration in Cisco Unity Connection 9.x” chapter of
the Networking Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/networking/guide/9xcucnetx.html.
Caution
Readding a server to a Unity Connection site can be a time-consuming process. Ensure that
you thoroughly understand the work required to readd a server to a site before you continue
with this procedure.
Step 7
On a DNS server, change the DNS record of the server to the new IP address. Update both the
forward (A) and reverse (PTR) records.
Step 8
Change the IP addresses of the server in Connection Administration:
a.
Sign in to Cisco Unity Connection Administration.
b.
Expand System Settings, and select Cluster.
c.
Select Find to display a list of servers in the cluster.
d.
Select the name of the server.
e.
Change the value of the Hostname/IP Address field to the new IP address.
Upgrade Guide for Cisco Unity Connection Release 9.x
12-6
Chapter 12
Changing the IP Addresses of Cisco Unity Connection 9.x Servers
Changing the IP Address of a Unity Connection 9.x Publisher Server that is Defined by a Hostname
f.
Step 9
Step 10
Select Save.
Change the IP address of the server and, if applicable, the default gateway:
a.
Sign in to Cisco Unified Operating System Administration.
b.
From the Settings menu, select IP > Ethernet.
c.
Under Port Information, change the value of the IP Address field and, if applicable, the Subnet Mask
field.
d.
If you are moving the server to a different subnet that requires a new default gateway address, under
Gateway Information, change the value of the Default Gateway field.
e.
Select Save, and the system restarts.
In the RTMT, confirm that the server is running and available:
a.
Using the RTMT, sign in to the server.
b.
In the left pane, under Tools, select Alert Central.
c.
In the right pane, on the System tab, if ServerDown is black, skip to Step 10.
If ServerDown is red, right-click ServerDown, and select Alert Details. Resolve the problem before
continuing.
Step 11
Update RTMT custom alerts and saved profiles.
•
RTMT custom alerts that are derived from performance counters include the hard-coded server IP
address. You must delete and reconfigure the custom alerts.
•
RTMT saved profiles that have performance counters include the hard-coded server IP address. You
must delete and readd the counters and then save the profiles to update them to the new IP address.
Step 12
Check associated components and change configurations as required. (Consult documentation for the
affected products to determine how to make the required changes.) See the “Associated Components on
Which the IP Address of a Unity Connection 9.x Server Must Be Changed” section on page 12-2.
Step 13
If the server was part of a Unity Connection site before you changed the IP address, readd the server to
the site. For instructions, see the
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/drs_administration/guide/9xcucdrsa
g.html.
Step 14
Back up the server by using the Disaster Recovery System. See the Disaster Recovery System
Administration Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/drs_administration/guide/9xcucdrsa
g.html.
Changing the IP Address of a Unity Connection 9.x Publisher
Server that is Defined by a Hostname
Caution
Do not change the IP address of a Unity Connection server during business hours. When a Unity
Connection cluster is configured, both servers must be restarted for changes to take effect.
Upgrade Guide for Cisco Unity Connection Release 9.x
12-7
Chapter 12 Changing the IP Addresses of Cisco Unity Connection 9.x Servers
Changing the IP Address of a Unity Connection 9.x Publisher Server that is Defined by a Hostname
If the Unity Connection server is configured to get an IP address from a DHCP server, you cannot
manually change the IP address of the server using Unity Connection processes. Instead, you must do
one of the following:
•
Change DHCP/DNS settings, and restart the Unity Connection server by running the CLI command
utils system restart.
•
Disable DHCP on the Unity Connection server by running the CLI command set network dhcp, and
then manually change the IP address by doing the following procedure.
For more information on the CLI commands, see the applicable version of the Command Line Interface
Reference Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
To Change the IP Address of a Unity Connection 9.x Publisher Server That Is Defined by a Hostname
Step 1
Review the list of associated components on which you also need to change the IP address of the Unity
Connection server if those components reference Unity Connection by IP address. See the “Associated
Components on Which the IP Address of a Unity Connection 9.x Server Must Be Changed” section on
page 12-2.
Caution
Step 2
If associated components reference the Unity Connection server by IP address and if you do
not change the IP address as applicable, the components will no longer be able to access the
Unity Connection server.
In the Real-Time Monitoring Tool (RTMT), confirm that the publisher and subscriber servers are running
and available:
a.
Using the RTMT, sign in to the publisher server.
b.
In the left pane, under Tools, select Alert Central.
c.
In the right pane, on the System tab, if ServerDown is black, skip to Step d.
If ServerDown is red, right-click ServerDown, and select Alert Details. Resolve the problem before
continuing.
d.
Step 3
Step 4
Repeat Step a. through Step c. on the subscriber server.
On the publisher server, sign in to Cisco Unified Serviceability, and check the status of the server:
a.
From the Tools menu, select Cluster Management.
b.
In the Server Status column, confirm that the value for the current server is either Primary or
Secondary. If the Server Status column has any other value, resolve the problem before continuing.
Check network connectivity and DNS server configuration by running the following CLI command:
Upgrade Guide for Cisco Unity Connection Release 9.x
12-8
Chapter 12
Changing the IP Addresses of Cisco Unity Connection 9.x Servers
Changing the IP Address of a Unity Connection 9.x Publisher Server that is Defined by a Hostname
admin: utils diagnose module validate_network
Log file: /var/log/active/platform/log/diag1.log
Starting diagnostic test(s)
===========================
test - validate_network
: Passed
Diagnostics Completed
admin:
Step 5
Back up the server by using the Disaster Recovery System. See the Disaster Recovery System
Administration Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/drs_administration/guide/9xcucdrsa
g.html.
Step 6
If intrasite networking is configured, remove the publisher server from the Unity Connection site. For
instructions, see the “Making Changes to the Networking Configuration in Cisco Unity Connection 9.x”
chapter of the Networking Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/networking/guide/9xcucnetx.html.
Caution
Readding a server to a Unity Connection site can be a time-consuming process. Ensure that
you thoroughly understand the work required to readd a server to a site before you continue
with this procedure.
Step 7
On a DNS server, change the DNS record of the publisher server to the new IP address. Update both the
forward (A) and reverse (PTR) records.
Step 8
On the subscriber server, change the IP address of the publisher server:
Step 9
a.
Sign in to Cisco Unified Operating System Administration.
b.
From the Settings menu, select IP > Publisher.
c.
Change the IP address of the publisher server.
d.
Select Save.
On the publisher server, change the IP address of the publisher server and, if applicable, the default
gateway:
a.
Sign in to Cisco Unified Operating System Administration.
b.
From the Settings menu, select IP > Ethernet.
c.
Under Port Information, change the value of the IP Address field and, if applicable, the Subnet Mask
field.
d.
If you are moving the publisher server to a different subnet that requires a new default gateway
address, under Gateway Information, change the value of the Default Gateway field.
e.
Select Save, and the system restarts.
Step 10
Sign in to the subscriber server by using an SSH application, and run the CLI command utils system
restart to restart the server, which updates the local name resolution files.
Step 11
In the RTMT, confirm that the publisher and subscriber servers are running and available:
a.
Using the RTMT, sign in to the publisher server.
Upgrade Guide for Cisco Unity Connection Release 9.x
12-9
Chapter 12 Changing the IP Addresses of Cisco Unity Connection 9.x Servers
Changing the IP Address of a Unity Connection 9.x Publisher Server That Is Defined by an IP Address
b.
In the left pane, under Tools, select Alert Central.
c.
In the right pane, on the System tab, if ServerDown is black, skip to Step d.
If ServerDown is red, right-click ServerDown, and select Alert Details. Resolve the problem before
continuing.
d.
Step 12
Repeat Step a. through Step c. on the subscriber server.
Update RTMT custom alerts and saved profiles.
•
RTMT custom alerts that are derived from performance counters include the hard-coded server IP
address. You must delete and reconfigure the custom alerts.
•
RTMT saved profiles that have performance counters include the hard-coded server IP address. You
must delete and readd the counters and then save the profiled to update them to the new IP address.
Step 13
Check associated components and change configurations as required. (Consult documentation for the
affected products to determine how to make the required changes.) See the “Associated Components on
Which the IP Address of a Unity Connection 9.x Server Must Be Changed” section on page 12-2.
Step 14
If the publisher server was part of a Unity Connection site before you changed the IP address of this
server, readd the server to the site. For instructions, see the “Making Changes to the Networking
Configuration in Cisco Unity Connection 9.x” chapter of the Networking Guide for Cisco Unity
Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/networking/guide/9xcucnetx.html.
Step 15
Back up the server by using the Disaster Recovery System. See the Disaster Recovery System
Administration Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/drs_administration/guide/9xcucdrsa
g.html.
Changing the IP Address of a Unity Connection 9.x Publisher
Server That Is Defined by an IP Address
Caution
Do not change the IP address of a Unity Connection server during business hours. When a Unity
Connection cluster is configured, both servers must be restarted for changes to take effect.
If the Unity Connection server is configured to get an IP address from a DHCP server, you cannot
manually change the IP address of the server using Unity Connection processes. Instead, you must do
one of the following:
•
Change DHCP/DNS settings, and restart the Unity Connection server by running the CLI command
utils system restart.
•
Disable DHCP on the Unity Connection server by running the CLI command set network dhcp, and
then manually change the IP address by doing the following procedure.
For more information on the CLI commands, see the applicable version of the Command Line Interface
Reference Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
Upgrade Guide for Cisco Unity Connection Release 9.x
12-10
Chapter 12
Changing the IP Addresses of Cisco Unity Connection 9.x Servers
Changing the IP Address of a Unity Connection 9.x Publisher Server That Is Defined by an IP Address
To Change the IP Address of a Unity Connection 9.x Publisher Server That Is Defined by an IP Address
Step 1
Review the list of associated components on which you also need to change the IP address of the Unity
Connection server if those components reference Unity Connection by IP address. See the “Associated
Components on Which the IP Address of a Unity Connection 9.x Server Must Be Changed” section on
page 12-2.
Caution
Step 2
If associated components reference the Unity Connection server by IP address and if you do
not change the IP address as applicable, the components will no longer be able to access the
Unity Connection server.
In the Real-Time Monitoring Tool (RTMT), confirm that the publisher and subscriber servers are running
and available:
a.
Using the RTMT, sign in to the publisher server.
b.
In the left pane, under Tools, select Alert Central.
c.
In the right pane, on the System tab, if ServerDown is black, skip to Step d.
If ServerDown is red, right-click ServerDown, and select Alert Details. Resolve the problem before
continuing.
d.
Step 3
Step 4
Repeat Step a. through Step c. on the subscriber server.
On the publisher server, sign in to Cisco Unified Serviceability, and check the status of the server:
a.
From the Tools menu, select Cluster Management.
b.
In the Server Status column, confirm that the value for the current server is either Primary or
Secondary. If the Server Status column has any other value, resolve the problem before continuing.
Check network connectivity and DNS server configuration by running the following CLI command:
admin: utils diagnose module validate_network
Log file: /var/log/active/platform/log/diag1.log
Starting diagnostic test(s)
===========================
test - validate_network
: Passed
Diagnostics Completed
admin:
Step 5
If intrasite networking is configured, remove the publisher server from the Unity Connection site. For
instructions, see the “Making Changes to the Networking Configuration in Cisco Unity Connection 9.x”
chapter of the Networking Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/networking/guide/9xcucnetx.html.
Caution
Readding a server to a Unity Connection site can be a time-consuming process. Ensure that
you thoroughly understand the work required to readd a server to a site before you continue
with this procedure.
Upgrade Guide for Cisco Unity Connection Release 9.x
12-11
Chapter 12 Changing the IP Addresses of Cisco Unity Connection 9.x Servers
Changing the IP Address of a Unity Connection 9.x Publisher Server That Is Defined by an IP Address
Step 6
Back up the server by using the Disaster Recovery System. See the Disaster Recovery System
Administration Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/drs_administration/guide/9xcucdrsa
g.html.
Step 7
On the publisher server, change the IP addresses of the publisher server in Connection Administration:
Step 8
Step 9
a.
Sign in to Cisco Unity Connection Administration.
b.
Expand System Settings, and select Cluster.
c.
Select Find to display a list of servers in the cluster.
d.
Select the name of the publisher server.
e.
Change the value of the Hostname/IP Address field to the new IP address.
f.
Select Save.
On the publisher server, change the IP address of the publisher server and, if applicable, the default
gateway in Cisco Unified Operating System Administration:
a.
Sign in to Cisco Unified Operating System Administration.
b.
From the Settings menu, select IP > Ethernet.
c.
Under Port Information, change the value of the IP Address field and, if applicable, the Subnet Mask
field.
d.
If you are moving the publisher server to a different subnet that requires a new default gateway
address, under Gateway Information, change the value of the Default Gateway field.
e.
Select Save, and the system restarts.
On the subscriber server, change the IP address of the publisher server:
a.
Sign in to Cisco Unified Operating System Administration.
b.
From the Settings menu, select IP > Publisher.
c.
Change the IP address of the publisher server.
d.
Select Save.
Step 10
Sign in to the subscriber server by using an SSH application, and run the CLI command utils system
restart to restart the server, which updates the local name resolution files.
Step 11
In the RTMT, confirm that the publisher and subscriber servers are running and available:
a.
Using the RTMT, sign in to the publisher server.
b.
In the left pane, under Tools, select Alert Central.
c.
In the right pane, on the System tab, if ServerDown is black, skip to Step d.
If ServerDown is red, right-click ServerDown, and select Alert Details. Resolve the problem before
continuing.
d.
Step 12
Repeat Step a. through Step c. on the subscriber server.
Update RTMT custom alerts and saved profiles.
•
RTMT custom alerts that are derived from performance counters include the hard-coded server IP
address. You must delete and reconfigure the custom alerts.
•
RTMT saved profiles that have performance counters include the hard-coded server IP address. You
must delete and readd the counters and then save the profiles to update them to the new IP address.
Upgrade Guide for Cisco Unity Connection Release 9.x
12-12
Chapter 12
Changing the IP Addresses of Cisco Unity Connection 9.x Servers
Changing the IP Address of a Unity Connection 9.x Subscriber Server that is Defined by a Hostname
Step 13
Check associated components and change configurations as required. (Consult documentation for the
affected products to determine how to make the required changes.) See the “Associated Components on
Which the IP Address of a Unity Connection 9.x Server Must Be Changed” section on page 12-2.
Step 14
If the publisher server was part of a Unity Connection site before you changed the IP address of this
server, readd the server to the site. For instructions, see the “Making Changes to the Networking
Configuration in Cisco Unity Connection 9.x” chapter of the Networking Guide for Cisco Unity
Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/networking/guide/9xcucnetx.html.
Step 15
Back up the server using the Disaster Recovery System. See the Disaster Recovery System
Administration Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/drs_administration/guide/9xcucdrsa
g.html.
Changing the IP Address of a Unity Connection 9.x Subscriber
Server that is Defined by a Hostname
Caution
Do not change the IP address of a Unity Connection server during business hours. When a Unity
Connection cluster is configured, both servers must be restarted for changes to take effect.
If the Unity Connection server is configured to get an IP address from a DHCP server, you cannot
manually change the IP address of the server using Unity Connection processes. Instead, you must do
one of the following:
•
Change DHCP/DNS settings, and restart the Unity Connection server by running the CLI command
utils system restart.
•
Disable DHCP on the Unity Connection server by running the CLI command set network dhcp, and
then manually change the IP address by doing the following procedure.
For more information on the CLI commands, see the applicable version of the Command Line Interface
Reference Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
To Change the IP Address of a Unity Connection 9.x Subscriber Server That Is Defined by a Hostname
Step 1
Review the list of associated components on which you also need to change the IP address of the Unity
Connection server if those components reference Unity Connection by IP address. See the “Associated
Components on Which the IP Address of a Unity Connection 9.x Server Must Be Changed” section on
page 12-2.
Caution
If associated components reference the Unity Connection server by IP address and if you do
not change the IP address as applicable, the components will no longer be able to access the
Unity Connection server.
Upgrade Guide for Cisco Unity Connection Release 9.x
12-13
Chapter 12 Changing the IP Addresses of Cisco Unity Connection 9.x Servers
Changing the IP Address of a Unity Connection 9.x Subscriber Server that is Defined by a Hostname
Step 2
In the Real-Time Monitoring Tool (RTMT), confirm that the publisher and subscriber servers are running
and available:
a.
Using the RTMT, sign in to the publisher server.
b.
In the left pane, under Tools, select Alert Central.
c.
In the right pane, on the System tab, if ServerDown is black, skip to Step d.
If ServerDown is red, right-click ServerDown, and select Alert Details. Resolve the problem before
continuing.
d.
Step 3
Step 4
Repeat Step a. through Step c. on the subscriber server.
On the subscriber server, sign in to Cisco Unified Serviceability, and check the status of the server:
a.
From the Tools menu, select Cluster Management.
b.
In the Server Status column, confirm that the value for the current server is either Primary or
Secondary. If the Server Status column has any other value, resolve the problem before continuing.
Check network connectivity and DNS server configuration by running the following CLI command:
admin: utils diagnose module validate_network
Log file: /var/log/active/platform/log/diag1.log
Starting diagnostic test(s)
===========================
test - validate_network
: Passed
Diagnostics Completed
admin:
Step 5
Back up the server by using the Disaster Recovery System. See the Disaster Recovery System
Administration Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/drs_administration/guide/9xcucdrsa
g.html.
Step 6
On a DNS server, change the DNS record of the subscriber server to the new IP address. Update both the
forward (A) and reverse (PTR) records.
Step 7
Confirm that the DNS change propagates to the publisher server by using the following two CLI
commands on the subscriber server and the publisher server:
utils network host
show tech network hosts
Step 8
On the subscriber server, change the IP address of the subscriber server and, if applicable, the default
gateway:
a.
Sign in to Cisco Unified Operating System Administration.
b.
From the Settings menu, select IP > Ethernet.
c.
Under Port Information, change the value of the IP Address field and, if applicable, the Subnet Mask
field.
d.
If you are moving the publisher server to a different subnet that requires a new default gateway
address, under Gateway Information, change the value of the Default Gateway field.
e.
Select Save, and the system restarts.
Upgrade Guide for Cisco Unity Connection Release 9.x
12-14
Chapter 12
Changing the IP Addresses of Cisco Unity Connection 9.x Servers
Changing the IP Address of a Unity Connection 9.x Subscriber Server that is Defined by an IP Address
Step 9
Sign in to the publisher server by using an SSH application, and run the CLI command utils system
restart to restart the server, which updates the local name resolution files.
Step 10
In the RTMT, confirm that the publisher and subscriber servers are running and available:
a.
Using the RTMT, sign in to the publisher server.
b.
In the left pane, under Tools, select Alert Central.
c.
In the right pane, on the System tab, if ServerDown is black, skip to Step d.
If ServerDown is red, right-click ServerDown, and select Alert Details. Resolve the problem before
continuing.
d.
Step 11
Repeat Step a. through Step c. on the subscriber server.
Update RTMT custom alerts and saved profiles.
•
RTMT custom alerts that are derived from performance counters include the hard-coded server IP
address. You must delete and reconfigure the custom alerts.
•
RTMT saved profiles that have performance counters include the hard-coded server IP address. You
must delete and readd the counters and then save the profiles to update them to the new IP address.
Step 12
Check associated components and change configurations as required. (Consult documentation for the
affected products to determine how to make the required changes.) See the “Associated Components on
Which the IP Address of a Unity Connection 9.x Server Must Be Changed” section on page 12-2.
Step 13
Back up the publisher server using the Disaster Recovery System. See the Disaster Recovery System
Administration Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/drs_administration/guide/9xcucdrsa
g.html.
Changing the IP Address of a Unity Connection 9.x Subscriber
Server that is Defined by an IP Address
Caution
Do not change the IP address of a Unity Connection server during business hours. When a Unity
Connection cluster is configured, both servers must be restarted for changes to take effect.
If the Unity Connection server is configured to get an IP address from a DHCP server, you cannot
manually change the IP address of the server using Unity Connection processes. Instead, you must do
one of the following:
•
Change DHCP/DNS settings, and restart the Unity Connection server by running the CLI command
utils system restart.
•
Disable DHCP on the Unity Connection server by running the CLI command set network dhcp, and
then manually change the IP address by doing the following procedure.
For more information on the CLI commands, see the applicable version of the Command Line Interface
Reference Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
Upgrade Guide for Cisco Unity Connection Release 9.x
12-15
Chapter 12 Changing the IP Addresses of Cisco Unity Connection 9.x Servers
Changing the IP Address of a Unity Connection 9.x Subscriber Server that is Defined by an IP Address
To Change the IP Address of a Unity Connection 9.x Subscriber Server That Is Defined by an IP Address
Step 1
Review the list of associated components on which you also need to change the IP address of the Unity
Connection server if those components reference Unity Connection by IP address. See the “Associated
Components on Which the IP Address of a Unity Connection 9.x Server Must Be Changed” section on
page 12-2.
Caution
Step 2
If associated components reference the Unity Connection server by IP address and if you do
not change the IP address as applicable, the components will no longer be able to access the
Unity Connection server.
In the Real-Time Monitoring Tool (RTMT), confirm that the publisher and subscriber servers are running
and available:
a.
Using the RTMT, sign in to the publisher server.
b.
In the left pane, under Tools, select Alert Central.
c.
In the right pane, on the System tab, if ServerDown is black, skip to Step d.
If ServerDown is red, right-click ServerDown, and select Alert Details. Resolve the problem before
continuing.
d.
Step 3
Step 4
Repeat Step a. through Step c. on the subscriber server.
On the subscriber server, sign in to Cisco Unified Serviceability, and check the status of the server:
a.
From the Tools menu, select Cluster Management.
b.
In the Server Status column, confirm that the value for the current server is either Primary or
Secondary. If the Server Status column has any other value, resolve the problem before continuing.
Check network connectivity and DNS server configuration by running the following CLI command:
admin: utils diagnose module validate_network
Log file: /var/log/active/platform/log/diag1.log
Starting diagnostic test(s)
===========================
test - validate_network
: Passed
Diagnostics Completed
admin:
Step 5
Back up the server by using the Disaster Recovery System. See the Disaster Recovery System
Administration Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/drs_administration/guide/9xcucdrsa
g.html.
Step 6
On the publisher server, change the IP addresses of the subscriber server:
a.
Sign in to Cisco Unity Connection Administration.
b.
Expand System Settings, and select Cluster.
c.
Select Find to display a list of servers in the cluster.
Upgrade Guide for Cisco Unity Connection Release 9.x
12-16
Chapter 12
Changing the IP Addresses of Cisco Unity Connection 9.x Servers
Changing the IP Address of a Unity Connection 9.x Site Gateway in a Cisco Voicemail Organization
Step 7
d.
Select the name of the subscriber server.
e.
Change the value of the Hostname/IP Address field to the new IP address.
f.
Select Save.
On the subscriber server, change the IP address of the subscriber server and, if applicable, the default
gateway:
a.
Sign in to Cisco Unified Operating System Administration.
b.
From the Settings menu, select IP > Ethernet.
c.
Under Port Information, change the value of the IP Address field and, if applicable, the Subnet Mask
field.
d.
If you are moving the publisher server to a different subnet that requires a new default gateway
address, under Gateway Information, change the value of the Default Gateway field.
e.
Select Save, and the system restarts.
Step 8
Sign in to the publisher server by using an SSH application, and run the CLI command utils system
restart to restart the server, which updates the local name resolution files.
Step 9
In the RTMT, confirm that the publisher and subscriber servers are running and available:
a.
Using the RTMT, sign in to the publisher server.
b.
In the left pane, under Tools, select Alert Central.
c.
In the right pane, on the System tab, if ServerDown is black, skip to Step d.
If ServerDown is red, right-click ServerDown, and select Alert Details. Resolve the problem before
continuing.
d.
Step 10
Repeat Step a. through Step c. on the subscriber server.
Update RTMT custom alerts and saved profiles.
•
RTMT custom alerts that are derived from performance counters include the hard-coded server IP
address. You must delete and reconfigure the custom alerts.
•
RTMT saved profiles that have performance counters include the hard-coded server IP address. You
must delete and readd the counters and then save the profiles to update them to the new IP address.
Step 11
Check associated components and change configurations as required. (Consult documentation for the
affected products to determine how to make the required changes.) See the “Associated Components on
Which the IP Address of a Unity Connection 9.x Server Must Be Changed” section on page 12-2.
Step 12
Back up the server by using the Disaster Recovery System. See the Disaster Recovery System
Administration Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/drs_administration/guide/9xcucdrsa
g.html.
Changing the IP Address of a Unity Connection 9.x Site Gateway
in a Cisco Voicemail Organization
For information on replacing a Unity Connection site gateway when Connection networking is
configured, see the “Making Changes to a Unity Connection Site Gateway” section in the “Managing
Licenses in Cisco Unity Connection 9.x” chapter in the System Administration Guide for Cisco Unity
Upgrade Guide for Cisco Unity Connection Release 9.x
12-17
Chapter 12 Changing the IP Addresses of Cisco Unity Connection 9.x Servers
Changing the IP Address of a Unity Connection 9.x Site Gateway in a Cisco Voicemail Organization
Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/guide/9xcucsagx.htm
l.
Upgrade Guide for Cisco Unity Connection Release 9.x
12-18
CH A P T E R
13
Adding or Changing the IPv6 Addresses of
Cisco Unity Connection
This chapter contains the following sections:
•
Enabling IPv6 and Adding an IPv6 Address to a Unity Connection, page 13-1
•
Changing the IPv6 Address, page 13-6
Enabling IPv6 and Adding an IPv6 Address to a Unity Connection
You can enable and configure Internet Protocol Version 6 (IPv6) for use with Cisco Unified
Communications Manager phone system integrations via SCCP or SIP. IPv6 is disabled by default. Note
the following considerations when deploying IPv6 for Cisco Unified CM integrations:
•
IPv6 is supported in Cisco Unified CM release 7.1(2) and later.
•
The CTL file required for security features (authentication and encryption) between Unity
Connection and Cisco Unified CM for SCCP integrations uses IPv4 addressing. Therefore, in order
to use authentication and encryption with SCCP secure ports, you must retain the IPv4 address or
host name for the Cisco Unified CM server(s) on the port group in Unity Connection.
•
Some versions of Cisco Adaptive Security Appliance (ASA) do not support application inspection
for IPv6 traffic for Unified Communications application servers and endpoints. Cisco recommends
not using IPv6 for Unified Communications if you are using a Cisco ASA version that does not
provide this support. See the documentation for your version of Cisco ASA to determine whether
application inspection is supported in your deployment.
Use the following task list to enable IPv6 and to configure the IPv6 address of a Unity Connection server
if the server is already integrated with Cisco Unified CM via SCCP or SIP. (If you have not yet integrated
the server with Cisco Unified CM, see the applicable integration guide for instructions.)
Note
Unity Connection platform can be configured either in IPv4 only mode or Dual (IPv4/IPv6) mode.
Upgrade Guide for Cisco Unity Connection Release 9.x
13-1
Chapter 13
Adding or Changing the IPv6 Addresses of Cisco Unity Connection
Enabling IPv6 and Adding an IPv6 Address to a Unity Connection
Caution
Do not enable IPv6 during business hours. The server must be restarted for changes to take effect.
1.
Note
Enable and configure IPv6 in Cisco Unified Operating System Administration. See the “IP Settings”
section in the “Settings” chapter of the Cisco Unified Communications Operating System
Administration Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/os_administration/guide/9xcuco
sagx.html.
You can also enable or disable IPv6 through CLI commands. See the Appendix 13, “Enabling or
Disabling IPv6 through Command Line Interface (CLI) Commands” section.
2.
If you have not already configured the Cisco Unified CM phone system for IPv6: Follow the steps in
the “Configuration Checklist for IPv6” section in the “Internet Protocol Version 6” chapter of the
Cisco Unified Communications Manager Features and Services Guide for your release of Cisco
Unified CM. The guides are available at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html.
3.
If the Unity Connection server is integrated with Cisco Unified CM via SIP: Configure the SIP trunk
with the IPv6 destination address, and reset the trunk. See the “To Configure a Cisco Unified
Communications Manager SIP Trunk with theCisco Unity Connection IPv6 Destination Address”
procedure on page 13-2.
4.
Configure the IPv6 address and addressing mode settings for the Cisco Unified CM integration(s).
See the “To Configure the IPv6 Address and Addressing Mode for Cisco Unified Communications
Manager Phone System Integrations in Cisco Unity Connection Administration” procedure on
page 13-2.
To Configure a Cisco Unified Communications Manager SIP Trunk with theCisco Unity Connection IPv6
Destination Address
Step 1
Sign in to Cisco Unified CM Administration.
Step 2
On the Device menu, select Trunk.
Step 3
Find the trunk corresponding to the Connection server, and select the name of the trunk.
Step 4
On the Trunk Configuration page, change the value of the Destination Address IPv6 field to the new
IPv6 address.
Step 5
Select Save to save the change.
Step 6
Select Reset to reset the trunk.
To Configure the IPv6 Address and Addressing Mode for Cisco Unified Communications Manager Phone System
Integrations in Cisco Unity Connection Administration
Step 1
Sign in to Cisco Unity Connection Administration.
Step 2
Expand System Settings, then select General Configuration.
Step 3
On the Edit General Configuration page, for IP Addressing Mode, select the option from the list to
control where Connection listens for incoming traffic:
Upgrade Guide for Cisco Unity Connection Release 9.x
13-2
Chapter 13
Adding or Changing the IPv6 Addresses of Cisco Unity Connection
Enabling IPv6 and Adding an IPv6 Address to a Unity Connection
•
IPv4
•
IPv6
•
IPv4 and IPv6
Step 4
Select Save.
Step 5
Optionally, to enable the Unity Connection server to contact the Cisco Unified Communications
Manager server via an IPv6 address or host name, do the following substeps:
a.
Expand Telephony Integrations, then select Port Group.
b.
On the Search Port Groups page, select the display name of the port group that you want to modify.
If the port group that you want to modify does not appear in the search results table, set the
applicable parameters in the search fields at the top of the page, and then select Find.
Note
c.
On the Port Group Basics page, on the Edit menu, select Servers.
d.
On the Edit Servers page, in the Cisco Unified Communications Manager Servers table, enter a value
for the IPv6 Address or Host Name for each Cisco Unified CM server that the port group connects
to. Do the same for the servers in the TFTP Server table.
Caution
Step 6
If you are using authentication and encryption with SCCP secure ports, you must also retain
the IPv4 address or host name for each Cisco Unified CM server and TFTP server.
e.
Select Save.
f.
Repeat substep a. through substep e. for each additional port group for which you want to configure
an IPv6 address or host name.
If you selected the IPv4 and IPv6 option in Step 3, do the following substeps to configure the call control
signalling and/or media addressing mode settings for the Cisco Unified CM integration:
a.
Expand Telephony Integrations, then select Port Group.
b.
On the Search Port Groups page, select the display name of the port group that you want to modify.
Note
If the port group that you want to modify does not appear in the search results table, set the
applicable parameters in the search fields at the top of the page, and then select Find.
c.
On the Port Group Basics page, on the Edit menu, select Servers.
d.
In the IPv6 Addressing Mode section, select either the IPv4 option or the IPv6 option for the
applicable settings:
•
Preference for Signaling (applicable to both SCCP integrations and SIP integrations)—This setting
determines the call control signaling preference when registering with Cisco Unified CM via SCCP
or when initiating SIP requests.
•
Preference for Media (applicable only to SIP integrations)—This setting determines the preferred
addressing mode for media events when communicating with dual-stack (IPv4 and IPv6) devices.
e.
Select Save.
Upgrade Guide for Cisco Unity Connection Release 9.x
13-3
Chapter 13
Adding or Changing the IPv6 Addresses of Cisco Unity Connection
Enabling IPv6 and Adding an IPv6 Address to a Unity Connection
Enabling or Disabling IPv6 through Command Line Interface (CLI) Commands
You can enable or disable IPv6 through command line interface (CLI) commands.
Enabling IPv6 through CLI Commands
To enable IPv6 through CLI commands:
Step 1
Run the following CLI command to check the IPv6 settings:
admin:show network ipv6 settings
Example 13-1 If you run the above command, the following message appears:
IPv6
: disabled
DHCPv6
: disabled
IPv6 Gateway : fe80::202:2cff:fed2:7e01
IPv6 addresses:
Address:fe80::250:56ff:fe8e:6cef
Mask:64
Scope:Link
Step 2
Run the following CLI command to enable IPv6 on platform level:
set network ipv6 service enable
Step 3
Perform one of the following steps:
– If global address appears in the IPv6 addresses row, restart the system.
– If global address does not appear in the IPv6 addresses row, do not restart the system.
Note
If global address does not appear in the IPv6 addresses, you need to configure IPv6 manually or
enable DHCPv6.
Configuring IPv6 Manually
Step 1
Run the following command on CLI to configure ipv6 address manually:
set network ipv6 static_address <IPv6 address>
Example 13-2 You can run the following command to enable IPv6
set network ipv6 static_address fec0::250:56ff:fe8e:6cef 64
Note
Step 2
The IPv6 address that you specify in the above command can either be a global IPv6 address or a unique
local unicast IPv6 address.
Restart the system to apply the above specified setting.
Enabling DHCPv6
Step 1
Run the following command on CLI to configure DHCPv6:
set network ipv6 dhcp enable
Upgrade Guide for Cisco Unity Connection Release 9.x
13-4
Chapter 13
Adding or Changing the IPv6 Addresses of Cisco Unity Connection
Enabling IPv6 and Adding an IPv6 Address to a Unity Connection
Step 2
Restart the system to apply the above specified setting.
Disabling IPv6 through CLI Commands
To disable IPv6 through CLI commands:
Step 1
Run the following command to disable IPv6:
set network ipv6 service disable
Step 2
Run the following command to disable DHCPv6:
set network ipv6 dhcp disable
Step 3
Restart the system to apply the above specified settings.
Upgrade Guide for Cisco Unity Connection Release 9.x
13-5
Chapter 13
Adding or Changing the IPv6 Addresses of Cisco Unity Connection
Changing the IPv6 Address
Changing the IPv6 Address
You can configure IPv6 for use with Cisco Unified Communications Manager phone system integrations
via SCCP or SIP. Because IPv6 addressing is not used between servers in a cluster or between locations
in a Cisco Voicemail Organization, you can use the following procedure to change the IP address of any
Unity Connection server, regardless of whether the server is part of a cluster or is networked with other
servers.
Do the following procedure to change the IPv6 address of a Unity Connection server on which IPv6 has
previously been enabled and configured.
Caution
Do not change the IPv6 address of a Unity Connection server during business hours. The server must be
restarted for changes to take effect.
To Change the IPv6 Address of a Cisco Unity Connection Server
Step 1
In the Real-Time Monitoring Tool (RTMT) confirm that the server is running and available:
a.
Using the RTMT, sign in to the server.
b.
In the left pane, under Tools, select Alert Central.
c.
In the right pane, on the System tab, if ServerDown is black, skip to Step 2.
If ServerDown is red, right-click ServerDown, and select Alert Details. Resolve the problem before
continuing.
Step 2
Step 3
Sign in to Cisco Unified Serviceability, and check the status of the server:
a.
From the Tools menu, select Cluster Management.
b.
In the Server Status column, confirm that the value for the current server is Primary. If the Server
Status column has any other value, resolve the problem before continuing.
Check network connectivity and DNS server configuration by running the following CLI command:
admin: utils diagnose module validate_network
Log file: /var/log/active/platform/log/diag1.log
Starting diagnostic test(s)
===========================
test - validate_network
: Passed
Diagnostics Completed
admin:
Step 4
Back up the server by using the Disaster Recovery System. See the Disaster Recovery System
Administration Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/drs_administration/guide/9xcucdrsa
g.html.
Step 5
On a DNS server, change the DNS record of the server to the new IPv6 address. Update both the
forward (AAAA) and reverse (PTR) records.
Upgrade Guide for Cisco Unity Connection Release 9.x
13-6
Chapter 13
Adding or Changing the IPv6 Addresses of Cisco Unity Connection
Changing the IPv6 Address
Step 6
Change the IPv6 address of the server:
a.
Sign in to Cisco Unified Operating System Administration.
b.
From the Settings menu, select IP > Ethernet IPv6.
c.
Under Address Source, if Router Advertisement or DHCP is selected, either select Manual Entry
to change to a static non-link-local IPv6 address and then continue to Substep d., or change the
assigned IPv6 prefix or address in the router or DHCPv6 server and then skip to Substep e.
Note
Step 7
Cisco recommends that you manually configure the Unity Connection server with a static
non-link-local IPv6 address.
d.
Under Address Source, change the value of the IPv6 Address field and, if applicable, the Subnet
Mask field.
e.
Check the Update with Reboot check box.
f.
Select Save, and the system restarts.
In the RTMT, confirm that the server is running and available:
a.
Using the RTMT, sign in to the server.
b.
In the left pane, under Tools, select Alert Central.
c.
In the right pane, on the System tab, if ServerDown is black, skip to Step 8.
If ServerDown is red, right-click ServerDown, and select Alert Details. Resolve the problem before
continuing.
Step 8
Back up the server by using the Disaster Recovery System. See the Disaster Recovery System
Administration Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/drs_administration/guide/9xcucdrsa
g.html.
Step 9
If the Unity Connection server is integrated with Cisco Unified Communications Manager via SIP:
Update the IPv6 address of the Cisco Unity Connection server on the SIP trunk in Cisco Unified
Communications Manager Administration:
a.
Sign in to Cisco Unified CM Administration.
b.
From the Device menu, select Trunk.
c.
Find the trunk corresponding to the Unity Connection server, and select the Name of the trunk.
d.
On the Trunk Configuration page, change the value of the Destination Address IPv6 field to the
new IPv6 address.
e.
Select Save to save the change.
f.
Select Reset to reset the trunk.
Upgrade Guide for Cisco Unity Connection Release 9.x
13-7
Chapter 13
Changing the IPv6 Address
Upgrade Guide for Cisco Unity Connection Release 9.x
13-8
Adding or Changing the IPv6 Addresses of Cisco Unity Connection
CH A P T E R
14
Renaming Cisco Unity Connection 9.x Servers
This chapter contains the following sections:
•
Task List for Renaming a Single 9.x Server Without a Unity Connection Cluster, page 14-1
•
Task List for Renaming the Publisher Server in a Unity Connection 9.x Cluster, page 14-4
•
Task List for Renaming the Subscriber Server in a Unity Connection 9.x Cluster, page 14-7
Task List for Renaming a Single 9.x Server Without a Unity
Connection Cluster
1.
Note
If you created and installed an SSL certificate on the server that you are renaming: Create a new
certificate signing request, and get a new signed certificate before you begin to rename the server.
If you do not get a new signed certificate before you rename the server, when you use web
applications to access the Unity Connection server, a security alert displays and explains that
there is a problem with the security certificate.
a. Run the CLI command set web-security to assign an alternate hostname to the server that you
are renaming. For more information, see the applicable Command Line Interface Reference
Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
b. Create a certificate signing request. Then download the certificate signing request to the server
on which you installed Microsoft Certificate Services or another application that issues
certificates, or download the request to a server that you can use to send the certificate signing
request to an external certification authority (CA). Do the “To Create and Download a
Certificate Signing Request” procedure in the “Creating and Installing an SSL Server
Certificate” subsection in the “Securing Cisco PCA and IMAP Email Client Access to
Cisco Unity Connection” section in the “Configuring SSL in Cisco Unity Connection 9.x”
chapter of the System Administration Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/guide/9xcuc
sagx.html.
c. If you are using Microsoft Certificate Services to export the root certificate and issue the server
certificate, do the “To Export the Root Certificate and Issue the Server Certificate (Only When
You Are Using Microsoft Certificate Services to Issue the Certificate)” procedure in the
“Creating and Installing an SSL Server Certificate” subsection in the “Securing Cisco PCA and
Upgrade Guide for Cisco Unity Connection Release 9.x
14-1
Chapter 14
Renaming Cisco Unity Connection 9.x Servers
Task List for Renaming a Single 9.x Server Without a Unity Connection Cluster
IMAP Email Client Access to Cisco Unity Connection” section in the “Configuring SSL in
Cisco Unity Connection 9.x” chapter of the System Administration Guide for Cisco Unity
Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/guide/9xcuc
sagx.html.
If you are using another application to issue the certificate, see the documentation for the
application for information on issuing certificates.
If you are using an external CA to issue the certificate, send the certificate signing request to
the external CA. When the external CA returns the certificate, continue with Step 2.
2.
If the server that you are renaming is a member server in a Unity Connection networking site (the
server is not a site gateway): Remove the server from the site. See the “Removing a Location From
a Cisco Unity Connection 9.x Site” section in the “Making Changes to the Networking
Configuration in Cisco Unity Connection 9.x” chapter of the Networking Guide for Cisco Unity
Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/networking/guide/9xcucnetx.ht
ml.
3.
Change the hostname of the server. See the “Changing the Hostname of a Single 9.x Server Without
a Unity Connection Cluster” section on page 14-3.
4.
If you created and installed an SSL certificate on the server that you are renaming: Upload the root
certificate and the server certificate to the Unity Connection server. Do the “To Upload the Root and
Server Certificates to the Cisco Unity Connection Server” procedure in the “Creating and Installing
an SSL Server Certificate” subsection in the “Securing Cisco PCA and IMAP Email Client Access
to Cisco Unity Connection” section in the “Configuring SSL in Cisco Unity Connection 9.x”
chapter of the System Administration Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/guide/9xcucsagx
.html.
5.
If you created and installed an SSL certificate on the server that you are renaming: Restart the Unity
Connection IMAP Server service so that Unity Connection and the IMAP email clients use the new
SSL certificates. Do the “To Restart the Unity Connection IMAP Server Service” procedure in the
“Creating and Installing an SSL Server Certificate” subsection in the “Securing Cisco PCA and
IMAP Email Client Access to Cisco Unity Connection” section in the “Configuring SSL in
Cisco Unity Connection 9.x” chapter of the System Administration Guide for Cisco Unity
Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/guide/9xcucsagx
.html.
6.
If the server was a member server in a Unity Connection networking site before you renamed the
server: Re-add the server to the site. See the “Setting up a Cisco Unity Connection Site” section in
the “Setting Up Networking Between Cisco Unity Connection 9.x Servers” chapter of the
Networking Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/networking/guide/9xcucnetx.ht
ml.
Note
7.
Verify that replication between locations in the site has completed before continuing with the
rest of the task list.
Back up the server by using the Disaster Recovery System. See the Disaster Recovery System
Administration Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/drs_administration/guide/9xcuc
drsag.html.
Upgrade Guide for Cisco Unity Connection Release 9.x
14-2
Chapter 14
Renaming Cisco Unity Connection 9.x Servers
Task List for Renaming a Single 9.x Server Without a Unity Connection Cluster
Changing the Hostname of a Single 9.x Server Without a Unity Connection
Cluster
Revised January 9, 2014
To Change the Hostname of a Single 9.x Server Without a Unity Connection Cluster
Step 1
On a DNS server, change the DNS record of the Unity Connection server to the new hostname.
Step 2
Confirm that the DNS change propagates to the server. Sign in to the server by using an SSH application,
and run the CLI command utils network host <hostname>.
Do not proceed if the new hostname does not resolve to the correct IP address.
Step 3
Step 4
Step 5
Step 6
Step 7
Optional: On the Unity Connection server, change the SMTP domain in Cisco Unity Connection
Administration:
a.
Expand System Settings > SMTP Configuration, and select Server.
b.
Select Change SMTP Domain, and change the value of the SMTP Domain field.
c.
Select Save.
In Unity Connection Administration, change the hostname of the server:
a.
Expand System Settings, and select Cluster.
b.
Select Find to display the list of servers.
c.
Select the hostname of the server that you want to rename.
d.
On the Server Configuration page, change the value of the Hostname/IP Address field to the new
name.
e.
Select Save.
Optional: In Unity Connection Administration, change the networking display name of the server:
a.
Expand Networking, and select Locations.
b.
Select the display name of the server that you want to rename.
c.
On the Edit Location page, change the value of the Display Name field to the new name. (This field
is for display purpose only and need not match the server hostname.)
d.
Select Save.
In Cisco Unified Operating System Administration, change the hostname of the server:
a.
From the Settings menu, select IP > Ethernet.
b.
Change the hostname of the Unity Connection server.
c.
Select Save.
d.
This causes the server to restart. If the server does not restart automatically, then hard reboot the
standalone server. Proceed with Step 7 once the server is back to running state.
Navigate to Cisco Unified Operating System Administration, and check if the old hostname of the
server is replaced by the new hostname.
Upgrade Guide for Cisco Unity Connection Release 9.x
14-3
Chapter 14
Renaming Cisco Unity Connection 9.x Servers
Task List for Renaming the Publisher Server in a Unity Connection 9.x Cluster
Task List for Renaming the Publisher Server in a Unity
Connection 9.x Cluster
The following procedure uses the CLI command set web-security to specify the new server name as the
alternate host name for the server. This allows you to continue using the original name for the server
while you send the certificate signing request (which will contain both the current name and the new,
alternate name) to a certificate authority and wait for the certificate to be returned. If you want to use
SSL, and if you want to use the CLI command set web-security to specify a shared alternate name to
the two servers in a cluster, you can omit Task 1.a., and you can do the remainder of Task 1.a. after you
rename the server, in Task 3. (When the two servers have a shared alternate name, you can configure
DNS to automatically reroute client requests to the other server when one server is unavailable.)
However, until you install the new certificate, clients will receive certificate warnings because the name
of the server does not match the name in the old SSL certificate.
1.
Note
If you created and installed an SSL certificate on the server that you are renaming: Create a new
certificate signing request, and get a new signed certificate before you begin to rename the server.
If you do not get a new signed certificate before you rename the server, when you use web
applications to access the Unity Connection server, a security alert displays and explains that
there is a problem with the security certificate.
a. Run the CLI command set web-security and, for the alternatehostname parameter, specify the
new name for the server. For more information, see the applicable Command Line Interface
Reference Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
b. Create a certificate signing request. Then download the certificate signing request to the server
on which you installed Microsoft Certificate Services or another application that issues
certificates, or download the request to a server that you can use to send the certificate signing
request to an external certification authority (CA). Do the “To Create and Download a
Certificate Signing Request” procedure in the “Creating and Installing an SSL Server
Certificate” subsection in the “Securing Cisco PCA and IMAP Email Client Access to
Cisco Unity Connection” section in the “Configuring SSL in Cisco Unity Connection 9.x”
chapter of the System Administration Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/guide/9xcuc
sagx.html.
c. If you are using Microsoft Certificate Services to export the root certificate and issue the server
certificate, do the “To Export the Root Certificate and Issue the Server Certificate (Only When
You Are Using Microsoft Certificate Services to Issue the Certificate)” procedure in the
“Creating and Installing an SSL Server Certificate” subsection in the “Securing Cisco PCA and
IMAP Email Client Access to Cisco Unity Connection” section in the “Configuring SSL in
Cisco Unity Connection 9.x” chapter of the System Administration Guide for Cisco Unity
Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/guide/9xcuc
sagx.html.
If you are using another application to issue the certificate, see the documentation for the
application for information on issuing certificates.
If you are using an external CA to issue the certificate, send the certificate signing request to
the external CA. When the external CA returns the certificate, continue with Step 2.
Upgrade Guide for Cisco Unity Connection Release 9.x
14-4
Chapter 14
Renaming Cisco Unity Connection 9.x Servers
Task List for Renaming the Publisher Server in a Unity Connection 9.x Cluster
2.
If the server that you are renaming is a member server in a Unity Connection networking site (the
server is not a site gateway): Remove the server from the site. See the “Removing a Location From
a Cisco Unity Connection 9.x Site” section in the “Making Changes to the Networking
Configuration in Cisco Unity Connection9.x” chapter of the Networking Guide for Cisco Unity
Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/networking/guide/9xcucnetx.ht
ml.
Caution
Re-adding a server to a site can be a time-consuming process. Ensure that you thoroughly
understand the work required to re-add a server to a site before you begin this procedure.
3.
Change the hostname of the server. See the “Changing the Hostname of the Publisher Server in a
Unity Connection 9.x Cluster” section on page 14-5.
4.
If you created and installed an SSL certificate on the server that you are renaming: Upload the root
certificate and the server certificate to the Unity Connection server. Do the “To Upload the Root and
Server Certificates to the Cisco Unity Connection Server” procedure in the “Creating and Installing
an SSL Server Certificate” subsection in the “Securing Cisco PCA and IMAP Email Client Access
to Cisco Unity Connection” section in the “Configuring SSL in Cisco Unity Connection 9.x”
chapter of the System Administration Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/administration/guide/8xcucsagx
.html.
5.
If you created and installed an SSL certificate on the server that you are renaming: Restart the Unity
Connection IMAP Server service so that Unity Connection and the IMAP email clients use the new
SSL certificates. Do the “To Restart the Unity Connection IMAP Server Service” procedure in the
“Creating and Installing an SSL Server Certificate” subsection in the “Securing Cisco PCA and
IMAP Email Client Access to Cisco Unity Connection” section in the “Configuring SSL in
Cisco Unity Connection 9.x” chapter of the System Administration Guide for Cisco Unity
Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/guide/9xcucsagx
.html.
6.
If the server was a member server in a Unity Connection networking site before you renamed the
server: Re-add the server to the site. See the “Setting up a Cisco Unity Connection Site” section in
the “Setting Up Networking Between Cisco Unity Connection 9.x Servers” chapter of the
Networking Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/networking/guide/9xcucnetx.ht
ml.
7.
Back up the server by using the Disaster Recovery System. See the Disaster Recovery System
Administration Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/drs_administration/guide/9xcuc
drsag.html.
Changing the Hostname of the Publisher Server in a Unity Connection 9.x
Cluster
Revised December 24, 2013
Upgrade Guide for Cisco Unity Connection Release 9.x
14-5
Chapter 14
Renaming Cisco Unity Connection 9.x Servers
Task List for Renaming the Publisher Server in a Unity Connection 9.x Cluster
To Change the Hostname of the Publisher Server in a Unity Connection 9.x Cluster
Step 1
On a DNS server, change the DNS record of the publisher server to the new hostname.
Step 2
Confirm that the DNS change propagates to the publisher server. Sign in to the publisher server by using
an SSH application, and run the CLI command utils network host <hostname>.
Do not proceed if the new hostname does not resolve to the correct IP address.
Step 3
Repeat Step 2 on the subscriber server.
Step 4
On the publisher server, change the SMTP domain in Cisco Unity Connection Administration (this
change is automatically replicated to the subscriber server):
Step 5
Step 6
Step 7
Step 8
Step 9
a.
Expand System Settings > SMTP Configuration, and select Server.
b.
Select Change SMTP Domain, and change the value of the SMTP Domain field.
c.
Select Save.
On the publisher server, change the hostname of the publisher server in Unity
Connection Administration:
a.
Expand System Settings, and select Cluster.
b.
Select Find to display a list of servers.
c.
Select the hostname of the server that you want to rename.
d.
On the Server Configuration page, change the value of the Hostname/IP Address field to the new
name.
e.
Select Save.
Optional: On the publisher server, change the networking display name of the server in Unity
Connection Administration:
a.
Expand Networking, and select Locations.
b.
Select the display name of the server that you want to rename.
c.
On the Edit Location page, change the value of the Display Name field to the new name. (This field
is for display purpose only and need not match the server hostname.)
d.
Select Save.
On the subscriber server, change the name by which the subscriber server knows the publisher server:
a.
In Cisco Unified Operating System Administration, from the Settings menu, select IP > Publisher.
b.
Change the hostname of the publisher server.
c.
Select Save.
On the publisher server, change the name of the publisher server in Cisco Unified Operating System
Administration.
a.
From the Settings menu, select IP > Ethernet.
b.
Change the hostname of the publisher server.
c.
Select Save.
d.
Hard boot the publisher server. Wait for the publisher server to finish restarting. When you are able
to sign-in to Unity Connection Administration on the publisher server, continue with Step 9.
Hard boot subscriber server. When you are able to sign-in to Unity Connection Administration on the
subscriber server, continue with Step 10.
Upgrade Guide for Cisco Unity Connection Release 9.x
14-6
Chapter 14
Renaming Cisco Unity Connection 9.x Servers
Task List for Renaming the Subscriber Server in a Unity Connection 9.x Cluster
Step 10
On the publisher server, to reset replication run the CLI command utils dbreplication reset all.
Note
Step 11
On all the publisher and subscriber servers, run the CLI command utils dbreplication stop
before running the utils dbreplication reset all command. For more information, see the
applicable secion in the Command Line Interface Reference Guide for Cisco Unified
Communications Solutions guide:
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
Wait until the replication reset process is complete. To determine when the process is completed:
a.
Sign in to Real-Time Monitoring Tool (RTMT) by connecting to the publisher server.
b.
On the System menu, select Performance > Open Performance Monitoring.
c.
In the right pane, expand Number of Replicates Created and State of Replication, then
double-click Replicate_State.
d.
In the Object Instances dialog box, select ReplicateCount and select Add.
e.
Wait until the value reaches 2.0.
For more information on possible values and their meaning, right-click Replicate_State, and select
Counter Description.
f.
Step 12
On the File menu, select Exit to exit RTMT.
Sign in to the publisher server by using an SSH application, and run the CLI command utils system
restart to restart the server.
This command causes the Unity Connection cluster servers to change server status so that the publisher
server has the secondary status and the subscriber server has the primary status.
Step 13
Run the CLI command utils cuc cluster makeprimary <name_of_publisher_server> to change the
publisher server to primary status.
Task List for Renaming the Subscriber Server in a Unity
Connection 9.x Cluster
The following procedure uses the CLI command set web-security to specify the new server name as the
alternate host name for the server. This allows you to continue using the original name for the server
while you send the certificate signing request (which will contain both the current name and the new,
alternate name) to a certificate authority and wait for the certificate to be returned. If you want to use
SSL, and if you want to use the CLI command set web-security to specify a shared alternate name to
the two servers in a cluster, you can omit Task 1.a., and you can do the remainder of Task 1.a. after you
rename the server, in Task 2. (When the two servers have a shared alternate name, you can configure
DNS to automatically reroute client requests to the other server when one server is unavailable.)
However, until you install the new certificate, clients will receive certificate warnings because the name
of the server does not match the name in the old SSL certificate.
1.
If you created and installed an SSL certificate on the server that you are renaming: Create a new
certificate signing request, and get a new signed certificate before you begin to rename the server.
Upgrade Guide for Cisco Unity Connection Release 9.x
14-7
Chapter 14
Renaming Cisco Unity Connection 9.x Servers
Task List for Renaming the Subscriber Server in a Unity Connection 9.x Cluster
Note
If you do not get a new signed certificate before you rename the server, when you use web
applications to access the Unity Connection server, a security alert displays and explains that
there is a problem with the security certificate.
a. Run the CLI command set web-security and, for the alternatehostname parameter, specify the
new name for the server. For more information, see the applicable Command Line Interface
Reference Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
b. Create a certificate signing request. Then download the certificate signing request to the server
on which you installed Microsoft Certificate Services or another application that issues
certificates, or download the request to a server that you can use to send the certificate signing
request to an external certification authority (CA). Do the “To Create and Download a
Certificate Signing Request” procedure in the “Creating and Installing an SSL Server
Certificate” subsection in the “Securing Cisco PCA and IMAP Email Client Access to
Cisco Unity Connection” section in the “Configuring SSL in Cisco Unity Connection 9.x”
chapter of the System Administration Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/guide/9xcuc
sagx.html.
c. If you are using Microsoft Certificate Services to export the root certificate and issue the server
certificate, do the “To Export the Root Certificate and Issue the Server Certificate (Only When
You Are Using Microsoft Certificate Services to Issue the Certificate)” procedure in the
“Creating and Installing an SSL Server Certificate” subsection in the “Securing Cisco PCA and
IMAP Email Client Access to Cisco Unity Connection” section in the “Configuring SSL in
Cisco Unity Connection 9.x” chapter of the System Administration Guide for Cisco Unity
Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/guide/9xcuc
sagx.html.
If you are using another application to issue the certificate, see the documentation for the
application for information on issuing certificates.
If you are using an external CA to issue the certificate, send the certificate signing request to
the external CA.
2.
Change the hostname of the server. See the “Changing the Hostname of the Subscriber Server in a
Unity Connection 9.x Cluster” section on page 14-9.
3.
If you created and installed an SSL certificate on the server that you are renaming: Upload the root
certificate and the server certificate to the Unity Connection server. Do the “To Upload the Root and
Server Certificates to the Cisco Unity Connection Server” procedure in the “Creating and Installing
an SSL Server Certificate” subsection in the “Securing Cisco PCA and IMAP Email Client Access
to Cisco Unity Connection” section in the “Configuring SSL in Cisco Unity Connection 9.x”
chapter of the System Administration Guide for Cisco Unity Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/guide/9xcucsagx
.html.
4.
If you created and installed an SSL certificate on the server that you are renaming: Restart the Unity
Connection IMAP Server service so that Unity Connection and the IMAP email clients use the new
SSL certificates. Do the “To Restart the Unity Connection IMAP Server Service” procedure in the
“Creating and Installing an SSL Server Certificate” subsection in the “Securing Cisco PCA and
IMAP Email Client Access to Cisco Unity Connection” section in the “Configuring SSL in
Cisco Unity Connection 9.x” chapter of the System Administration Guide for Cisco Unity
Upgrade Guide for Cisco Unity Connection Release 9.x
14-8
Chapter 14
Renaming Cisco Unity Connection 9.x Servers
Task List for Renaming the Subscriber Server in a Unity Connection 9.x Cluster
Connection at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/administration/guide/9xcucsagx
.html.
5.
Back up the server by using the Disaster Recovery System. See the Disaster Recovery System
Administration Guide for Cisco Unity Connection Release 9.x at
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/9x/drs_administration/guide/9xcuc
drsag.html.
Changing the Hostname of the Subscriber Server in a Unity Connection 9.x
Cluster
Revised December 24, 2013
To Change the Hostname of the Subscriber Server in a Unity Connection 9.x Cluster
Step 1
On a DNS server, change the DNS record of the subscriber server to the new hostname.
Step 2
Confirm that the DNS change propagates to the publisher server. Sign in to the publisher server by using
an SSH application, and run the CLI command utils network host <hostname>.
Do not proceed if the new hostname does not resolve to the correct IP address.
Step 3
Repeat Step 2 on the subscriber server.
Step 4
On the publisher server, change the name by which the publisher server knows the subscriber server:
Step 5
a.
In Cisco Unity Connection Administration, expand System Settings, and select Cluster.
b.
Select Find to display a list of servers.
c.
Select the hostname of the subscriber server.
d.
On the Server Configuration page, change the value of the Hostname/IP Address field to the new
name.
e.
Select Save.
On the subscriber server, change the name of the subscriber server in Cisco Unified Operating System
Administration.
a.
From the Settings menu, select IP > Ethernet.
b.
Change the hostname of the server.
c.
Select Save.
d.
Hard boot the subscriber server and wait for the subscriber server to finish restarting. When you can
sign in to Connection Administration on the subscriber server, continue with Step 6.
Step 6
Hard boot the publisher server. Wait for the publisher server to finish restarting. When you are able to
sign-in to Unity Connection Administration on the publisher server, continue with Step 7.
Step 7
On the publisher server, run the CLI command utils dbreplication reset all to reset replication.
Step 8
Sign in to the publisher server by using an SSH application, and run the CLI command utils system
restart to restart the server a second time.
This command causes the Unity Connection cluster servers to change server status so that the publisher
server has the secondary status and the subscriber server has the primary status.
Upgrade Guide for Cisco Unity Connection Release 9.x
14-9
Chapter 14
Step 9
Run the CLI command utils cuc cluster makeprimary <name_of_publisher_server> to change the
publisher server to primary status.
Upgrade Guide for Cisco Unity Connection Release 9.x
14-10
Renaming Cisco Unity Connection 9.x Servers
CH A P T E R
15
Changing DNS Settings or the Domain Name for a
Cisco Unity Connection 9.x Server
This chapter contains the following sections:
•
CLI Commands Used to Change Cisco Unity Connection 9.x DNS Settings, page 15-1
•
Changing the Domain Name of the Cisco Unity Connection 9.x Server, page 15-1
CLI Commands Used to Change Cisco Unity Connection 9.x DNS
Settings
You change Unity Connection DNS settings by using CLI commands. Table 15-1 lists the available
options and the corresponding CLI commands.
For more information on the CLI commands, see the applicable Command Line Interface Reference
Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
Table 15-1
CLI Commands Used to Change DNS Settings in Unity Connection 9.x
DNS Setting
CLI Command
Delete the IP address for a DNS server
delete dns
Specify or change the IP address for the primary or secondary DNS server
set network dns
Set the DNS request time-out period in seconds
set network dns options
Set the number of times to attempt a DNS request before quitting
set network dns options
Rotate among the configured DNS servers, distributing the load
set network dns options
Changing the Domain Name of the Cisco Unity Connection 9.x
Server
The method you use to change the domain name of the Unity Connection server depends on whether you
have DHCP configured. Do the applicable procedure.
Upgrade Guide for Cisco Unity Connection Release 9.x
15-1
Chapter 15 Changing DNS Settings or the Domain Name for a Cisco Unity Connection 9.x Server
Changing the Domain Name of the Cisco Unity Connection 9.x Server
For more information on the CLI commands, see the applicable Command Line Interface Reference
Guide for Cisco Unified Communications Solutions at
http://www.cisco.com/en/US/products/ps6509/prod_maintenance_guides_list.html.
To Change the Domain Name of the Connection Server When DHCP Is Configured
Step 1
On the applicable DHCP and DNS servers, change the domain name of the Unity Connection server.
Step 2
Restart the Unity Connection server by using the utils system restart CLI command.
Step 3
Restart the Unity Connection server again by using the utils system restart CLI command.
To Change the Domain Name of the Connection Server When DHCP Is Not Configured
On the Unity Connection server, run the set network domain CLI command.
Upgrade Guide for Cisco Unity Connection Release 9.x
15-2