7-115
Cisco Unified Communications Manager Managed Services Guide
OL-22523-01
Chapter 7 Cisco Management Information Base
CISCO-CCM-MIB
Windows and Cisco Unified CM version 4.x
Collect the following logs for analysis:
•
Set the Alarm level from the ccmservice Alarm Configuration window for Cisco Unified CM to
Detailed.
•
Set the RIS Trace configuration from the ccmservice window to Detailed.
•
Do a snmpwalk on the ccm MIB from the network management application or execute command
from any linux box by using the
snmpwalk - c
<
community
>
-v2c
<
ipaddress
> 1.3.6.1.4.1.9.9.156.
•
Capture the ouput of the snmpwalk.
•
Collect the logs under C:\Program Files\Cisco\Trace\RIS\CCMSNMP_*.log.
•
Collect the logs under C:\Program Files\Cisco\Trace\DBL\ DBL_SNMP*.txt.
•
Event logs (both application and system).
•
mmfSpy output for 'misc', 'CMnode' tables.
•
MMFSpy tool to dump registration status (C:\Program Files\Cisco\Bin\MMFSpy.exe, gives
different options). Usage: "mmfSpy -j > OutputFileName".
CISCO-CCM-MIB only supports a limited amount of configuration information about a device. For
more complete configuration information, the AXL interface accessing the data in DB serves the
purpose.
The list of MMFs that are created by the Cisco Unified CM Agent are as follows:
•
cmnode
•
cmgroup
•
cmgroupmember
•
region
•
regionmatrix
•
timezone
•
devicepool
•
phonefailed
•
phonestatsupd
•
cmproduct
•
cmmodel
Limitations
If multiple OIDs are specified in the SNMP request and if the variables are pointing to empty tables in
CISCO-CCM-MIB, then the request will take longer. In case the getbulk/getnext/getmany request has
multiple OIDs in its request PDU with the subsequent tables being empty in the CISCO-CCM-MIB, the
responses may be NO_SUCH_NAME for SNMP v1 version or GENERIC_ERROR for SNMP v2c or v3
version.
•
Reason—This timeout occurs due to the code added to enhance the performance of the CCMAgent
and throttle when it gets a large number of queries thus protecting the priority of Cisco Unified CM
callprocessing engine.
