4-6
Cisco Unified Communications Manager Managed Services Guide
OL-22523-01
Chapter 4 Simple Network Management Protocol
SNMP Troubleshooting
If Cisco CallManager SNMP service is not running, only the following tables in the MIB respond:
• ccmGroupTable
• ccmRegionTable
• ccmRegionPairTable
• ccmDevicePoolTable
• ccmProductTypeTable
• ccmQualityReportAlarmConfigInfo
• ccmGlobalInfo
To get Cisco CallManager SNMP service running, activate and start the service in Cisco Unified
Serviceability. Query the following tables in the SYSAPPL-MIB:
• SysApplInstallPkgTable to get an inventory of Cisco Unified Communications Manager
applications that are installed on the system.
• SysApplRunTable to get an inventory of Cisco Unified Communications Manager applications that
are running on the system.
Note Cisco Unified Communications Manager uses the following Web application services and servlets:
Cisco CallManager Admin, Cisco CallManager Cisco IP Phone Services, Cisco CallManager Personal
Directory, Cisco CallManager Serviceability, Cisco CallManager Serviceability RTMT, Cisco Extension
Mobility, Cisco Extension Mobility Application, Cisco RTMT Reporter Servlet, Cisco Tomcat Stats
Servlet, Cisco Trace Collection Servlet, Cisco AXL Web Service, Cisco Unified Mobile Voice Access
Service, Cisco Extension Mobility, Cisco IP Manager Assistant, Cisco Web Dialer Service, Cisco CAR
Web Service, and Cisco Dialed Number Analyzer.
SNMP Troubleshooting
In general ensure that all the feature and network services are running and verify that the community
string or SNMP user is properly configured on the Cisco Unified CM system. You configure the SNMP
community string or user by choosing SNMP > V1/V2 > Community String or SNMP > V3> User in
Cisco Unified Serviceability.
Other tips are as follows:
• Cannot poll any MIBs from the system—This condition means that the community string or the
SNMP user is not configured on the system or they do not match with what is configured on the
system. Check the configuration and reconfigure if necessary.
Note By default, no community string or user is configured on the system.
• Cannot receive any notifications from the system—This condition means that the notification
destination is not configured correctly on the system. Verify that you configured the notification
destination properly in the Notification Destination (V1/V2c or V3) Configuration window.
• Cannot receive SNMP traps from Cisco Unified Communications Manager node—Verify that you
configured the following MIB Object IDentifiers (OIDs) that relate to phone
registration/deregistration/failure to the following values (the default for both values equals 0):
To Next Page
Loading...
Need help?
General