Specifications

6-76
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
Chapter 6 Cisco Unified Serviceability Alarms and CiscoLog Messages
Critical-Level Alarms
CodeYellowEntry
CallManager has initiated call throttling due to unacceptably high delay in handling incoming calls.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Critical
Parameters
Expected Average Delay [UInt] Entry Latency [UInt] Exit Latency [UInt] Sample Size [UInt] Total
Code Yellow Entry
[UInt]
Recommended Action
Memory problems or high CPU usage are generally at the root of a Code Yellow state. A bad disk could
also be the cause. Also, trace level settings can consume tremendous amounts of CPU (especially when
the Enable SDL TCP Event Trace checkbox is enabled on the SDL Trace Configuration window in Cisco
Unified Serviceability). Check these areas to try to correct the Code Yellow condition. You can also
determine the level of fragmentation on the hard disk by issuing the File Fragmentation command from
the CLI for the trace directories. Monitor the situation and collect existing trace files. If the
CodeYellowExit alarm is not issued in a reasonable amount of time as deemed by your organization, or
if the system is frequently entering Code Yellow state, contact TAC and supply the trace information
you have collected.
DChannelOOS
The D-channel is out of service. D-channel indicated by this alarm has gone out of service. Common
reasons for a D-channel going out of service include losing T1/E1/BRI cable connectivity; losing the
gateway data link (Layer 2) due to an internal or external problem; or gateway reset.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
History
Cisco Unified Communications
Release Action
8.0(1) Severity changed from Error to Critical.
History
Cisco Unified Communications
Release Action
8.0(1) Severity changed from Error to Critical.