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

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

7-117
Cisco Unified Communications Manager Managed Services Guide
OL-22523-01
Chapter 7 Cisco Management Information Base
CISCO-CCM-MIB
Syslog' destination from the Alarm configuration available on Cisco Unified CM Serviceability web
page->Alarm->Configuration. Then repro the traps and see if corresponding alarms are logged in
CiscoSyslog file.
Receiving syslog messages as traps —To receive syslog messages above a particular severity as traps,
set the following 2 MIB objects in the clogBasic table:
•
clogNotificationsEnabled (1.3.6.1.4.1.9.9.41.1.1.2) —Set this to true(1) to enable syslog trap
notification. Default value is false (2). For example, snmpset -c < Community String > -v 2c
< transmitter ip address > 1.3.6.1.4.1.9.9.41.1.1.2.0 i < value >.
• clogMaxSeverity (1.3.6.1.4.1.9.9.41.1.1.3) —Set the severity level above which traps are desired.
Default value is warning (5). All syslog messages with alarm severity lesser than or equal to
configured severity level will be sent as traps if notification is enabled. For example,
snmpset -c
< Community String > -v 2c < transmitter ip address > 1.3.6.1.4.1.9.9.41.1.1.3.0 i < value >
What are the different traps defined for Cisco Unified Communication Manager?
The CISCO-CCM-MIB contains the traps related information. Following are the list of defined traps
defined:
•
ccmCallManagerFailed—Indication that the CallManager process detects a failure in one of its
critical subsystems. It can also be detected from a heartbeat/event monitoring process.
• ccmPhoneFailed—Notification that the intervals specified in ccmPhoneFailedAlarmInterval
indicate at least one entry in the ccmPhoneFailedTable.
•
ccmPhoneStatusUpdate—Notification that is generated in the intervals specified in
ccmPhoneStatusUpdateInterv if there is at least one entry in the ccmPhoneStatusUpdateTable.
•
ccmGatewayFailed—Indication that at least one gateway has attempted to register or communicate
with the CallManager and failed.
Note ccmGatewayFailed is deprecated and replaced by ccmGatewayFailedReason.
• ccmMediaResourceListExhausted—Indication that the CallManager has run out a certain specified
type of resource
•
ccmRouteListExhausted—Indication that the CallManager could not find an available route in the
indicated route list.
• ccmGatewayLayer2Change—Sent when the D-Channel/Layer 2 of an interface in a skinny gateway
that has registered with the CallManager changes state.
•
ccmMaliciousCall—Sent when a user registers a call as malicious with the local Cisco Unified CM
• ccmQualityReport—Sent when a user reports a quality problem using the Quality Report Tool
•
ccmTLSConnectionFailure—Sent when CallManager fails to open TLS connection for the indicated
device
The mapping of the traps to alarms is as follows:
•
ccmCallManagerFailed—CallManagerFailure
• ccmPhoneFailed—DeviceTransientConnection
•
ccmPhoneStatusUpdate
• ccmGatewayFailed—DeviceTransientConnection
•
ccmMaliciousCall—MaliciousCall
•
ccmMediaResourceListExhausted—MediaResourceListExhausted