Upgrade Guide for Cisco Unified Presence
Release 8.6
July 1, 2016
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this
URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the
document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
Upgrade Guide for Cisco Unified Presence Release 8.6
© 2014 Cisco Systems, Inc. All rights reserved.
Contents
CHAPTER
1
Preface
1-1
Change History
1-1
About this Guide
Audience
1-1
1-1
Organization
1-2
Related Documents
Conventions
1-2
1-3
Obtain Documentation and Submit a Service Request
Cisco Product Security Overview
CHAPTER
2
Before You Begin
1-4
1-4
2-1
Read this First 2-1
System Availability after Upgrade 2-1
Support for Intercluster Peers 2-2
Multi-node Clusters 2-2
Cisco Unified Communications Manager Business Edition 5000 to Cisco Unified Communications
Manager 2-2
Types of Upgrades 2-2
Standard Upgrades 2-3
Refresh Upgrades 2-3
Upgrade Time Requirements 2-3
Disable Throttling to Decrease the Time Required to Upgrade
License Requirements
Bridged Upgrade
2-4
2-4
2-4
Refresh Upgrade to Cisco Unified Presence Release 8.6(4) 2-5
Special Considerations for Refresh Upgrades 2-6
Upgrade of an MCS-7825-H3 or MCS-7828-H3 Server 2-6
COP File Installation 2-6
Refresh Upgrade Stages 2-6
Preparation Phase 2-6
Installation Phase 2-6
System Startup Phase 2-7
Data Migration Messages during a Refresh Upgrade 2-7
Upgrade Paths and Requirements 2-7
Upgrade Paths to Cisco Unified Presence Release 8.6(1), 8.6(2) and 8.6(3)
Upgrade Paths to Cisco Unified Presence Release 8.6(4) 2-7
Upgrade Paths to Cisco Unified Presence Release 8.6(5) 2-8
Upgrade Notes 2-9
2-7
Upgrade Guide for Cisco Unified Presence Release 8.6
1
Contents
Upgrade from Cisco Unified Presence Release 7.0(x) to Release 8.6 2-9
Upgrade from Cisco Unified Presence Release 8.0(x) or Release 8.5 to Release 8.6
Intercluster Upgrades 2-10
Prerequisites for an Intercluster Upgrade 2-10
Roster Migration for Intercluster Upgrade 2-11
Contact List Size for Intercluster Upgrade 2-11
SIP Remote Contact Limit for Intercluster Upgrade
Pre-Upgrade Tasks
CHAPTER
3
2-11
2-12
Upgrade Procedures
3-1
Multi-node Software Upgrade Procedures
Standard Upgrades 3-2
Refresh Upgrades 3-3
3-1
Upgrade Software Procedures 3-5
Upgrade from Local Source 3-5
Upgrade from Remote Source 3-7
Upgrading to Cisco Unified Presence Release 8.6(4) and later on a Virtual Server
Switch Cisco Unified Presence Software Version 3-9
Revert to the Previous Software Version 3-9
Switch Versions from Cisco Unified Presence Release 8.6(4) or Later
Perform an Intercluster Upgrade 3-11
Verify that the Roster Migration is Complete on Cisco Unified Presence
Troubleshoot Roster Migration 3-14
CHAPTER
4
Post Upgrade Tasks
High Availability
CHAPTER
5
Troubleshooting
3-10
3-13
4-1
4-1
5-1
Cisco Unified Presence User Phone Presence Problems
5-1
Cisco Unified Presence User Experiences Issues Obtaining Presence Availability
Real-Time Monitoring Tool Alert for the Cisco UP SIP Proxy Service
Cannot Find Upgrade File on Remote Server
Upgrade File Checksum Values do not Match
Database Replication Did Not Complete
5-2
5-2
5-2
Cisco UP Presence Engine Database Does Not Restart
Refresh Upgrade Error
Failed Refresh Upgrade
5-3
5-3
Upgrade Guide for Cisco Unified Presence Release 8.6
2
5-2
5-2
5-1
3-8
2-9
Contents
Upgrade from Pre Release 8.6(4) Fails
Cancelled or Failed Upgrade
CHAPTER
6
Reference
5-3
5-3
6-1
Effects of I/O Throttling 6-1
Overview 6-1
Disable Throttling 6-1
Server Models 6-1
Write-Cache 6-2
Locale Specific Upgrades 6-4
About Locales 6-4
Locale Installation 6-5
Upgrade Guide for Cisco Unified Presence Release 8.6
3
Contents
Upgrade Guide for Cisco Unified Presence Release 8.6
4
CH A P T E R
1
Preface
•
Change History, page 1-1
•
About this Guide, page 1-1
•
Audience, page 1-1
•
Organization, page 1-2
•
Related Documents, page 1-2
•
Conventions, page 1-3
•
Obtain Documentation and Submit a Service Request, page 1-4
•
Cisco Product Security Overview, page 1-4
Change History
Table 1-1
Change History
Revision
Location
First revision of restructured document
All chapters
Updates for Release 8.6(4)
Before You Begin, Upgrade Procedures,
Troubleshooting
Updates for Release 8.6(5)
Before You Begin, Upgrade Procedures
About this Guide
This document describes how to upgrade to Cisco Unified Presence Release 8.6.
Audience
This Upgrade Guide is intended for administrators who are responsible for upgrading to
Cisco Unified Presence Release 8.6.
Upgrade Guide for Cisco Unified Presence Release 8.6
1-1
Chapter 1
Preface
Organization
Organization
This document contains the following chapters:
•
Preface—contains information about this document including the document change history, the
intended audience, typographic conventions and a list of related documents.
•
Before You Begin—describes the upgrade process, upgrade time requirements, license
requirements, intercluster upgrades, supported upgrade paths and the tasks that you must perform
before you begin an upgrade.
•
Upgrade Procedures—describes all the procedures to upgrade Cisco Unified Presence including
how to revert to an earlier software version or switch to the newer software version.
•
Post Upgrade Tasks—describes the tasks that you must perform after you upgrade
Cisco Unified Presence.
•
Troubleshooting—describes performance issues and includes possible causes and solutions.
•
Reference—describes the effects of I/O throttling and how to disable throttling. This section also
describes user locales and locale installation.
Related Documents
We strongly recommend that you read this entire document to familiarize yourself with the upgrade
process and prerequisites. See the following Cisco Unified Presence guides for more information.
•
Online Help for Cisco Unified Presence Administration
Provides step-by-step instructions for configuring, maintaining, and administering
Cisco Unified Presence.
•
Hardware and Software Compatibility Information for Cisco Unified Presence
http://www.cisco.com/en/US/products/ps6837/products_device_support_tables_list.html
Indicates compatible hardware servers and software with your current version of
Cisco Unified Presence.
•
Cisco Unified Operating System Maintenance Guide for Cisco Unified Presence
http://www.cisco.com/en/US/products/ps6837/prod_maintenance_guides_list.html
Provides information about the utilities that are available via the operating system and the command
line interface.
•
Installation Guide for Cisco Unified Presence
http://www.cisco.com/en/US/products/ps6837/prod_installation_guides_list.html
Provides information about installing Cisco Unified Presence software and instructions on how to
perform software installations.
•
Deployment Guide for Cisco Unified Presence
http://www.cisco.com/en/US/products/ps6837/products_installation_and_configuration_guides_lis
t.html
Provides an overview of the configuration process for Cisco Unified Presence and Cisco Unified
Communications Manager, as well as information about integrating Cisco Unified Presence with
Microsoft Live Communications Server, Microsoft Active Directory, and Microsoft Office
Communicator. Also contains Cisco recommendations for high availability.
•
Real-Time Monitoring Tool Administration Guide for Cisco Unified Presence
http://www.cisco.com/en/US/products/ps6837/prod_maintenance_guides_list.html
Upgrade Guide for Cisco Unified Presence Release 8.6
1-2
Chapter 1
Preface
Conventions
Provides descriptions of Cisco Unified Presence serviceability, as well as step-by-step instructions
for configuring alarms, traces, and other reporting.
•
Disaster Recovery System Administration Guide
http://www.cisco.com/en/US/products/ps6837/prod_maintenance_guides_list.html
Describes how to configure the backup settings, how to back up Cisco Unified Presence data, and
how to restore the data.
•
For Cisco Unified Communications Manager information, see the following URL:
http://cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html?q=
Conventions
This document uses the following conventions.
Note
Caution
Convention
Description
boldface font
Commands and keywords are in boldface.
italic font
Arguments for which you supply values are in italics.
[]
Elements in square brackets are optional.
{x|y|z}
Alternative keywords are grouped in braces and separated by
vertical bars.
[x|y|z]
Optional alternative keywords are grouped in brackets and
separated by vertical bars.
string
A nonquoted set of characters. Do not use quotation marks
around the string or the string will include the quotation marks.
screen font
Terminal sessions and information the system displays are in
screen font.
boldface screen font
Information you must enter is in boldface screen font.
italic screen font
Arguments for which you supply values are in italic screen
font.
^
The symbol ^ represents the key labeled Control—for example,
the key combination ^D in a screen display means hold down the
Control key while you press the D key.
<>
Nonprinting characters, such as passwords, are in angle
brackets.
Means reader take note. Notes contain helpful suggestions or references to material not covered in the
publication.
Means reader be careful. In this situation, you might do something that could result in equipment damage
or loss of data.
Upgrade Guide for Cisco Unified Presence Release 8.6
1-3
Chapter 1
Preface
Obtain Documentation and Submit a Service Request
Timesaver
Tip
Means the described action saves time. You can save time by performing the action described in the
paragraph.
Means the information contains useful tips.
Obtain Documentation and Submit 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.
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 Unified Presence Release 8.6
1-4
CH A P T E R
2
Before You Begin
•
Read this First, page 2-1
•
Types of Upgrades, page 2-2
•
Upgrade Time Requirements, page 2-3
•
License Requirements, page 2-4
•
Bridged Upgrade, page 2-4
•
Refresh Upgrade to Cisco Unified Presence Release 8.6(4), page 2-5
•
Upgrade Paths and Requirements, page 2-7
•
Intercluster Upgrades, page 2-10
•
Pre-Upgrade Tasks, page 2-12
Read this First
Read the following important notes before you begin an upgrade.
Caution
Do not make any changes to Cisco Unified Presence configuration during an upgrade. If data is written
to the database during the upgrade, the upgrade may fail.
•
All refresh upgrades must be performed during a maintenance window because the system will not
be available during the upgrade.
•
If you cancel an upgrade at any stage, or if an upgrade fails, you must reboot the
Cisco Unified Presence server before you attempt another upgrade.
System Availability after Upgrade
For standard upgrades, when you activate the upgraded software, the system restarts and is out of service
for up to 30 minutes on the publisher node. The length of the outage on subscriber nodes depends on
how long database replication takes to complete and on the size of the database.
Also, if you need to revert to an earlier software version, you must restart the system which results in a
similar service outage period.
Upgrade Guide for Cisco Unified Presence Release 8.6
2-1
Chapter 2
Before You Begin
Types of Upgrades
Support for Intercluster Peers
Cisco Unified Presence Release 8.6 supports intercluster peers to clusters running Release 7.0(x) and
Release 8.6 only. Intercluster peers to clusters running Release 8.0(x) or Release 8.5(x) are not
supported.
If you perform an upgrade from Cisco Unified Presence Release 7.0(x) to Release 8.6 on one, or both,
of the clusters in an intercluster deployment, you must follow the recommended upgrade procedure in
Perform an Intercluster Upgrade, page 3-11.
Multi-node Clusters
If you have a Cisco Unified Presence cluster comprising multiple nodes, you must upgrade all nodes in
the cluster. If you have a multi-node cluster, you must upgrade the publisher node prior to upgrading the
subscriber nodes. Also, you cannot perform a fresh installation on the publisher node and then perform
an upgrade on subscriber nodes.
Cisco Unified Communications Manager Business Edition 5000 to Cisco Unified
Communications Manager
There is no upgrade path in VMware to upgrade from Cisco Unified Communications Manager Business
Edition 5000 to Cisco Unified Communications Manager. A fresh installation is needed. After you
perform the fresh installation, Cisco Unified Presence re-synchronizes data with the new Cisco Unified
Communications Manager. The Syncagent uses the primary key (pkid) as a comparison field for the
synchronization. When the Cisco Unified Communications Manager is re-installed, all the pkid on Cisco
Unified Communications Manager are changed. As such, any existing data on Cisco Unified Presence is
cleaned up and the Syncagent deletes the old data. Be sure to backup your data before performing this
procedure.
Types of Upgrades
Cisco Unified Presence allows you to install upgrade software on your server while the system continues
to operate. There are two types of upgrades:
•
standard upgrades—upgrades which do not upgrade the operating system and do not require
multiple reboots during installation
•
refresh upgrades—upgrades which require multiple reboots during installation to upgrade the
underlying operating system
The server automatically determines whether you need to perform a standard upgrade or a refresh
upgrade.
Note
•
All upgrades to Cisco Unified Presence Release 8.6(4) are refresh upgrades.
•
All refresh upgrades must be performed during a maintenance window because the system will not
be available during the upgrade.
Upgrade Guide for Cisco Unified Presence Release 8.6
2-2
Chapter 2
Before You Begin
Upgrade Time Requirements
Standard Upgrades
For standard upgrades, when you install upgrade software, you install the software as an inactive version.
The system continues to function normally while you are installing the software. When the upgrade is
complete, you can choose to automatically reboot the system to the upgraded software or you can
manually switch to the new software at a later time. When you reboot to the new software, the old
software version remains on the system. This allows you to switch back to the old version in the unlikely
event of issues with the new software. During an upgrade your configuration information migrates
automatically to the upgraded version.
Note
You can only make changes to the database on the active software. The database for the inactive software
is not updated. If you make changes to the database after an upgrade, you must repeat those changes after
switching to the new software.
Refresh Upgrades
Note
All refresh upgrades must be performed during a maintenance window because the system will not be
available during the upgrade.
For refresh upgrades, the system allows you to choose whether or not to automatically run the new
upgrade software when the upgrade completes. If you select not to run the new software, the system will
reboot to the old software version when the upgrade is complete and you can manually switch to the new
software at a later time. Refresh upgrades differ from standard upgrades because with refresh upgrades
the system reboots if you want to continue to run the old software version; the system does not need to
reboot to switch to the new version. For more information about refresh upgrades, see Refresh Upgrade
to Cisco Unified Presence Release 8.6(4), page 2-5.
If for any reason you decide to revert to the prior software version, you can switch versions to the older
version of the software. This switch version requires a reboot. Be aware that any configuration changes
that you made after upgrading the software will be lost.
If you downgrade from Cisco Unified Presence Release 8.6(4) or later, you must install a COP file after
you switch to the older software version. See Switch Versions from Cisco Unified Presence Release
8.6(4) or Later, page 3-10 for more information.
Note
If you deploy MCS-7825-H3 or MCS-7828-H3 servers you cannot revert to the prior version; you must
perform a fresh installation.
Upgrade Time Requirements
The time required to upgrade Cisco Unified Presence software is variable and depends on a number of
factors, such as the number of users, the average contact list size of each user, whether the upgrade is on
the publisher or a subscriber node and the hardware deployed. For large deployments, installation of the
the upgrade software may take several hours.
Upgrade Guide for Cisco Unified Presence Release 8.6
2-3
Chapter 2
Before You Begin
License Requirements
Disable Throttling to Decrease the Time Required to Upgrade
To preserve system stability during upgrades, the system throttles the upgrade process, which may take
considerably longer to complete in Cisco Unified Presence 8.x than it did in earlier releases.
However, if the upgrade process is taking much longer than you would like, you can disable throttling.
Although disabling throttling decreases the time it takes to perform the upgrade, it may degrade system
performance. For more information about throttling and the causes of slow upgrades, see Effects of I/O
Throttling, page 6-1.
License Requirements
Cisco Unified Presence must be operating in permanent Production mode before you can commence an
upgrade. See the Installation Guide for Cisco Unified Presence for more information about licensing
modes.
If you are performing an upgrade to Cisco Unified Presence Release 8.6 from Cisco Unified Presence
Release 7.0(x), you must obtain a software version (upgrade) license. This also applies to bridged
upgrades. You require one software version license for each Cisco Unified Presence cluster. The
software version license enables service startup for the Cisco UP Presence Engine and Cisco UP SIP
Proxy services on Cisco Unified Presence after an upgrade. See the Installation Guide for
Cisco Unified Presence for more information about how to obtain and upload license files.
Note
•
You require a new software version license only if you are upgrading from Cisco Unified Presence
Release 7.0(x). For upgrades from Release 8.0(1) and 8.0(2), the same software version license that
would be used for a 7.0(x) upgrade to Release 8.6 should be used.
•
Direct upgrades to Release 8.6(4) or later from Release 7.x and below are not supported. To upgrade
from Release 7.x to Release 8.6(4) or later, you must first upgrade to an earlier 8.x version.
Bridged Upgrade
Cisco Unified Presence supports bridged upgrades to customers who wish to migrate from discontinued
hardware to supported hardware.
The bridged upgrade allows you to create a Disaster Recovery System (DRS) backup on the discontinued
hardware. You can then restore the DRS backup on supported hardware after you complete a fresh
Cisco Unified Presence installation on the supported hardware.
When you attempt an upgrade on the discontinued hardware, Cisco Unified Presence displays a warning
on the interface, and on the CLI, and informs you that Cisco Unified Presence only supports the
functionality to create a DRS backup on this server.
If you perform a bridged upgrade to supported hardware from Cisco Unified Presence 7.0(x), you must
request new server license and software version license files, with a new MAC address for the physical
server, or the new License MAC value for VMware. To do this send an email to [email protected]
requesting a rehost of your license. You can obtain the physical MAC Address and License MAC values
from the Cisco Unified Operating System Administration GUI by selecting Show > Network.
Upgrade Guide for Cisco Unified Presence Release 8.6
2-4
Chapter 2
Before You Begin
Refresh Upgrade to Cisco Unified Presence Release 8.6(4)
Cisco Unified Presence supports bridged upgrades from a number of discontinued servers. See the
Hardware and Software Compatibility Information for Cisco Unified Presence for the list of
discontinued servers.
For more information about DRS backups, see the Disaster Recovery System Administration Guide.
Refresh Upgrade to Cisco Unified Presence Release 8.6(4)
If required, the server automatically determines if you need to perform a standard upgrade or a refresh
upgrade. The initial upgrade to Release 8.6(4) or later is a refresh upgrade (upgrades from Release 8.6(4)
to 8.6(5) are standard upgrades). You can initiate standard and refresh upgrades in the same way using
the Command Line Interface or the Cisco Unified Operating System Administration GUI. A refresh
upgrade has the following differences from a standard upgrade:
Tip
•
multiple reboots as part of the upgrade
•
once started, the console displays status information similar to that of a fresh installation
•
16GB USB Flash Drive is required for MCS-7825-H3 and MCS-7828-H3 DRS backup. Do not
remove the USB key until the upgrade (data migration) is complete.
•
COP file installation is required for upgrades from Release 8.0(1) to 8.6(1), see COP File
Installation, page 2-6.
•
different options to switch versions following completion of the upgrade
•
e-mail notification is sent upon successful completion of the upgrade
Several reboots will occur during a refresh upgrade, therefore, you must perform a refresh upgrade
during a maintenance window.
In a standard upgrade, you are prompted to either Reboot to upgraded partition or Do not reboot after
upgrade. The Reboot to upgraded partition option forces a reboot. This option is required to switch
the node to the new software release.
In a refresh upgrade, you are prompted to select one of the following options:
•
Switch to new version after upgrade—no reboot required
•
Do not switch to new version after upgrade—reboot required
If you want to remain on the upgraded software version, select the Switch to new version after upgrade
option.
If you want the system to automatically reboot and switch back to the old software version, select the
Do not switch to new version after upgrade option.
You can select the Do not switch to new version after upgrade option to perform a staged upgrade. An
example of a staged upgrade would be upgrading a publisher node one night, reverting back to the
inactive software, and then switching to the new active software the following night before upgrading
the subscriber node(s). In this scenario, you must upgrade all subscriber nodes during the same upgrade
window and not switch back the publisher node again. If you switch back the publisher node again, you
must follow the procedure outlined in Switch Versions from Cisco Unified Presence Release 8.6(4) or
Later, page 3-10.
Upgrade Guide for Cisco Unified Presence Release 8.6
2-5
Chapter 2
Before You Begin
Refresh Upgrade to Cisco Unified Presence Release 8.6(4)
Special Considerations for Refresh Upgrades
Note
Cisco highly recommends that you perform a DRS backup before you begin a refresh upgrade.
Upgrade of an MCS-7825-H3 or MCS-7828-H3 Server
If an upgrade fails for any server other than an MCS-7825-H3 or MCS-7828-H3 server, you can revert
back to the previous software version. However, during an upgrade of an MCS-7825-H3 or
MCS-7828-H3 server, the disk is completely reformatted, preventing a switch back to the previous
version. As a result, Cisco highly recommends that you have a 16GB USB key to which you can backup
the DRS.
You should format the USB key. For more information, see the section covering the Answer File
Generator in the Installation Guide for Cisco Unified Presence.
COP File Installation
For all upgrades from Cisco Unified Presence Release 8.0.x through Release 8.6(1) to Release 8.6(4) or
later, you must install a COP file. The name of the COP file is
ciscocm.cup.refresh_upgrade_v<latest_version>.cop and you can download it from Cisco.com.
Note
You must install the COP file on all nodes before you begin the upgrade.
Failing to install the required COP file when necessary results in the following error: Error encountered:
The selected upgrade is disallowed from the current version. The system aborts the upgrade and
automatically reverts back to the previous version of the software. This “COP file check” occurs very
early in the upgrade process (preparation phase), prior to the first reboot and reformat of the drive.
Note
The COP file can not be installed in Cisco Unified Presence Release 7.x upgrades. You must upgrade to
an earlier version of 8.x before you can upgrade to Release 8.6(4) or later.
Refresh Upgrade Stages
Preparation Phase
The preparation phase of a refresh upgrade occurs immediately after the upgrade is initiated. During this
phase, the upgrade progress can be monitored via the GUI or the CLI. After the preparation phase is
completed, the server will automatically reboot to continue the upgrade process. The duration of this
phase varies depending on the size and the complexity of the database configuration.
Installation Phase
The installation phase of a refresh upgrade is very similar to that of a fresh installation with a few
exceptions. The status of this stage can be monitored via the console. No further GUI updates will occur.
During this phase, there is no service support.
Upgrade Guide for Cisco Unified Presence Release 8.6
2-6
Chapter 2
Before You Begin
Upgrade Paths and Requirements
Note
If the upgrade fails on any server other than an MCS-7825-H3 or MCS-7828-H3, the server reboots back
to the previous software version and you can inspect the install logs using the Command Line Interface.
On an MCS-7825-H3 or MCS-7828-H3 server, the disk is completely reformatted; there is no option to
revert to the previous software version. For these servers, Cisco recommends that you dump the
diagnostic logs to the USB flash drive.
System Startup Phase
This is the last phase of a refresh upgrade. Following the completion of a refresh upgrade, all
Cisco Unified Presence applications run the new active software.
Data Migration Messages during a Refresh Upgrade
•
Migration Failed: the pop-up window displays a message stating “Migration failed. Click here to see
the logs.”
•
Migration Abandoned: This option is only visible if the migration has failed. If the user abandons
the migration, it will alert the user that “this will delete all the call records”.
•
Migration Postponed: This option is only visible if the migration has failed. The user can postpone
the migration to a different date and time. Migration will automatically start at the scheduled time
and date.
•
Migration In Progress: There is a message in the pop-up window stating the “Migration is in
progress. Click here to see logs”.
•
Migration Completed: This displays a message stating “Previous Migration was successful”.
Upgrade Paths and Requirements
Upgrade Paths to Cisco Unified Presence Release 8.6(1), 8.6(2) and 8.6(3)
Cisco Unified Presence Release 8.6(1), 8.6(2) and 8.6(3) support the following upgrade paths:
•
Upgrade from Cisco Unified Presence Release 7.0(x)
•
Upgrade from Cisco Unified Presence Release 8.0(x)
•
Upgrade from Cisco Unified Presence Release 8.5(1)
Upgrade Paths to Cisco Unified Presence Release 8.6(4)
All upgrades to Cisco Unified Presence Release 8.6(4) are refresh upgrades.
Upgrade Guide for Cisco Unified Presence Release 8.6
2-7
Chapter 2
Before You Begin
Upgrade Paths and Requirements
Caution
All upgrade paths to Cisco Unified Presence Release 8.6(4) from 8.0(1) through 8.6(1) require the
installation of a COP file. The COP file delivers functionality to allow the upgrade path to be supported
as well as provides various enhancements to the user experience. If you do not install the required COP
file on each node before you begin a refresh upgrade, the upgrade will fail. The COP file is called
ciscocm.cup.refresh_upgrade_v<latest_version>.cop and it can be downloaded from cisco.com.
The following upgrade paths are supported with the required COP file:
•
8.0(1) - 8.6(4)
•
8.0(2) - 8.6(4)
•
8.0(3) - 8.6(4)
•
8.0(4) - 8.6(4)
•
8.5(1) - 8.6(4)
•
8.5(2) - 8.6(4)
•
8.5(3) - 8.6(4)
•
8.5(4) - 8.6(4)
•
8.6(1) - 8.6(4)
The following upgrade paths are supported without a COP file:
Note
•
8.6(2) - 8.6(4)
•
8.6(3) - 8.6(4)
Direct upgrades to Release 8.6(4) from Release 7.x and below are not supported.
Upgrade Paths to Cisco Unified Presence Release 8.6(5)
Caution
All upgrade paths to Cisco Unified Presence Release 8.6(5) from 8.0(1) through 8.6(1) require the
installation of a COP file. The COP file delivers functionality to allow the upgrade path to be supported
as well as provides various enhancements to the user experience. If you do not install the required COP
file on each node before you begin a refresh upgrade, the upgrade will fail. The COP file is called
ciscocm.cup.refresh_upgrade_v<latest_version>.cop and it can be downloaded from cisco.com.
The following upgrade paths are supported with the required COP file and all of these upgrades are
refresh upgrades:
•
8.0(1) - 8.6(5)
•
8.0(2) - 8.6(5)
•
8.0(3) - 8.6(5)
•
8.0(4) - 8.6(5)
•
8.5(1) - 8.6(5)
•
8.5(2) - 8.6(5)
•
8.5(3) - 8.6(5)
Upgrade Guide for Cisco Unified Presence Release 8.6
2-8
Chapter 2
Before You Begin
Upgrade Paths and Requirements
•
8.5(4) - 8.6(5)
•
8.6(1) - 8.6(5)
The following upgrade paths are supported without a COP file:
Note
•
8.6(2) - 8.6(5) (refresh upgrade)
•
8.6(3) - 8.6(5) (refresh upgrade)
•
8.6(4) - 8.6(5) (standard upgrade)
Direct upgrades to Release 8.6(5) from Release 7.x and below are not supported.
Upgrade Notes
Upgrade from Cisco Unified Presence Release 7.0(x) to Release 8.6
If you upgrade from Cisco Unified Presence Release 7.0(x) to Release 8.6, note the following:
•
New software licenses—If you upgrade from Cisco Unified Presence Release 7.0(x) or Release
8.0(2), you require a new software version license for each Cisco Unified Presence cluster in your
deployment. Upload this license to the publisher node in a cluster.
•
High Availability—If you upgrade a Cisco Unified Presence Release 7.0(x) cluster that has High
Availability (HA) enabled to Release 8.6, Cisco recommends that you disable HA on each subcluster
before you begin the upgrade. You can re-enable HA on each cluster after the switch version is
complete, database replication is complete and all services are back up and running.
•
Contact list size—The default value for the maximum number of contacts is 200. However, you can
configure this to a higher value, or configure 0 to set it to unlimited value. After you perform the
upgrade, check that the contact list size for users has not reached the maximum value. If you have a
large number of contacts per user, the number of users that a Cisco Unified Presence node supports
is reduced.
•
Cluster ID—Ensure that the Cluster ID value does not contain the underscore character (_).
Cisco Unified Presence Release 8.6 does not permit this character in the Cluster ID value.
•
Cisco Unified Presence migrates contact lists for users during the upgrade. Cisco Unified Presence
synchronizes the contacts lists across SIP (via SOAP) and XMPP clients. Note the following for
upgrades from 7.0(x):
– Cisco Unified Presence does not synchronize empty groups until a contact is added to the group.
– Cisco IP Phone Messenger users must sign out and sign in to receive dynamic contact list
synchronization.
•
Federated domains—If you have federated domains that are configured using an IP address, you
must reconfigure the federated domains to use the domain name before you begin the upgrade.
Alternatively, delete the federated domains before you begin the upgrade.
Upgrade from Cisco Unified Presence Release 8.0(x) or Release 8.5 to Release 8.6
If you upgrade from Cisco Unified Presence Release 8.0(x) or Release 8.5 to Release 8.6, note the
following:
Upgrade Guide for Cisco Unified Presence Release 8.6
2-9
Chapter 2
Before You Begin
Intercluster Upgrades
•
If you have intercluster peers to Cisco Unified Presence Release 8.0(x) or Release 8.5 clusters, you
will not have intercluster availability until you upgrade all of these clusters to Release 8.6. After the
upgrade is complete, the previously configured peers will start working and intercluster availability
will be restored.
•
If you upgrade a Cisco Unified Presence Release 8.5 cluster that has High Availability (HA) enabled
to Release 8.6, Cisco recommends that you disable HA on each subcluster before you begin the
upgrade. You can re-enable HA on each cluster after the switch version is complete, database
replication is complete and all services are back up and running.
•
During a software upgrade from 8.5(x), the Cisco UP Replication Watcher service delays feature
service startup on the publisher node for up to 20 minutes and on subscriber nodes indefinitely until
replication is established.
Intercluster Upgrades
Cisco Unified Presence Release 8.6 supports intercluster peers to clusters running Release 7.0(x) and
Release 8.6 only. Intercluster peers to clusters running Release 8.0(x) or Release 8.5(x) are not
supported.
Note
Intercluster upgrades from Cisco Unified Presence Release 7.0(x) to 8.6(2) are not supported in
Cisco Unified Presence Release 8.6(4) and later.
•
Prerequisites for an Intercluster Upgrade, page 2-10
•
Roster Migration for Intercluster Upgrade, page 2-11
•
Contact List Size for Intercluster Upgrade, page 2-11
•
SIP Remote Contact Limit for Intercluster Upgrade, page 2-11
Prerequisites for an Intercluster Upgrade
Before you perform the software upgrade to Cisco Unified Presence Release 8.6, we highly recommend
that you turn off (deactivate) the Cisco UP Presence Engine service in the local Cisco Unified Presence
cluster.
If you intend to upgrade all clusters to Release 8.6, you should turn off (deactivate) the Cisco UP
Presence Engine on all clusters until you complete the intercluster upgrade in your intercluster
deployment. After you complete the upgrades in your deployment, verify that the status of the
intercluster peer connections are ok, and that there are no pending system notifications. You can then
turn on (activate) the Cisco UP Presence Engine on all nodes in all clusters. You may experience high
CPU (possibly for several hours) while the Cisco UP Presence Engine attempts to reestablish any
availability subscriptions with remote contacts.
If you intend to leave an intercluster peer on Release 7.0(x), verify that the status of the intercluster peer
connections are ok. Enable the Cisco UP XCP SIP Federation Connection Manager service before you
turn on (activate) the Cisco UP Presence Engine service, as described in the intercluster upgrade
procedure Perform an Intercluster Upgrade, page 3-11. You may experience high CPU (possibly for
several hours) while the Cisco UP Presence Engine attempts to reestablish any availability subscriptions
with remote contacts.
Upgrade Guide for Cisco Unified Presence Release 8.6
2-10
Chapter 2
Before You Begin
Intercluster Upgrades
Note
For intercluster availability to work between a Cisco Unified Presence Release 7.0(x) cluster and a
Cisco Unified Presence Release 8.6 cluster, the proxy service parameter RecordRoute must be enabled
and the Add Record-Route Header parameter must be set to On.
Roster Migration for Intercluster Upgrade
When you turn on the Cisco UP Presence Engine on the local publisher node and the remote publisher
node, Cisco Unified Presence migrates the remote contact information to the local cluster (roster
migration), and reestablishes the availability subscriptions with remote contacts in both the local and
remote cluster.
To allow Cisco Unified Presence to reestablish the availability subscriptions with remote contacts in
both the local and the remote cluster, you must reestablish the intercluster router to router connections
(by restarting the Cisco UP XCP Router) before you turn on the Cisco UP Presence Engine. Until the
roster migration is complete, local users will not see the availability status of remote contacts, and
remote contacts will not see the availability of their contacts belonging to the local cluster.
Note
Cisco Unified Presence does not automatically start the roster migration immediately after you
reestablish the intercluster router to router connections. Therefore, if you do not follow the sequence
described in Perform an Intercluster Upgrade, page 3-11, and manually turn on the Cisco UP Presence
Engine after you restart the Cisco UP XCP Router, it may take up to one day for Cisco Unified Presence
to reestablish the availability subscriptions to remote contacts in both the local and remote clusters. If
this availability subscription interval time (one day) elapses before Cisco Unified Presence has
successfully reestablished availability subscriptions, you can restart the Cisco UP Presence Engine to
reset the interval.
Contact List Size for Intercluster Upgrade
If you upgrade from Cisco Unified Presence Release 7.0(x) to Release 8.6, availability subscriptions to
remote contacts will not work for users who have reached their contact list size limit on the local or
remote cluster. The System Troubleshooter in Cisco Unified Presence Administration indicates if there
are users who have reached the contact list limit. To fix this issue, you must increase the maximum
contact list size value.
SIP Remote Contact Limit for Intercluster Upgrade
Cisco Unified Presence has a maximum limit on the number of SIP remote contacts that can be active at
one time. This maximum value changes based on platform type, see Table 2-1.
Upgrade Guide for Cisco Unified Presence Release 8.6
2-11
Chapter 2
Before You Begin
Pre-Upgrade Tasks
If you leave an intercluster peer running Release 7.0(x), you may exceed this limit depending on the
number of remote contacts on the 7.0(x) peer clusters. If you exceed the limit, Cisco Unified Presence
will not process the remaining contacts.
Table 2-1
SIP Subscription Limits
Platform
Simultaneous SIP Subscriptions
Simultaneous SIP Call-legs
MCS-7825 (100MB
pre-allocation)
45000
5000
MCS-7845 (450MB
pre-allocation)
202500
22500
You can configure the pre-allocated SIP stack memory value on Cisco Unified Presence. Select
Cisco Unified Presence Administration > System > Service Parameters > Cisco UP XCP SIP
Federation Connection Manager, and configure the Pre-allocated SIP stack memory (bytes) value.
Pre-Upgrade Tasks
Before you begin to upgrade Cisco Unified Presence software, you must perform the following tasks.
1.
Read the release notes and documentation for the new release and be sure you understand the
supported upgrades, new features, and how the upgrade interacts with the other products associated
with your system.
2.
Ensure that your Cisco Unified Presence server is operating in Production mode and that you have
obtained and uploaded the necessary license files for this upgrade.
Note
If you perform an upgrade from Cisco Unified Presence Release 7.0(x), you must obtain a
software version (upgrade) license. This also applies if you perform a bridged upgrade from
Cisco Unified Presence Release 7.0(x).
For more information about how to obtain and upload licenses to Cisco Unified Presence server, see
the Installation Guide for Cisco Unified Presence.
3.
Ensure that your hardware is supported on the version of Cisco Unified Presence software that you
are upgrading to. See the Hardware and Software Compatibility Information for
Cisco Unified Presence Release 8.0, 8.5 and 8.6 for more information.
4.
After you upload the new license files, you must issue the following CLI command to remove the
original license files and restart the license manager to stop the grace period.
file delete license invalid-license-filename
Note
5.
You can only use the CLI command file delete license to remove the license files that become
invalid due to the publisher re-host. Do not use this command to manually remove any license
files that are still considered valid.
Disable High-Availability on the Cisco Unified Presence subcluster. Select Cisco Unified Presence
Administration > System > Cluster Topology.
For more information, see the Deployment Guide for Cisco Unified Presence.
6.
Back up your system.
Upgrade Guide for Cisco Unified Presence Release 8.6
2-12
Chapter 2
Before You Begin
Pre-Upgrade Tasks
For more information, see the Disaster Recovery System Administration Guide for
Cisco Unified Presence.
Note
If you have to upgrade Cisco Unified Communications Manager as part of your Cisco Unified Presence
upgrade, note the following:
•
You must stop and restart Cisco Unified Presence Sync Agent service. To restart the Sync Agent
service, navigate to Cisco Unified Serviceability and select Tools > Control Center - Network
Services.
•
You must configure a SIP PUBLISH trunk on Cisco Unified Communications Manager to
communicate with Cisco Unified Presence. For more information, see the Deployment Guide for
Cisco Unified Presence.
Upgrade Guide for Cisco Unified Presence Release 8.6
2-13
Chapter 2
Pre-Upgrade Tasks
Upgrade Guide for Cisco Unified Presence Release 8.6
2-14
Before You Begin
CH A P T E R
3
Upgrade Procedures
•
Multi-node Software Upgrade Procedures, page 3-1
•
Upgrade Software Procedures, page 3-5
•
Switch Cisco Unified Presence Software Version, page 3-9
•
Perform an Intercluster Upgrade, page 3-11
Caution
Do not make any changes to Cisco Unified Presence configuration during an upgrade. If data is written
to the database during the upgrade, the upgrade may fail.
Note
If you cancel an upgrade at any stage, or if an upgrade fails, you must reboot the Cisco Unified Presence
server before you attempt another upgrade.
Multi-node Software Upgrade Procedures
This section describes the high-level procedure for performing a standard upgrade and a refresh upgrade
in a multi-node deployment.
Upgrade Guide for Cisco Unified Presence Release 8.6
3-1
Chapter 3
Upgrade Procedures
Multi-node Software Upgrade Procedures
Standard Upgrades
Figure 3-1
Multi-node Software Upgrade Flowchart - Standard Upgrade
Perform pre-upgrade
tasks
Switch version on each
subscriber node
Upgrade publisher node do not switch version
Check the database
replication
Upgrade each
subscriber node do not switch version
Ensure that the
Presence Engine
has restarted
Switch version
on publisher node
Request that all client users
sign out and sign back in
End
Caution
209566
Multi-node software
upgrade - standard upgrade
If you perform an upgrade from Cisco Unified Presence Release 7.0(x) to Release 8.6 on one, or both,
of the clusters in an intercluster deployment, you must follow the recommended upgrade procedure in
Perform an Intercluster Upgrade, page 3-11.
Restrictions
Your hardware must comply with the multi-node hardware recommendations. See the Deployment Guide
for Cisco Unified Presence for more information.
Before You Begin
Disable High Availability for Cisco Unified Presence nodes that are configured for redundancy. See the
Deployment Guide for Cisco Unified Presence for more information.
Procedure
Step 1
Perform pre-upgrade tasks. See Pre-Upgrade Tasks, page 2-12.
Step 2
Upgrade the publisher node. Do not switch the software to the new software release at this point.
Step 3
Upgrade each subscriber node in the cluster. Again, do not switch the software version to the new
software release at this point.
Upgrade Guide for Cisco Unified Presence Release 8.6
3-2
Chapter 3
Upgrade Procedures
Multi-node Software Upgrade Procedures
Step 4
Switch the software to the new software release on the publisher node. Wait until the publisher node has
successfully restarted (is at the sign in prompt) before you proceed to the next step.
Step 5
On the subscriber nodes, switch the software to the new software release.
Step 6
Once the first subscriber has restarted and has come back online with the new software release, switch
the software release on the next subscriber node. Wait until each subscriber node has successfully
restarted (is at the sign in prompt) before you proceed with the software switch on the next subscriber
node.
Step 7
Repeat Step 5 until the new software release is running on all subscriber nodes.
Step 8
Run the following CLI command (on the publisher or subscriber node) to check if the database
replication is active on a node:
utils dbreplication runtimestate
If database replication is active on all nodes, the output lists all the nodes and the replication setup value
for each node is 2.
Note
If database replication is not complete (a value other than 2 is returned), core services will not
start on the subscriber node until replication is complete. Select Cisco Unified Presence
Administration > System > Notifications to determine whether database replication is
complete.
Step 9
On each subscriber node, restart the Presence Engine service after the database replication becomes
active on the node.
Step 10
Request that all Cisco Unified Presence client users in the local and remote cluster sign out, and sign
back in to the application.
Troubleshooting Tips
Check that the contact list size for users has not reached the maximum value. The System Troubleshooter
in Cisco Unified Presence Administration indicates if there are users who have reached the contact list
limit.
Refresh Upgrades
This section describes the high-level procedure to perform a refresh upgrade in a multi-node deployment.
Upgrade Guide for Cisco Unified Presence Release 8.6
3-3
Chapter 3
Upgrade Procedures
Multi-node Software Upgrade Procedures
Figure 3-2
Multi-node Software Upgrade Flowchart - Refresh Upgrade
Multi-node software
upgrade - refresh upgrade
On VM platform only,
modify Guest
Operating System
Install the COP file on all
nodes
Check database
replication
Upgrade publisher node
- switch to new software
Ensure that the
Presence Engine has
restarted
On VM platform only,
modify Guest
Operating System
Request that all client users
sign out and sign back in
Upgrade each subscriber
node - switch to
new software
End
284957
Perform pre-upgrade tasks
Restrictions
Your hardware must comply with the multi-node hardware recommendations. See the Deployment Guide
for Cisco Unified Presence for more information.
Procedure
Step 1
Perform pre-upgrade tasks. See Pre-Upgrade Tasks, page 2-12.
Step 2
Install the following COP file on each Cisco Unified Presence node:
ciscocm.cup.refresh_upgrade_v<latest_version>.cop
Step 3
Upgrade the publisher node and switch the software to the new software release. To do this, select
Switch to new version after upgrade.
Step 4
On VM platforms only, modify the Guest Operating System on the publisher node to Red-Hat Enterprise
Linux 5 (32-bit). See Upgrading to Cisco Unified Presence Release 8.6(4) and later on a Virtual Server,
page 3-8.
Step 5
Upgrade each subscriber node in the cluster and switch to the new software release by selecting Switch
to new version after upgrade.
Note
Step 6
The publisher node must be running the new software before you upgrade each subscriber node.
On VM platforms only, modify the Guest Operating System on the each subscriber node to Red-Hat
Enterprise Linux 5 (32-bit). See Upgrading to Cisco Unified Presence Release 8.6(4) and later on a
Virtual Server, page 3-8.
Upgrade Guide for Cisco Unified Presence Release 8.6
3-4
Chapter 3
Upgrade Procedures
Upgrade Software Procedures
Step 7
Run the following CLI command (on the publisher or subscriber node) to check if the database
replication is active on a node:
utils dbreplication runtimestate
If database replication is active on all nodes, the output lists all the nodes and the replication setup value
for each node is 2.
Note
If database replication is not complete (a value other than 2 is returned), core services will not
start on the subscriber node until replication is complete. Select Cisco Unified Presence
Administration > System > Notifications to determine whether database replication is
complete.
Step 8
On each subscriber node, restart the Presence Engine service after the database replication becomes
active on the node.
Step 9
Request that all Cisco Unified Presence client users in the local and remote cluster sign out, and sign
back in to the application.
Troubleshooting Tips
Check that the contact list size for users has not reached the maximum value. The System Troubleshooter
in Cisco Unified Presence Administration indicates if there are users who have reached the contact list
limit.
Upgrade Software Procedures
You can access the upgrade file during the installation process from either a local CD or DVD or from a
remote FTP or SFTP server. Be aware that directory names and filenames that you enter to access the
upgrade file are case-sensitive.
Note
•
Upgrade from Local Source, page 3-5
•
Upgrade from Remote Source, page 3-7
•
Upgrading to Cisco Unified Presence Release 8.6(4) and later on a Virtual Server, page 3-8
If you cancel an upgrade at any stage, or if an upgrade fails, you must reboot the Cisco Unified Presence
server before you attempt another upgrade.
Upgrade from Local Source
You can upgrade Cisco Unified Presence using software from a CD or DVD in the local disc drive.
Before You Begin
•
Obtain the upgrade file from cisco.com. Copy the upgrade file to a writable CD or DVD. Because
of their size, some upgrade files may not fit on a CD and require a DVD.
•
Review the software upgrade process and ensure that you have completed the prerequisite system
backup procedures. Cisco highly recommends that you perform a backup of the Disaster Recovery
System (DRS).
Upgrade Guide for Cisco Unified Presence Release 8.6
3-5
Chapter 3
Upgrade Procedures
Upgrade Software Procedures
•
Stop all configuration tasks.
•
Perform data migration on MCS-7825-H3 or MCS-7828-H3 servers using a 16GB USB Flash Drive.
Do not remove the USB key until the data migration is complete.
Note
During a refresh upgrade on either the MCS-7825-H3 or MCS-7828-H3 platform, the hard drive needs
to be formatted; it will not be possible to switch back to the older version of Cisco Unified Presence after
the refresh upgrade has been started. As a result, Cisco highly recommends that you perform a DRS
backup.
Tip
During a refresh upgrade, traffic is no longer processed and several reboots are required, therefore, you
must perform a refresh upgrade during a maintenance window.
Note
•
Do not rename the upgrade file before you install it because the system will not recognize it as a
valid file.
•
Do not decompress the file. If you do, the system may not be able to read the upgrade file.
Procedure
Step 1
Insert the CD or DVD into the disc drive on the local server that is to be upgraded.
Step 2
Sign in to Cisco Unified Operating System Administration.
Step 3
If you are upgrading to Cisco Unified Presence Release 8.6(4) or later from 8.0(1) through 8.6(1), install
the required COP file, ciscocm.cup.refresh_upgrade_v<latest_version>.cop.
Step 4
Select Software Upgrades > Install/Upgrade.
Step 5
Select DVD/CD from the Source list.
Step 6
In the Directory field, enter the path to the patch file on the CD or DVD. If the file is in the root directory,
enter a slash (/).
Step 7
Enter your email address and IP address in the Email Notification and SMTP Server fields.
This will enable you to receive an email notification upon successful completion of the upgrade.
Note
These fields are only visible if you are upgrading to Cisco Unified Presence Release 8.6(4) or later.
Step 8
Select Next to continue the upgrade process.
Step 9
Select the upgrade version that you want to install and select Next.
Step 10
Monitor the progress of the download, which includes the filename and the number of megabytes that
are being transferred.
Step 11
When the download completes, verify the checksum value against the checksum for the file that you
downloaded from Cisco.com.
Step 12
Perform one of the following actions:
For standard upgrades:
Upgrade Guide for Cisco Unified Presence Release 8.6
3-6
Chapter 3
Upgrade Procedures
Upgrade Software Procedures
•
If this is a single-node deployment and you want to install the upgrade and automatically reboot to
the upgraded software, select Reboot to upgraded partition.
•
If this is a multi-node deployment, select Do not reboot after upgrade. This allows you to install
the upgrade and then manually reboot to the upgraded software at a later time. For more information
about how to manually reboot the system and activate the upgrade, see Switch
Cisco Unified Presence Software Version, page 3-9.
For refresh upgrades:
Step 13
•
Select Do not switch to new version after upgrade only if you are performing a staged upgrade.
•
Select Switch to new version after upgrade to remain on the new active software version.
Select Next and select Finish when the installation completes.
Upgrade from Remote Source
You can upgrade Cisco Unified Presence using software from a network drive or remote server. The
network drive or remote server must be running a SFTP/FTP server that can be accessed by each
Cisco Unified Presence server that you want to upgrade.
Before You Begin
Tip
•
Review the software upgrade process and ensure that you have completed the prerequisite system
backup procedures. Cisco highly recommends that you perform a backup of the Disaster Recovery
System (DRS).
•
Stop all configuration tasks.
•
Perform data migration on MCS-7825-H3 or MCS-7828-H3 servers using a 16GB USB Flash Drive.
Do not remove the USB key until the data migration is complete.
Several reboots will occur during a refresh upgrade, therefore, Cisco highly recommends that you
perform a refresh upgrade during off-peak hours.
Procedure
Step 1
Sign in to Cisco Unified Operating System Administration.
Step 2
If you are upgrading to Cisco Unified Presence Release 8.6(4) or later from 8.0(1) through 8.6(1), place
the required COP file on an FTP or SFTP server that is accessible from Cisco Unified Presence server
and install the COP file, ciscocm.cup.refresh_upgrade_v<latest_version>.cop.
Step 3
Select Software Upgrades > Install/Upgrade.
Step 4
Select Remote Filesystem from the Source list.
Step 5
In the Directory field, enter the path to the patch file on the remote system.
Step 6
In the Server field, enter the FTP or SFTP server name.
Step 7
In the User Name field, enter the user name for the remote server.
Step 8
In the User Password field, enter the password for the remote server.
Step 9
Enter your email address and IP address in the Email Notification and SMTP Server fields.
This will enable you to receive an email notification upon successful completion o f the upgrade.
Upgrade Guide for Cisco Unified Presence Release 8.6
3-7
Chapter 3
Upgrade Procedures
Upgrade Software Procedures
Note
These fields are only visible if you are upgrading to Cisco Unified Presence Release 8.6(4) or later.
Step 10
From the Transfer Protocol field, select the transfer protocol, for example, SFTP.
Step 11
Select Next to continue the upgrade process.
Step 12
Select the upgrade version that you want to install and select Next.
Step 13
Monitor the progress of the download, which includes the filename and the number of megabytes that
are getting transferred.
Step 14
When the download completes, verify the checksum value against the checksum for the file that you
downloaded from Cisco.com.
Step 15
Perform one of the following actions:
For standard upgrades:
•
If this is a single-node deployment and you want to install the upgrade and automatically reboot to
the upgraded software, select Reboot to upgraded partition.
•
If this is a multi-node deployment, select Do not reboot after upgrade. This allows you to install
the upgrade and then manually reboot to the upgraded software at a later time. For more information
about how to manually reboot the system and activate the upgrade, see Switch
Cisco Unified Presence Software Version, page 3-9.
For refresh upgrades:
Step 16
•
Select Do not switch to new version after upgrade only if you are performing a staged upgrade.
•
Select Switch to new version after upgrade to remain on the new active software version.
Select Next and select Finish when the installation completes.
Upgrading to Cisco Unified Presence Release 8.6(4) and later on a Virtual
Server
You can upgrade to Cisco Unified Presence Release 8.6(4) and later on a virtual server.
Procedure
Step 1
Upgrade the virtual machine to the latest release. For information about installing or upgrading Cisco
Unified Presence on a virtual server, see
http://docwiki.cisco.com/wiki/Implementing_Virtualization_Deployments
Step 2
After you finish the upgrade, shut down the virtual machine.
Step 3
Change the Guest Operating System to Red-Hat Enterprise Linux 5 (32-bit).
Step 4
Compare the Virtual Machine settings on each node to be upgraded with the OVA template for the target
upgrade release and the number of users for the node. In particular, compare the following settings:
•
number of CPUs
•
reserved CPU MHz
•
RAM size
Upgrade Guide for Cisco Unified Presence Release 8.6
3-8
Chapter 3
Upgrade Procedures
Switch Cisco Unified Presence Software Version
•
RAM reservation
•
number and size of hard disk
See the Virtualization Docwiki for more information about OVA template details:
http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_O
VA/OVF_Templates%29#Cisco_Unified_Presence.
Step 5
Save the changes.
Step 6
Restart the virtual machine.
Switch Cisco Unified Presence Software Version
Caution
This procedure causes the system to restart and become temporarily out of service.
When you upgrade Cisco Unified Presence, the new software is installed as an inactive version. You can
reboot to the new software version during the upgrade process or you can switch to the new version later.
When you switch versions, the system restarts, and the inactive software becomes active. The system
restart may take up to 15 minutes. When you perform this procedure both the active and inactive software
versions are indicated.
Note
If you switch versions in a multi-node deployment, you must switch the publisher node first. It may take
some time for all the services on the Cisco Unified Presence nodes to move to the Started state. Select
Cisco Unified Presence Administration > System > Cluster Topology and select a node from the tree
view to monitor the status of the services on the node.
Procedure
Step 1
Sign in to Cisco Unified Operating System Administration.
Step 2
Select Settings > Version.
Step 3
Verify the version of the active software and the inactive software.
Step 4
Select Switch Versions to switch versions and restart the system.
Revert to the Previous Software Version
Caution
This procedure causes the system to restart and become temporarily out of service.
After you upgrade and reboot Cisco Unified Presence to a new software version, the earlier software
version remains inactive on the system. If you need to revert to the earlier software version, you can
switch versions.
Upgrade Guide for Cisco Unified Presence Release 8.6
3-9
Chapter 3
Upgrade Procedures
Switch Cisco Unified Presence Software Version
Caution
Note
You can not revert to the earlier software version on an MCS-7825-H3 or MCS-7828-H3 server. The
entire disk has been reformatted and old install and data has been erased.
Any changes you made to the database after an upgrade will be lost if you revert to the earlier software
version. Therefore, if you make changes to the database after an upgrade, you must repeat those changes
after you switch back to the earlier software version.
Procedure
Step 1
Sign in to Cisco Unified Operating System Administration.
Step 2
Select Settings > Version.
Step 3
Verify the version of the active and inactive software.
Step 4
Select Switch Versions to switch versions and restart the system.
Switch Versions from Cisco Unified Presence Release 8.6(4) or Later
Cisco Unified Presence Release 8.6(4) and later does not support the Cisco UP Presence Engine
database. If you upgrade to Cisco Unified Presence Release 8.6(4) or later from Release 8.6(3) or earlier
and you subsequently want to revert to the previous release, you must install a COP file that will reinstall
the Cisco UP Presence Engine database. The COP filename is ciscocm.cup.pe_db_install.cop
and you can download it from Cisco.com.
Note
In a multi-node environment, you must install the COP file on every node in the cluster after you switch
versions from Cisco Unified Presence Release 8.6(4) or later.
The COP file can only be installed on the following versions of Cisco Unified Presence after a
downgrade from Cisco Unified Presence Release 8.6(4) or later:
•
8.0(1)
•
8.0(2)
•
8.0(3)
•
8.0(4)
•
8.5(1)
•
8.5(2)
•
8.5(3)
•
8.5(4)
•
8.6(1)
•
8.6(2)
•
8.6(3)
Upgrade Guide for Cisco Unified Presence Release 8.6
3-10
Chapter 3
Upgrade Procedures
Perform an Intercluster Upgrade
Note
You must restart the system after you install the COP file.
Procedure
Step 1
Download the following COP file from Cisco.com: ciscocm.cup.pe_db_install.cop
Step 2
Sign in to Cisco Unified Operating System Administration.
Step 3
Select Settings > Version.
Step 4
Verify the version of the active and inactive software.
Note
This procedure only applies if you want to switch from Release 8.6(4) or later back to a release
earlier than 8.6(4).
Step 5
Select Switch Versions to switch from Cisco Unified Presence Release 8.6(4) or later and restart the
system.
Step 6
After the system has restarted, install the COP file.
Note
In a multi-node environment, you must install the COP file on every node in the cluster.
Step 7
After you have installed the COP file, manually restart the system. To do this, select Settings > Version
and select Restart.
Step 8
Run the following CLI command (on the publisher or subscriber node) to check if the database
replication is active on the node:
utils dbreplication runtimestate
If database replication is active on all nodes, the output lists all the nodes and the replication setup value
for each node is 2. If database replication is not complete (a value other than 2 is returned), core services
will not start on the subscriber node until replication is complete.
Step 9
Select Cisco Unified Presence Administration > System > Notifications to determine whether
database replication is complete.
Step 10
If database replication cannot be established, use the following CLI command on the publisher node to
reset replication:
utils dbreplication reset all
Perform an Intercluster Upgrade
Note
Cisco Unified Presence Release 8.6 supports intercluster peers to clusters running Release 7.0(x) and
Release 8.6 only. Intercluster peers to clusters running Release 8.0(x) or Release 8.5(x) are not
supported.
Upgrade Guide for Cisco Unified Presence Release 8.6
3-11
Chapter 3
Upgrade Procedures
Perform an Intercluster Upgrade
This section describes the high-level procedure to perform an intercluster upgrade from
Cisco Unified Presence Release 7.0(x) to Release 8.6.
Note
Intercluster upgrades from Cisco Unified Presence Release 7.0(x) to 8.6(2) are not supported in
Cisco Unified Presence Release 8.6(4) or later.
For information about the following tasks in this procedure, see the Deployment Guide for
Cisco Unified Presence:
•
Restart the Cisco UP XCP Router Service
•
Verify the Intercluster Peer Status
•
Update Intercluster Sync Agent Tomcat Trust Certificates
•
Turn On the Cisco Unified Presence Services
Before You Begin
Turn off the Cisco UP Presence Engine on all nodes in the local cluster.
Procedure
Step 1
Perform the software upgrade in the local cluster.
Step 2
Select Cisco Unified Presence Administration > Presence > Inter-Clustering to check the status of
the intercluster peer connection. If the tomcat certificate is out-of-sync, you must manually update the
tomcat trust certificate.
Step 3
On each node in the upgraded cluster, turn on the XCP services that are applicable to your deployment.
Step 4
Check the following:
•
Check the status of the intercluster peer connection again. If the intercluster peer status is ok, move
to the next step.
•
Select Cisco Unified Presence > System > Notifications and verify that there are no active
notifications. If there are no active notifications, move to the next step.
Step 5
If the remote cluster has an intercluster peer connection with a Cisco Unified Presence Release 7.0(x)
cluster, or the remote cluster is running interdomain federation over SIP, restart the Cisco UP XCP SIP
Federation Connection Manager service on all nodes in the remote cluster that you have already
upgraded to Cisco Unified Presence Release 8.6. If the remote cluster does not have an intercluster peer
connection with a 7.0(x) cluster, or is not running interdomain federation over SIP, turn off the Cisco UP
XCP SIP Federation Connection Manager.
Step 6
If the local cluster that you upgrade to Cisco Unified Presence Release 8.6 has an intercluster peer
connection with a remote Cisco Unified Presence Release 7.0(x) cluster, you must turn on the Cisco UP
XCP SIP Federation Connection Manager service on all nodes in the local cluster.
Note
Step 7
If, following this upgrade, all peer clusters in your intercluster deployment are running
Cisco Unified Presence Release 8.6, and no clusters are running interdomain federation over
SIP, you can turn off the Cisco UP XCP SIP Federation Connection Manager service on all
clusters.
Turn on the Cisco UP Presence Engine on all nodes in the local cluster,
Upgrade Guide for Cisco Unified Presence Release 8.6
3-12
Chapter 3
Upgrade Procedures
Perform an Intercluster Upgrade
Step 8
Turn on the Cisco UP Presence Engine on all nodes in any remote cluster that you have already upgraded
to Cisco Unified Presence Release 8.6 prior to this upgrade.
Step 9
Verify that the roster migration is complete, see Verify that the Roster Migration is Complete on
Cisco Unified Presence, page 3-13.
Step 10
Request that all Cisco Unified Presence client users in the local and remote cluster sign out, and sign
back in to the application.
Troubleshooting Tip
The Presence Viewer does not display watchers from a Cisco Unified Presence Release 7.x cluster.
Clusters that are running Cisco Unified Presence Release 8.6 show watchers across all clusters.
Verify that the Roster Migration is Complete on Cisco Unified Presence
Note
This procedure only applies to intercluster upgrades from Release 7.x to 8.x.
After you perform the intercluster upgrade, the roster migration process continues on
Cisco Unified Presence for the remote users. However, note that roster migration is a CPU intensive
process, and a process that takes a significant time to complete. The completion time is dependent on the
size of the remote contact and rosters table in your deployment.
Use this procedure to verify that the roster migration is complete and the system is ready.
Before You Begin
Complete the following procedures:
•
Perform the upgrade
•
Switch Cisco Unified Presence software versions
•
Complete the required configuration on Cisco Unified Presence (licensing, feature configuration
and start the required services)
Procedure
Step 1
Run this CLI command on all nodes in the Cisco Unified Presence 8.6 local cluster and all nodes in the
Cisco Unified Presence 8.6 remote clusters:
run sql select count(*) from rosterupgradequeue
Step 2
Check the rosterupgradequeue table:
•
Empty—If the rosterupgradequeue table for all of the local or remote clusters is empty, the roster
migration is complete.
•
Not empty—If the rosterupgradequeue table for any of the local or remote clusters is not empty, the
roster migration is not complete yet. See Troubleshoot Roster Migration, page 3-14.
Upgrade Guide for Cisco Unified Presence Release 8.6
3-13
Chapter 3
Upgrade Procedures
Perform an Intercluster Upgrade
Troubleshooting Tips
If you switch the software version from Cisco Unified Presence Release 8.6 back to
Cisco Unified Presence Release 7.0(x) on the local cluster, make sure that the rosterupgradequeue table
is empty on all nodes in the remote 8.6 clusters before you perform an upgrade in the local cluster again.
Troubleshoot Roster Migration
If the rosterupgradequeue is not empty after an upgrade and the entry on rosterupgradequeue has not
decreased over time, perform the following procedure to empty the rosterupgradequeue table.
Procedure
Step 1
Check the following on the publisher node in both the local and remote Cisco Unified Presence 8.6
clusters:
•
maximum contact list size is set to zero
•
system notifications
•
the correct license file is present
•
the required services are running, and if they are not, perform these steps:
– Restart the Cisco UP Intercluster Sync Agent on all nodes in the Cisco Unified Presence 8.6
local cluster and all nodes in the Cisco Unified Presence 8.6 remote clusters.
– On the local publisher node, restart the Cisco UP Config Agent service.
Step 2
Restart the Cisco UP XCP Router service on all local Cisco Unified Presence nodes and on all remote
Cisco Unified Presence nodes.
Step 3
Restart the Cisco UP Presence Engine service on all local Cisco Unified Presence nodes and on all
remote Cisco Unified Presence nodes.
Step 4
Restart the Cisco UP XCP SIP Federation Connection Manager service on all remote 8.6
Cisco Unified Presence clusters.
Step 5
Verify that the roster migration is complete, see Verify that the Roster Migration is Complete on
Cisco Unified Presence, page 3-13.
Step 6
Repeat this procedure until the rosterupgradequeue tables are empty on all nodes in the local
Cisco Unified Presence cluster and remote Cisco Unified Presence clusters.
Upgrade Guide for Cisco Unified Presence Release 8.6
3-14
CH A P T E R
4
Post Upgrade Tasks
•
High Availability, page 4-1
High Availability
If your deployment supports high-availability, you must turn high-availability back on in each subcluster.
Do this after you switch versions, finish the database replication and restart all services. For information
about how to turn on high-availability, see the Deployment Guide for Cisco Unified Presence.
Upgrade Guide for Cisco Unified Presence Release 8.6
4-1
Chapter 4
High Availability
Upgrade Guide for Cisco Unified Presence Release 8.6
4-2
Post Upgrade Tasks
CH A P T E R
5
Troubleshooting
•
Cisco Unified Presence User Phone Presence Problems, page 5-1
•
Cisco Unified Presence User Experiences Issues Obtaining Presence Availability, page 5-2
•
Real-Time Monitoring Tool Alert for the Cisco UP SIP Proxy Service, page 5-2
•
Cannot Find Upgrade File on Remote Server, page 5-2
•
Upgrade File Checksum Values do not Match, page 5-2
•
Database Replication Did Not Complete, page 5-3
•
Cisco UP Presence Engine Database Does Not Restart, page 5-3
•
Refresh Upgrade Error, page 5-3
•
Failed Refresh Upgrade, page 5-3
•
Upgrade from Pre Release 8.6(4) Fails, page 5-4
•
Cancelled or Failed Upgrade, page 5-4
•
Upgrading Release 8.5, page 5-4
Cisco Unified Presence User Phone Presence Problems
Problem After a Cisco Unified Presence server upgrade, when all activated feature services and network
services are started, Cisco Unified Presence phone availability from users is delayed or slow to update.
Solution You must restart the Cisco UP SIP Proxy service. In Cisco Unified Serviceability, select Tools
> Control Center - Features Services.
Upgrade Guide for Cisco Unified Presence Release 8.6
5-1
Chapter 5
Troubleshooting
Cisco Unified Presence User Experiences Issues Obtaining Presence Availability
Cisco Unified Presence User Experiences Issues Obtaining
Presence Availability
Problem After a Cisco Unified Presence server upgrade, when all activated feature services and network
services are started, a Cisco Unified Presence user experiences inconsistent availability. The user can log
in to Cisco Unified Presence but experiences issues obtaining availability information mainly from
SIP-based clients.
Solution This issue is caused when users are provisioned while Cisco Unified Presence is being
upgraded. You must unassign and then reassign the user.
Real-Time Monitoring Tool Alert for the Cisco UP SIP Proxy
Service
Problem After a Cisco Unified Presence server upgrade, when all activated feature services and network
services are started, a Real-Time Monitoring Tool CoreDumpFileFound alert was generated for the Cisco
UP SIP Proxy service.
Solution You must restart the Cisco UP SIP Proxy service. In Cisco Unified Serviceability, select Tools
> Control Center - Features Services.
Cannot Find Upgrade File on Remote Server
Problem You cannot find the upgrade file on the remote server.
Solution If the upgrade file is located on a Linux or Unix server, you must enter a forward slash at the
beginning of the directory path that you want to specify. For example, if the upgrade file is in the patches
directory, you must enter /patches. If the upgrade file is located on a Windows server, check with your
system administrator for the correct directory path.
Upgrade File Checksum Values do not Match
Problem The checksum value of the upgrade file does not match the checksum indicated on Cisco.com.
Solution The two checksum values must match to ensure the authenticity and integrity of the upgrade
file. If the checksum values do not match, download a fresh version of the file from Cisco.com and try
the upgrade again.
Upgrade Guide for Cisco Unified Presence Release 8.6
5-2
Chapter 5
Troubleshooting
Database Replication Did Not Complete
Database Replication Did Not Complete
Problem After an upgrade, database replication did not complete and the result of the command utils
dbreplication runtimestate
was not 2.
Solution After a successful upgrade and switch version to the new software, database replication should
take place automatically. During this time core services on the subscriber nodes will not start. Database
replication in large deployments can take several hours to complete. If, after several hours, the utils
dbreplication runtimestate command shows that database replication did not complete, you need to
reset the database replication. Run the following command on the publisher node:
utils dbreplication reset all
Cisco UP Presence Engine Database Does Not Restart
Problem After you switch back from Cisco Unified Presence Release 8.6(4) or later to an earlier
software version, the Cisco UP Presence Engine database does not restart.
Solution Ensure that you installed the required COP file, ciscocm.cup.pe_db_install.cop, on
every node in the cluster after you switched back from Cisco Unified Presence Release 8.6(4) or later.
Refresh Upgrade Error
Problem During a refresh upgrade, the following error is reported: Error encountered: The selected
upgrade is disallowed from the current version.
Solution You did not install the required COP file on the node. Download the following COP file from
Cisco.com: ciscocm.cup.refresh_upgrade_v<latest_version>.cop. Restart the server. Install the COP
file on every node in the cluster before you attempt the refresh upgrade again.
Failed Refresh Upgrade
Problem A refresh upgrade failed.
Solution Restart the system, it should reboot to the software version that was running before you
attempted the refresh upgrade. If you cannot access the system, you must use the Recovery CD to recover
the node.
Upgrade Guide for Cisco Unified Presence Release 8.6
5-3
Chapter 5
Troubleshooting
Upgrade from Pre Release 8.6(4) Fails
Upgrade from Pre Release 8.6(4) Fails
Problem You are upgrading from a release earlier than Cisco Unified Presence 8.6(4) and the upgrade
fails on both the publisher and subscriber nodes.
Solution The Cisco Unified Communications Manager hostname is case-sensitive. You must ensure that
the entry for the Cisco Unified Communications Manager publisher node on the Cisco Unified Presence
Administration interface matches exactly the Cisco Unified Communications Manager hostname.
Complete the following procedure:
1.
Log into Cisco Unified Presence Administration interface and choose System > CUCM
Publisher.
2.
If the CUCM Publisher Hostname value does not match the hostname, modify it and click Save.
3.
Restart the Cluster Manager service with the following CLI command: utils service restart Cluster
Manager
4.
Open the platformConfig.xml file at the following location: /usr/local/platform/conf/
5.
Verify that the values for IPSecMasterHost and NTPServerHost match exactly the Cisco Unified
Communications Manager hostname.
6.
If necessary, modify the values for IPSecMasterHost and NTPServerHost, save the
platformConfig.xml file and restart the Cluster Manager service again.
Cancelled or Failed Upgrade
If you cancel an upgrade at any stage, or if an upgrade fails, you must reboot the Cisco Unified Presence
server before you attempt another upgrade.
Upgrading Release 8.5
When upgrading Cisco Unified Communications Manager, Release 8.5, note that the Cisco Unified Communications Manager hostname is case sensitive.
After you have upgraded from Release 8.5, ensure that the entry for the Cisco Unified Communications Manager publisher node in the Cisco Unified Presence Administration > System > CUCM Publisher window, matches the case of the Cisco Unified Communications Manager’s hostname. If not, modify the entry and restart the Cluster Manager service using the command: service clm restart
On Cisco Unified Presence, confirm that the entry for IPSecMasterHost in the /usr/local/platform/conf/platformConfig.xml file, matches the case of the Cisco Unified Communications Manager hostname. If a change is required, manually update this file and restart the Cluster Manager service.
Upgrade Guide for Cisco Unified Presence Release 8.6
5-4
CH A P T E R
6
Reference
•
Effects of I/O Throttling, page 6-1
•
Locale Specific Upgrades, page 6-4
Effects of I/O Throttling
•
Overview, page 6-1
•
Disable Throttling, page 6-1
•
Server Models, page 6-1
•
Write-Cache, page 6-2
Overview
This section describes how throttling affects the upgrade process, identifies possible causes of slow or
stalled upgrades, and provides actions you can take to speed up the upgrade.
Throttling may cause the upgrade to take longer. Throttling is enabled by default and is necessary if you
perform the upgrade during normal business hours.
Disable Throttling
To disable throttling, use the following command in the CLI before you start the upgrade:
utils iothrottle disable
Note
If you want to restart throttling after you start the upgrade, you must cancel the upgrade, restart
throttling, and then restart the upgrade.
Server Models
The Server model you have also impacts the upgrade speed. Upgrades on servers that have SATA hard
drives, such as MCS-7816 and MCS-7825, take longer than servers with SAS/SCSI hard drives, such as
MCS-7835 and MCS-7845.
Upgrade Guide for Cisco Unified Presence Release 8.6
6-1
Chapter 6
Reference
Effects of I/O Throttling
Write-Cache
A disabled write-cache on the server also causes the upgrade process to run more slowly. Multiple factors
can cause the write-cache to become disabled, including dead batteries on older servers.
Before starting an upgrade, verify the status of the write-cache on the MCS-7835/45 disk controllers.
You do not need to verify the write-cache status on the MCS-7816, MCS-7825 servers. To verify
write-cache status, access the Cisco Unified Operating System Administration, and select Show >
Hardware.
If you determine that your write-cache is disabled because of a dead battery, you need to replace the hard
disk controller cache battery. Follow your local support procedures to get this battery replaced.
See the following examples of output from the Show > Hardware menu for details on determining the
battery and write-back cache status.
In the following example write-cache is enabled. The example indicates that 50 percent of the cache is
reserved for write and 50 percent of the cache is reserved for read. If the write-cache was disabled, 100
percent of the cache would be reserved for read or the Cache Status would not equal “OK”. Also, the
battery count equals “1”. If the controller battery was dead or missing, it would indicate “0”.
Example 6-1
7835/45-H1 and 7835/45-H2 Servers with Write-Cache Enabled
------------------------------RAID Details
:
Smart Array 6i in Slot 0
Bus Interface: PCI
Slot: 0
Cache Serial Number: P75B20C9SR642P
RAID 6 (ADG) Status: Disabled
Controller Status: OK
Chassis Slot:
Hardware Revision: Rev B
Firmware Version: 2.80
Rebuild Priority: Low
Expand Priority: Low
Surface Scan Delay: 15 sec
Cache Board Present: True
Cache Status: OK
Accelerator Ratio: 50% Read / 50% Write
Total Cache Size: 192 MB
Battery Pack Count: 1
Battery Status: OK
SATA NCQ Supported: False
The following example indicates that the battery status is enabled and that the write-cache mode is
enabled.
Example 6-2
7835/45-I2 Servers with Write-Cache Enabled
---------RAID Details
:
Controllers found: 1
---------------------------------------------------------------------Controller information
---------------------------------------------------------------------Controller Status
: Okay
Channel description
: SAS/SATA
Upgrade Guide for Cisco Unified Presence Release 8.6
6-2
Chapter 6
Reference
Effects of I/O Throttling
Controller Model
: IBM ServeRAID 8k
Controller Serial Number
: 20ee0001
Physical Slot
: 0
Copyback
: Disabled
Data scrubbing
: Enabled
Defunct disk drive count
: 0
Logical drives/Offline/Critical
: 2/0/0
--------------------------------------------------Controller Version Information
--------------------------------------------------BIOS
: 5.2-0 (15421)
Firmware
: 5.2-0 (15421)
Driver
: 1.1-5 (2412)
Boot Flash
: 5.1-0 (15421)
--------------------------------------------------Controller Battery Information
--------------------------------------------------Status
: Okay
Over temperature
: No
Capacity remaining
: 100 percent
Time remaining (at current draw)
: 4 days, 18 hours, 40 minutes
--------------------------------------------------Controller Vital Product Data
--------------------------------------------------VPD Assigned#
: 25R8075
EC Version#
: J85096
Controller FRU#
: 25R8076
Battery FRU#
: 25R8088
---------------------------------------------------------------------Logical drive information
---------------------------------------------------------------------Logical drive number 1
Logical drive name
: Logical Drive 1
RAID level
: 1
Status of logical drive
: Okay
Size
: 69900 MB
Read-cache mode
: Enabled
Write-cache mode
: Enabled (write-back)
Write-cache setting
: Enabled (write-back) when protected by battery
Number of chunks
: 2
Drive(s) (Channel,Device)
: 0,0 0,1
Logical drive number 2
Logical drive name
: Logical Drive 2
RAID level
: 1
Status of logical drive
: Okay
Size
: 69900 MB
Read-cache mode
: Enabled
Write-cache mode
: Enabled (write-back)
Write-cache setting
: Enabled (write-back) when protected by battery
Number of chunks
: 2
Drive(s) (Channel,Device)
: 0,2 0,3
Example 6-3
HW Platform
Processors
Type
CPU Speed
Memory
Object ID
OS Version
7845/45-I3 Servers with Write-Cache Enabled
:
:
:
:
:
:
:
7845I3
2
Intel(R) Xeon(R) CPU
2530
8192 MBytes
1.3.6.1.4.1.9.1.587
UCOS 4.0.0.0-44
E5540
@ 2.53GHz
Upgrade Guide for Cisco Unified Presence Release 8.6
6-3
Chapter 6
Reference
Locale Specific Upgrades
Serial Number
: KQNDPGG
RAID Version
:
Raid firmware version: 11.0.1-0024
BIOS Information :
IBMCorp. -[D6E145FUS-1.07]- 04/26/2010
...
...
Logical Drives Information:
==========================
Virtual Disk: 0 (Target Id: 0)
Name:
RAID Level: Primary-1, Secondary-0, RAID Level Qualifier-0
Size:278.464 GB
State: Optimal
Stripe Size: 128 KB
Number Of Drives:2
Span Depth:1
Default Cache Policy: WriteBack, ReadAheadNone, Direct, No
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No
Access Policy: Read/Write
Disk Cache Policy: Disk's Default
Encryption Type: None
Virtual Disk: 1 (Target Id: 1)
Name:
RAID Level: Primary-1, Secondary-0, RAID Level Qualifier-0
Size:278.464 GB
State: Optimal
Stripe Size: 128 KB
Number Of Drives:2
Span Depth:1
Default Cache Policy: WriteBack, ReadAheadNone, Direct, No
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No
Access Policy: Read/Write
Disk Cache Policy: Disk's Default
Encryption Type: None
Write Cache if Bad BBU
Write Cache if Bad BBU
Write Cache if Bad BBU
Write Cache if Bad BBU
...
...
Locale Specific Upgrades
•
About Locales, page 6-4
•
Locale Installation, page 6-5
About Locales
Cisco provides locale-specific versions of the Cisco Unified Presence Locale Installer on
www.cisco.com. The locale installer allows the user to view/receive the chosen translated text or tones,
if applicable, when a user works with supported interfaces.
User locale files provide translated text and voice prompts, if available, for phone displays, user
applications, and user web pages in the locale that the user selects. User-only locale installers exist on
the web.
Upgrade Guide for Cisco Unified Presence Release 8.6
6-4
Chapter 6
Reference
Locale Specific Upgrades
When installing Cisco Unified Presence locales, you must install the user locale files, which contain
language information for a specific language and country and use the following naming convention:
ps-locale-language-country-version.cop
Locale Installation
Note
Before you install a locale for a country on Cisco Unified Presence, you must first install the
Cisco Unified Communications Manager locale file for the same country on the
Cisco Unified Communications Manager cluster.
You can install more than one locale file on each node in the cluster. You must restart each server in the
cluster after installation to activate the new locales. For more information about installing locales, see
the Deployment Guide for Cisco Unified Presence.
Upgrade Guide for Cisco Unified Presence Release 8.6
6-5
Chapter 6
Locale Specific Upgrades
Upgrade Guide for Cisco Unified Presence Release 8.6
6-6
Reference