Chapter 1. Introduction

About Cisco Prime Collaboration Deployment

Related Documentation

Obtaining Documentation and Submitting a Service Request

Chapter 2. New and Changed Information

Network Address Translation Support

Configure Cisco Prime Collaboration Deployment Behind the NAT

Discover a Cluster

Add a New Cluster for a Fresh Install

Create a Migration Cluster

Upgrade and Migration

Updates to Supported Releases

DRS CLI Command

Chapter 3. Important Notes

Cisco Unified Communications Manager Upgrades to Release 10.5(2) using Prime Collaboration Deployment

Conflicting Upgrade Path for Release 6.0(1)

Deployment

DNS

Install Tasks

ISO File Permissions for Install and Migration Tasks

Migration Requirements

New Upgrade is not Allowed While Another Upgrade is Running

Readdress

Upgrades

Virtualization Software License Feature Level Compatibility

Chapter 4. Caveats

Bug Search Tool

Resolved Caveats

Resolved Caveats for SU1

Open Caveats

Copyright Page

Chapter 1. Introduction

- About Cisco Prime Collaboration Deployment

- Related Documentation

- Obtaining Documentation and Submitting a Service Request

About Cisco Prime Collaboration Deployment

These release notes describe new features, requirements, restrictions, and caveats for Cisco Prime Collaboration Deployment. These release notes are updated for every maintenance release.

Cisco Prime Collaboration Deployment is an application designed to assist in the management of Unified Communications applications. It allows the user to perform tasks such as migration of older software versions of clusters to new virtual machines, fresh installs, and upgrades on existing clusters.

Cisco Prime Collaboration Deployment has four primary, high-level functions:

- Migrate an existing cluster of Unified Communications servers to a new 10.5(x) cluster (this may be MCS to virtual or virtual to virtual)

- Perform operations on existing clusters (8.6.1 or higher). Examples of these operations include:

- Upgrade the cluster to a new version of software

- Switch version

- Restart the cluster

- Changing IP addresses or hostnames in the cluster on existing Release 10.x clusters

- Fresh install a new Release 10.x Unified Communications cluster

Note

Cisco Prime Collaboration Deployment does not support internationalization or languages other than English.

Related Documentation

You can view documentation that is associated with supported applications.

Application

Documentation Link

Cisco Unified Communications Manager

Click Here

Cisco Unified Contact Center Express

Click Here

Cisco Unity Connection

Click Here

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation, at: Click Here .

Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation as an RSS feed and delivers content directly to your desktop using a reader application. The RSS feeds are a free service.

Chapter 2. New and Changed Information

- Network Address Translation Support

- Discover a Cluster

- Add a New Cluster for a Fresh Install

- Create a Migration Cluster

- Upgrade and Migration

Network Address Translation Support

Cisco Prime Collaboration Deployment supports Network Access Translation (NAT). You can use Cisco Prime Collaboration Deployment in the following scenarios:

- When Cisco Prime Collaboration Deployment is in a local network or private network and application nodes are behind the NAT.

- When Cisco Prime Collaboration Deployment is behind the NAT and application nodes are in a private network.

To support application nodes behind the NAT, Cisco Prime Collaboration Deployment tracks the private IP address and the NAT IP address. Use Cisco Prime Collaboration Deployment to specify the NAT IP address for deployment nodes and the application. Cisco Prime Collaboration Deployment uses the NAT IP address to communicate with the application node. However, when you configure a node using the platformConfig.xml file, the node uses its private address.

- Configure Cisco Prime Collaboration Deployment Behind the NAT

Configure Cisco Prime Collaboration Deployment Behind the NAT

When Cisco Prime Collaboration Deployment is behind the NAT and communicates with an application virtual machine or an ESXi host, the communication occurs using the NAT IP address.

Note

When Cisco Prime Collaboration Deployment is behind the NAT and application nodes are in a private network, the application nodes communicate with the NAT IP address.

Use the NAT Settings window in the Administration menu to set the NAT IP address for Cisco Prime Collaboration Deployment. The NAT IP address that you enter on this window does not appear on any window on the GUI.

Procedure

Step 1

From the Cisco Prime Collaboration Deployment application, select Administration > NAT Settings. The NAT Settings window appears and is prepopulated with the hostname and the private IP address.

Step 2

Enter the NAT IP address in the NAT IP field.

Step 3

Click Save. The NAT IP address is saved as an entry in a configuration file on Cisco Prime Collaboration Deployment. This entry is used when the application nodes try to contact Cisco Prime Collaboration Deployment, then the application nodes read the configuration file to get the NAT IP address, and then try to communicate Cisco Prime Collaboration Deployment with that IP address.

Step 4

(Optional)Click Reset. The NAT IP address is reset to the earlier saved NAT IP address.

Discover a Cluster

With the Discover Cluster feature, Cisco Prime Collaboration Deployment communicates with the servers that are already running Unified Communications applications and adds that cluster information into the Cisco Prime Collaboration Deployment inventory.

When you perform the Discover Cluster operation, the Cisco Prime Collaboration Deployment server communicates with the publisher of the cluster and retrieves the cluster information. Then, it communicates with each server, installs the ciscocm.ucmap_platformconfig.cop file on the server (to retrieve configuration information), and collects information about the hostname, IP, product type, and both active and inactive versions for that server.

Note

When the publisher is behind the NAT, providing the private IP address of the publisher does not reach to the node. You must provide the proper IP address for successful node discovery.

Note

To know which applications are supported, see Supported Releases.

Note

If a cluster includes Cisco Unified Communications Manager and Cisco Unified Presence (Cisco Unified Communications and IM and Presence Service servers), the Cluster Discovery discovers the Cisco Unified Presence or IM and Presence Service nodes as part of the Cisco Unified Communications Manager cluster.

Procedure

Step 1

From the Cisco Prime Collaboration Deployment application, select Inventory > Clusters. The Clusters window appears.

Step 2

Click the Discover Cluster button to discover the existing clusters. The Discover Cluster wizard appears.

Step 3

Enter details in the following fields:

- Choose a Nickname for this Cluster

- Hostname/IP Address of Cluster Publisher
Note:
For a cluster that has both Unified Communications Manager and IM and Presence Service nodes, enter the hostname or IP address of the Cisco Unified Communications Manager publisher.

- OS Admin Username

- OS Admin Password

- Enable NAT

Step 4

(Optional)Check the Enable NAT check box, and then click Next.

Important: During discovery, the ciscocm.ucmap_platformconfig.cop file is installed automatically on the active partition of all nodes in the cluster. This COP file is used for the cluster discovery process and does not affect Cisco Unified Communications Manager.

Note:   When a cluster is behind NAT, the application tries to establish communication with each node using its private address. So, the nodes are unreachable. A pop-up shows the unreachable nodes.

Cisco Prime Collaboration Deployment generates a list of cluster nodes from the inventory of the publisher server. The list generation process may take several minutes to complete. After the list is generated, a confirmation message appears indicating the completion of the cluster discovery process.

Step 5

Click Edit to add NAT IP address, and click OK. The Nat IP address is set for the hostname.

Step 6

Click Resume Discovery to resume the discovery of unreachable nodes. Cisco Prime Collaboration Deployment retries to discover the cluster with the NAT IP address instead of the private IP address and to get the cluster details, such as version. The discovery is successful when the cluster details appear on the window.

Step 7

Click Next.

Step 8

(Optional)Click Assign Functions to assign functions to each of the cluster nodes.

Note:   The assignment of functions has no effect on the services that are to be activated. However, this information can be used to determine the default sequence of tasks.

The Assign Functions dialog box appears.

Step 9

Click Finish. The cluster appears in the Clusters window, showing the cluster name, the product and version, the cluster type as Discovered, and the discovery status.
Note:
It might take a few minutes to discover a cluster. After the discovery is complete, the information for each node in the cluster is listed in the Cluster Inventory window. If you cancel the discovery before it is complete, the data is lost and you will have to repeat the discovery procedure.

Note:
The following are the different statuses that appear for the Discovery Status field:

- Contacting—Indicates that Cisco Prime Collaboration Deployment is establishing communication with clusters.

- Discovering—Indicates that the cluster discovery is in process.

- Successful—Indicates that the cluster discovery is successful.

- Node Unreachable—Indicates that the cluster node is inaccessible.

- Timeout—Indicates that the duration that is configured for the cluster discovery is complete but no cluster was discovered.

- Internal Error—Indicates that cluster discovery is failed because of an incorrect NAT IP address.

Add a New Cluster for a Fresh Install

Procedure

Step 1

Select Inventory > Clusters from the menu of the Cisco Prime Collaboration Deployment application.

Step 2

Click Define New UC Cluster.

Step 3

The Define Cluster wizard appears. Under Step 1 of the wizard, enter the Cluster name. Click Next.

Step 4

Step 2 of the Add Cluster wizard allows you to add nodes to your cluster. Begin by clicking Add Node at the top of the Cluster Name table.

Step 5

The Add Node dialog box appears. The dialog box contains a table that lists all available VMs, sorted by name and by host. At the top of the page, fill in the Network settings for this Node. In the middle of the page, choose the Functions for the node, and near the bottom, choose a VM for this node. Select the VM you wish to add and then enter the following information in the sections below the VM table:

1. Under Network, select either Use DHCP with reservations or Static IP Address. If you select the DHCP with reservations option, you must enter the IP address you have a reservation for on your DHCP server (associated with the MAC address for that VM) in addition to the hostname. If you select Static IP Address, you must enter the IP Address and subnets. If you are adding a UCCX server, do not use DHCP for network settings.

2. Under Functions, assign specific functions to your VM by checking the applicable check boxes. You must check the Publisher function for at least one node in the cluster being defined, for each application type.
You can also add a note about the function or functions assigned in the Notes field below.

3. Under Virtual Machines, choose the VM for this node. VMs to be used for fresh install clusters should be new VMs that are in the powered off state. Do not install over an existing running Unified Communications Manager node, this must be a fresh VM created with the appropriate OVA for the application you will be installing.

Step 6

Click OK.

Step 7

The VM you added is now listed in the Cluster Name table. (To add more nodes to the cluster, repeat steps 4 through 6 until all nodes are added.) After all nodes are added to the Cluster Node table, click Next.

Step 8

The Configure Cluster Wide Settings page appears. Enter the OS Administration Credentials, Application Credentials, Security Password, SMTP Settings, and Certificate Information for this cluster. Click Next.
Note:   The certificate attributes consist of the following:

- Country

- Organization

- Organizational Unit

- State/Province

- Time Zone

Step 9

The Configure DNS Settings screen appears. DNS settings are optional. If you wish to add a DNS setting for a node, select the node and click Assign DNS Settings. The Cisco Unified Contact Center Express application must use DNS.

Step 10

The Configure NTP Settings screen appears. You must enter at least one NTP server. If you are not using DNS, you must enter an IP address. If you are using DNS, you can enter an FQDN.
Note:   We recommend that you define at least two NTP servers.
Click Next.

Step 11

The Configure NIC Settings page appears. This step is optional. To use the default value of 1500, click Next to continue. Or, if you wish to change the settings, choose the server, and enter an MTU size between 552 and 1500, and click Apply to Selected. Click Next after you configure the NIC settings.

Step 12

Choose a time zone for each node in the cluster. To choose the time zone, select the node and choose the desired time zone settings in the boxes at the top, and click the Apply to Selected. When you finish setting time zones for all the nodes, click Finish.

Step 13

The new install cluster is listed on the Clusters screen, with a cluster type of "New Install." The cluster is defined but not yet created. When you are ready to install the cluster, create an install task. The install task uses the install cluster that you defined, and creates the cluster.

Create a Migration Cluster

Before You Begin

To create a migration task, perform the following procedure:

1. Discover the existing cluster you wish to migrate. See the "Discover a Cluster" procedure at Discover a Cluster.

2. Define a migration cluster.

Note

After you define the migration cluster, see "Migration Task" at Migration Task to define when and how to perform the migration.

Procedure

Step 1

From the Cisco Prime Collaboration Deployment application, select Inventory > Cluster.

Step 2

Click Define Migration Destination Cluster. The Define Migration Destination Cluster wizard appears.

Step 3

In the Specify Clusters section, specify the name of the cluster, select the source UC cluster from the drop-down list. Enter a name in the Destination Cluster Name field and select one of the following Destination Network Settings options:

- To retain the default network options, select the Use the source node network settings for all destination nodes option.

- To modify the default network settings or enter new network options, select the Enter new network settings for one or more destination nodes option.

Note:
If you select the Use the source node network settings for all destination nodes option, same IP address appears for both the source node NAT IP and Dest NAT IP columns Assign Destination Cluster Nodes. If you select the Enter new network settings for one or more destination nodes option, only source hostname appears and not the destination hostname on the Assign Destination Cluster Nodes window.

Step 4

Click Next. The Assign Destination Cluster Nodes window appears.

Step 5

Click the Assign Destination Cluster Nodes button to select the destination virtual machine for each source node.

Note:
If DHCP is in use on your source node, the destination node will also be configured to use DHCP, and you will not have the option of changing your network settings in this wizard.

The Configure Destination Cluster window appears.

Step 6

Select a virtual machine, click Next Node to go to the next node in the cluster, and select another virtual machine for the destination virtual machine, and click Done.
Note:
If there is more than one node in the cluster, repeat these steps - (assigning VM, and entering new IP/hostname settings, if needed) for each node in the source cluster.

Step 7

Click Next. The Configure NTP/SMTP Settings window appears.

Step 8

Enter the Network Time Protocol (NTP) server settings to be applied to the migration nodes when the migration task runs, and optionally, enter the SMTP server settings.
Important:
In a proxy TFTP setup, if a network migration is performed "off-cluster", you need to manually configure the new hostname and IP address of that off-cluster in the proxy TFTP. Off-cluster refers to situations where TFTP functionality is being performed by a proxy that is not part of that specific Unified Communications Manager cluster. During a migration, that TFTP server (that is not part of the cluster) is not modified. If you want to change the hostname or IP address of that server, you must do it as a separate process and not with Cisco Prime Collaboration Deployment.

Step 9

Click Next. The Define DNS Settings window appears.

Step 10

To change the DNS setting for a node, select the node or nodes from the table and click Assign DNS Settings. Enter the primary and secondary DNS, then click OK to apply the changes.
Important:
You cannot change the domain name during a migration.

Step 11

Click Finish.
The changes are saved and a row is added to the clusters table to reflect the new migration cluster that you have created.

Upgrade and Migration

For information about supported releases for Cisco Prime Collaboration Deployment, see Supported Releases.

For information about direct upgrade paths, see the Cisco Unified Communications Manager Software Compatibility Matrix at the following URL: Click Here .

For upgrade and migration information that is not covered in the above references (for example, upgrading from Release 4.x), see the Drive to Collaboration site at the following URL: Click Here .

- Updates to Supported Releases

- DRS CLI Command

Updates to Supported Releases

Supported Releases of Each Task in Cisco Prime Collaboration Deployment

Product and Functions

Cluster Discovery

Migration to 10.x Cluster

Upgrade Task

(Upgrade Application Server or Install COP Files)

Restart Task

Switch Version Task

Fresh Install a New 10.x Cluster

Readdress Task

(Change Hostname or IP Addresses for One or More Nodes in a Cluster)

Cisco Unified Communications Manager

6.1(5), 7.1(3), 7.1(5), 8.0(1), 8.0(2), 8.0(3), 8.5(1), 8.6(1), 8.6(2), 9.0.(1), 9.1(1), 9.1(2), 10.0(1), 10.5(1), 10.5(2)

6.1(5), 7.1(3), 7.1(5), 8.0(1), 8.0(2), 8.0(3), 8.5(1), 8.6(1), 8.6(2), 9.0.(1), 9.1(1), 9.1(2), 10.0(1)

8.6(1), 8.6(2), 9.0.(1), 9.1(1), 9.1(2), 10.0(1), 10.5(1), 10.5(2)

8.6(1), 8.6(2), 9.0.(1), 9.1(1), 9.1(2), 10.0(1)

8.6(1), 8.6(2), 9.0.(1), 9.1(1), 9.1(2), 10.x

10.x, 10.5(1), 10.5(2)

10.x

Cisco Unified Presence

8.5, 8.6

8.5(4), 8.6(3), 8.6(4), 8.6(5)

8.6(3), 8.6(4), 8.6(5)

8.6(3), 8.6(4), 8.6(5)

8.6(3), 8.6(4), 8.6(5)

—

—

IM and Presence Service

9.0(1), 9.1(1), 10.x

9.0(1), 9.1(1), 10.x

9.0(1), 9.1(1), 10.x

9.0(1), 9.1(1), 10.x

9.0(1), 9.1(1), 10.x

10.x, 10.5(1), 10.5(2)

Not Supported

Cisco Unified Contact Center Express

8.5.1, 9.0, 9.0.2, and 10.x

Not Supported

9.0(2), 10.x

9.0(2), 10.x

9.0(2), 10.x

10.5(x)

10.5(x)

Cisco Unity Connection

8.6.1, 8.6.2, 9.x and 10.x

Not Supported

From 8.6(x) to 8.6(x)

From 8.6(x) to 9.x

From 9.x to 9.x

From 10.0(1) to 10.x

8.6(1), 8.6(2), 9.x, 10.x

8.6(1), 8.6(2), 9.x, 10.x

10.5(x)

10.5(x)

Note

The supported releases table does not include the Engineering Special (ES)/ Service Update (SU) versions. To upgrade or migrate to ES/SU versions, see the release notes of the corresponding product, such as IM and Presence, Cisco Unified Communications Manager, and Unity.

The following table lists the supported paths of restricted and unrestricted versions in Cisco Prime Collaboration Deployment.

Supported Paths

From

To

Task Types Supported

Export Restricted (K9)

Export Restricted (K9)

Supported for Upgrade paths

Supported for Migration paths

Export Restricted (K9)

Export Unrestricted (XU)

Not supported for Upgrade paths

Supported for Migration paths

Export Unrestricted (XU)

Export Restricted (K9)

Not supported for Upgrade paths

Not supported for Migration paths

Export Unrestricted (XU)

Export Unrestricted (XU)

Supported for Upgrade paths

Supported for Migration paths

DRS CLI Command

Following is the new CLI command that is available in Cisco Unified Communications Manager Release 10.5(2):

utils disaster_recovery show_registration SERVER—Shows the features that you need to back up. For example, if you want to back up PCD, choose PCD from the feature list. The SERVER field is mandatory.

For more information, see the DRS documentation for Cisco Unified Communications Manager, at Click Here .

Chapter 3. Important Notes

- Cisco Unified Communications Manager Upgrades to Release 10.5(2) using Prime Collaboration Deployment

- Conflicting Upgrade Path for Release 6.0(1)

- Deployment

- DNS

- Install Tasks

- ISO File Permissions for Install and Migration Tasks

- Migration Requirements

- New Upgrade is not Allowed While Another Upgrade is Running

- Readdress

- Upgrades

- Virtualization Software License Feature Level Compatibility

Cisco Unified Communications Manager Upgrades to Release 10.5(2) using Prime Collaboration Deployment

Follow these guidelines if you are using Cisco Prime Collaboration Deployment to upgrade Cisco Unified Communications Manager to release 10.5(2):

- PCD upgrades or non-PCD upgrades from release 10.0(1) or 10.5(1) are supported. Migrations from 10.0(1) or 10.5(1) using Prime Collaboration Deployment are not supported. For definitions of migrations and upgrades, see the latest release of the Cisco Prime Collaboration Deployment Administration Guide. For additional details, see CSCur99079.

- Before upgrading to release 10.5(2), you must download and install the COP file ciscocm.version3-keys.cop.sgn on every node in the cluster prior to upgrading. This Cisco Options Package (COP) file has the RSA keys that are required to validate the upgrade.

- If you are upgrading from 6.1(5), 7.x, 8.x, 9.x, or 10.x, you must disable the time synchronization between the VM instance and the ESXi. To disable the time synchronization issue, follow the instructions at the following URL:

Click Here

An alternative method is to configure the ESXi server and the Cisco Unified Communications Manager publisher node to point to the same NTP server.

This resolves CSCur94973.

You can download COP files from the following location on cisco.com: Downloads > Products > Unified Communications > Call Control > Unified Communications Manager (CallManager) > Cisco Unified Communications Manager Version 10.5

Conflicting Upgrade Path for Release 6.0(1)

This update resolves CSCup45479.

The document Migration to Cisco Unified Communications Manager Release 10.5(1) Using Prime Collaboration Deployment contains conflicting information if you are upgrading from Cisco Unified Communications Manager release 6.0(1). If you are upgrading from that release, you must first upgrade to release 6.1(2). From 6.1(2), you can then upgrade to 6.1(3), then 6.1(5), then 10.5(1) through Cisco Prime Collaboration Deployment.

Deployment

Cisco only supports virtualized deployments of Cisco Prime Collaboration Deployment. Cisco Prime Collaboration Deployment is deployed using an OVA that contains the pre-installed Cisco Prime Collaboration Deployment application. This OVA is obtained with a licensed copy of Cisco Unified Communications Manager Release 10.5(1) software. For information about how to extract and deploy the PCD_VAPP.OVA file, see topics relating to the installation of Cisco Prime Collaboration Deployment in the Cisco Prime Collaboration Deployment Administration Guide.

For more information about the deployment of Cisco Prime Collaboration Deployment in a virtualized environment, see:

Click Here

DNS

If you require DNS on a Cisco Prime Collaboration Deployment system, be sure to administer the DNS during Cisco Prime Collaboration Deployment install.

Install Tasks

A Cisco Prime Collaboration install task assumes that all cluster nodes are being installed at the same time. You can not, for example, use a migration task to migrate a Cisco Unified Communications Manager Release 6.1(1) cluster to Release 10.5(1) and then use a separate install task to add IM and Presence Service nodes to the same cluster.

ISO File Permissions for Install and Migration Tasks

Before you perform an install or migration task, copy your ISO files to the fresh_install folder and make sure that those files contain the following permissions: rw-r-r.

Migration Requirements

This information addresses CSCum18394.

For a migration from Release 10.0(1) to Release 10.5(1) to be successful, you must upgrade all source cluster Cisco Unified Communications Manager nodes to 10.0(1)SU1, at a minimum, before using Cisco Prime Collaboration Release 10.5(1) to perform a migration.

New Upgrade is not Allowed While Another Upgrade is Running

This information addresses CSCui69450.

If you start a new upgrade task before the previous upgrade task finishes, you are notified immediately that this scenario is not supported.

Readdress

Readdress Caveats

- Readdress tasks that require gateway and subnet changes may cause the readdress task to fail.

Cisco Prime Collaboration Deployment can lose the communication with Cisco Unified Communications Manager due to network issues, even after the readdress task is completed successfully on the Cisco Unified Communications Manager. Users may need to complete post network change steps outlined in the Changing the IP Address and Hostname for Cisco Unified Communications Manager Guide before proceeding to the next step.

- Cisco Unified Communications Manager IM and Presence Service readdress is not available on Cisco Prime Collaboration Deployment. The Readdress feature can only be used to change hostnames and IP Addresses for Cisco Unified Communications Manager servers. In a cluster with both Cisco Unified Communications Manager and IM and Presence Service nodes, the readdress feature can be used to change the Cisco Unified Communications Manager server hostname and IP addresses, but not the IM and Presence Service nodes for that cluster.

Upgrades

For information about upgrading Cisco Prime Collaboration Deployment, as well as requirements for hardware and software, see the latest release of the Cisco Prime Collaboration Deployment Administration Guide here Click Here .

Cisco Prime Collaboration Deployment supplements but does not replace native application install and upgrade functionality. Cisco Prime Collaboration Deployment does not have 100% feature parity with native install and upgrade functionality. When troubleshooting upgrade or install issues on Cisco Unified Communications Manager or Cisco Unified Communications Manager IM and Presence Service nodes, the upgrade (or install) logs will need to be retrieved from node being upgraded. Use normal upgrade and install troubleshooting actions.

Upgrade Caveats

Not all versions of supported applications can be upgraded to Release 10.x using Cisco Prime Collaboration Deployment. See Supported Releases for more information.

Virtualization Software License Feature Level Compatibility

Cisco Prime Collaboration Deployment is not compatible with all license feature levels of VMware vSphere ESXi, as some license feature levels do not enable required VMware APIs.

The following are compatible with Cisco Prime Collaboration Deployment:

- Cisco UC Virtualization Foundation (appears as "Foundation Edition" in vSphere Client)

- VMware vSphere Standard Edition, Enterprise Edition, or Enterprise Plus Edition

- The evaluation mode license feature level

The following are not compatible with Cisco Prime Collaboration Deployment:

- Cisco UC Virtualization Hypervisor (appears as "Hypervisor Edition" in vSphere Client)—preloaded on Cisco Business Edition 6000 and Business Edition 7000

- VMware vSphere Hypervisor Edition

Chapter 4. Caveats

- Bug Search Tool

- Resolved Caveats

- Resolved Caveats for SU1

- Open Caveats

Bug Search Tool

The system grades known problems (bugs) according to severity level. These release notes contain descriptions of the following bug levels:

- All severity level 1 or 2 bugs

- Significant severity level 3 bugs

- All customer-found bugs

You can search for open and resolved caveats of any severity for any release using the Cisco Bug Search tool, an online tool available for customers to query defects according to their own needs.

To access the Cisco Bug Search tool, you need the following items:

- Internet connection

- Web browser

- Cisco.com user ID and password

Follow these steps to use Cisco Bug Search tool:

1. Access the Cisco Bug Search tool: Click Here .

2. Log in with your Cisco.com user ID and password.

3. If you are looking for information about a specific problem, enter the bug ID number in the Search for: field, and click Go.

Tip

Click Help on the Bug Search page for information about how to search for bugs, create saved searches, and create bug groups.

Resolved Caveats

You can find the latest resolved caveat information for Cisco Prime Collaboration Deployment by using the Bug Search tool, an online tool available for customers to query defects according to their own needs.

Tip

You need an account with Cisco.com to use the Bug Search tool to find open and resolved caveats of any severity for any release.

See Click Here .

Resolved Caveats for SU1

Cisco Prime Collaboration Deployment Release 10.5.3 SU1 provides fixes to the following defects:

- CSCuv33259—Crashed status while discovering large clusters with NAT

- CSCus76770—Fix usage of SSL in JAVA to address poodle vulnerability

Open Caveats

Caveat

Severity

Product

Headline

CSCuo72650

3

Cisco Unified Communications Manager (CallManager)

ENG:CUCM:Wrong Platform API version in the UK locale

CSCun30432

4

Cisco Unified Communications Manager (CallManager)

UCMAP: No proper error msg while cancelling the install task.

CSCun08515

4

Cisco Unified Communications Manager (CallManager)

Cluster discovery should verify node status marked as Publisher function.

CSCum58350

4

Cisco Unified Communications Manager (CallManager)

Manual start tasks should have edit action.

CSCul35818

5

Cisco Unified Communications Manager (CallManager)

In Upgrade Task, seeing green check marks where they shouldn't be.

CSCuo05500

5

Cisco Unified Communications Manager (CallManager)

Edit ESXi Host in Cisco Prime Collaboration Deployment results in IP address used in Hostname/IP address field

CSCuo08038

4

Cisco Unified Communications Manager (CallManager)

Cisco Prime Collaboration Deployment Cluster Creation Role Checks for CUC and UCCX

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: Click Here . 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)