Table Of Contents

Objects and Counters

Overview

Microsoft Performance

Real-Time Monitoring

SNMP MIBs

Counter Similarities

Phone Counters

Gateway Counters

Where to Find More Information

Objects and Counters

---

This chapter provides an overview of Cisco CallManager objects and counters and contains the following topics:

•Overview

•Microsoft Performance

•Real-Time Monitoring

•SNMP MIBs

•Counter Similarities

•Where to Find More Information

Overview

Cisco CallManager supports three real-time information monitoring applications:

•Microsoft Performance

•Real-Time Monitoring

•SNMP management information base

The following sections provide a brief description of the applications and how Cisco CallManager uses them.

Microsoft Performance

Cisco CallManager directly updates Microsoft Performance counters (called perfmon counters), which are call-processing-related counters. The counters contain simple, useful counts such as number of registered phones, number of active calls, and number of available conference bridge resources.

The following list identifies the 11 Cisco CallManager perfmon objects (objects contain the counters):

•Cisco CallManager

•Cisco Phones

•Cisco Lines

•Cisco H323

•Cisco MGCP Gateways

•Cisco MOH Device

•Cisco Analog Access

•Cisco MGCP FXS Device

•Cisco MGCP FXO Device

•Cisco MGCP T1CAS Device

•Cisco MGCP PRI Device

The Cisco CallManager object contains most of the perfmon counters, and these counters have only one instance. The instance-based counters belonging to the other objects can have zero or more instances. For example, if two phones are registered to Cisco CallManager, two instances of each counter belonging to the Cisco Phones object exist.

The counters within each object contain descriptions. The Microsoft Performance counter descriptions match the Real-Time Monitoring tool counter descriptions.

Real-Time Monitoring

The Cisco CallManager Real-Time Monitoring (RTM) tool provides monitoring of Cisco CallManager performance objects and devices. The device information includes device registration status, IP address, description, and model type. RTM provides cluster-wide information stored in six tables. The tables include phone, gateway devices, media, H323 devices, CTI, and voice mail.

RTM also displays perfmon counter information kept by each Cisco CallManager node in the cluster. RTM perfmon counters directly monitor the perfmon counters (the same as Microsoft Performance).

The counters within each object contain descriptions. The Microsoft Performance counter descriptions match the RTM counter descriptions.

For more information about Real-Time Monitoring, see Chapter 8, "Real-Time Monitoring."

SNMP MIBs

The Cisco CallManager SNMP extension agent resides in each Cisco CallManager node and exposes the CCM_SNMP_MIB that provides detailed information about devices known to the node. The CCM_SNMP_MIB provides device information such as device registration status, IP address, description, and model type for the node (not the cluster).

The following list identifies the CCM_SNMP_MIB device tables:

•ccmPhoneTable

•ccmPhoneExtensionTable

•ccmPhoneFailedTable

•ccmPhoneStatusUpdateTable

•ccmGatewayTable

•ccmMediaDeviceTable

•ccmGatekeeperTable

•ccmCTIDeviceTable

CCM_SNMP_MIB supports four counters as follows:

•ccmActivePhones

•ccmInActivePhones

•ccmActiveGateways

•ccmInActiveGateways

For more information about SNMP, see Chapter 15, "Simple Network Management Protocol."

Counter Similarities

The perfmon counters for phones and gateways have related or overlapping information that is also used by RTM device monitoring and CCM_SNMP_MIB. See "Cisco CallManager Perfmon Counters, RTM, and CCM_SNMP_MIB," for related information.

Phone Counters

CCM_SNMP_MIB defines four counters (see SNMP MIBs); one counter matches the perfmon counter: ccmActivePhones matches RegisteredHardwarePhones.

If RTM searches for all registered phones for a particular node, the number of matching phones found equals the perfmon RegisteredHardwarePhones and CCM_SNMP_MIB ccmActive Phones counters.

Gateway Counters

The CCM_SNMP_MIB counter and ccmActiveGateway relate to the RegisteredAnalogAccess and RegisteredMGCPGateway perfmon counters but are not the same; for example, the VG200 with two FXS ports and one T1 port. Because each port individually registers and communicates with Cisco CallManager, Cisco CallManager treats each port as a separate device and generates device alarms for each separately. Cisco CallManager considers the VG200 to be a single gateway and, at the same time, three separate devices (2 FXS ports and 1 T1 port).

Device alarm provides the basis for CCM_SNMP_MIB and basis counting for that. The ccmActiveGateway counts the number of registered devices; RegisteredMGCPGateway perfmon counter counts number of registered gateways. Cisco CallManager considers a gateway registered if any of its subdevices is registered to Cisco CallManager. In the previous example, Cisco CallManager considers the VG200 with two FXS port and one T1 port registered when only the T1 port is registered to Cisco CallManager, and the count remains one. When the two FXS ports are also registered, the count remains one because all the interface/ports are on the same VG200 gateway.

Where to Find More Information

Related Topics

•Chapter 8, "Real-Time Monitoring"

•Chapter 9, "Microsoft Performance"

•Chapter 15, "Simple Network Management Protocol"

•"Cisco CallManager Perfmon Counters, RTM, and CCM_SNMP_MIB"

•Understanding Performance Counters, Cisco CallManager Serviceability Administration Guide

•Viewing Performance Statistics, Cisco CallManager Serviceability Administration Guide

Additional Cisco Documentation

•Cisco CallManager Troubleshooting Guide