Table Of Contents
Cisco Prime Collaboration Manager 1.2
Release Notes
New Features and Enhancements
Limitations
Known Issues
Related Documentation
Obtaining Documentation and Submitting a Service Request
Cisco Prime Collaboration Manager 1.2
Release Notes
August 17, 2012, OL-26268-01
Cisco Prime Collaboration Manager is a video service-assurance and management system that helps you to monitor, troubleshoot, and report the Cisco TelePresence sessions. It provides service and network operators with a real-time, unified view of all Cisco TelePresence sessions.
Prime CM also provides immediate visibility into the associated media paths of each session, and isolates the source of problems. When Cisco Mediatrace-capable devices are deployed in the network, Prime CM provides network path visibility, down to the granularity of video flow statistics.
Prime CM:
•
Supports timely, end-to-end visibility and isolates video-related issues for sessions, endpoints, and the network.
•Reduces time to troubleshoot and recover from service-affecting problems.
•Provides detailed analysis of the media path with critical fault and performance statistics that enable you to isolate network devices that cause service degradation.
•Validates large-scale deployments through comprehensive inventory, health, and status of Cisco TelePresence endpoints, as well as service and network infrastructure devices.
•Delivers reports that allow operators to track usage and problem history.
For detailed information about Prime CM features, see the Cisco Prime Collaboration Manager 1.2 User Guide.
New Features and Enhancements
The following are the new features, enhancements, and changes in Prime CM 1.2:
•End-to-end visibility, real-time troubleshooting, and inventory support for Cisco TelePresence and personal video endpoints.
•360° Session View of pertinent data about the endpoint, infrastructure devices, alarms, and call records.
•Assessment of a network's readiness to deploy Cisco Video or TelePresence Systems, using the Video SLA Assessment Agent (VSAA or VSA agent).
•Set of predefined and user-defined groups on all pages (Session Monitoring, Endpoint Monitoring, and Device Inventory pages; Alarm and Event browser) to easily access and manage a single device, or a group of devices.
•Customization of endpoint visibility to enable you to determine the monitoring level operation for endpoints.
•Root cause analysis of call quality issues identified during troubleshooting, including reports on configuration changes that you have made versus the Cisco-recommended best practice.
•Application diagnostics for troubleshooting Mediatrace statistics, and display of root causes and recommendations.
•Customizable dashboards, new dashboards (Endpoints and Infrastructure), and new dashlets to give you at-a-glance status of health and utilization of endpoints and infrastructure devices.
•Customization and configuration of multiple threshold values corresponding to different event severity levels.
•Past session statistics, including maximum and average diagnostic values such as maximum jitter, maximum packet loss, and maximum latency.
•Viewing of session details for multiple days.
•Cross-launch of all managed devices from the Video Collaboration dashboard, Device Inventory page, and Endpoint Monitoring page.
•Scheduling and other options for managing and monitoring jobs.
•Deeper visibility on Medianet-enabled networks into flow-related statistics at network nodes (using Performance Monitor).
•Verification of credentials when device discovery fails because of incorrect credentials.
•Management of clusters or multiple servers for Cisco TelePresence Manager (CTS-Manager) or Cisco TelePresence Management System (Cisco TMS) only, to enable uninterrupted monitoring of sessions.
•New, out-of-box reports that can be filtered, and a reporting framework that includes scheduling.
•New licensing information for Prime CM 1.2 deployment.
•Application diagnostics for troubleshooting IP Service Level Agreements (IP SLA) statistics, and display of root causes and recommendations.
•Support for Internet Explorer and additional versions of the Firefox browser. See Cisco Prime Collaboration Manager 1.2 Quick Start Guide.
For more information, see the following in the Cisco Prime Collaboration Manager 1.2 User Guide:
•"Introducing Cisco Prime Collaboration Manager"—For links to relevant topics that describe these new and enhanced features.
•"Usage Scenarios" and "Best Practices"—To help you to use Prime CM effectively.
Limitations
•Cisco Prime Collaboration Manager supports only the default e-mail template for the Booking Confirm e-mail in Cisco TMS. The session import feature will not work, if the default e-mail template is not used.
•If the IP address of a Cisco TelePresence System (CTS) endpoint is changed, Prime CM raises two alarms: Unregistered and Unreachable. The Prime CM server clears the Unregistered alarm within a few minutes, but the Unreachable alarm is not cleared.
You can clear the Unreachable alarm manually; otherwise, the Prime CM server clears the alarm after 24 hours, if there are no updates.
•When you have scheduled a multipoint session using the Cisco TelePresence Server but have not entered either the Call-out or Call-in Match parameter for the endpoint in the Cisco TelePresence Server, Prime CM does not change the status of the scheduled multipoint session to in-progress.
Whenever you schedule a session using the Cisco TelePresence Server, we recommend that you add the endpoint in the Cisco TelePresence Server along with the Call-out and Call-in Match parameter details. Also, the endpoint name in the Cisco TelePresence Server must be the same in the CTS-Manager, if CTS-Manager is used as the management system in your network.
•The Prime CM Session Monitoring feature does not support endpoints, which are configured with multiple lines in Cisco Unified CM. However, you can manage these endpoints in the Prime CM inventory database.
•On the Session Monitoring page, Prime CM does not display past session information and session statistics for Cisco Cius and Cisco IP phones. This applies only if you have set real-time visibility to Full for Cisco Cius and Cisco IP phones.
•If the IP address of a DHCP-enabled endpoint registered to Cisco Unified CM changes, Prime CM may not be able to automatically discover this endpoint. The endpoints registered to Cisco TelePresence Video Communication Server (Cisco VCS) are always automatically discovered when their IP address changes.
•The endpoints registered to the Cisco VCS Expressway may be displayed as unknown endpoints in the Session Topology pane. This is because these endpoints are behind the firewall.
•Only the Peripherals and Session details are displayed on the Session Monitoring page, if there is a session between a TelePresence and an audio endpoint (such as a WebEx call). This session is identified as an Inlocalconference session.
•The endpoint statistics may not be displayed in this scenario:
a. A TelePresence endpoint (endpoint A) calls another TelePresence endpoint (endpoint B).
Details for all endpoint statistics are displayed on the Session Monitoring page.
b. The same endpoint A conferences with another endpoint (endpoint C).
Details for all endpoint statistics are displayed on the Session Monitoring page.
c. Endpoint A conferences again with another endpoint (endpoint D) and disconnects from endpoint C.
Details for the endpoint statistics are displayed only for endpoints C and D. Details might not be displayed for endpoint B.
•Cross-launching Cisco Prime LMS 4.1 and 4.2 from Prime CM fails if the managed IP address of the network device is different in these applications. You must install the Cisco Prime LMS patch to fix this problem. See CSCtt98949 for details on the patch.
•The troubleshooting workflow is not supported between an endpoint and Cisco Multipoint Control Units (MCU); that is, you cannot troubleshoot from an endpoint to Cisco MCU and vice versa.
•If an endpoint is in the Unknown state, you cannot troubleshoot from or to this endpoint.
•Audio statistics are not displayed for Cisco TelePresence 500, 1000, or 3000 series when there is a session between
–Cisco TelePresence 500, 1000, and/or 3000 series
and
–C and/or Ex series.
Only video statistics are displayed for Cisco TelePresence 500, 1000, and 3000 series. Peripheral, session, and system details are displayed for all endpoints.
•On the Session Monitoring page:
–Multipoint sessions using Cisco TelePresence Server 2.2 (1.0) are displayed as static sessions when the call is not configured as permanent on the Cisco TelePresence Server.
–Multipoint sessions using Cisco TelePresence Server 2.2 (1.48) are displayed as ad hoc sessions when the call is configured as permanent on the Cisco TelePresence Server.
•On Cisco TelePresence C series (running TC 4.1 software), the HTTP username, which you define for the Cisco Prime Collaboration Manager application, must be in lowercase.
•For Cisco Cius devices:
–Audio statistics are not displayed when there is a session between CTS endpoints and Cisco Cius.
–The access point is not displayed for a Cisco Cius endpoint in the topology view during the troubleshooting workflow.
•Prime CM proactively monitors the health of the Prime CM server every hour. The Prime CM server is restarted at 1:23 a.m. whenever:
–The consumed swap space exceeds 85% of its limit.
–The out-of-memory exception occurs.
The Prime CM server is back online within 5 minutes.
Make sure that you have configured the appropriate time zone on the Prime CM server. See "Configuring Time Zone and Refresh Interval" in the Cisco Prime Collaboration Manager 1.2 User Guide.
•If you have observed that the Prime CM server disk space has been utilized more than expected, contact Cisco Technical Assistance Center (TAC) with the reference bug ID CSCua45317.
Known Issues
Table 1 lists the Open Caveats in the Prime CM 1.2 release.
Click the identifier to view the impact and workaround for the caveat. This information is displayed in the Bug Toolkit. You can track the status of the open caveats using the Bug Toolkit.
Table 1 Open Caveats in the Prime CM 1.2 Release
Identifier
|
Description
|
CSCts26936
|
Prime CM will not list sessions among:
•CTS 500, 1000, or 3000 series TelePresence systems that are in the Unmanaged state
and
•C or Ex series TelePresence systems that are in the Managed state.
Also, CTS 500, 1000, or 3000 series TelePresence systems are registered with Cisco Unified CM, and Cisco C or Ex series TelePresence systems are registered with Cisco VCS.
|
CSCtt34785
|
If a device is in the Inaccessible state, Prime CM does not discover that device during the troubleshooting workflow.
|
CSCtz74355
|
Credential verification fails for Cisco Unified CM if the JTAPI password contains semicolon (;) or equal (=) characters.
|
CSCua07501
|
On the Reports and Endpoint Monitoring pages, an invalid endpoint name is displayed for Cisco Cius and Cisco IP phones (89xx/99xx).
|
Related Documentation
The Cisco Prime Collaboration Manager 1.2 Documentation Overview provides a list of all Cisco Prime Collaboration Manager 1.2 guides.
Note We sometimes update the documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates.
Click here to access the Cisco Prime Collaboration Manager training videos.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as an RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS Version 2.0.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
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: www.cisco.com/go/trademarks. 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)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2012 Cisco Systems, Inc. All rights reserved.
Feedback
