Cisco MCS-7825-H3-IPC1, Руководство по обслуживанию

Страница: 761 / 974

7-119
Cisco Unified Communications Manager Managed Services Guide
OL-22523-01
Chapter 7 Cisco Management Information Base
CISCO-CCM-MIB
–
Dial 9XXXX in one of the phone.
– Then check if a "RouteListExhausted" Alarm/Alert/Trap is generated.
•
MaliciousCallFailed trap
– Similar as QRT, create a softkey template. In the template, add all available "MaliciousCall"
softkey to the phone's different status.
–
Assign the new softkey template to real phones, reset the phones.
– Making calls, select the "MaliciousCall" in the phone screen during or after the call.
–
Then check if a "MaliciousCallFailed" Alarm/Alert/Trap is generated
• GatewayFailed trap (Method 1)
–
Remove the configuration of the gateway from the database through Web Admin (or) Change
the MAC address of the gateway to some invalid value and update.
– Reboot the gateway
–
Another way is to restart the Cisco Unified CM service to which the gateway is connected.
• GatewayFailed trap (Method 2)
–
Set GatewayAlarmEnable=true in ccmAlarmConfigInfo mib table
– In ccm serviceability->Snmp configuration page, make sure you have SNMP community string
and trap destination set correctly.
–
Create a gateway failure event and the trap will be seen on the trap receiver.
– To cause a gateway fail, Restart Cisco Unified CM service which will cause gateway failover to
the redundant ccm manager server. On that server, the gateway should not be configured in the
database.
•
ccmGatewayLayer2Change trap
– ccmGatewayLayer2Change trap is triggered during DChannelOOS(D Channel Out of service)
or DChannelISV (D Channel Inservice) from Cisco Unified CM. Please check if any such events
can be triggered to test it out
•
ccmCallManagerFailed trap
– The CallManager Failed Alarm is generated when an internal error is encountered. These
include an internal thread dying due to lack of CPU, timer issues and a couple others. This trap
would be something that is hard to reproduce unless the CallManager team give a friendly that
intentionally causes one of these occurrences.
If the Cisco Unified CM Agent consumes high CPU continuously, what needs to be done?
Collect the logs as mentioned above (under Troubleshooting) for analysis and refer to defect
CSCsm74316 to check if it is being hit. Verify if the fix for the defect has gone into the Cisco Unified
CM version used by the customer.
If the CTI Routepoint is deleted from Cisco Unified CM Admin UI, an entry exists for that in ccmCTIDeviceTable
mib. Why?
There is service parameter called “RIS Unused Cisco CallManager Device Store Period” which defines
how long Unregistered devices (when a registered device is removed from db, it unregisters) will remain
in RISDB and hence in the MIB. The ccmadmin page and the SNMP MIB WALK may or may not be in
sync, since the ccmadmin page shows the info from the database however SNMP uses the RISDB.