Cisco MCS-7825-H3-IPC1 Service Guide - Page 762

CISCO-CCM-MIB Chapter 7 Cisco Management Information Base When ccmPhoneType is queried from ccmPhoneTable in Cisco-CCM-MIB, no information is returned. Why? The ccmPhoneType has been made obsolete. The same information can be retrieved from ccmPhoneProductTypeIndex against CcmProductTypeEntry. In the table, the indexes correspond to the index and name as listed in that table. Some of other obsolete and alternate OIDs to be referred: • ccmGatewayType is obsolete and need to refer ccmGateWayProductTypeIndex. • ccmMediaDeviceType is obsolete and need to refer to ccmMediaDeviceProductTypeIndex • ccmCTIDeviceType is obsolete and need to refer to ccmCTIDeviceProductTypeIndex A query on ccmPhoneProductTypeIndex returns zero. Why? Verify that the Cisco Unified CM release that you are using has this capability. While performing a WALK on ccmPhoneTable, ccmPhoneUserName is not returning any value. How are usernames associated to the IP Phones? Create an end user and then go to the phone that has been registered and associate the Owner User ID. Once this is done, the user will be shown by the OID in the SNMP Walk. How do I get the firmware versions of each phone by using SNMP? ccmPhoneLoadID object in the ccmPhoneTable will give the firmaware version of each phone. But this value may differ if new image download failed. In case of 7.x versions SNMP will expose both configured firmware ID (ccmPhoneLoadID) and the actual running firmware (ccmPhoneActiveLoad). CCM MIB returns ccmVersion as 5.0.1, which is the incorrect. Verify the Cisco Unified CM release that you are using has this capability. If it does not, upgrade. CCM MIB returns incorrect ccmPhoneLoadID ccmPhoneLoadID values are picked up from RISDB which is populated based on the alarm received during Phone registration. Perform the following steps and collect the logs for further analysis: Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Go to Serviceability web page -> Alarm -> Configuration -> Service Group (CM Services) -> Service (Cisco CallManager). Check Local Syslog, SDI Trace, SDL Trace. Ensure the Alarm Event Level for these selected destinations is set to Informational. Set the Cisco CallManager trace level to Detailed. Reset the phones showing incorrect LoadID. Collect the Syslog and Cisco CallManager traces. Collect the phone details. How Cisco Unified CM status (START/STOP) monitored? For service monitoring we have following options: • SYSAPPL MIB • HOST-RESOURCE-MIB • CISCO-CCM-MIB (ccmStatus) 7-120 Cisco Unified Communications Manager Managed Services Guide OL-22523-01