Cisco Unified CallManager Serviceability System Guide, Release 4.2(3)
Real-Time Monitoring Tool
Downloads: This chapterpdf (PDF - 408.0KB) The complete bookPDF (PDF - 5.76MB) | Feedback

Real-Time Monitoring Tool

Table Of Contents

Real-Time Monitoring Tool

Understanding the Real-Time Monitoring Tool

Monitoring Objects

Devices Category

Servers Category

Services Category

Call Activities Category

RTMT Service Parameters

RTMT Logon

RTMT Window Overview

RTMT Default Configuration

RTMT Window Configuration Checklist

RTMT Window Components

Menu Bar

System Menu

Monitor Menu

Search Menu

Device Search

CTI Search

Edit Menu

Device Menu

Perfmon Menu

Alert Menu

Window Menu

Application Menu

Help Menu

Monitor Window

View Tab

Summary

Call Process Activity Monitoring

Service Monitoring

Cisco TFTP

Directory Servers

RTMT Heartbeat Feature

Device Monitoring

CTI Monitoring

Perfmon Monitoring

Category Tabs

Sample Rate

Perfmon Counters Table View/Chart View

Remove Chart/TableEntry

Understanding Perfmon Monitoring

Add a Counter to Monitor

Configure Alert Notification for Counter

Zoom Counter

Counter Properties

Property Description

Data Sample

View All Data for a Counter

Perfmon Monitoring Configuration Checklist

Alert Tab

Alert Customization

Alert Action Configuration

Preconfigured Alerts

Alert Configuration Checklist

Logging in RIS

Logger

Alert Log

Server Log

Service Log

Call Log

Device Log

Perfmon Log

Where to Find More Information


Real-Time Monitoring Tool


This chapter provides information on the Real-Time Monitoring Tool (RTMT) for Cisco Unified CallManager Serviceability and comprises the following topics:

Understanding the Real-Time Monitoring Tool

RTMT Service Parameters

RTMT Logon

RTMT Window Overview

RTMT Default Configuration

RTMT Window Configuration Checklist

RTMT Window Components

Menu Bar

Monitor Window

View Tab

Understanding Perfmon Monitoring

Alert Tab

Alert Configuration Checklist

Logging in RIS

Where to Find More Information

Understanding the Real-Time Monitoring Tool

Cisco Unified CallManager Serviceability provides a client-side standalone plug-in, RTMT, that monitors real-time behavior of the components in a Cisco Unified CallManager cluster. RTMT runs as an application and uses HTTP and TCP to monitor device status, system performance, device discovery, and CTI applications. It also connects directly to devices by using HTTP for troubleshooting system problems.

RTMT continuously monitors a set of management objects that are preconfigured and generates various alerts, in the form of e-mails, for these objects when values go over/below user-configured thresholds. RTMT then generates daily reports for these objects. See the "Monitoring Objects" section for more information about the preconfigured monitoring objects.


Note RTMT continues to monitor real-time behavior of Cisco Unified CallManager components in the background even when RTMT is not running.


Monitoring Objects

The RTMT arranges the preconfigured monitoring objects into four major categories:

Devices

Call Activities

Servers

Services

The following sections provide more information about each category, including what objects RTMT monitors, the alert, threshold and defaults, and what kind of reports RTMT generates for each. Refer to Chapter 11, "Serviceability Reports Archive" for more information on viewing the RTMT reports.

Devices Category

The Devices category monitors phones, gateways, and media devices on each Cisco Unified CallManager and Cisco Unified CallManager cluster. Table 9-1 provides information about the objects that RTMT monitors, the alert, thresholds, and defaults, and what kind of reports that RTMT generates for those devices.

Table 9-1 Devices Category 

Monitored Objects (displayed)
Alert/Threshold/Default
Report

Number of registered phones for each Cisco Unified CallManager and cluster.

Total number of registered phones drops by X percent in consecutive polls. Default specifies 10 percent.

Daily reports on number of registered devices. See the "Device Statistics Report" section on page 11-3 for detailed information.

Number of registered gateways on each Cisco Unified CallManager and cluster.

(Warning) Clusterwide total number of registered gateways decreased in consecutive polls.

(Informational) Clusterwide total number of registered gateways increased in consecutive polls.

Number of registered media devices on each Cisco Unified CallManager and cluster.

(Warning) Clusterwide total number of registered media devices decreased in consecutive polls.

(Informational) Clusterwide total number of registered media devices increased in consecutive polls.

Media List exhausted.


Servers Category

The Servers category monitors CPU usage, disk space usage, and critical services on each Cisco Unified CallManager server. Table 9-2 provides information about the objects that RTMT monitors, the alert, thresholds, and defaults, and what kind of reports that RTMT generates for those servers.

Table 9-2 Servers Category 

Monitored Objects (displayed)
Alert/Threshold/Default
Report

CPU Usage (100% Idle) on each server.

Memory Usage (& memory in use out of total) on each server.

CPU and memory usage for all processes on each server (% Processor Time, VirtualBytes, PrivateBytes, Working Set, Open handles, Thread count, and PID).

Call Processing node - CPU usage pegged X percent over X seconds. Default specifies 90 percent, 30 seconds.

Non-CallProcessing node - CPU Usage pegged X percent over X seconds. Default specifies 99 percent, 120 seconds.

Available memory equals less than X percent. Default specifies 10 percent.

When CPU peg or excessive memory usage alerts occur, the name of the top process displays in the alert message. In case of dllhost service, the real meaningful name displays instead of generic name dllhost.

Daily CPU, memory, and disk usage reports. See the "Server Statistics Report" section on page 11-7 for detailed information.

Disk space usage for all logical drives on each server.

Available disk space on the largest logical drive equals less than X percent. Default specifies 10 percent.

State of activated critical services on each server.

Service state changed from Up->Down.


Services Category

The Services category monitors CTI Manager information for each CTI Manager, Cisco TFTP server information, directory server information, and heartbeat rate information. Table 9-3 provides information about the objects that RTMT monitors, the alert, thresholds, and defaults, and what kind of reports that RTMT generates for those services.

Table 9-3 Services Category 

Monitored Objects (displayed)
Alert/Threshold/Default
Report

Number of open devices, lines, CTI connections, and active Cisco Unified CallManager links for each CTI Manager.

N/A

Daily report on CTI and Cisco TFTP usage statistics. See the "Service Statistics Report" section on page 11-10 for detailed information.

TotalTftpRequests and TotalTftpRequestsAborted, for each Cisco TFTP server.

N/A

Connection and replication status for each Directory server.

Connection failed.

Replication failed.

Heartbeat rate for each Cisco CallManager, Cisco TFTP, and TCD services.

Cisco CallManager heartbeat rate equals <0.x. Default equals 0.5.

Cisco TFTP heartbeat rate equals <0.x. Default specifies 0.5.

TCD heartbeat rate equals <0.x. Default specifies 0.5.


Call Activities Category

The Call Activities category monitors all call activity information for each Cisco Unified CallManager node and cluster. Table 9-3 provides information about the objects that RTMT monitors, the alert, thresholds, and defaults, and what kind of reports that RTMT generates for those call activities.

Table 9-4 Call Activities Category 

Monitored Objects (displayed)
Alert/Threshold/Default
Report

CallsAttempted, CallsCompleted, and CallsInProgress for each Cisco Unified CallManager node and cluster.

N/A

Daily report on Cisco Unified CallManager call activities. See the "Call Activities Report" section on page 11-14 for more detailed information.

CallsAttempted, CallsCompleted, and CallsInProgress of each type of MGCP FXS/FXO/PRI/T1CAS/H.323 gateway, as well as SIP and H.323 Trunks for each Cisco Unified CallManager node and cluster.

N/A

Channel/Port Status of each MGCP FXS/FXO/PRI/T1CAS gateway.

N/A

SDL Queue activity on each Cisco Unified CallManager node.

N/A

MGCP FXS Gateway - Number of In-Service and Active ports for each Cisco Unified CallManager node and cluster.

Route-List exhausted

MGCP FXO Gateway - Number of In-Service and Active ports for each Cisco Unified CallManager node and cluster.

Route-List exhausted

MGCP PRI Gateway - Number of In-Service and Active channels for each Cisco Unified CallManager node and cluster.

D-Channel out of service

Route List exhausted

 

MGCP T1CAS Gateway - Number of In-Service and Active ports for each Cisco Unified CallManager node and cluster.

Route List exhausted


RTMT Service Parameters

The following list comprises the service parameters that are associated with RTMT:

Data Collection Enabled

Data Collection Polling Rate

Data Collection Reenumeration Interval

Server Synchronization Period

Primary Collector

Failover Collector

For more information about service parameter configuration, refer to the Cisco Unified CallManager Administration Guide.

RTMT Logon

You will find that RTMT is available as a download from the Cisco Unified CallManager Install Plugins window. When you are ready to download RTMT, you can click Cisco Unified CallManager Serviceability Real-Time Monitoring Tool from the Tools menu in Cisco Unified CallManager Serviceability Administration.

When you launch RTMT from the desktop icon, or from Start > Programs > Cisco Unified CallManager Serviceability > RTMT, the logon window displays.

To connect to a Cisco Unified CallManager node (any node in the Cisco Unified CallManager cluster), you must enter the user authentication information in the User Name and Password fields. The Host IP Address field can comprise either digital IP address or host name.

If the authentication fails or if the server is not reachable, you will be prompted to reenter the server and authentication details, or you can click the Cancel button to exit the application. If the authentication succeeds, RTMT launches the monitoring module either from local cache or from a remote node when the local cache does not contain a monitoring module that matches the backend version.

After you enter the authentication information, the RTMT window opens and displays with the default configuration. See the "RTMT Default Configuration" section.

RTMT Window Overview

See the following sections for some general information about the RTMT window:

RTMT Default Configuration

RTMT Window Components

RTMT Default Configuration

When you initially load RTMT, the load includes a default configuration that is called CM-Default. Dynamically created, CM-Default monitors all registered phones in all the Cisco Unified CallManager nodes. If your cluster has five configured Cisco Unified CallManager nodes, CM-Default displays all the registered phones for each node in a Cisco Unified CallManager cluster, as well as calls in progress and active gateway ports and channels.

You can save, restore, and delete Cisco Unified CallManager configuration information by using Profile in the System menu. See the "RTMT Window Components" section.

RTMT Window Configuration Checklist

Table 9-5 provides an overview of the steps for configuring the RTMT window.

Table 9-5 RTMT Window Configuration Checklist 

Configuration Steps
Related Procedures and Topics

Step 1 

Load RTMT.

Loading Real-Time Monitoring, Cisco Unified CallManager Serviceability Administration Guide

Step 2 

View existing configuration preferences.

RTMT Default Configuration, Cisco Unified CallManager Serviceability Administration Guide

Step 3 

Change to another configuration setting.

Creating Configuration Profiles, Cisco Unified CallManager Serviceability Administration Guide


RTMT Window Components

The RTMT window comprises two main components: the Menu Bar and the Monitor Window. You can access several different monitoring functions by using both and/or either of these components.

See the "Menu Bar" section and the "Monitor Window" section for information about the menu bar and monitor window functions.

Menu Bar

The RTMT menu bar comprises several menu items that you can use to access different monitoring components. See the following sections for information about RTMT menu bar items:

System Menu

Monitor Menu

Search Menu

Edit Menu

Device Menu

Perfmon Menu

Alert Menu

Window Menu

Application Menu

Help Menu

System Menu

The System menu provides access to application-wide functionality, such as Profile and logout.

The System menu includes the following menu items:

Profile—This menu item allows you to save, restore, and delete existing Cisco Unified CallManager configurations.

JVM Information—This menu contains Java Heap Memory Usage monitoring.

Serviceability Reports Archive—This menu takes you to the Serviceability Report Archive in Cisco Unified CallManager Serviceability. See Chapter 11, "Serviceability Reports Archive," for more information.

Log Off—This menu item allows you to log off of RTMT.

Monitor Menu

The Monitor menu provides access capability to preconfigured items in the menu system. It includes the following categories:

Cluster Summary—This menu item provides a summary of every Cisco Unified CallManager in a cluster.

Server—This menu item provides server monitoring information such as CPU and memory status, disk usage, and the status of critical services.

Call Process—This menu item provides call-processing monitoring information, such as call, gateway, and trunk activity monitoring, and SDL queue information.

Service—This menu item provides service status monitoring and includes directory server and system heartbeat information. See the "Directory Servers" section and the "RTMT Heartbeat Feature" section for more information.

Device Summary—This menu item provides a summary of the devices within a Cisco Unified CallManager cluster.

CTI Manager—This menu item provides information that pertains to CTI Manager such as the number of open lines, devices, and CTI connections per CTI Manager.


Tip To monitor the preconfigured set of monitoring objects in RTMT, you can use either the menu bar at the top of the monitor window or the left controlling panel of the monitor window. For more information about the left controlling panel, see the "Monitor Window" section.


Search Menu

This menu provides device-based and CTI-based search functionality. Using the Search menu, you can search for any and all devices within a Cisco Unified CallManager, as well as the CTI applications, lines, and devices per each CTI Manager. See the "Device Search" section and the "CTI Search" section for more information.

Device Search

The Device search menu comprises the following menu items on which you can search:

Phone

Gateway Devices

H323 Devices

CTI Devices

VoiceMail Devices

Media Resources

Hunt List

SIP Trunk

Within these menu items, you can search on the basis of any device in the Cisco Unified CallManager cluster and choose the status of the devices, including registered, unregistered, rejected, any status, and devices that are only configured in the database. You can also search by any model, or a specific device model, and set up criteria that include several different attributes.

You can monitor chosen devices on the basis of the criteria that you specify for that device. You can search by the status of the device, device name, and application pattern.

RTMT queries RIS to find the matching device. Results display in a table with a row for each matched device, a column for each of the specified attributes, and a time stamp of the device that has been opened/closed and the application that controls the device media.

When you search for a device by choosing the any status option, RTMT does not display a snapshot of the matched device type, but rather it displays data for that device type from the RIS database for all specified Cisco Unified CallManager nodes for a period of time. As a result, you may see multiple entries of a device with multiple statuses (Registered, Unregistered, and so on) in RTMT.

When you see multiple entries of a device, the current status of the device reflects the entry that has the latest time stamp. By configuring the RIS Unused Cisco CallManager Device Store Period service parameter for the Cisco RIS Data Collector service in Cisco Unified CallManager Administration, you can configure the period of time that the RIS database keeps information on unregistered or rejected device. Refer to Cisco Unified CallManager Administration Guide for more information on configuring service parameter.

CTI Search

The CTI search menu allows you to search on the following CTI components:

CTI Applications

CTI Devices

CTI Lines

Using the CTI Search menu, you can search chosen CTI components on the basis of the criteria that you specify. You can also choose any or all the CTI Managers on which you want to search.

You can specify criteria for the CTI applications, devices, and lines that include CTI status, device name, application pattern, and attributes. After you set up your search criteria, RTMT queries the RIS for matched CTI applications, devices, or lines. The results display in a table with a row for each matched application and a column for each attribute; a Time Stamp of provider opened/closed status also displays.


Note You can monitor each search result or bring up Cisco Unified CallManager Administration in a separate browser by right-clicking on each item.


Edit Menu

Use this menu to specify context-sensitive edit actions that are also available in right-click popup menus. You can also use the "Trace Setting" item in the menu to trace and debug the RTMT application.

The Edit menu comprises the following menu items:

New TAB—You can use this menu item to create a new category tab. Refer to Chapter 12, "Real-Time Monitoring Configuration," in the Cisco Unified CallManager Serviceability Administration Guide for procedural information about the New TAB item.

Delete TAB—You can use this menu item to delete an existing category tab. Refer to "Real-Time Monitoring Tool," in the Cisco Unified CallManager Serviceability Administration Guide for procedural information about the Delete TAB item.

Rename TAB—You can use this menu item to rename an existing category tab.

Polling Rate—With this menu item, you can set the polling rate of a perfmon counter.


Note The "Polling Rate" item does not apply for preconfigured monitoring objects.


Hide QuickLaunch Channel—Check this menu item if you want to hide the QuickLaunch channel on the left controlling center panel of the RTMT.

Trace Setting—You can use this menu item to trace and debug the RTMT application. The menu includes the following trace settings:

None

Fatal

Error

Warning

Information

Debug

Refer to "Real-Time Monitoring Tool," in the Cisco Unified CallManager Serviceability Administration Guide for procedural information about the menu items in the Edit menu.

Device Menu

The Device menu provides the following device-related menu items:

Open Device Search

App Info

Port/Channel Status

Properties

Open

Perfmon Menu

The Perfmon menu provides access to Perfmon functionality and includes the following menu items:

Open Perfmon Monitoring

Counter Description

Counter Instances

Counter Monitoring

Monitoring Properties

Zoom Chart

Remove Chart/TableEntry

Alert Menu

The Alert menu provides all alert-related functionality including alert defining, setting, and viewing. This menu comprises the following menu options:

Alert Central—This option comprises the current status and history of every alert in the Cisco Unified CallManager cluster.


Note You can also access Alert Central by using the Alert tab in the left controlling center in the RTMT monitoring pane.


Set Alert/Properties—This menu category allows you to set alerts and alert properties.

Remove Alert—This menu category allows you to remove an alert.

Enable Alert—With this menu category, you can enable alerts.

Disable Alert—You can disable an alert with this category.

Suspend cluster/node Alerts—This menu category allows you to temporarily suspend alerts on a particular Cisco Unified CallManager node or on the entire cluster.

Clear Alerts—This menu category allows you to reset an alert (change the color of an alert item from red to black) to signal that you took care of an alert. After an alert gets raised, its color automatically changes to red in RTMT and stays that way until you manually clear the alert.

Clear All—This menu category allows you to clear all alerts.

Alert Events Detail—This menu category provides detailed information on alert events.

Config Email Server—In this category, you can configure your e-mail server to enable alerts.

Config Alert Action—This category allows you to set actions to take for specific alerts that you can configure to send to desired e-mail recipients.

Two kinds of alerts occur: preconfigured and user-defined. You can further configure both, but the difference is that you cannot delete preconfigured alerts whereas you can add and delete user-defined alerts.

For more information on customizing alerts, refer to Chapter 12, "Real-Time Monitoring Configuration," in the Cisco Unified CallManager Serviceability Administration Guide.

Window Menu

You can use the Window menu to close opened monitoring windows by using two menu items: Close and Close All Windows. You can use the Close menu item to close the current active window in the right content viewing panel. Use the Close All Windows menu item to close all opened monitoring windows.

Application Menu

The Application menu provides a way to access Cisco Unified CallManager Administration and Cisco Unified CallManager Serviceability.

Help Menu

The Help menu provides information about product name, client and server software versions, and third-party libraries software version information, as well as RTMT online help.

Monitor Window

To support the preconfigured set of monitoring objects, the RTMT main user interface comprises two parts: left controlling center pane and right content viewing panel.

The controlling center comprises the View tab and the Alert tab. The View tab comprises several different monitoring categories, and the Alert tab comprises only the Alert category.

The View and Alert tabs differ in that anything related to the View tab gets saved as a profile that can be restored at any time that RTMT is invoked. The Alert tab relates only to the systemwide alert functionality. You cannot save the states. See the "View Tab" section and the "Alert Tab" section for more information about each tab.

The polling rate in each preconfigured monitoring window remains fixed, and the default value specifies 30 seconds. If the collecting rate of RISDC (real-time information system directory) changes in the Cisco Unified CallManager Administration service parameters, the polling rate in the preconfigured window also updates. In addition, the local time of the RTMT client application, and not the backend server time, provides the basis for the time stamp in each chart.

View Tab

The View tab in the RTMT monitor window comprises several different monitoring categories. See the following sections for more information on each category:

Summary

Call Process Activity Monitoring

Service Monitoring

Device Monitoring

CTI Monitoring

Perfmon Monitoring

Summary

The Summary window provides monitoring of important common information. Monitored information includes

Memory usage

CPU usage

Registered phones

Calls in progress

Active gateway ports and channels

The Server category monitors preconfigured objects such as CPU and memory usage, disk usage, and critical Cisco Unified CallManager services.

The Critical Services monitoring category provides the name of the critical service, the status (whether the service is up, down, or activated), and the elapsed time during which the services have been in a particular status for a particular Cisco Unified CallManager node.

Call Process Activity Monitoring

The Call Process monitoring category monitors Cisco Unified CallManager call- processing activity. Call-processing monitored items include

Call Activity—You can monitor the number of calls that were attempted, calls that were completed, and call in progress for a particular Cisco Unified CallManager node or the entire cluster.

Gateway Activity—You can monitor gateway activity for each gateway type. Gateway activity monitoring includes the number of active ports, the number of ports in service, and the number of calls that were completed for each gateway type for a particular Cisco Unified CallManager node or the entire cluster.

Trunk Activity—The system monitors trunk activity by trunk type for a particular node or cluster. Trunk activity monitoring includes the number of calls in progress and the number of calls that were completed for a particular trunk type.

SDL Queue—SDL Queue monitoring monitors the number of signals in the SDL queue and the number of signals that were processed for a particular signal distribution layer (SDL) queue type. The SDL queue types comprise high, normal, low, and lowest queue. You can monitor the SDL queue for a particular node or the entire cluster.

Service Monitoring

The Service monitoring category monitors the activities of the Cisco TFTP, the directory server, and the heartbeat information. See the following sections for more information on the directory server and heartbeat:

Cisco TFTP

Directory Servers

RTMT Heartbeat Feature

Cisco TFTP

The Cisco TFTP service builds and serves files that are consistent with the trivial file transfer protocol, which is a simplified version of the File Transfer Protocol (FTP). Cisco TFTP builds configuration files and serves embedded component executables, ringer files, and device configuration files.

You can view the total Cisco TFTP requests, requests not found, and requests that were aborted.

Directory Servers

Directory servers comprise database repositories that store user and device information such as user name, password, and location. The Cisco Unified CallManager publisher database server contains the directory where the directory settings are similar to SQL. Each node in the cluster has its own copy of the directory. The directory supports three types of directory: embedded, active, and Netscape. An embedded directory resides on the same node as its associated Cisco Unified CallManager (other types reside on other nodes in the cluster). A directory that resides on the publisher node provides write permission.

You can view the directory servers connection status. Directory server connection status and replication status get checked when an alert is pending. If the server is not connected, an alert occurs. The directory server connection status gets polled every 10 minutes; replication status gets polled once every hour.

RTMT Heartbeat Feature

The Real-Time Monitoring tool monitors the heartbeat of Cisco CallManagers, Cisco TFTPs, and Cisco TCDs. The heartbeat acts as an indicator of the life of whatever it is monitoring. When the heartbeat is lost, a blinking icon appears in the lower, right corner of the RTMT window. To find when the heartbeat loss was detected, click the blinking icon. An e-mail can notify you of the heartbeat loss.

Device Monitoring

The Device monitoring category provides a summary of devices and device search capability. The device summary monitors registered phone, gateway, and media resource devices on a particular Cisco Unified CallManager and an entire cluster. The device search category allows you to search for every device in a Cisco Unified CallManager cluster on the basis of the search criteria that you set up.


Note You can also access the device summary information in Device Summary in the Monitor menu in the menu bar. See "Monitor Menu" section for more information. You can also search for devices by using the Search menu in the menu bar. See the "Search Menu" section for more information.


CTI Monitoring

The CTI category monitors CTI Manager activities and provides CTI search capability. With CTI Manager, you can monitor the number of open devices, lines, and CTI connections.


Note You can also monitor the CTI Manager from CTI Manager in the Monitor menu in the menu bar. See the "Monitor Menu" section for more information. You can also search on CTI applications, devices, and lines by using the Search menu in the menu bar. See the "Search Menu" section for more information.


Perfmon Monitoring

RTMT displays performance information of all Cisco Unified CallManager components in a cluster. The tool integrates with Cisco Unified CallManager administration and serviceability software. RTMT provides an alert notification mechanism to ease the system administrator troubleshooting tasks. It also monitors various aspects of the Cisco Unified CallManager performance by periodically polling NT/2000 performance counter values. The system continuously monitors a set of common, preconfigured objects, and various alerts in the form of e-mail messages get generated for these objects when values are over or below user-configured thresholds. In addition, the system generates daily reports for these objects.

Perfmon monitoring provides the following services:

From the Cisco Unified CallManager cluster, monitors performance counters including Cisco Unified CallManager nodes, TFTP servers, and database servers.

Continuously monitors a set of preconfigured objects and notifies administrator in the form of an e-mail message.

Presents counters hierarchically for easy navigation.

Associates counter threshold settings to alert notification. An e-mail or popup message provides notification to the administrator.

Permits saving and restoring settings, such as counters being monitored, threshold settings, and alert notifications, for customized troubleshooting tasks.

Displays up to six perfmon counters in one chart for performance comparisons.

See the following sections for configuration options in the RTMT perfmon monitoring pane:

Category Tabs

Sample Rate

Perfmon Counters Table View/Chart View

Remove Chart/TableEntry

Refer to Chapter 12, "Real-Time Monitoring Configuration," in the Cisco Unified CallManager Serviceability Administration Guide for more configuration options.

Category Tabs

A category comprises monitored performance counters. A tab in the RTMT monitoring pane contains the category name. All performance counters that are monitored in this tab belong to a category. The system polls the performance counters in the tab at the same rate, with each category configured to have its own polling rate.

You can create custom categories in the RTMT monitoring pane to view information that helps you troubleshoot specific performance or device problems. If your Cisco Unified CallManager system is experiencing performance problems with specific objects, create custom categories to monitor the performance of the counters within the object. If the system is experiencing problems with specific devices, create custom categories to monitor the devices within the cluster. In addition, you can create alert notifications for counters and gateways in these custom categories.

To create custom categories, you add a new category tab. When the tab is created, you specify the specific performance counters, devices, and alerts within that tab and then save your custom category by using Profile.

Sample Rate

The Cisco Unified CallManager software polls counters, devices, and gateway ports to gather status information. In the RTMT monitoring pane, you configure the polling intervals for the performance counters, devices, and gateway ports for each category tab that you create.


Note High-frequency polling rate affects Cisco Unified CallManager performance. The minimum polling rate for monitoring a performance counter in chart view equals 5 seconds; the minimum rate for monitoring a performance counter in table view equals 1 second. The default for both specifies 10 seconds.


Perfmon Counters Table View/Chart View

The Cisco Unified CallManager software displays performance counters in chart or table format. Chart format looks like a miniature screen of information. Up to six charts display in the RTMT performance monitoring pane for each category tab that you create. You can display a particular counter by double clicking the counter in the perfmon monitoring pane. Because chart view represents the default, you configure the performance counters to display in table format when you create a category.

Remove Chart/TableEntry

You can remove a counter chart (table entry) with the Remove Chart/TableEntry menu item in the Perfmon menu in the menu bar. See the "Perfmon Menu" section for an example of the Perfmon menu.

Understanding Perfmon Monitoring

You can monitor the performance of the Cisco Unified CallManager software by choosing the counters for any object. The counters for each object display when the folder is expanded.

Add a Counter to Monitor

To troubleshoot system performance problems, you add the counter that is associated with the perfmon object to the RTMT performance monitoring pane, which displays a chart for the counter. Before you add counters, see the "Category Tabs" section.

Category tabs contain up to six perfmon counter charts.

Configure Alert Notification for Counter

Using the alert notification feature, Cisco Unified CallManager notifies you of system problems. Perform the following configuration setup to activate alert notifications for a system counter:

From the RTMT Perfmon Monitoring pane, choose the system perfmon counter.

Set up an e-mail or a message popup window for alert notification.

Determine the threshold for the alert (for example, an alert activates when calls in progress exceed the threshold of over 100 calls or under 50 calls).

Determine the frequency of the alert notification (for example, the alert occurs once or every hour).

Determine the schedule for when the alert activates (for example, on a daily basis or at certain times of the day).

Refer to "Real-Time Monitoring Configuration" in the Cisco Unified CallManager Serviceability Administration Guide for more detailed information.

Zoom Counter

To get a closer look at performance monitors, zoom the monitor counter in the RTMT perfmon monitoring pane by highlighting the counter chart and choosing Zoom Chart in the Perfmon menu.

Counter Properties

Counter properties provide two capabilities: display a description of the counter and configure data sampling parameters.

Property Description

Use one of two ways to obtain a description of the counter:

In the monitoring objects pane, right-click the counter to display only the description of the counter.

In the RTMT perfmon monitoring pane, right-click the counter chart to display the description and configure the data sampling parameters.

Data Sample

The Counter Property window contains the option to configure data samples for a counter. The performance counters that display in the RTMT performance monitoring pane contain green dots that represent samples of data over time. You can configure the number of data samples to collect and the number of data points to show in the chart. After the data sample is configured, view the information by using the View All Data/View Current Data menu selection. See View All Data for a Counter.

View All Data for a Counter

Use this view data for a monitor option to view all the data that was collected for a perfmon counter. See Counter Properties, for a description of data sample configuration.

Perfmon Monitoring Configuration Checklist

Table 9-6 provides an overview of the steps for monitoring perfmon counters.

Table 9-6 Performance Monitoring Configuration Checklist 

Configuration Steps
Related Procedures and Topics

Step 1 

Load RTMT.

Loading Real-Time Monitoring, Cisco Unified CallManager Serviceability Administration Guide

Step 2 

Choose a Cisco Unified CallManager object/counter to monitor and activate alert notification for the counter.

Adding a Counter to Monitor by Using the Perfmon Category, Cisco Unified CallManager Serviceability Administration Guide


Alert Tab

In RTMT you can configure alert notification for perfmon counter value thresholds, schedule for alert checking, and status change of device (for example, port is out of service).

The Alert tab in the left controlling center in the RTMT monitor window comprises the Alert Central category. Alert Central provides both the current status and the history of all the alerts in the Cisco Unified CallManager cluster.

Use the Alert tab in conjunction with the Alert menu in the RTMT menu bar to monitor Cisco Unified CallManager alerts. See the "Alert Menu" section for more information about the alert menu.

Alert Customization

You can configure both preconfigured and user-defined alerts in RTMT; however, you cannot delete preconfigured alerts. You can add and delete user-defined alerts. You can also disable both preconfigured and user-defined alerts in RTMT.

Table 9-7 provides a list of fields that you will use to configure each alert; consider all preconfigured fields as user-configurable unless otherwise marked.

Table 9-7 Alert Customization 

Field
Description
Comment

Alert Name

High-level name of the monitoring item with which RTMT associates an alert

Descriptive name. For preconfigured alerts, you cannot change this field. See the "Preconfigured Alerts" section.

Description

Description of the alert

You cannot edit this field for preconfigured alerts. See the "Preconfigured Alerts" section.

Perfmon Counters

List of source perfmon counters

For preconfigured alerts, you cannot change this field.

Value Threshold

Condition to raise alert (value is...)

Specify up < - > down, less than #, %, rate greater than #, %, rate.

Evaluation Method

Method used to check the threshold condition

Specify value to be evaluated as absolute, delta (present - previous), or % delta.

Duration Threshold

Condition to raise alert (how long value threshold has to persist before raising alert)

Options include right away and specify at least X minutes.

Number of Events Threshold

Raise alert only when a configurable number of events exceeds a configurable time interval (in minutes).

For ExcessiveVoiceQualityReports, the default thresholds equal 10 within 60 minutes.

For RouteListExhausted and MediaListExhausted, the defaults equal 0 within 60 minutes.

For MLAUserLoginFailed, the default equals 1 within 1 minute.

Node IDs

Cluster or list of nodes to monitor

Cisco Unified CallManager nodes, Cisco TFTP node, or publisher database node.

Note When you deactivate both Cisco CallManager and Cisco TFTP services for a node, the system considers that node removed from the currently monitored node list. When you reactivate both Cisco CallManager and Cisco TFTP services, that node gets added back, and its settings get restored to default values.

Alert Action ID

ID of alert action to take (System always logs alerts no matter what the alert action.)

Alert action gets defined first (see the "Alert Action Configuration" section). If this field is blank, that indicates that e-mail is disabled.

Disabled

Alert disabled

Options include enabled or disabled.

Clear Alert

To reset alert (change the color of an alert item from red to black) to signal that the alert has been resolved

After an alert is raised, its color will automatically change to red and stay that way until you manually clear the alert. Use Clear All to clear all alerts.

In Safe Range

To indicate whether an alert threshold condition has been met (not configurable)

This field does not apply to MaliciousCall and Registered YYY types of alerts. For DChannel OOS alert, this field specifies YES only when you no longer have any outstanding OOS devices. The Code Yellow alert goes back to safe range only when you receive a CodeYellowExit event from Cisco Unified CallManager.

Alert Details

To view the detail of an alert (not configurable)

For ExcessiveVoiceQualityReports, RouteListExhausted, MediaListExhausted, and MLAUserLoginFailed up to 30 current event details display in the current monitoring interval if an alert was raised in the current interval. Otherwise, the previous 30 event details in the previous interval display. For DChannel OOS alert, the list of outstanding OOS devices at the time that the alert was raised displays.

Alert Generation Rate

How often to generate alert when alert condition persists

Specify every X minutes. (Raise alert once every X minutes if condition persists.)

Specify every X minutes up to Y times. (Raise alert Y times every X minutes if condition persists.)

User Provide Text

Administrator to append text on top of predefined alert text

N/A

Severity

For viewing purposes (for example, show only Sev. 1 alerts)

Specify defaults that are provided for predefined alerts (for example, Error, Warning, Information).

Collection Polling Rate

Same rate for both preconfigured and user-defined alerts

Although not configurable through RTMT Alert Central, you can customize this rate through the service parameters in Cisco Unified CallManager Administration.


Alert Action Configuration

In RTMT, you can configure alert actions for every alert that is generated and have the alert action sent to e-mail recipients that you specify in the alert action list.

RTMT provides a list of fields that you use to configure alert actions. Consider all fields as user-configurable unless otherwise marked.

Table 9-8 Alert Action Configuration 

Field
Description
Comment

Alert Action ID

ID of alert action to take

Specify descriptive name.

Mail Recipients

List of e-mail addresses. You can selectively enable/disable an individual e-mail in the list.

N/A

Global Alert Action Flag

Flag to effectively disable all e-mails

If you have disabled this flag, you disabled all the e-mails, and no e-mails get sent out, even though alerts occur.


Preconfigured Alerts

RTMT comprises a set of preconfigured alerts. You cannot delete these alerts; however, you can enable or disable them in Alert Central. The following list comprises the preconfigured alerts in RTMT:

CallProcessingNodeCpuPegging

Code Yellow

CriticalServiceDown

DirectoryConnectionFailed

DirectoryReplicationFailed

ExcessiveVoiceQualityReports

LowAvailableDiskSpace

LowAvailableVirtualMemory

LowCallManagerHeartbeatRate

LowTcdServerHeartbeatRate

LowTFTPServerHeartbeatRate

MaliciousCallTrace

MediaListExhausted

MgcpDChannelOutOfService

MLAUserLoginFailed

NonCallProcessingNodeCpuPegging

NumberOfRegisteredGatewaysDecreased

NumberOfRegistedGatewaysIncreased

NumberOfRegisteredMediaDevicesDecreased

NumberOfRegisteredMediaDevicesIncreased

NumberOfRegisteredPhonesDropped

RouteListExhausted

Alert Configuration Checklist

Table 9-9 provides an overview of the steps for configuring alerts.

Table 9-9 Alert Configuration Checklist 

Configuration Steps
Related Procedures and Topics

Step 1 

Load RTMT.

Loading Real-Time Monitoring, Cisco Unified CallManager Serviceability Administration Guide

Step 2 

For non-preconfigured alerts, set up alert for counters within a category.

Adding a Counter to Monitor by Using the Perfmon Category, Cisco Unified CallManager Serviceability Administration Guide

Step 3 

Set up alert notification for a perfmon counter.

Configuring Alert Notification for a Counter, Cisco Unified CallManager Serviceability Administration Guide


Logging in RIS

See the following sections for information about logging in RIS in RTMT:

Logger

Alert Log

Server Log

Service Log

Call Log

Device Log

Perfmon Log

Logger

RTMT Collector uses the logger to log preconfigured monitoring objects information, and Alert Manager uses logger to log alert histories into log files. Each preconfigured object belongs to one of the four categories, namely devices, services, servers, and call activities. Each category has a separate log file. Alert details get logged in a separate file. Also, another log file exists for perfmon that logs the important perfmon object values for Cisco Unified CallManager-related services and processes.

The primary collector invokes the logger with the data from the whole of the Cisco Unified CallManager cluster. The locally written log files appear in the primary collector server at C:\Program Files\Common Files\Cisco\Logs\RTMTLogger. As the primary collector can change due to failover/fallback scenarios, the log files can exist in more than one server in the Cisco Unified CallManager cluster.

Log files exist in csv format. You can read log files, except alert log file, by native NT perfmon viewer. New log files get created every day at 00:00 hours on the local system. New logs for devices, services, servers, and calls get created when the time zone changes or when a new node is added to the cluster, or during failover/fallback scenarios. The first column of all these logs comprises the time zone information and the number of minutes from the Greenwich Meridian Time (GMT). Reporter uses these log files as data source to generate daily summary reports.

Alert Log

The Alert log stores the alert, which also gets stored in memory. The memory gets cleared at a constant interval, leaving the last 30 minutes of data in the memory. When the service starts/restarts, the last 30 minutes of alert data gets loaded into the memory by the system reading from the alert logs that exist in all servers in the cluster. The alert data in the memory gets sent to the RTMT clients on request.

Upon RTMT startup, RTMT shows all logs that occurred in the last 30 minutes in the Alert Central log history. Alert log periodically gets updated, and new logs get inserted into the log history window. After the number of logs reaches 100, RTMT removes the oldest 40 logs.

The file name format of the alert log will be AlertLog_MM_DD_YYYY_hh_mm.csv.

The alert log includes the following attributes:

Time Stamp—Time when RTMT logs the data

Alert Name—Descriptive name of the alert

Node ID—Name for node where RTMT raised the alert

Alert Message—Detailed description about the alert

Monitored Object Name—Name of the object monitored

Severity—Severity of the alert

PollValue—Value of the monitored object where the alert condition occurred

Action—Alert action taken

The first line of each log file comprises the header. Details of each alert get written in a single line, separated by a comma.

Server Log

The server data accumulates in the memory whenever the LogServer API is called. Every 5 minutes, the data gets logged into the file as a single record, and RTMT cleans the memory.

The system logs the data every 5 minutes for the following counters, based on the following calculation:

cpuUsage—Average of all the values that were collected in the last 5 minutes

MemoryInUse—Average of all the values that were collected in the last 5 minutes

DiskSpaceInUse—Average of all the values that were collected in the last 5 minutes

RISDC logs the server data in Windows Performance tool-compatible csv format. The header of the log comprises the time zone information and a set of columns with the previous counters for a Cisco Unified CallManager node. These sets of columns get repeated for every node.

The following file name format of the server log applies: ServerLog_MM_DD_YYYY_hh_mm.csv.

The first line of each log file comprises the header.

Service Log

The service data accumulates in the memory whenever RTMT calls the LogService API. Every 5 minutes, RTMT logs the data into the file as a single record and cleans the memory.

The data gets logged every 5 minutes for the following counters, based on the following calculation:

ctiOpenDevices—Average of all the values that were collected in last 5 minutes

ctiLines—Average of all the values that were collected in last 5 minutes

ctiConnections—Average of all the values that were collected in last 5 minutes

ctiActiveCMLinks—Average of all the values that were collected in last 5 minutes

tftpRequests—Cumulative value (difference between last collected value and the first collected value in last 5 minutes)

tftpAbortedRequests—Cumulative value (difference between last collected value and the first collected value in last 5 minutes)

RISDC logs the service data in Windows Performance tool-compatible scv format. The header of the log comprises the time zone information and a set of columns with the counters that were previously listed for a Cisco Unified CallManager node. These sets of columns repeat for every node.

The following file name format of the Service Log applies: ServiceLog_MM_DD_YYYY_hh_mm.csv.

The first line of each log comprises the header.

Call Log

The system accumulates call data in the memory whenever RTMT calls the LogCall API. Every 5 minutes, RTMT logs the data into the file as a single record and cleans the memory.

The system logs data every 5 minutes for the following counters on the basis of the following calculation:

cmCallsAttempted—Cumulative value (difference between last collected value and the first collected value in last 5 minutes)

cmCallsCompleted—Cumulative value (difference between last collected value and the first collected value in last 5 minutes)

cmCallsInProgress—Average of all the values that were collected in last 5 minutes

gwMGCP_FXS_CallsCompleted—Cumulative value (difference between last collected value and the first collected value in last 5 minutes)

gwMGCP_FXO_CallsCompleted—Cumulative value (difference between last collected value and the first collected value in last 5 minutes)

gwMGCP_PRI_CallsCompleted—Cumulative value (difference between last collected value and the first collected value in last 5 minutes)

gwMGCP_T1_CAS_CallsCompleted—Cumulative value (difference between last collected value and the first collected value in last 5 minutes)

gwH323_CallsAttempted—Cumulative value (difference between last collected value and the first collected value in last 5 minutes)

gwH323_CallsInProgress—Average of all the values that were collected in last 5 minutes

gwH323_CallsCompleted—Cumulative value (difference between last collected value and the first collected value in last 5 minutes)

trunkH323_CallsAttempted—Cumulative value (difference between last collected value and the first collected value in last 5 minutes)

trunkH323_CallsInProgress—Average of all the values collected in last 5 minutes

trunkH323_CallsCompleted—Cumulative value (difference between last collected value and the first collected value in last 5 minutes)

trunkSIP_CallsAttempted—Cumulative value (difference between last collected value and the first collected value in last 5 minutes)

trunkSIP_CallsInProgress—Average of all the values that were collected in last 5 minutes

trunkSIP_CallsCompleted—Cumulative value (difference between last collected value and the first collected value in last 5 minutes)

gwMGCP_FXS_PortsInService—Average of all the values that were collected in last 5 minutes

gwMGCP_FXO_PortsInService—Average of all the values that were collected in lasts 5 minutes

gwMGCP_PRI_SpansInService—Average of all the values that were collected in last 5 minutes

gwMGCP_T1_CAS_SpansInService—Average of all the values that were collected in last 5 minutes

gwMGCP_FXS_ActivePorts—Average of all the values that were collected in last 5 minutes

gwMGCP_FXO_ActivePorts—Average of all the values that were collected in last 5 minutes

gwMGCP_PRI_ActiveChannels—Average of all the values that were collected in last 5 minutes

gwMGCP_T1_CAS_ActiveChannels—Average of all the values that were collected in last 5 minutes

RISDC logs the call data in Windows Performance tool-compatible csv format. The header of the log comprises the time zone information and a set of columns with the previously listed counters for a node. These sets of columns repeat for every node.

The following file name format of the Call Log applies: CallLog_MM_DD_YYYY_hh_mm.csv.

The first line of each log file comprises the header.

Device Log

The device data accumulates in the memory whenever RTMT calls the LogDevice API. Every 5 minutes, RTMT logs the data into the file as a single record and cleans the memory.

The data gets logged every 5 minutes for the following counters based on the following calculation:

gatewayDevicesFXS—Average of all the values that were collected in last 5 minutes

gatewayDevicesFXO—Average of all the values that were collected in last 5 minutes

gatewayDevicesPRI—Average of all the values that were collected in last 5 minutes

gatewayDevicesT1—Average of all the values that were collected in last 5 minutes

gatewayDevicesH323—Average of all the values that were collected in last 5 minutes

RISDC logs the device data in Windows Performance tool-compatible csv format. The header of the log comprises the time zone information and a set of columns with the previously listed counters for a node. These sets of columns repeat for every node.

The following file name format of the Device Log applies: DeviceLog_MM_DD_YYYY_hh_mm.csv.

The first line of each log file comprises the header.

Perfmon Log

The Perfmon data gets logged whenever RTMT calls the LogPerfMon API. You can open the file log, which is compatible with the Windows Performance tool csv format, by using the Performance tool for analysis.

When you add new counters, RTMT changes the header to accommodate the new counters and logs the values correspondingly. When data is unavailable for an already existing counter (already added to header), RTMT inserts blank values in the file. If the character length of the new counters that are added is greater than 2000, the new file gets generated with all the counters.

The following file name format of the PerfMon Log applies: PerfMonLog_<NodeName>_MM_DD_YYYY_hh_mm.csv.

The following lists comprise the perfmon counters that RTMT logs:

At System Level

Cisco CallManager System Performance\QueueSignalsPresent 1-High

Cisco CallManager System Performance\QueueSignalsPresent 2-Normal

Cisco CallManager System Performance\QueueSignalsPresent 3-Low

Cisco CallManager System Performance\QueueSignalsPresent 4-Lowest

Cisco CallManager System Performance\QueueSignalsProcessed 1-High

Cisco CallManager System Performance\QueueSignalsProcessed 2-Normal

Cisco CallManager System Performance\QueueSignalsProcessed 3-Low

Cisco CallManager System Performance\QueueSignalsProcessed 4-Lowest

For Each Process That is Running on the System

Process\% Processor Time

Process\ID Process

Process\Private Bytes

Process\Virtual Bytes

Where to Find More Information

Related Topics

"Microsoft Performance"

Chapter 18, "Simple Network Management Protocol"

"Cisco Unified CallManager Performance Counters, RTMT, and CISCO-CCM-MIB"

Chapter 12, "Real-Time Monitoring Configuration," Cisco Unified CallManager Serviceability Administration Guide

Chapter 23, "Microsoft Performance," Cisco Unified CallManager Serviceability Administration Guide

Chapter 31, "Simple Network Management Protocol Configuration," Cisco Unified CallManager Serviceability Administration Guide