6-210
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
Chapter 6 Cisco Unified Serviceability Alarms and CiscoLog Messages
Warning-Level Alarms
6 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).
8 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.
9 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 re-register automatically.
10 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
re-register automatically.
11 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.
12 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.
13 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 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).
14 ConfigurationMismatch (SIP only) The configuration on the device does not match the
configuration in Cisco Unified CM. This can be caused by database replication errors or
other internal Cisco Unified CM communication errors. First go to the Cisco Unified
Reporting web page, generate a Unified CM Database Status report, and verify "all
servers have a good replication status". If this device continues to unregister with this
reason code, go to the CCMAdmin Device web page for the device and click Save. This
allows a change notify to be generated to the Unified CM and TFTP services and rebuild
a new config file. If the problem still persists, restart the TFTP service and Cisco Unified
CM service.
15 CallManagerRestart - A device restart was initiated from Cisco Unified CM, either due
to an explicit command from an administrator, or due to a configuration change such as
adding, deleting or changing a DN associated with the device. No action necessary, the
device will re-register automatically.
Comments to this Manuals