Cisco Prime Collaboration Assurance Guide - Advanced, 10.0
Prime Collaboration Dashboards
Downloads: This chapterpdf (PDF - 1.48MB) The complete bookPDF (PDF - 8.14MB) | Feedback

Prime Collaboration Dashboards

Contents

Prime Collaboration Dashboards

Prime Collaboration Dashboards

The Prime Collaboration dashboards provide consolidated information for devices, applications, and endpoints. With these dashboards, you can:
  • Monitor all endpoints for a user using a single interface.
  • Determine service experience for all endpoints.

The data in dashboards is displayed based on your Prime Collaboration deployment - Standard or Advanced (MSP or Enterprise) and endpoints licenses (Mass, Midrange, single-codec, and/or High-end).

For data to be populated in the dashboards, you must complete the following tasks:
  • Discover the devices
  • Import the sessions (for Session-related dashboards)
  • Poll the devices

The Prime Collaboration dashboards are:

Dashboard

Description

Prime Collaboration Deployment

End-Users Impact

Information about sessions and alarms.

Prime Collaboration Advanced

Endpoints Utilization

Information about endpoints and their utilization.

Prime Collaboration Advanced

Infrastructure

Information about conferencing devices, management devices, call and session devices, and video ports.

Prime Collaboration Advanced

Topology

Provides a logical top-level view of your IP telephony network. This view focuses on call control relationships.

Prime Collaboration Advanced

UC Performance Monitor

Provides details on critical performance metrics of each managed element.

Prime Collaboration Advanced and Prime Collaboration Standard


Note


  • The Enterprise dashboards (End-Users Impact, Endpoints Utilization, Infrastructure, Topology, Contact Center Topology, depending on the licenses you have) in Prime Collaboration do not filter content by default through the global customer selection field.
  • If you select another customer through global selection the user interface will refresh and the home page showing the Customer Summary dashboard appears.
  • To change the customer you need to click the customer name from the Customer Summary dashboard.

You can view data either as a chart or in a tabular format. By default, reports are displayed as charts that are interactive; that is, you can click on the data to launch the associated page. When you view a report in the tabular format, you can export data in the CSV format.

In the dashboard, you can view data for:

  • A day—Data collected from 00:00:00 hours to current time.
  • A week—Data collected during the last seven days including today, starting from 00:00:00 hours.
  • Four weeks—Data collected during the last 28 days including today, starting from 00:00:00 hours.

    Note


    On all pages, the time displayed is the Prime Collaboration server time. In the converged mode, Assurance server time will be displayed.


Prime Collaboration Advanced Dashboards

End-Users Impact Dashboard

The End-Users Impact dashboard helps you to identify the most impacted TelePresence endpoints, sessions with alarms, and poor call quality locations.

It contains the following dashlets:

Top 10 Impacted TelePresence Endpoints with Alarms

Displays the top 10 TelePresence endpoints with alarms. The alarm count includes alarm with the severity Cleared.

You can view the graph for endpoints and service infrastructure devices.

You can click on the bar chart to launch the Alarm Browser to view all endpoints and service infrastructure devices that have this specific alarm type.

Sessions with Alarms

Displays the number of in-progress sessions with alarms.

You can launch the 360 Session View from this dashlet.

Top 10 TelePresence Endpoints with Call Quality Alarms

Displays the top 10 endpoints with call quality alarms (for packet loss, jitter, and latency).

You can click on the alarm data to launch the Alarms page.

Endpoints Health Summary

Provides a summary of the status of all the endpoints in the network. You can view a summary for hard endpoints (such as E20, Phones, and CIUS), soft clients (Cisco Unified Personal Communicator, Cisco IP Communicator, iPhone, Android, Cisco Jabber, and Client Services Framework [CSF]), and Jabber endpoints separately also.

The dashboard displays the summary as a pie chart or table. It provides information about the endpoints in the following modes:

  • Unregistered—Endpoints that are not registered with Cisco Unified CM and VCS. Displayed in red. The count displayed for “Unregistered from UCM” includes the devices that are in SRST mode and Energy Save mode. You can click on the SRST mode and Energy Save mode data to launch the phone reports.

    Note


    If all phones with a single SRST reference are in Unregistered state with a status reason code other than “energyWisePowerSavePlus,” they are classified as being in SRST mode.


  • Registered—Endpoints that are registered with Cisco Unified CM and VCS. Displayed in green. The count displayed for “Registered Hard Phones” includes the TelePresence endpoints.
  • Unknown—Endpoints that are in Unknown state (registration status of the endpoints is unknown). Displayed in blue.

Click the pie chart to view the Endpoint Health Troubleshooting window, which has the links to the following pages:

  • Endpoint Diagnostics
  • Phone Report
  • UCM Troubleshoot
  • VCS Troubleshoot

The phone counts shown in the UC Topology View, Diagnostics Summary View, and Endpoint Health Summary dashlet will be in synchronized, with a maximum of 10 minutes delay. You can schedule cluster discovery to trigger this synchronization manually, if required. Cluster discovery will also resynchronize the registration status for all phones. If cluster discovery is not scheduled manually, synchronization takes place as part of nightly cluster discovery.

Top 5 Call Failure Locations

Displays the top five locations that experienced the most call failures in the last hour. Prime Collaboration aggregates the available CDR data at fixed time intervals and displays it in this dashlet.

The top five locations are chosen taking into account all the Cisco Unified CM clusters that are added in Prime Collaboration. For example, if three Cisco Unified CM clusters are added in Prime Collaboration, and each cluster has 30 locations, then the top five locations are chosen from among these 90 locations.

If there are fewer than five locations that are experiencing call failures, only those locations are shown. If the percentage of failed calls in a location is less than 0.5, the location is ignored.

You can click the bubble in the Z axis to view the following details:

  • Cluster
  • Failed Calls
  • Total Calls

Click Troubleshoot to open the Call Failure Troubleshooting page.

Top 5 Poor Voice Call Quality Locations

Provides information about the top five locations that experienced the poorest call quality in the last hour.

The X axis shows the location. The Y axis shows the number of poor calls. The Z axis shows the percentage of poor calls, represented as bubbles. If the percentage of failed calls in a location is less than 0.5, the location is ignored.


Note


TelePresence call details are not included in this dashlet.


Click the bubble in the Z axis to view the following details:

  • Cluster
  • Poor calls
  • Total calls

Click Troubleshoot to open the Call Quality Troubleshooting page. The Call Quality Trend pane shows the poor calls for the last 24 hours, per location. The Impacted Devices pane shows the devices that were involved in the call for that particular hour. Click any bar in the Impacted Devices pane to open the Call Details pane.


Note


To view the call details, phone access switch must be monitored or discovered from the phone using CDP neighbor discovery.


Endpoints Utilization Dashboard

This dashboard helps you to identify the No Show endpoints, most commonly used and least used TelePresence endpoints, and endpoint models.

It contains the following dashlets:


Note


Mass endpoint details are not included in the TelePresence Utilization reports. Polycom, which is a midrange TelePresence endpoint, is included in these reports.


Top 10 Utilized TelePresence Endpoints

Displays the top 10 utilized endpoints in your network.

You can view the graph either by duration or session.

  • By duration—The utilization is by usage hours. For example, if the utilization is shown as 0.634 hours, it means the endpoint has been utilized for approximately 38 minutes (0.634 x 60).
  • By session—The utilization is by number of sessions. Here, only completed sessions are considered. If the number of sessions is one, the value of the x-axis is displayed in decimals (0.2, 0.4...). If the number of sessions is more than one, the value of the x-axis is displayed in absolute numbers (1, 2, 3...).

You can click on the bar chart to launch the All Sessions Summary Report for the selected endpoint.

Top 10 Utilized TelePresence Endpoint Models

Displays the utilization, based on specific endpoint models.

You can view the data:

  • For a day—The maximum utilization is ten hours. That is, if the utilization is 120 minutes for a day, the average utilization for a day is 20% ((120/[10*60])*100).
  • For a week—The maximum utilization is 50 hours. That is, if the utilization is 1500 minutes for a week, the average utilization for a week is 50% ((1500/[50*60])*100).
  • For four weeks—The maximum utilization is 200 hours. That is, if the utilization is 10,800 minutes for a month, the average utilization for a month is 90% ((10,800/[200*60])*100).

You can click on the bar chart to launch the Endpoint Utilization Report for the selected endpoint model.

Top 10 No Show TelePresence Endpoints

Displays the top 10 endpoints that did not participate in the scheduled sessions.

You can click on the bar chart to launch the No Show Sessions Summary Report for the selected endpoint.

Least 10 Utilized TelePresence Endpoints

Displays the least 10 utilized endpoints in your network.

You can view the graph either by duration or session.

  • By duration—The utilization is by usage hours. For example, if the utilization is shown as 0.634 hours, it means, the endpoint has been utilized for approximately 38 minutes (0.634 * 60). If the utilization is zero, this is not shown in the bar chart. To see this data, you should launch the tabular format.
  • By session—The utilization is by number of sessions. Here, only completed sessions are considered. If the number of sessions is one, the value of the x-axis is displayed in decimals (0.2, 0.4...). If the number of sessions is more than one, the value of the x-axis is displayed in absolute numbers (1, 2, 3...).

You can click on the bar chart to launch the All Sessions Summary Report for the selected endpoint.

Least 10 Utilized TelePresence Endpoint Models

Displays the utilization, based on specific endpoint models. If the utilization is zero, this is not shown in the bar chart. To see this data you should launch the tabular format.

You can view the data:

  • For a day—The maximum utilization is ten hours. That is, if the utilization is 120 minutes for a day, the average utilization for a day is 20% ((120/[10*60])*100).
  • For a week—The maximum utilization is 50 hours. That is, if the utilization is 1500 minutes for a week, the average utilization for a week is 50% ((1500/[50*60])*100).
  • For four weeks—The maximum utilization is 200 hours. That is, if the utilization is 10,800 minutes for a month, the average utilization for a month is 90% ((10,800/[200*60])*100).

You can click on the bar chart to launch the Endpoint Utilization Report for the selected endpoint model.

Number of TelePresence Sessions

Displays the number of in-progress and completed sessions. Click on the chart to launch the Session Detail report for a particular session.

The session data is aggregated for every two hours. For example, on a day, assume that you had only two sessions. The first session started at 01:00 hours and ended at 03:00 hours, and the second session started from 02:20 hours and ended at 05:50 hours.

The data is displayed as:

  • 0:00—Zero
  • 2:00—1; an in-progress session from 01:00 to 03:00 is displayed between 0:00 and 02:00 hours.
  • 4:00—2; a completed session from 01:00 to 03:00 and an in-progress session from 02:20 to 05:50 are displayed between 02:00 and 04:00 hours.
  • 6:00—1; a completed session from 02:20 to 05:50 is displayed between 04:00 and 06:00 hours.
  • 8:00—Zero; no sessions occurred between 06:00 and 08:00 hours.
  • 10:00—Zero
  • 12:00—Zero
  • ...
  • 24:00—Zero; no sessions occurred between 22:00 and 24:00 hours.

You can view the data as a chart or in a tabular format. You can also export the data into an Excel spreadsheet.

Infrastructure Dashboard

This dashboard provides information about management devices, conferencing devices, video ports, and call and session control devices. It also provides an infrastructure and service health summary.

It contains the following dashlets:

Infrastructure Health Summary

Displays the number of infrastructure devices with and without alarms. In addition, you can also view the number of devices, based on the alarm severity.

You can click on the total device data to launch the Device Inventory page. You can also click on the devices with alarms data to launch the Alarms and Events page.

By default, the information is displayed in a pie chart. The pie chart is updated when the UI is refreshed. You can change this display to a table.

Top 10 Utilized Conferencing Devices

Displays the top 10 utilized conferencing devices.

You can view the average and peak usage of the ports in the conferencing device.

The utilization is shown as 100% even if the utilization is more than 100%.

All data is in percentage. You can click on any data to launch the conferencing device utilization report.

Video Ports Utilization Summary

Displays the video ports utilization of the conferencing devices.

You can view the utilization as:

  • Percentage
  • Actual numbers

Click the utilization data under the column Video Ports Used to launch the Session Monitoring page.

You can view the following details:

  • Name and IP Address—You can click on the device name or IP address to launch its application in a browser. Rest your mouse pointer over the Name column and click the quick view icon to view the:
    • Media Processing Engine, Call Control Process, Conference Manager, Security Key Exchange, and Media Switching status.
    • CPU and memory utilization.
  • Device Type.
  • Video Ports Used.

Management Devices

Displays the management devices in your network.

You can see the following details:

  • Status—Displays whether the device is normal, suspended or contains errors. You can click on the status icon to launch the Alarm browser. This icon is displayed when there is a critical service infrastructure, unreachable, or inaccessible alarm.
  • Name and IP Address—You can click on the device name or IP address to launch it in a browser. Rest your mouse pointer over the Name column and click the quick view icon to view the:
    • Database, LDAP server, Cisco Unified CM, calendar service, room phone UI, multipoint conference, and WebEx status.
    • CPU and memory utilization. For Cisco Multipoint Control Unit (MCU) systems, if the CPU utilization is less than 1%, the value is displayed as zero. For Cisco TelePresence Server (TS), these details are not displayed and you cannot launch quick view.
  • Device Type
  • Last Device Poll—Displays the date and time when the device statuses were last polled by Prime Collaboration.

Conferencing Devices

Displays the conferencing devices in your network.

You can see the following details:

  • Status—Displays whether the device is normal, suspended or contains errors. You can click on the status icon to launch the Alarm browser. This icon is displayed when there is a critical service infrastructure, unreachable, or inaccessible alarm.
  • Name and IP Address—You can click on the device name or IP address to launch it in a browser. Rest your mouse pointer over the Name column and click the quick view icon to view the:
    • Media Processing Engine, Call Control Process, Conference Manager, Security Key Exchange, and Media Switching status (for Cisco TelePresence Multipoint Switch only).
    • Audio Load, Video Load, Media Load, Video ports in use, Battery Status, Temperature Status and Voltage status (for MCU only).
    • CPU and memory utilization.
  • Last Device Poll
  • Device Type
  • Video Ports Used
  • Audio Ports Used
  • Master Conductor

Prime License Manager

The licensing information for voice is categorized under Prime License Manager licenses. This dashlet displays usage of all UC applications licenses (CUCM and Unity Connection). Whenever the ELM and Unified CM co-reside, you need to activate the Enterprise License Management Resource API manually. For more information, see the Setting up Devices for Prime Collaboration Assurance wiki.

You can see the following details:

  • License Type—Displays the different types of licenses available, such as, CUWLPremium, CUWLStandard, UCM Advanced, and so on.
  • Product Type—The product type to which the license type belongs.
  • Status—The status for a license type - valid, violated, demo.
  • Remaining—Count of licenses available or unused, for each license type.

This dashlet is populated once, after nightly CDT discovery is completed, by default. This dashlet is also refreshed after every CDT discovery.

Call and Session Control Devices

Displays the call and session control devices in your network.

You can see the following details of these devices:

  • Status—Displays whether the device is normal, suspended or contains errors. You can click on the status icon to launch the Alarm browser.
  • Name and IP Address—You can click on the device name or IP address to launch it in a browser. Rest your mouse pointer over the Name column and click the quick view icon to view the:
    • Cisco DB, Cisco CTI Manager, or Cisco Call Manager status.
    • CPU and memory utilization.
  • Device Type
  • Last Device Poll

For VCS application in virtual environment, hardware details such as fan, temperature, and voltage will not be displayed in the quick view. Instead, the following message will be displayed:

Data available only for Cisco VCS appliance.

Top 5 WAN Traffic Locations

Provides information about the top five locations at which bandwidth usage is the highest.

You can view the location name, number of failed calls in the last hour, and bandwidth used (as a percentage, per location).

By default, the table is sorted based on the number of failed calls. If there are no failed calls, then the table is sorted based on bandwidth used. If two or more locations have the same number of failed calls, the sort order is based on the bandwidth used.

Data is polled every 4 minutes.

Service Availability Summary

Provides the most recent data about the devices listed under the Unified Communication device group.

The X axis displays the number of applications. The Y axis displays the application type.

Green indicates applications that are active. Orange indicates applications that are down.

Click the bar to open a popup that provides links to Detailed Device View and Event Details page.

Top 10 Devices with Alarms

Displays the top 10 devices with alarms. The alarm count includes alarms with the severity Cleared.

You can click the bar chart to launch the Alarm Browser to view all endpoints and service infrastructure devices that have this specific alarm type.

You can launch the Device Work Center and click either on the Endpoint or Service Infrastructure links to view the device details.


Note


Clusters are not treated as devices and are not shown in this dashlet.


Top 10 Utilized Trunks/Route Groups

Provides information about the top ten utilized trunks and route groups in terms of channel usage.

Click the channel utilization bar to display a graph that plots trunk utilization or route group utilization against time. The data for the last polling cycle is displayed.

You can view popups that display the usage as a percentage when you place the cursor on the X axis coordinates for each four-minute interval. To open a detailed performance graph showing trunk or route usage, click the points on the graph or the channel utilization bar that correspond to the X axis coordinates.

Prime Collaboration allows you to calculate the Route Group aggregation and configure maximum capacity for SIP Trunks.

Click the Utilization Settings link, under the SIP Trunk Max Capacity tab, select the Gateway that is a Border Element and select the IP of the Border Element. Specify the maximum number of calls that can go through the SIP Trunk.

To calculate Route Group aggregation: under the Route Group Aggregation tab, select the Unified Communication System (UCS) cluster, Route Group, then select the Trunks that belong to the specified Route Group.

VCS License Usage

You can view the Traversal and Non Traversal license usage for all VCS clusters, and individual VCS servers in a cluster, and standalone VCS server(s).

Click on a particular cluster name to see the VCS servers in that cluster. You can view Traversal and Non Traversal license usage, Registration usage (number of endpoints, MCUs etc registered with the VCS), and cluster to which the VCS server belongs to.

Click None to see the data for standalone VCS server(s).

Mouse over the Traversal Usage, Non Traversal Usage and Registered Usage columns in the dashlet to view the number of licenses available, number of licenses used and number of licenses not used.

This dashlet does not auto refresh. You have to refresh the dashlet to get current data.

For VCS version 7.0 and later, any traversal or non-traversal call licenses that have been installed on a cluster peer are available for use by any peer in the cluster. For versions earlier than 7.0 licenses are not shared across the cluster; each peer can only use the licenses that are installed in it.

The number of licenses that can be installed on any one individual peer is limited to the maximum capacity of each VCS unit, as follows:
  • 500 non-traversal calls
  • 100 traversal calls
  • 2,500 registrations

The registration licenses are not shared across a cluster. If a cluster peer becomes unavailable, the shareable licenses installed on that peer will remain available to the rest of the cluster peers for two weeks from the time the cluster lost contact with the peer. This will maintain the overall license capacity of the cluster - however, each peer is still limited by its physical capacity as listed above. After this two week period, the licenses associated with the unavailable peer are removed from the cluster. To maintain the same capacity for your cluster, you should ensure that either the problem with the peer is resolved or new option keys are installed on another peer in the cluster.

Topology Dashboard

This dashboard provides a logical top-level view of your IP telephony network. This view focuses on call control relationships. It also displays Cisco Unified CMs, VCS, Unity Connection clusters, devices, route groups, and route lists.

You can use the Topology view to:
  • Search for phones.
  • View a summary of IP Communications devices.
  • View device events.
  • View maps at cluster level.
  • View detailed device information through Device 360° View. For more information, see Device 360° View.

In the Topology view, icons appear next to the device when an event is generated on the device. When an event is generated, it remains in the Topology view until it is cleared. The cleared event is removed from the Events display after you invoke the Prime Collaboration purge operation.

There are two ways to search for phones and devices in Topology view:

  • Search report panel—Searches for phones by domain name, IP address, or MAC address and for devices by domain name or IP address.
  • Phone search panel—Searches for phones by phone extension, IP address, MAC address, or SIP URI.

    Tip


    To enlarge or reduce the size of the map display, use the size slider at the top of the pane.


Map Display Pane

The map display pane shows the registration status of IP telephony devices and SRST status of SRST-enabled devices.

You can navigate down to an object in the display pane by clicking on the object. The devices under the object are then displayed.

The top-level view shows Cisco Unified CM clusters and Cisco Unified Contact Center solution groups. If objects are excessively large, they are displayed in a report page when selected. For smaller objects, the IP telephony devices are displayed along with registration status.

Pause your mouse pointer over the Cisco Unified CM cluster cloud to view the following details:

  • Cluster Name
  • Registered Phones
  • Unregistered Phones
  • Unknown Phones
  • Devices

For Cisco Unified Contact Center, the top-level view displays only one Unified Contact Center Enterprise (CCE) cloud. When you navigate down on this cloud, the individual CCEs appear again as clouds. Navigating down on these clouds, shows the individual devices with relevant information.

Pause your mouse pointer over a Unity Connection device to view the following details:

  • Name
  • IP Address
  • Capability
  • Status
  • Cluster status
  • Role (subscriber/publisher)
  • Alternate Node

You can also view the connectivity of neighbor devices by using the right-click menu. For every selected device, the next-hop devices that are physically connected are displayed.

Detailed Device View

You can right-click on a device in UC Topology View and launch the Detailed Device View.

The component categories pane lists the components of the device. You can select a component to view detailed information pertaining to that component, such as CPU usage for a processor, total used memory, and so on.

If the device you are viewing is an aggregate device, the subdevice also appears in the component categories pane.

The system information pane displays the IP address, MAC address, device capability, discovery status, model, platform name, system location, and system object ID.


Note


All the performance counters are not listed by default. The performance counters are listed based on the polling settings configured for that device group.


You can suspend or resume device or component monitoring by clicking the Suspend or Resume button.

You can launch Cluster Diagnostic View, Device 360 View, Alarm Browser, UCM Diagnostic View, diagnostic tests, and performance graphs by using the Launch Tools option. The tools that are available vary depending on the device type and its configuration.

UC Performance Monitor Dashboards

The UC Performance Monitor page displays system-defined dashboards based on the performance counters.


Note


You can monitor only one cluster per product for a single installation of Prime Collaboration—Standard.


To view the dashboards, select the product and cluster from the Cluster drop-down list and then select the required dashboard from the Dashboard drop-down list.

Unified CM and Unity Connection

The following system-defined dashboards are available for Unified CM:


Note


For Unity Connection, you can see these dashlets only- System Summary, CPU and Memory, Disk Usage, Process, and Port Monitor.
System Summary

Displays information about CPU usage, Virtual Memory usage, Common Partition Usage, and the Critical Services status.

CPU Usage

Displays the real time CPU usage and the maximum value in the past 3 minutes.

Virtual Memory Usage

Displays the real-time Virtual Memory usage and the maximum value in the past 3 minutes.

Common Partition Usage

Displays the real-time Common Partition Usage and the maximum value in the past 3 minutes.

Services

Displays the name of the service, the status (whether the service is up, down, activated, stopped by the administrator, starting, stopping, or in an unknown state), and the elapsed time during which the services existed in a particular state for the server or for a particular server in a cluster (if applicable).


Note


If the service status is displayed as Unknown State, the system cannot determine the state of the service.


CallManager Summary

Displays registered phones, calls in progress, and active gateway ports and channels.

Registered Phones

Displays the total number of phones that are registered and the delta of phones that are registered in the last minute. A negative value indicates that phones were unregistered; a positive value indicates new phones were registered.

Calls in Progress

Displays the total number of calls in progress and the delta calls in progress in the last minute. A negative value indicates that calls were completed or dropped; a positive value indicates new calls were established.

Active MGCP Ports and Channels

Displays the total number of active MGCP ports and channels and the delta of active MGCP ports and channels in the past minute. A negative value indicates that active MGCP ports and channels decreased; a positive value indicates that active MGCP ports and channels increased.

Call Activity
Call Activity

Displays the call activity on Cisco Unified Communications Manager, including calls completed, calls attempted, calls in progress, and logical partition total failures. This includes all servers in the cluster, if applicable.

Calls Completed

Displays the total number of calls completed. Also displays the delta of calls completed in the past 1 minute. It can have positive or negative values based on the calls completed in the past minute.

Calls Attempted

Displays the total number of calls completed. Also displays the delta of calls completed in the past 1 minute. It can have positive or negative values based on the calls attempted in the past minute.

Calls in Progress

Displays the total number of calls in progress and the delta calls in progress in the past 1 minute. A negative value indicates that calls were completed or dropped; a positive value indicates that new calls were established.

Logical Partition Failures

Displays the total Logical Partition Failures. Also displays the delta of Logical Partition Failures in the past 1 minute.

Gateway Activity

Displays gateway activity on Cisco Unified Communications Manager, including active ports, ports in service, and calls completed. Gateway Activity includes all nodes in the cluster, if applicable.

MGCP FXS
  • Ports in Service: Displays the number of FXS ports that are currently available for use in the system.
  • Ports Active: Displays the number of FXS ports that are currently in use (active) on this Unified Communications Manager.
  • Calls Completed: Displays the total number of successful calls that were made from all the FXS port instances on the MGCP FXS device.
MGCP FXO
  • Ports in Service: Displays the number of FXO ports that are currently available for use in the system.
  • Ports Active: Displays the number of FXO ports that are currently in use (active) on this Unified Communications Manager.
  • Calls Completed: Displays the total number of successful calls that were made from all the FXO port instances on the MGCP FXO device.
MGCP T1
  • Spans in Service: Displays the number of T1 CAS spans that are currently available for use.
  • Channel Active: Displays the number of T1 CAS voice channels that are in an active call on this Unified Communications Manager.
  • Calls Completed: Displays the total number of successful calls that were made from all the instances of MGCP T1 CAS device.
MGCP PRI
  • Spans In Service: Displays the number of PRI spans that are currently available for use.
  • Channel Active: This represents the number of PRI voice channels that are in an active call on this Unified Communications Manager.
  • Calls Completed: Displays the total number of successful calls that were made made from all the instances of MGCP PRI device.

Displays the trunk activity on Cisco Unified Communications Manager, including calls in progress and calls completed. This counter includes all nodes in the cluster, if applicable.

H323

Calls In Progress: Displays the total number of calls currently in progress on all the instances of Cisco H323 device.

Calls Completed: Displays the total number of successful calls made from all the instances of Cisco H323 device.

SIP Trunk

Calls In Progress: Displays the total number of calls that are currently in progress on all the instances of SIP device, including all active calls. When all calls that are in progress are connected, the number of calls in progress and the number of active calls are the same.

Calls Completed: Displays the total number of calls that were actually connected (a voice path was established) from all the instances of SIP device. This number increments when the call is terminated.

SDL Queue

Displays SDL queue information, including the number of signals in queue and number of processed signals.

Signals in SDL Queue

High: Indicates the number of high-priority signals in the Unified Communications Manager queue. High-priority signals include timeout events, internal Unified Communications Manager KeepAlives, certain gatekeeper events, and internal process creation, among other events. A large number of high-priority events will cause degraded performance on Unified Communications Manager, resulting in slow call connection or loss of dial tone. Use this counter in conjunction with the Queue Signals Processed High counter to determine the processing delay on Unified Communications Manager.

Normal: Indicates the number of normal-priority signals in the Unified Communications Manager queue. Normal priority signals include call processing functions, key presses, and on-hook and off-hook notifications, among other events. A large number of normal-priority events will cause degraded performance on Unified Communications Manager, sometimes resulting in delayed dial tone, slow call connection, or loss of dial tone. Use this counter in conjunction with the Queue Signals Processed Normal counter to determine the call processing delay on Unified Communications Manager. Remember that high-priority signals must complete before normal-priority signals begin to process, so check the high-priority counters as well to get an accurate picture of the potential delay.

Low: Indicates the number of low-priority signals in the Unified Communications Manager queue. Low-priority signals include station device registration (except the initial station registration request message), among other events. A large number of signals in this queue could result in delayed device registration.

Lowest: Indicates the number of lowest-priority signals in the Unified Communications Manager queue. Lowest priority signals include the initial station registration request message during device registration. A large number of signals in this queue could result in delayed device registration.

Processed SDL Signals

High: Indicates the number of high-priority signals that are processed by Unified Communications Manager for each 1-second interval. Use this counter in conjunction with the Queue Signals Present High counter to determine the processing delay on this queue.

Normal: Indicates the number of normal-priority signals that are processed by Unified Communications Manager for each 1-second interval. Use this counter in conjunction with the Queue Signals Present Normal counter to determine the processing delay on this queue. Remember that high-priority signals are processed before normal-priority signals.

Low: Indicates the number of low-priority signals that are processed by Unified Communications Manager for each 1-second interval. Use this counter in conjunction with the Queue Signals Present Low counter to determine the processing delay on this queue. The number of signals that are processed gives an indication of how much device registration activity is being processed in this time interval.

Lowest: Indicates the number of lowest-priority signals processed by Unified Communications Manager for each 1-second interval. Use this counter in conjunction with the Queue Signals Present Lowest counter to determine the processing delay on this queue. The number of signals that are processed gives an indication of how many devices began the Unified Communications Manager registration process in this time interval.

Cisco TFTP

Displays Cisco trivial file transfer protocol (TFTP) status on the Cisco Unified Communications Manager node, including total TFTP requests, total TFTP requests found, and total TFTP requests aborted.

TFTP Requests

This counter includes all nodes in the cluster, if applicable. This counter represents the total number of file requests (such as requests for XML configuration files, phone firmware files, and audio files) that the TFTP server handles. This counter represents the sum total of the following counters after the TFTP service has started: RequestsProcessed, RequestsNotFound, RequestsOverflow, RequestsAborted, RequestsInProgress.

CPU and Memory

Displays information about CPU usage, virtual memory usage, memory usage, and processors for the server.

CPU Usage

Displays the total CPU that is consumed, and the maximum CPU that is consumed in the last 3 minutes.

Virtual Memory Usage

Displays the total virtual memory that is consumed, and the maximum virtual memory that is consumed in last 3 minutes.

Memory Usage

Displays the following information:

  • % VM Used: Represents the percentage of system virtual memory utilization on the system. The value of the % VM Used counter is equal to the value that is derived from either of the following two equations: (Total KBytes - Free KBytes - Buffers KBytes - Cached KBytes + Shared KBytes + Used Swap KBytes ) / (Total KBytes + Total Swap KBytes) Used VM KBytes / Total VM KBytes
  • Total: Represents the total amount of memory in the system in kilobytes.
Used

Represents the amount of system physical memory that is in use, in kilobytes, in the system. The value of the Used KBytes counter is equal to the value that is derived from the following equation:

Total KBytes - Free KBytes - Buffers KBytes - Cached KBytes + Shared KBytes

The Used KBytes value is different from the Linux Used value that is shown in top or free command output. The used value that is shown in Linux top or free command output is equal to Total KBytes - Free KBytes, and it also includes the sum of Buffers KBytes and Cached KBytes.

Free

Represents the total amount of memory that is available in the system, in kilobytes.

Shared

Represents the amount of shared memory in the system, in kilobytes.

Buffers

Represents the capacity of buffers in the system, in kilobytes.

Cached

Represents the amount of cached memory, in kilobytes.

Total Swap

Represents the total amount of swap space, in kilobytes, in the system.

Used Swap

Represents the amount of swap space, in kilobytes, that is in use on the system.

Free Swap

Represents the amount of free swap space, in kilobytes, that is available in the system.

Processors

Displays the following information:

  • Processor: Instance of the processor. For example, a a quad-core CPU has four processors: 0, 1, 2, and 3.
  • % CPU: The processor's share of the elapsed CPU time excluding the idle time since last update, expressed as a percentage of CPU time.
  • User: Displays the percentage of CPU utilization that the CPU spent executing at the user level (application).
  • Nice: Displays the percentage of CPU utilization that the CPU spent executing at the user level with nice priority.
  • System: Displays the percentage of CPU utilization that the CPU spent executing at the system level (kernel).
  • Idle: Displays the percentage of time that the CPU or CPUs were idle and the system did not have an outstanding disk I/O request.
  • IRQ: Displays the percentage of time that the processor spent executing the interrupt request, which is assigned to devices for interrupt, or sending a signal to the computer when it finished processing.
  • Soft IRQ: Displays the percentage of time that the processor spent executing the software interrupt (softirq), which means that task switching is deferred until later to achieve better performance.
  • IO Wait: Displays the percentage of time that the CPU or CPUs were idle, during which the system had an outstanding disk I/O request.
Disk Usage

Displays information about disk usage on the node. It has the following dashlets: Common Partition Usage, Swap Partition Usage, Spare Partition Usage, Shared Memory Partition Usage, Active Partition Usage, Boot Partition Usage.

Each of the dashlets displays the following information:

Used

Represents the percentage of disk space that is in use on this file system.

Max Past 3 min

Represents the percentage of disk space that is in use on this file system in the past 3 minutes.

Used Space

Represents the amount of disk space, in megabytes, that is in use on this file system.

Total Space

Represents the amount of total disk space, in megabytes, that is on this file system. The number in this counter may differ from other total size values for disk space that you may see on the system, because the value of the Total Mbytes counter is the sum of Used Mbytes performance counter and the Free value that is shown in the CLI (show status) output. The Total Mbytes value is less than this CLI output for Total, which includes the minfree percentage of reserved file system disk blocks. Keep a minfree reserved to ensure a sufficient amount of disk space for the file system to operate at high efficiency.

CTI Manager

Displays information about the devices and applications that interfaces with the CTI Manager. Its displays the following information

Open Devices

The number of devices open by all applications that are connected to CTI Manager.

Open Lines

The number of lines open by all applications that are connected to CTI Manager.

CTI Connection

The number of applications that are connected to CTI Manager.

CM Links

The active Unified Communication Manager link to CTI Manager.

Heartbeat
Displays heartbeat information for the Cisco Unified Communications Manager and Cisco TFTP service.
CM Heartbeat

Current Value represents the heartbeat of Unified Communications Manager. This is an incremental count that indicates that Unified Communications Manager is running. If the count does not increment, then Unified Communications Manager is down. Past 1 min displays the delta; a value of 0 indicates that Unified Communications Manager is down.

TFTP Heartbeat

Current Value represents the heartbeat of the TFTP server. This is an incremental count that indicates that the TFTP server is running. If the count does not increment, then the TFTP server is down. Past 1 min displays the delta; a value of 0 indicates the TFTP server is down.

SIP Activity

Displays SIP activity on Cisco Unified Communications Manager, including summary requests, summary responses, summary of failure responses in, summary of failure responses out, retry requests out, and retry responses out. SIP Activity includes all nodes in the cluster, if applicable.

Summary Requests

Displays the summation of total number of SIP request messages received by the SIP device, including retransmissions + the total number of SIP request messages sent out (originated and relayed) by the device. Where a particular message is sent more than once, for example as a retransmission or as a result forking, each transmission is counted separately.

Summary Responses

Displays the summation of total number of SIP response messages received by the SIP device, including retransmissions + the total number of SIP response messages sent (originated and relayed) by the SIP device, including retransmissions.

Summary Failure Responses In

Displays the summation of total number of 4xx class SIP responses received by the SIP device, including retransmissions. This class of responses indicates request failure by a SIP device that provides a client function + the total number of 5xx class SIP responses received by the SIP device, including retransmissions. This class of responses indicates failure responses received by a SIP device that provides a client function + the total number of 6xx class SIP responses received by the SIP device, including retransmissions. This class of responses indicates failure responses received by a SIP device that provides a client function. The responses generally indicate that a node has definitive information about a particular called party, not just the particular instance indicated in the Request-URI.

Summary Failure Responses Out

Displays the summation total number of 4xx class SIP responses sent by the SIP device, including retransmissions. This class of responses indicates request failure by a SIP device that provides a node function + the total number of 5xx class SIP responses sent by the SIP device, including retransmissions. This class of responses indicates failure responses sent by a SIP device that provides a node function + the total number of 6xx class SIP responses sent by the SIP device, including retransmissions. This class of responses indicates failure responses sent by a SIP device that provides a node function. The responses generally indicate that a node has definitive information about a particular called party, not just the particular instance indicated in the Request-URI.

Retry Requests Out

Displays the total number of Request retries that have been sent by the SIP device.

Retry Responses Out

Displays the summation of the total number of Final Response retries that have been sent by the SIP device + the total number of non-Final Response retries that have been sent by the SIP device.

Process

Displays information about the processes that are running on the node.

Process

Name of the process.

PID

The task's unique process ID, which periodically wraps, although it never restarts at zero.

& CPU

The task's share of the elapsed CPU time since the last update and is expressed as a percentage of total CPU time.

Status
The task's process status:
  • 0: Running
  • 1: Sleeping
  • 2: Uninterruptible disk sleep
  • 3: Zombie
  • 4: Traced or stopped (on a signal)
  • 5: Paging
  • 6: Unknown
Shared Memory

The amount of shared memory, in kilobytes, that a task is using. Other processes could potentially share the same memory.

Nice

The nice value of the task. A negative nice value indicates that the process has a higher priority while a positive nice value indicates that the process has a lower priority. If the nice value equals zero, do not adjust the priority when you are determining whether to run the task.

VmRSS

The virtual memory (Vm) resident set size (RSS) that is currently in physical memory in kilobytes, including Code, Data, and Stack.

VmSize

The total amount of virtual memory, in kilobytes, that the task is using. It includes all code, data, shared libraries, and pages that have been swapped out: Virtual Image = swapped size + resident size.

VmData

The virtual memory usage of the heap for the task in kilobytes.

Thread Count

The number of threads that are currently grouped with the task. The negative value –1 indicates that this counter is currently not available because thread statistics (including all performance counters in the Thread object as well as the Thread Count counter in the Process object) have been turned off because the system's total processes and threads have exceeded the default threshold value.

Datastack Size

The stack size for task memory status.

Page Fault Count

The number of major page faults that a task encountered that required the data to be loaded into memory.

Database Summary

Provides connection information for the server, such as the change notification requests that are queued in the database, change notification requests that are queued in memory, the total number of active client connections, the number of devices that are queued for a device reset, the number of replicates that have been created, and the status of the replication.

Change Notification Requests Queued in DB

Displays the number of records from the DBCNQueue table.

Change Notification Requests Queued in Memory

Displays the number of change notification requests that are queued in memory.

Total Number of Connection Clients

Displays the number of change notification requests that are queued in memory.

Replicates Created

Displays the number of replicates that were created by Informix for the DB tables. Every table contains at least one replicate. This counter displays information during Replication Setup.

Replication Status
Displays the state of replication:
  • 0 = Initializing ReplTask thread
  • 1 = Replication setup script fired from this node
  • 2 = Replication is good; replication is set up correctly and most of the tables in the database should be in sync for all nodes of the cluster

    Note


    Run the CLI command utils dbreplication status to see if any tables are out of sync


  • 3 = Replication data transfer is bad in the cluster

    Note


    When the counter shows a value of 3, replication is bad in the cluster. This value does not mean that replication is bad on that particular node. Run the CLI command utils dbreplication status find out where and what exactly is broken.


  • 4 = Replication Setup did not succeed

Phone Summary

Displays information about the Cisco Unified Communications Manager node, including the number of registered phones, registered SIP phones, registered SCCP phones, partially registered phones, and the number of failed registration attempts. This includes all nodes in the cluster, if applicable.

Registered Devices

Displays the number of SIP phones, SCCP phones and total phones that are registered in Unified Communications Manager. The Past 1 Minute column displays the delta of phones that were registered or unregistered in the past 1 minute.

Registration Issues

Displays the registration issues of all the phones in Unified Communications Manager. The Failed Attempts tab displays the number of attempts that are failed to register phones; the Partial Registration tab displays the number of partial registrations of phones. The Past 1 Minute column displays the delta of values in the past 1 minute.

Device Summary

Displays information about the Cisco Unified Communications Manager node, including the number of registered phone devices, registered gateway devices, and registered media resource devices. Device Summary includes all nodes in the cluster, if applicable.

Registered Phone Devices

Displays the total phones registered in Call Manager cluster; Past 1 Minute displays the delta of total registered phones in the past 1 minute.

Registered Gateway Devices

Displays the total gateways (FXS, FXO, T1CAS and PRI) registered in Unified Communications Manager cluster; Past 1 Minute displays the delta of total registered gateways in the past 1 minute.

Registered Media Resource Devices

Displays the total media resources (MOH, MTP, XCODE and CFB) that are registered in Unified Communications Manager cluster; Past 1 Minute displays the delta of total registered media resources in the past 1 minute.

Registered Other Station Devices

Displays the total other station devices registered in Unified Communications Manager cluster; Past 1 Minute displays the delta of total other station devices in the past 1 minute.

Device Services

Displays the details of all different types of devices: Phones, Gateways, Media Resources, and Other Station devices. Details for each type are displayed separately.

IM and Presence Summary
PE Active JSM Sessions

The Number of Active JSM Sessions performance counter contains the number of client emulation sessions between the Cisco Presence Engine and Cisco XCP Router. The value of this counter should always equal the number of licensed users on the box.

Past 1 Minute displays the delta of counter value in the past 60 seconds.

Active Calendar Subscriptions

The Number of Active Calendar Subscriptions performance counter contains the number of calendar subscriptions that are currently active on the box.

Past 1 Minute displays the delta of counter value in the past 60 seconds.

Incoming SIP Subscriptions

The Number of Active Inbound SIP Subscriptions performance counter contains the current number of active inbound SIP subscriptions that are maintained by the Cisco XCP SIP Federation Connection Manager service on the IM and Presence Service node. Monitor this counter if the IM and Presence Service node is configured for SIP Interdomain Federation or SIP Intradomain Federation.

Past 1 Minute displays the delta of counter value in the past 60 seconds.

Outgoing SIP Subscriptions

The Number of Active Outbound SIP Subscriptions performance counter contains the current number of active outgoing SIP subscriptions being maintained by the Cisco XCP SIP Federation Connection Manager service on the IM and Presence Service node. Monitor this counter if IM and Presence Service node is configured for SIP Interdomain Federation or SIP Intradomain Federation.

The total combined count of SubscriptionsOut and SubscriptionsIn must not rise above 260,000 on any single IM and Presence Service node.

Past 1 Minute displays the delta of counter value in the past 60 seconds.

Total Ad Hoc Chat Rooms

The Total Ad Hoc Group Chat Rooms performance counter contains the total number of ad hoc chat rooms that are currently hosted on the node.


Note


Ad hoc chat rooms are automatically destroyed when all users leave the room, so this counter rises and falls in value regularly.


Past 1 Minute displays the delta of counter value in the past 60 seconds.

Total Persistent Chat Rooms

The Total Persistent Chat Rooms performance counter contains the total number of persistent chat rooms that are hosted on the node. The room owner must explicitly destroy persistent chat rooms. This counter can be monitored to identify whether the total number of persistent chat rooms is very large and also to help identify whether some persistent chat rooms are not being used regularly anymore.

Past 1 Minute displays the delta of counter value in the past 60 seconds.

Cisco Jabber Summary
Jabber Login Failures

Represents the number of failed login requests that were received by the Cisco Simple Object Access Protocol (SOAP) interface. After 1 minute, the counter displays the delta of counter value in the last 60 seconds.

Current Connected Jabber or XMPP Clients

Contains the current number of XMPP clients that are connected to the Cisco XCP Connection Manager on an individual IM and Presence Service server. This number rises and falls based on the usage patterns of your deployment. Further investigation may be required if this number is higher than expected for your user base. After 1 minute, the counter displays the delta of counter value in the last 60 seconds.

IM Packets Since Last Restart

Provides the total number of IM packets that are handled by the IM and Presence Service node across all users. After 1 minute, the counter displays the delta of counter value in the last 60 seconds.

IM Packets in Last 60 Seconds

The total number of IM packets that are handled by the IM and Presence Service node across all users in the past 60 seconds. This counter is reset to zero every 60 seconds. The same rules for counting IM packets apply as for TotalMessagePackets. Monitor this counter to help identify the busy IM hours in your organization. After one minute, the counter displays the delta of counter value in the last 60 seconds.

Learned Patterns

Learned Pattern reports and Service Advertisement Framework (SAF) forwarder reports support the Call Control Discovery feature. When you configure the Call Control Discovery feature, Cisco Unified Communications Manager advertises itself and its hosted DN patterns to other remote call-control entities that use the SAF network. Likewise, these remote call-control entities advertise their hosted DN patterns, which Unified Communications Manager can learn and insert in digit analysis.

Column Description

Pattern

Displays the name of the learned pattern from the remote call-control entity.

TimeStamp

Displays the date and time that the local Unified Communications Manager marked the pattern as a learned pattern.

Status

Indicates whether the learned pattern was reachable or unreachable.

Protocol

Displays the protocol for the SAF-enabled trunk that was used for the outgoing call to the learned pattern. If the remote call-control entity has QSIG tunneling configured for the SAF-enabled trunk, the data indicates that QSIG tunneling was used; for example, EMCA is listed along with H.323 in this column.

AgentID

Displays the name of the remote call-control entity that advertised the learned pattern.

IP Address

Displays the IP address for the call-control entity that advertised the learned pattern; Displays the port number that the call-control entity uses to listen for the call.

ToDID

Displays the PSTN failover configuration for the learned pattern.

CUCMNodeId

Displays the ID from the local Unified Communications Manager node.

Port Monitor

The Port Monitor lets you monitor the activity of each Cisco Unity Connection voice messaging port in real-time. This information can help you determine whether they system has too many or too few ports.

The Port Monitor displays the information for each port as described in the following table.

Field

Description

Port Name

The display name of the port in Cisco Unity Connection Administration.

Caller

For incoming calls, the phone number of the caller.

Called

For incoming calls, the phone number that was dialed.

Reason

If applicable, the reason why the call was redirected.

Redir

The extension that redirected the call. If the call was redirected by more than one extension, this field shows the extension prior to the last extension

Last Redir

The last extension that redirected the call.

Application Status

The name of the conversation that Cisco Unity Connection is playing for the caller. When the port is not handling a call, the status appears as Idle.

Display Status

The action that the conversation is currently performing. When the port is not handling a call, the status appears as Idle.

Conversation Status

Specific details about the action that the conversation is performing. When the port is not handling a call, the status appears as Idle.

Port Ext

The extension of the port.

Connected To

For Cisco Unified Communications Manager SCCP integrations, the IP address and port of the Cisco Unified Communications Manager node to which the ports are registered.

Creating Custom UC Performance Monitor Dashboards

You can create custom dashboards based on your requirements, from Prime Collaboration Standard home page. Each dashboard can have a maximum of six dashlets.

To create custom dashboards:


    Step 1   Choose the product and the cluster from the Cluster drop-down list.
    Step 2   Click the + button adjacent to the Dashboard drop-down list.
    Step 3   In the Create Custom Dashboard window, enter the dashboard name and the polling interval.
    Step 4   Select the desired performance counters from the Available Counters drop-down. You can add up to six counters.
    Step 5   Select the attribute for the counter you selected, from the attribute drop-down list. Add the instance value from the Instance drop-down, if the counter is instance-based.
    Step 6   Select the server from the Server drop-down.
    Step 7   Click Create.

    You can also edit or delete a custom dashboard you created, using the Edit and Delete buttons. For information about creating a new performance counter event, see Creating Custom Alerts. When you create custom events from the custom dashboards, you need not provide the cluster details.


    Adding a Customized Dashboard

    You can add customized dashboards in the home page.

    You can also do the following:

    • Add the existing dashlets to a different dashboard.
    • Move the dashlets around under a dashboard by dragging and dropping them.

    To add a new dashboard:


      Step 1   Click the icon on the top-right corner of the home page, and then click Add New Dashboard.
      Step 2   Enter a name in the box provided, and click Apply.
      Step 3   Click Add Dashlet(s).
      Step 4   Click Add adjacent to the dashlets you want to add.
      Note   

      For Prime Collaboration Assurance - Advanced mode—If your endpoints or devices are configured with a common prefix names, you can shorten the display name using the Dashlet Label Prefix Removal setup in the General Settings page.