6-33
Cisco Unified Communications Manager Managed Services Guide
OL-22523-01
Chapter 6 Cisco Unified Serviceability Alarms and CiscoLog Messages
Preconfigured CallManager Alarm Notifications
• NumberOfRegisteredGatewaysIncreased, page 6-47
• NumberOfRegisteredMediaDevicesDecreased, page 6-48
• NumberOfRegisteredMediaDevicesIncreased, page 6-49
• NumberOfRegisteredPhonesDropped, page 6-49
• RouteListExhausted, page 6-49
• SDLLinkOutOfService, page 6-50
• TCPSetupToIMEFailed, page 6-51
• TLSConnectionToIMEFailed, page 6-51
BeginThrottlingCallListBLFSubscriptions
This alert occurs when the BeginThrottlingCallListBLFSubscriptions event gets generated. This
indicates that the Cisco Unified Communications Manager initiated a throttling of the CallList BLF
Subscriptions to prevent a system overload.
CallProcessingNodeCpuPegging
This alert occurs when the percentage of CPU load on a call processing server exceeds the configured
percentage for the configured time.
Note If the administrator takes no action, high CPU pegging can lead to a crash, especially in
CallManager service. CoreDumpFound and CriticalServiceDown alerts might also get issued.
The CallProcessingNodeCpuPegging alert gives you time to work proactively to avoid a Cisco
Unified Communications Manager crash.
Table 6-23 Default Configuration for the BeginThrottlingCallListBLFSubscriptions RTMT Alert
Value Default Configuration
Enable Alert Selected
Severity Critical
Enable/Disable this
alert on the
following servers
Enabled on listed servers
Threshold Trigger alert when following condition met:
BeginThrottlingCallListBLFSubscriptions event generated
Duration Trigger alert immediately
Frequency Trigger alert on every poll
Schedule 24 hours daily
Enable E-mail Selected
Trigger Alert Action Default