6-334
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
Chapter 6 Cisco Unified Serviceability Alarms and CiscoLog Messages
Informational-Level Alarms
StationConnectionError
Station device is closing its connection with Cisco Unified Communications Manager because of the
reason that is stated in this alarm.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Informational
Parameters
Device Name [String]
Reason Code[Enum]
Enum Definitions -Reason Code
History
Cisco Unified Communications
Release Action
8.0(1) • Reason Code[Enum] parameter added.
• Enum Definitions for Reason Code table added.
Code Reason
0 deviceInitiatedReset—The device has initiated a reset, possibly due to a power cycle or
internal error. No action required; the device will re-register automatically.
1 sccpDeviceThrottling—(SCCP only) The indicated SCCP device exceeded the maximum
number of events allowed per-SCCP device. Events can be phone calls, KeepAlive messages,
or excessive SCCP or non-SCCP messages. The maximum number of allowed events is
controlled by the Cisco CallManager service parameter, Max Events Allowed. When an
individual device exceeds the number configured in that service parameter, Unified CM closes
the TCP connection to the device; automatic reregistration generally follows. This action is an
attempt to stop malicious attacks on Unified CM or to ward off excessive CPU usage. No
action necessary, the device will re-register automatically.
2 keepAliveTimeout—Unified CM did not receive a KeepAlive message from the device.
Possible causes include device power outage, network power outage, network configuration
error, network delay, packet drops and packet corruption. It is also possible to get this error if
the Unified CM node is experiencing high CPU usage. Verify the device is powered up and
operating, verify network connectivity between the device and Unified CM, and verify the
CPU utilization is in the safe range (this can be monitored using RTMT via CPU Pegging
Alert). No action necessary, the device will re-register automatically.
Comments to this Manuals