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 Unified Communications Manager or Instant Messaging and Presence serivce.
Do not modify any of the Instant Messaging and Presence Service server entries on the Application Server or Server configuration pages of the Cisco Unified CM Administration interface. The Instant Messaging and Presence Service upgrade process automatically updates these entries on the Unified Communications Manager cluster during the final stages (switch version) of the upgrade process.
For upgrades from Release 8.x or 9.x to Release 10.x or later, any manual modification of these entries during the upgrade process will result in data migration failures between Instant Messaging and Presence Service and Unified Communications Manager. If such failures occur, you must restart the entire upgrade process for both Unified Communications Manager and Instant Messaging and Presence Service clusters.
This section describes the limitations that apply when you install or upgrade Unified Communications Manager or the Instant Messaging and Presence Service.
Do not install Unified Communications Manager in a large Class A or Class B subnet that contains a large number of devices.
The number of Unified Communications Manager 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 Unified Communications Manager publisher node, TFTP server, and media servers, cannot exceed 21.
The maximum number of Instant Messaging and Presence nodes in a cluster is 6.
For more information, see "Cisco Collaboration Solutions Design Guidance" at http://www.cisco.com/go/ucsrnd
Support for Intercluster Peers
The Instant Messaging and Presence supports intercluster peers to clusters that are running different software versions. To find the interdomain federations that are supported, see the "Supported Integrations" chapter in the Compatibility Matrix for Cisco Unified Communications Manager and IM and Presence Service .
With the merging of Cisco Unified Communications Manager and IM and Presence Service, enterprise and service parameters are now shared between nodes in a cluster. As such, both types of nodes use the same settings for enterprise and 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 both Cisco Unified Communications Manager and IM and Presence Service retain the value specified on Cisco Unified Communications Manager only, with one exception. The User Assignment Mode parameter is the only enterprise parameter that is retained during upgrade. 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.
This section lists the requirements that your network must meet before you can deploy Unified Communications Manager and the Instant Messaging and Presence.
IP Address Requirements
A complete collaboration solution relies on DNS in order to function correctly for a number of services and thus requires a highly available DNS structure in place. If you have a basic IP telephony deployment and do not want to use DNS, you can configure Unified Communications Manager and IM and Presence Service to use IP addresses rather than hostnames to communicate with gateways and endpoint devices.
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.
Note the following requirements:
Mixed-mode DNS deployments not supported—Cisco does not support mixed-mode deployments. Both Unified Communications Manager and Instant Messaging and Presence must either use or not use DNS.
If your deployment uses DNS—Unified Communications Manager and Instant Messaging and Presence should use the same DNS server. If you use different DNS servers between Instant Messaging and Presence and Unified Communications Manager, it is likely to cause abnormal system behavior.
If your deployment does not use DNS, will need to edit the following Host Name/IP Address fields:
Server—In the Cisco Unified CM Administration Server Configuration window, set IP addresses for your cluster nodes.
IM and Presence UC Service—In the Cisco Unified CM Administration UC Service Configuration window, create an IM and Presence UC service that points to the IP address of the IM and Presence database publisher node
CCMCIP Profiles—In the Cisco Unified CM IM and Presence Administration CCMCIP Profile Configuration window, point any CCMCIP profiles to the IP address of the host.
Multinode considerations—If you are using the multinode feature in Instant Messaging and Presence, see the section regarding multinode deployments in the Configuration and Administration of 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 Solution Partner Program (CSPP). CSPP partners, such as GlobalSCAPE, certify their products with specified versions of Unified Communications Manager. For information on which vendors have certified their products with your version of Unified Communications Manager, go to the following URL and select "Collaboration" from the Technology list in the navigation pane.
For information on using GlobalSCAPE with supportedUnified Communications Manager versions, refer to the following URL:
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 tohttp://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 CSPP process, contact the third-party vendor for support.
In this release, you cannot install or run 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 Unified Communications Manager and the IM and Presence Service on virtual machines.
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.
Cisco Unified Communications Manager on Virtualized Servers
Release Notes for your product release
- Configuration and Administration of IM and Presence 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.
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.
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, Cisco Unified Communications Manager is dependent on the capabilities of the virtualization software or physical server's service processor. Please see documentation for those products for support, if any.
The following sections provide information about the software requirements that your deployment must meet.
Unified Communications Manager and the Instant Messaging and Presence 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.
You can access Unified Communications Manager with this browser...
...if you use one of these operating systems
Microsoft Internet Explorer 8
Mozilla Firefox 3.x or 4.x (if 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.
Duplicate ENUMS Break Upgrades and Migrations from 9.1(2)
If you are upgrading or migrating from Release 9.1(2) of Cisco Unified Communications Manager to any 10.x, 11.x or 12.x release, an issue exists with older locale installations that causes upgrade and migration failures. This issue exists if you are using one of the following three locales, and your locale installer is dated prior to August 31, 2017;
en-GB (United Kingdom)
To ensure that your upgrade does not fail, update your Unified Communications Manager and phone locale installation to use a locale that is dated after August 31, 2017 as this issue does not exist for any locale file issued after that date. After you update your locale installation, you can begin the upgrade or migration.