Table Of Contents
Upgrading Cisco Unified Presence
How to Upgrade to a Later Release of Cisco Unified Presence Software
Upgrading from a Local Disk
Upgrading from a Remote Server
Retrieving the Remote Patch
How to Perform Intercluster Upgrades
Prerequisites for an Intercluster Upgrade
Roster Migration for Intercluster Upgrade
Contact List Size for Intercluster Upgrade
SIP Remote Contact Limit
Performing an Intercluster Upgrade
Verifying that the Roster Migration is Complete on Cisco Unified Presence
If Cisco Unified Presence User Experiences Issues Obtaining Presence Availability After Upgrade
Upgrading Cisco Unified Presence
January 18, 2013
How to Upgrade to a Later Release of Cisco Unified Presence Software
Note 
If your Cisco Unified Presence server is operating in Evaluation or Evaluation-Expire mode following a fresh installation, you cannot upgrade it. To upgrade a Cisco Unified Presence server that is already in production, refer to the Cisco Unified Operating System Maintenance Guide for Cisco Unified Presence. Select Software Upgrades > Install/Upgrade to perform your software upgrade in the Operating System interface. For specific release information, see the Release Notes for Cisco Unified Presence at http://www.cisco.com/en/US/products/ps6837/prod_release_notes_list.html
Caution Prior to initiating an upgrade from Cisco Unified Presence Release 8.5(x) and on, you should disable High-Availability on the Cisco Unified Presence subcluster. If High-Availability is not disabled, the subclusters will failover and a manual failback is required following the upgrade of both nodes in the subcluster. After you have completed the upgrade, High-Availability should be re-enabled. For more information, see the
Deployment Guide for Cisco Unified Presence.
Note If you are upgrading from Cisco Unified Presence Release 7.x and 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.
If you chose Apply Additional Release during a fresh installation of Cisco Unified Presence, the installation wizard first installs the software version on the DVD and then restarts the system. You are then prompted to enter certain network configuration parameter values and the location of the upgrade file. Determine whether you want to upgrade from:
–LOCAL—Retrieves the upgrade file from a local CD or DVD.
–SFTP—Retrieves the upgrade file from a remote server by using the Secure File Transfer Protocol (SFTP).
–FTP—Retrieves the upgrade file from a remote server by using File Transfer Protocol (FTP).
•Upgrading from a Local Disk
•Upgrading from a Remote Server
•Retrieving the Remote Patch
Upgrading from a Local Disk
Before You Begin
Before you can upgrade from a local drive, you must download the appropriate patch file from Cisco.com and copy the file to a CD or DVD. Because of the size of the patch files, you will need to copy the files to a DVD in most cases.
The patch-file name has the following format:
UCSInstall_UCOS_*.sgn.iso
Procedure
Step 1 Enter the patch directory and patch name, if required, and select OK. The window displays the patch file that is available on the CD or DVD.
Step 2 Select Continue to update the system with this patch. After the system restarts, the Preexisting Configuration Information window displays.
Troubleshooting Tips
You only need to enter the patch directory when the patch is not stored in the root directory of the CD or DVD.
What To Do Next
Configuring the Basic Installation
Upgrading from a Remote Server
Before You Begin
If you chose to upgrade through an FTP or SFTP connection to a remote server, you must first configure the network settings.
Procedure
Step 1 Perform one of the following actions in the Auto Negotiation Configuration window:
If you want to:
|
Action
|
Automatically set the speed and duplex settings of the Ethernet network interface card (NIC) using automatic negotiation
|
Select Yes.
Note To use this option, your hub or Ethernet switch must support automatic negotiation.
|
Disable automatic negotiation
|
a. Select No.
b. Complete the following tasks in the Duplex Configuration window:
–Manually select the appropriate NIC Speed and Duplex settings.
–Select OK to continue.
|
Step 2 Perform one of the following actions in the DHCP Configuration window:
If you want to:
|
Action
|
Use Dynamic Host Configuration Protocol (DHCP)
|
a. Select Yes.
b. Skip to the procedure that describes how to retrieve a remote patch.
|
Set up a static IP address for the server and gateway
|
a. Select No
b. Perform the following actions in the Static Network Configuration window:
–Enter your static network configuration values.
–Select OK.
c. Perform the following actions in the DNS Client Configuration window:
–Select Yes, and enter your DNS client information.
–Select OK.
|
What To Do Next
Retrieving the Remote Patch
Retrieving the Remote Patch
Procedure
Step 1 Enter the location and sign in information for the remote file server.
Step 2 Select the upgrade patch that you want to install, after the system connects to the remote server and retrieves a list of available upgrade patches. The system downloads, unpacks, and installs the patch and then restarts the system.
Related Topics
Configuring the Basic Installation
How to Perform Intercluster Upgrades
This section is applicable to the following Cisco Unified Presence intercluster upgrades:
•Cisco Unified Presence Release 7.x to Release 8.0(x)
•Cisco Unified Presence Release 7.x to Release 8.5(x)
•Prerequisites for an Intercluster Upgrade
•Roster Migration for Intercluster Upgrade
•Contact List Size for Intercluster Upgrade
•SIP Remote Contact Limit
•Performing an Intercluster Upgrade
Prerequisites for an Intercluster Upgrade
Before you perform the software upgrade to Cisco Unified Presence Release 8.x, 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.x, you should turn off (deactivate) the Cisco UP Presence Engine on all clusters until you complete the intercluster upgrade in your intercluster deployment. Once you complete the upgrades in your deployment, verify the status of the intercluster peer connections are ok, and 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 presence subscriptions with remote contacts.
If you intend to leave an intercluster peer on Release 7.0(x), verify 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 Performing an Intercluster Upgrade. You may experience high CPU (possibly for several hours) while the Cisco UP Presence Engine attempts to reestablish any presence subscriptions with remote contacts.
For intercluster presence to work between a Cisco Unified Presence Release 7.0(x) cluster and a Cisco Unified Presence Release 8.0(x), the proxy service parameter RecordRoute should be enabled.
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 presence subscriptions with remote contacts in both the local and remote cluster.
To allow Cisco Unified Presence to reestablish the presence 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 here, 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 presence subscriptions to remote contacts in both the local and remote clusters. If this presence subscription interval time (one day) elapses before Cisco Unified Presence has successfully reestablished presence subscriptions, you can restart the Cisco UP Presence Engine to reset the interval.
Related Topics
Performing an Intercluster Upgrade
Contact List Size for Intercluster Upgrade
If you upgrade from Cisco Unified Presence Release 7.0(x) to Release 8.x, presence 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
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 B-1.
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 B-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
Performing an Intercluster Upgrade
To perform an intercluster upgrade from Cisco Unified Presence Release 7.0(x) to Release 8.0(x), follow the intercluster upgrade procedure outlined in this topic. To perform an intercluster upgrade from Cisco Unified Presence Release 7.0(x) to Release 8.5(x) follow the intercluster upgrade procedure outlined in this topic, however skip steps 4 and 5, as you no longer need to restart the Cisco UP XCP Router.
Note In your intercluster deployment, if Cisco Unified Presence cluster A is running Release 8.0(x), and cluster B is running Release 8.5(x), when you upgrade cluster A to Release 8.5(x), you do not need to restart the Cisco UP XCP Router on cluster B.
Before You Begin
Before you perform the software upgrade, turn off the Cisco UP Presence Engine on all nodes in the local cluster, see Prerequisites for an Intercluster Upgrade.
Procedure
Step 1 Perform the software upgrade in the local cluster.
Step 2 Check the status of the intercluster peer connection. If the tomcat certificate is out-of-sync, you need to manually update the tomcat trust certificate following the procedure we describe in this module.
Step 3 On each node in the upgraded cluster, turn on the XCP services that are applicable to your deployment.
Step 4 Restart the Cisco UP XCP Router on all nodes in the local cluster.
Step 5 Restart the Cisco UP XCP Router on all nodes in any remote cluster that you have already upgraded to Cisco Unified Presence Release 8.0(x) prior to this upgrade.
When you restart the Cisco UP XCP Router, Cisco Unified Presence establishes the connection between intercluster router to router connectors in the home and remote clusters.
Step 6 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 7 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.x. 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 8 If the local cluster that you upgrade to Cisco Unified Presence Release 8.x 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 If, following this upgrade, all peer clusters in your intercluster deployment are running Cisco Unified Presence Release 8.x, 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.
Step 9 Turn on the Cisco UP Presence Engine on all nodes in the local cluster,
Step 10 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.x prior to this upgrade.
Note If you perform an intercluster upgrade from Cisco Unified Presence Release 8.0(x) to Cisco Unified Presence Release 8.0(x), you must restart the Cisco UP XCP Router on all nodes in both the local and remote clusters.
Step 11 Verify that the roster migration is complete, see Verifying that the Roster Migration is Complete on Cisco Unified Presence.
Step 12 Request that all Cisco Unified Personal Communicator users in the local and remote cluster sign out, and sign back in to the application.
Troubleshooting Tips
The Presence Viewer only displays local watchers. Therefore, if you configure an intercluster peer connection between a Cisco Unified Presence Release 8.0(x) cluster and a Cisco Unified Presence Release 7.0(x) cluster. when you view the profile of a user on the Presence viewer on Cisco Unified Presence Release 7.0(x), any Cisco Unified Presence Release 8.0(x) watchers are not displayed. Similarly, if you view the profile of a user on the Presence Viewer on Cisco Unified Presence Release 8.0(x), any Cisco Unified Presence Release 7.0(x) watchers are not displayed.
Related Topics
•For information on performing a software upgrade from Cisco Unified OS Administration, see the Cisco Unified Operating System Maintenance Guide for Cisco Unified Presence at this URL:
http://www.cisco.com/en/US/products/ps6837/prod_maintenance_guides_list.html
Verifying that the Roster Migration is Complete on Cisco Unified Presence
After you perform the intercluster upgrade, the roster migration process continues on Cisco Unified Presence for the remote users for a long period. Use this procedure to verify that the roster migration is complete and the system is ready.
Note Only perform this procedure after you complete the upgrade procedure, switch Cisco Unified Presence software versions, and complete the required configuration on Cisco Unified Presence (licensing, feature configuration and start the required services).
Procedure
Step 1 Run this CLI command to check the roster upgrade queue on all nodes in the Cisco Unified Presence 8.x local cluster and all nodes in the Cisco Unified Presence 8.x remote clusters
run sql select count(*) from rosterupgradequeue
If the rosterupgradequeue table for all of the local or remote clusters is empty, the roster migration is complete. If the rosterupgradequeue table for any of the local or remote clusters is not empty, the roster migration is not complete yet (proceed to step 2).
Step 2 If the rosterupgradequeue is not empty and the entry on rosterupgradequeue has not decreased over time, then perform the following steps on Cisco Unified Presence:
•On the publisher node in both the local and remote Cisco Unified Presence 8.x clusters, check that the maximum contact size limitation is set to zero.
•On the publisher node in both the local and remote Cisco Unified Presence 8.x clusters, check for any system notifications.
•On the publisher node in both the local and remote Cisco Unified Presence 8.0(x) clusters, check that the correct license file is present.
•On the publisher node, check that 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.0(x) local cluster and all nodes in the Cisco Unified Presence 8.0(x) remote clusters.
–On the local publisher node, restart the Cisco UP Config Agent service.
•Restart the Cisco UP XCP Router service on all local Cisco Unified Presence nodes and on all remote Cisco Unified Presence nodes.
•Restart the Cisco UP Presence Engine service on all local Cisco Unified Presence nodes and on all remote Cisco Unified Presence nodes.
•Restart the Cisco UP XCP SIP Federation Connection Manager service on all remote 7.0(x) Cisco Unified Presence clusters.
Step 3 It may be necessary to repeat steps 1-2 until the rosterupgradequeue tables are empty on all nodes in the local Cisco Unified Presence cluster and remote Cisco Unified Presence clusters. 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.
Troubleshooting Tips
If you switch the software version from Cisco Unified Presence Release 8.0(x) back to Cisco Unified Presence Release 7.0(x) on local cluster, make sure that the rosterupgradequeue table is empty on all nodes in the remote 8.0(x) clusters before you perform an upgrade in local cluster again.
If Cisco Unified Presence User Experiences Issues Obtaining Presence Availability After Upgrade
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 presence. 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.
Related Topics
Performing an Intercluster Upgrade
Feedback