Configuring Remote Serviceability for Cisco CallManager, Release 3.0
Using the Performance Console

Table Of Contents

Using the Performance Console

Monitoring Cisco CallManager System Performance

Performance Data Structure

Objects, Counters and Instances in Cisco CallManager Release 3.0

Using Performance with Cisco CallManager

Starting Performance

Setting up Performance

Cisco CallManager Release 3.0 Counters

Generating Performance Statistics

Reporting Cisco CallManager Performance Statistics

Extending Your Data Display


Using the Performance Console


Performance is a Windows 2000 server application that can display the activities and status of your Cisco CallManager system. It reports both general and specific information in real time.

Cisco CallManager Release 3.0 was designed to run in a Windows 2000 environment. Using the Windows 2000 Performance console, you can monitor the performance of Cisco CallManager Release 3.0 on local or remote installations.

For more information about Performance, consult your Windows 2000 documentation.

Monitoring Cisco CallManager System Performance

You can use Windows 2000 Performance to collect and display system and device statistics for any Cisco CallManager installation. This administrative tool allows you to gain a full understanding of a system without studying the operation of each of its components.

You can use Performance to monitor a variety of system variables in real time. After adding the Cisco CallManager parameters, you can define the terms under which Cisco CallManager will display statistics generated by the system.

Performance Data Structure

Cisco CallManager uses the Performance framework to display performance monitoring statistics. Performance categorizes collections of data as object-oriented code, and the Cisco CallManager installation process expands this collection by adding a set of object counters which describe Cisco CallManager functions.

The Cisco CallManager counters are available for display in the Performance interface (see Figure 4-1). The Windows 2000 documentation gives additional information on objects and counters available from the operating system or from other applications.

Figure 4-1 Text Report of Cisco CallManager Release 3.0 Counters

Objects, Counters and Instances in Cisco CallManager Release 3.0

Each Cisco CallManager object includes counters that keep track of statistics like the number of calls in progress or number of calls attempted. These counters define current conditions within groups of related information.

Each group of related information can be considered an object which contains multiple counters, and each of those objects can have more than one instance. All of the objects and counters are automatically added during the Cisco CallManager installation process, and the system parses this information before any statistics are displayed.

This arrangement allows you to retrieve detailed, relevant and timely information from the system for display. You can also customize Performance to track additional objects and counters.

Using Performance with Cisco CallManager

You may want to use Performance to monitor any number of conditions on a Cisco CallManager Release 3.0 system. For example, you can discover the number of calls in progress on a particular Cisco CallManager system at any time, or the number of calls currently being attempted on a Cisco CallManager system.

Starting Performance

To launch the Performance tool:


Step 1 From the Windows 2000 desktop, go to Start > Programs > Administrative Tools > Performance.

Step 2 The Performance graphical interface (Figure 4-2) appears.


Once the tool has been launched, you can start setting up, generating, and reporting Cisco CallManager performance data.

Figure 4-2 Windows 2000 Performance Monitoring Tool

Setting up Performance

Setting up Performance can yield statistics that are customized to reflect your Cisco CallManager system. For example, you may use the information Performance returns to manage traffic on the system by monitoring the number of calls in progress at any particular moment. (See Figure 4-3.)

Figure 4-3 Setting Up Performance Monitoring

To set up performance monitoring:


Step 1 From the Windows 2000 desktop, go to Start > Programs > Administrative Tools > Performance. The Performance graphical interface (Figure 4-3) appears.

Step 2 Select the Cisco CallManager system you will be monitoring. If the system is local, the computer name will be detected automatically.

Step 3 Use the Explain button to get a description of each of the counters available.

Step 4 Select a Cisco CallManager Performance object. Select the counter or counters which will describe the statistics you want to monitor.

Step 5 Select Add to start gathering data for the counters you specified. The Add Counter dialog box will disappear and the Performance interface will reappear.


Cisco CallManager Release 3.0 Counters

This table describes each of the counters available for Cisco CallManager Release 3.0.

Table 4-1 Cisco CallManager Release 3.0 Counters 

Object/Counter
Description

Calls Active

The number of connections with active voice streaming.

Calls Attempted

The number of calls attempted. Any time a phone goes off-hook and back on-hook it is considered an attempted call, regardless of whether any digits were dialed or if it connected to a destination. Some call attempts are made by the system during transfer operations and are considered attempted calls.

Calls Completed

The number of calls connected—that is, calls for which a voice path was established. This number is incremented when the call is terminated.

Calls In Progress

The number of calls currently in progress anywhere on the system. This includes all active calls. Once all calls that are attempted have connected, the number of calls in progress and the number of active calls are the same.

Licenses Available Station

The number of total station licenses purchased minus the currently allocated station licenses.

Licenses In Use Station

The number of station licenses assigned. This includes only purchased licenses.

MediaTermPoints Active

The number of media termination points currently active in the system.

MediaTermPoints Available

The number of media termination points currently available for use.

MediaTermPoints Out of Resources

The number of times a media termination point allocation was requested and there was none available.

Multicast Conferences Active

The number of Multicast conferences that are currently active. An active Multicast conference has one or more call connections.

Multicast Conferences Completed

The number of Multicast conferences that have been activated and de-activated. A Multicast conference is activated when the first call is connected to the Multicast conference. The conference is de-activated when the last call is disconnected from the Multicast point.

Multicast Active Conference Participants

The number of participants currently active in all the Multicast conferences.

Multicast Available Conferences

The number of new Multicast conferences that can be started at this point in time. (A minimum of three streams must be available for each new conference.)

Multicast Out of Resources

The number of times a Multicast conference was attempted when there was no available Multicast conference resource.

Registered Analog Accesses

The number of Cisco Access Analog gateways registered with this system. This does not include the number of analog access ports.

Registered Digital Accesses

The number of Cisco Access Digital gateways registered with this system. This does not include the number of digital access ports.

Registered MGCP Gateway

The number of Cisco MGCP gateways registered with this system.

Registered Phones

The number of currently registered Cisco CallManager devices. This device type includes all models of Cisco IP Phones.

Unicast Active Conference Participants

The number of participants currently active in all the Unicast conferences.

Unicast Available Conferences

The number of new Unicast conferences that can be started at this point in time. (A minimum of three streams must be available for each new conference.)

Unicast Conferences Active

The number of Unicast conferences that are currently active. An active Unicast conference has one or more call connections.

Unicast Conferences Completed

The number of Unicast conferences that have been activated and de-activated. A Unicast conference is activated when the first call is connected to the bridge. The conference is de-activated when the last call is disconnected from the bridge.

Unicast Out of Resources

The number of times a Unicast conference was attempted when there was no available Unicast conference resource.


Generating Performance Statistics

The statistical data that is retrieved through Performance provides the structure for analysis and interpretation of any local or remote Cisco CallManager system. You may have selected specific counters to return data describing changing activity levels in your system, or you may have chosen to simply react as events occur.

Performance visually formats the statistical data to facilitate your quick comprehension of the state of the system. Using the visual formats provided, you can display Cisco CallManager data in graphical, histogram or report form.

Reporting Cisco CallManager Performance Statistics

To report Cisco CallManager performance statistics:


Step 1 From the Windows 2000 desktop, go to Start > Programs > Administrative Tools > Performance. The Performance graphical interface (Figure 4-3) appears.

Step 2 Select the Cisco CallManager system you will be monitoring. If the system is local, the computer name will be detected automatically.

Step 3 Select one of the three report forms represented by the icons at the top of the window and allow Performance to display your statistics.


Extending Your Data Display

Each report form offers a different visual rendition of the statistical data. You may want to repeat the process to choose the most effective display.

You may want to try adding counters from other objects to see how dynamic data affects your Cisco CallManager data. For purposes of illustration, Figure 4-4 shows active operating system conditions with inactive Cisco CallManager data. When your Cisco CallManager data is added, you can interpret that information in the context of any number of system counters.

By combining standard counters with the Cisco CallManager criteria, you can get a clear picture of your systems so that you can manage them more efficiently.

Figure 4-4 Line Graph of Static Call Data