Cisco MCS-7825-H3-IPC1 Service Manual page 388

Error-Level Alarms
Enum Definitions -Reason Code
Value
1
2
3
4
5
6
7
8
9
10
11
12
13
Cisco Unified Communications Manager Managed Services Guide
6-154
Definition
Unknown—The device has unregistered for an unknown reason. If the device does not
reregister within 5 minutes, verify it is powered-up and verify network connectivity between
the device and Cisco Unified CM.
NoEntryInDatabase—Device not configured properly in the Cisco Unified CM database.
DatabaseConfigurationError—Device configuration error in the Cisco Unified CM database.
DeviceNameUnresolveable—The Cisco Unified CM is unable to resolve the device name to
an IP Address internally.
MaxDevRegExceeded—Maximum number of device registrations have been reached.
ConnectivityError—Network communication between the device and Cisco Unified CM has
been interrupted. 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 Cisco Unified CM node is experiencing high CPU usage. Verify
the device is powered up and operating, verify network connectivity between the device and
Cisco Unified CM, and verify the CPU utilization is in the safe range (this can be monitored
using RTMT via CPU Pegging Alert).
InitializationError—Indicates that an error occurred when the Cisco Unified CM tries to
initialize the device.
DeviceInitiatedReset—The device has initiated a reset, possibly due to a power cycle or
internal error. No action required; the device will reregister automatically.
CallManagerReset—A device reset was initiated from Cisco Unified CM Administration,
either due to an explicit command from an administrator, or due to internal errors
encountered. No action necessary, the device will reregister automatically.
DeviceUnregistered—The device has explicitly unregistered. Possible causes include a
change in the IP address or port of the device. No action is necessary, the device will reregister
automatically.
MalformedRegisterMsg—(SIP only) A SIP REGISTER message could not be processed
because of an illegal format. Possible causes include a missing Call-ID header, a missing AoR
in the To header, and an expires value too small. Verify the REGISTER message does not
suffer from any of these ills.
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 reregister automatically.
KeepAliveTimeout—A KeepAlive message was not received. 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 reregister automatically.
Chapter 6 Cisco Unified Serviceability Alarms and CiscoLog Messages
OL-22523-01