Upgrade Guide for Cisco Unified Communications Manager, Release 10.0(1)
Upgrade planning
Downloads: This chapterpdf (PDF - 1.31MB) The complete bookPDF (PDF - 2.63MB) | The complete bookePub (ePub - 261.0KB) | Feedback

Upgrade planning

This chapter provides the following information:

Requirements and limitations

The following sections provide information about the requirements that your system must meet, and limitations that apply when you install or upgrade Cisco Unified Communications Manager or the IM and Presence Service.

System limitations

This section describes the limitations that apply when you install or upgrade Cisco Unified Communications Manager or the IM and Presence Service.

Subnet limitations

Do not install Cisco Unified Communications Manager in a large Class A or Class B subnet that contains a large number of devices.

Cluster size

The number of call processing subscriber nodes in a cluster cannot exceed 4 subscriber nodes and 4 standby nodes, for a total of 8 subscribers. The total number of servers in a cluster, including the publisher node, TFTP server, media servers, and IM and Presence nodes can not exceed 20.


Note


The maximum number of IM and Presence nodes in a cluster is 6.


Support for intercluster peers

This release of IM and Presence supports intercluster peers to clusters running Cisco Unified Presence Release 8.6 and IM and Presence Release 9.x. Intercluster peers to clusters running Release 8.0(x) or Release 8.5(x) are not supported.

Parameter settings

With the merging of Cisco Unified Communications Manager and IM and Presence Service, parameters are now shared between servers. As such, both types of servers use the same setting for cluster-wide parameters. You need to be aware that not all parameter settings are retained during an upgrade to Release 10.0(1). All enterprise parameters and cluster-wide service parameters that are common to Cisco Unified Communications Manager and IM and Presence Service retain the value specified on Cisco Unified Communications Manager only. Service parameters that apply to IM and Presence only are retained after an upgrade.

Cisco recommends that before you begin an upgrade, you make a note of parameter settings and evaluate the best settings for the combined cluster. This will allow you to easily configure those settings after the upgrade is complete.

Network requirements

This section lists the requirements that your network must meet before you can deploy Cisco Unified Communications Manager and the IM and Presence Service.

IP address requirements

You must configure the server to use static IP addressing to ensure that the server obtains a fixed IP address. Using a static IP address also ensures that Cisco Unified IP Phones can register with the application when you plug the phones into the network.

DNS requirements

Note the following DNS requirements:

  • Mixed-mode DNS deployments not supported—Cisco does not support mixed-mode deployments. Both Cisco Unified Communications Manager (Unified Communications Manager) and IM and Presence must either use or not use DNS.
  • If your deployment uses DNS—Unified Communications Manager and IM and Presence should use the same DNS server. If you use different DNS servers between IM and Presence and Unified Communications Manager, it is likely to cause abnormal system behavior.
  • If your deployment does not use DNS—You must modify the Host Name/IP Address field in the service profile for the Presence and IM UC service. If DNS is not supported, you must change the Host Name/IP Address field to the IP address of the IM and Presence publisher node. For more information about configuring services, see Cisco Unified Communications Manager Administration Guide.
  • Multinode considerations—If you are using the multinode feature in IM and Presence, see the section regarding multinode deployments in the Deployment Guide for IM and Presence on Cisco Unified Communications Manager for DNS configuration options.

SFTP server support

Cisco allows you to use any SFTP server product but recommends SFTP products that have been certified with Cisco through the Cisco Technology Developer Partner program (CTDP). CTDP partners, such as GlobalSCAPE, certify their products with specified versions of Cisco Unified Communications Manager. For information on which vendors have certified their products with your version of Cisco Unified Communications Manager, refer to the following URL:

http://www.cisco.com/pcgi-bin/ctdp/Search.pl

For information on using GlobalSCAPE with supported Cisco Unified Communications versions, refer to the following URL:

http://www.globalscape.com/gsftps/cisco.aspx

Cisco uses the following servers for internal testing. You may use one of the servers, but you must contact the vendor for support:

  • Open SSH (refer to http://sshwindows.sourceforge.net/)
  • Cygwin (refer to http://www.cygwin.com/)
  • Titan (refer to http://www.titanftp.com/)

Cisco does not support using the SFTP product free FTDP. This is because of the 1GB file size limit on this SFTP product.

For issues with third-party products that have not been certified through the CTDP process, contact the third-party vendor for support.

Platform requirements

In this release, you cannot install or run Cisco Unified Communications Manager and the IM and Presence Service directly on server hardware; you must run these applications on virtual machines.

Before you can install or upgrade the software on a virtual machine, you must:

  • configure the platform
  • install and configure ESXi virtualization software
  • deploy the correct OVA template for the release

This section provides information about the platform requirements that you must meet before you can deploy Cisco Unified Communications Manager and the IM and Presence Service on virtual machines.

Supported platforms

Cisco supports virtualized deployments of Unified Communications Manager and the IM and Presence Service on Cisco Unified Computing System servers, or on a Cisco-approved third-party server configuration.

Whether you use a Cisco Unified Computing System server or a Cisco-approved third-party server configuration, you must ensure that the server meets the configuration requirements of the release. The following options are available:

  • a tested reference configuration (TRC)
  • a specifications-based configuration

For information about the platform configuration specifications, such as CPU, memory, and storage specifications, see UC Virtualization Supported Hardware.

Information about supported platforms is also available in the following documentation:
  • Cisco Unified Communications Manager on Virtualized Servers
  • Release Notes for your product release
  • Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager

ESXi and VMware Tools

You must install a version of vSphere ESXi hypervisor that meets the requirements of the release, as well as VMWare Tools. VMware Tools are specialized drivers for virtual hardware that is installed in the UC applications when they are running virtualized. It is very important that the VMware tools version be in sync with the version of ESXi being used. For more information, see Cisco Unified Communications Manager on Virtualized Servers.

If the server is running VMware EX/ESXi and the motherboard has an ICH10 onboard SATA controller, you must disable the SATA controller in the BIOS. The ICH10 onboard SATA controller is not supported by EX/ESXi.

Related Tasks
Related References

OVA templates

Once ESXi is running on the hardware platform, it is ready to host the virtual machines. The first step is to create the virtual machines on the host. You must use Cisco-generated OVA templates to create the virtual machines to run the Unified Communications Manager application. These OVA templates contain aligned disk partitions and other specific configurations that are required. See Virtualization for Cisco Unified Communications Manager to download the OVA file for your release.

Power supply

Ensure that you connect each node to an uninterruptible power supply (UPS) to provide backup power and protect your system. Failure to do so may result in damage to physical media and require a new installation.

If you want the node to automatically monitor UPS signaling and automatically initiate a graceful shutdown upon power loss, you should use specific UPS and server models. For more information on supported models and configurations, refer to the Release Notes for your product release.

Software requirements

The following sections provide information about the software requirements that your deployment must meet.

Browser requirements

Cisco Unified Communications Manager and the IM and Presence Service both provide interfaces that you can use to configure and manage the system. You can access the interfaces by using the browsers and operating systems listed in the following table. Cisco does not support or test other browsers.

Table 1 Supported Browsers and Operating Systems

You can access Cisco Unified Communications Manager with this browser...

...if you use one of these operating systems

Microsoft Internet Explorer 8

  • Microsoft Windows XP SP3
  • Microsoft Windows Vista SP2 (or latest service pack available)
  • Microsoft Windows 7 (32-bit) (with latest service pack available)

Mozilla Firefox 3.x or 4.x (if available)

  • Microsoft Windows XP SP3
  • Microsoft Windows Vista SP2 (or latest service pack available)
  • Microsoft Windows 7 (32-bit) (latest service pack available)
  • Apple Mac OS X (latest service pack available)

Safari 4.x or 5.x (if available)

Apple Mac OS X (or newest OS release available)

Upgrade time requirements

The time required to upgrade the software is variable and depends on a number of factors. For large deployments, installation of the upgrade software may take several hours.

Throttling affects time required to upgrade

To preserve system stability during upgrades, the system throttles the upgrade process, which may increase the time required to complete the upgrade.

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.

To disable throttling, use the following command in the CLI before you start the upgrade:

utils iothrottle disable

If you want to restart throttling after you start the upgrade, you must cancel the upgrade, restart throttling, and then restart the 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, depending on the size of the database. The length of the outage on subscriber nodes depends on how long database replication takes to complete.

If you need to revert to an earlier software version, you must restart the system which results in a similar service outage period.

Supported upgrade paths

The following sections provide information about the supported upgrade paths for the Cisco Unified Communications Manager and the IM and Presence Service.

Version requirements

All servers in a cluster must run the same release of Cisco Unified Communications Manager. The only exception is during a cluster software upgrade, during which a temporary mismatch is allowed.

If you are installing IM and Presence nodes, the software version of the first IM and Presence node (the IM and Presence database publisher node) must match the first two numbers of the software version installed on the Unified Communications Manager publisher node. For example, IM and Presence Service software version 10.0.1.10000-1 is compatible with Cisco Unified Communications Manager software version 10.0.1.30000-2.

After you install the first IM and Presence node, the software version of any IM and Presence subscriber nodes that you install must match all five version numbers of the first IM and Presence node.

Upgrade paths for Cisco Unified Communications Manager

The following table lists the range of upgrade paths that are supported for Unified Communications Manager. For more detailed information about supported upgrade paths, see the Cisco Unified Communications Manager Software Compatibility Matrix.

Table 2 Cisco Unified Communications Manager upgrade paths
From To Upgrade Type
8.5(x) or older 10.0(1) Refresh upgrade, COP file needed
8.6(x) to 9.x 10.0(1) Refresh upgrade
10.0(1)x 10.0(1)y Standard upgrade

Upgrade paths for IM and Presence Service

The following table lists the range of upgrade paths that are supported for the IM and Presence Services. For more detailed information about supported upgrade paths, see the Cisco Unified Communications Manager Software Compatibility Matrix.

Table 3 IM and Presence Service upgrade paths
From Cisco Unified Presence Release To IM and Presence Release Upgrade Type
8.5(4) 10.0(1) Refresh upgrade, COP file needed
8.6(3) to 9.x 10.0(1) Refresh upgrade
10.0.1.x 10.0.1.y Standard upgrade

For upgrades from Cisco Unified Presence 8.5(4), you must install a COP file on all nodes before you begin the upgrade process. You can download the COP file from Cisco.com. The name of the COP file is:

cisco.com.cup.refresh_upgrade_v<latest_version>.cop

The COP file delivers functionality to allow the upgrade path to be supported and provides various enhancements to the user experience.


Caution


If you do not install the COP file on all nodes for the required releases, the upgrade will fail.

Upgrade from Cisco Unified Presence Release 8.5(4)

If you upgrade from Cisco Unified Presence Release 8.0(x) or Release 8.5 to the current release, note the following:

  • 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 or to Release 9.x and later. 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 9.x or later, Cisco recommends that you disable HA on each presence redundancy group before you begin the upgrade. You can reenable 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, the Cisco 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.

    Note


    In IM and Presence Release 10.0(1), the Cisco Replication Watcher service has been renamed to the Cisco IM and Presence Data Monitor service.

Licensing

The following sections provide information about the licensing requirements for Cisco Unified Communications Manager and the IM and Presence Service.

Cisco Unified Communications Manager license requirements

Use the Cisco Prime License Manager to allocate and monitor the licenses for Cisco Unified Communications Manager, its applications and endpoints. See the Cisco Prime License Manager User Guide for information about generating and installing licenses.

Important:

Unused PAKs and/or licenses for versions prior to Release 9.0 cannot be installed once your system has been upgraded to Release 9.0 or later. If you have uninstalled PAKs, install all licenses before upgrading.

IM and Presence license requirements

The IM and Presence Service does not require a server license or software version license. However, you must assign users and enable the IM and Presence Service for each assigned user.


Note


With the Jabber for Everyone Offer, no end user licenses are required to enable IM and Presence functionality. See the Jabber for Everyone Quick Start Guide for more information.


You can assign IM and Presence on a per user basis, regardless of the number of clients you associate with each user. When you assign IM and Presence to a user, this enables the user to send and receive IMs and also to send and receive availability updates. If users are not enabled for IM and Presence, they will not be able to log in to the IM and Presence server to view the availability of other users, send or receive IMs, and other users will not see their availability status.

You can enable a user for IM and Presence using any of the following options:

  • The End User Configuration window in Cisco Unified Communications Manager. See the Cisco Unified Communications Manager Administration Guide for more information.
  • The Bulk Administration Tool (BAT)
  • Assign IM and Presence to a feature group template which you can reference from the Quick User/Phone Add window in Unified Communications Manager.

See the IM and Presence chapter in the Cisco Unified Communications Manager Features and Services Guide for more information.

IM and Presence capabilities are included within both User Connect Licensing (UCL) and Cisco Unified Workspace Licensing (CUWL). IM and Presence capabilities can also be acquired for users that are not Cisco Unified Communications Manager IP Telephony users through the Jabber for Everyone Offer. See the Jabber for Everyone Quick Start Guide for more information.

Export unrestricted

This release of Cisco Unified Communications Manager and IM and Presence Service supports an export unrestricted (XU) version.


Note


Unrestricted versions of software are intended only for a very specific set of customers who do not want various security capabilities; unrestricted versions are not intended for general deployments.

Export unrestricted versions differs from restricted versions as follows:

  • Encryption of user payload (information exchange) is not supported.
  • External SIP interdomain federation with Microsoft OCS/Lync or AOL is not supported.
  • After you install an unrestricted release, you can never upgrade to a restricted version. A fresh install of a restricted version on a system that contains an unrestricted version is also not supported.
  • All nodes within a single cluster must be in the same mode. For example, Cisco Unified Communications Manager and IM and Presence nodes in the same cluster must either all be in unrestricted mode or all be in restricted mode.
  • IP phone security configurations will be modified to disable signaling and media encryption (including encryption provided by the VPN phone feature)
You can perform a fresh install of an unrestricted version by downloading the required UCSInstall file.

Note


Be aware that after you install an unrestricted release, you can never upgrade to a restricted version. You are not allowed to perform a fresh installation of a restricted version on a system that contains an unrestricted version.


For all Graphical User Interfaces (GUIs) and Command Line Interfaces (CLIs), the Administrator can view the product version (restricted or export unrestricted).

The following table describes the GUI items that are not available for the export unrestricted version of IM and Presence.

Export unrestricted GUI item location

Description

Cisco Unified CM IM and Presence Administration

System > Security > Settings

You cannot check the Enable XMPP Client to IM/P Service Secure Mode setting.

You cannot check the Enable XMPP Router-to-Router Secure Mode setting.

You cannot check the Enable Web Client to IM/P Service Secure Mode setting.

The option to set SIP intra-cluster Proxy-to-Proxy Transport Protocol to TLS has been removed.

System > Service Parameters - Cisco SIP Proxy service

All TLS options have been removed for the Transport Preferred Order parameter.

The TLS option has been removed from the SIP Route Header Transport Type parameter.

Presence > Inter-domain Federation > SIP Federation

When you configure interdomain federation to OCS/Lync, you will receive warning popup to indicate that it is only possible to directly federate with another OCS/Lync within the enterprise. Interdomain federation to OCS/Lync outside the enterprise is not supported in unrestricted mode.

Presence > Inter-domain Federation > XMPP Federation > Settings

You cannot configure the security mode; It is set to "NO TLS".

Presence > Routing > Settings

You cannot set any TLS or HTTPS listeners as the preferred proxy listener.