Release Notes for Cisco Unified Communications Manager, Release 9.1(1a)
Important Notes
Downloads: This chapterpdf (PDF - 1.23MB) The complete bookPDF (PDF - 2.82MB) | The complete bookePub (ePub - 367.0KB) | The complete bookMobi (Mobi - 687.0KB) | Feedback

Important Notes

Important Notes

Bridge Upgrade Fails with Insufficient Disk Space

This information applies to CSCuj24138.

Bridge upgrades may fail due to insufficient disk space on servers that have 72GB hard drives, such as the MCS-7835-H2 or the MCS-7835-I2. When this failure occurs, the install.log file displays a message indicating that there is no more space left on the partition.

This failure may occur when you are upgrading a large cluster, when the database is large, or when the server contains a large amount of TFTP data. If a failure occurs when you upgrade from Cisco Unified Communications Manager Release 7.x to Release 9.1(1), perform one or more of the following actions to create more disk space on the partition:

  • Move log files to other machines.
  • Install the ciscocm.free_common_space_<latest_version>.cop.sgn file; this COP file removes the inactive side in the common partition to increase available disk space.

Note


If you install the COP file, you will not be able to switch back to the inactive version.

Changed License Calculations for Extension Mobility

This information applies to CSCue14471.

The Cisco Extension Mobility feature consumes an essential license for Unified Communications Manager 9.0(1) through 9.1(1). With 9.1(1a) this is changed; a user configured with Extension Mobility (device profiles configured under Extension Mobility) only will no longer consume an Essential license. So, a user configured with Extension Mobility only, with no other devices assigned, will not consume an Essential license.

Cisco Prime Unified Provisioning Manager Business Edition Compatibility

This information applies to CSCue09155.

Cisco Unified Communications Manager 9.1(1) is not compatible with Cisco Prime Unified Provisioning Manager Business Edition 9.0(1).

Cisco Unified Mobility Disclaimer


Caution


The Cisco Mobility solution is verified with only Cisco equipment. This solution may also work with other third-party PSTN gateways and Session Border Controllers (SBCs), but each Cisco Mobility feature is not guaranteed to work as expected.

If you are using this solution with third-party PSTN gateways or SBCs, Cisco technical support may not be able to resolve problems that you encounter.


Configure LDAP Directory

You can add users from your corporate directory to the Cisco Unified Communications Manager database by synchronizing the user data to the database. Cisco Unified Communications Manager allows synchronization from the following directories to the database:


Note


This is an updated list for this release.
  • Microsoft Active Directory 2000
  • Microsoft Active Directory 2003 R1 & R2 (32-bit)
  • Microsoft Active Directory 2008 R1 (32-bit) & R2 (64-bit)
  • Microsoft Active Directory Application Mode 2003 R1 & R2 (32-bit)
  • Microsoft Lightweight Directory Services 2008 R1 (32-bit) & R2 (64-bit)
  • Sun ONE Directory Server 5.2
  • Sun ONE Directory Server 6.x
  • Oracle Directory Server Enterprise Edition 11gR1
  • OpenLDAP 2.3.39
  • OpenLDAP 2.4

Jabber Certificate Warnings with IM and Presence Service

This information applies to CSCum63324.

When using the Cisco Jabber client, certificate warning messages can be encountered if the IP address is configured as the IM and Presence Service node name. To prevent Cisco Jabber from generating certificate warning messages, the FQDN should be used as the node name.

Phone Support for URI Dialing Display Preference Service Parameter

Most Cisco Unified IP Phones do not support the URI Dialing Display Preference service parameter. Regardless of how you configure the service parameter, the phone displays a directory URI, if one is available. To ensure full support of this service parameter, make sure that you install the latest phone builds. This service parameter is fully functional system-wide only after the phone firmware implements the changes.


Note


The default value of URI Dialing Display Preference has been changed from "URI" to "DN."


Upgrade to 9.1(1) Fails with Insufficient Disk Space

This information applies to CSCuc63312.

When upgrading Cisco Unified Communications Manager to Version 9.1(1), the upgrade may fail due to insufficient disk space. You will see the following error message:

There is not enough disk space in the common partition to perform the upgrade. For steps to resolve this condition please refer to the Cisco Unified Communications Manager 9.1(1) Release Notes or view defect CSCuc63312 in Bug Toolkit on cisco.com.

Reduce Disk Space Utilization

Follow this procedure to reduce disk space utilization during an upgrade.

Procedure
    Step 1   Reduce the amount of traces on the system by lowering the low and high watermarks in the Cisco Log Partition Monitoring Tool. The low watermark adjusts by changing the properties of the LogPartitionLowWaterMarkExceeded alert. The high watermark adjusts by changing the properties of the LogPartitionHighWaterMarkExceeded alert. For more information about the Cisco Log Partition Monitoring Tool, see the Cisco Unified Real-Time Monitoring Tool Administration Guide.
    Note   

    After the upgrade, you must restore the high and low watermarks to their original values in order to avoid premature purging of traces. The default value for the high watermark is 85. The default value for the low watermark is 80.

    Step 2   If you still get the error message, install the COP file named ciscocm.free_common_space_v1.0.cop.sgn that you can find on Cisco.com at Cisco Unified Communications Manager Version 9.1 > Unified Communications Manager/ CallManager/ Cisco Unity Connection Utilities > COP-Files.

    This COP file frees disk space to allow the upgrade to proceed.

    Note   

    You must perform an upgrade after applying the COP file.

    Caution   

    You will not be able to switch to the previous version after the COP file is installed. For example, if you are upgrading from Cisco Unified Communications Manager 9.0(1) to Cisco Unified Communications Manager 9.1(1) and the previous version is Cisco Unified Communications Manager 8.6, the COP file clears the space by removing the 8.6 version data that resides in the common partition. So after you apply the COP file, you will not be able to switch to the 8.6 version.

    Note   

    If you are unable to perform the upgrade and continue to receive the error message after applying this COP file, the amount of data present on the running version does not leave adequate space for expanding and executing the upgrade. In this case, you can recover more space by removing unused device firmware from the TFTP path. In some cases, having sufficient space for an upgrade will require that you take a backup, reinstall to a larger capacity disk or larger sized Open Virtual Appliance (OVA), and restore. Contact Cisco Technical Assistance Center (TAC) if you require further assistance.