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

Chapter 6 Cisco Unified Serviceability Alarms and CiscoLog Messages
126
131
132
133
134
227
228
229
230
232
254
255
30027
30028
30032
Enum Definition
Code
1
6
8
9
10
11
OL-22523-01
TONE_ANNOUNCEMENT_PLAYER
SIP_TRUNK
SIP_GATEWAY
WSM_TRUNK
REMOTE_DESTINATION_PROFILE
7915_12_BUTTON_LINE_EXPANSION_MODULE
7915_24_BUTTON_LINE_EXPANSION_MODULE
7916_12_BUTTON_LINE_EXPANSION_MODULE
7916_24_BUTTON_LINE_EXPANSION_MODULE
CKEM_36_BUTTON_LINE_EXPANSION_MODULE
UNKNOWN_MGCP_GATEWAY
UNKNOWN
ANALOG_PHONE
ISDN_BRI_PHONE
SCCP_GATEWAY_VIRTUAL_PHONE
Reason
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.
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).
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.
Cisco Unified Communications Manager Managed Services Guide
Warning-Level Alarms
6-229