/mcp[HighPriorityQueueDepth=Long][NormalPriorityQueueDepth=Long][LowPriorityQueueDepth=Long] [AppID=String][ClusterID=String][NodeID=String]: Unified CM has exited Code Yellow. Explanation Unified CM has ceased throttling calls and has exited the Code Yellow state Recommended Action Notification purposes only; no action is required Error Message %UC_CALLMANAGER-2-CodeRedEntry: %[AverageDelay=UInt][EntryLatency=UInt][ExitLatency=UInt] [SampleSize=UInt][CodeYellowDuration=UInt][NumberOfCallsRejectedDueToCallThrottling=UInt] [TotalCodeYellowEntry=UInt][TotalCodeYellowExit=UInt][HighPriorityQueueDepth=Long] [NormalPriorityQueueDepth=Long][LowPriorityQueueDepth=Long][AppID=String][ClusterID=String] [NodeID=String]: Unified CM has entered Code Red condition and will restart. Explanation Unified CM has been in Code Yellow state for an extended period and is unlikely to recover on its own. The Cisco CallManager service automatically restarts in an attempt to clear the condition that is causing the Code Yellow state. The amount of time that the system will remain in Code Yellow state is configurable in the Code Yellow Duration service parameter. If the duration of this parameter is set to 99999, Code Red condition will never occur. Recommended Action Make certain that you have attempted the steps in the recommended actions defined in the CodeYellowEntry alarm. If you have not, try those after the system is online. There is no other action for Code Red because the only action is to restart which occurs automatically. Error Message %UC_CALLMANAGER-2-SignalCongestionEntry: %[Thread=String][AverageDelay=UInt] [EntryLatency=UInt][ExitLatency=UInt][SampleSize=UInt][TotalSignalCongestionEntry=UInt] [HighPriorityQueueDepth=Long][NormalPriorityQueueDepth=Long][LowPriorityQueueDepth=Long] [AppID=String][ClusterID=String][NodeID=String]: Unified CM has detected signal congestion in an internal thread and has throttled activities for that thread. Explanation Unified CM has initiated throttling for an internal thread due to unacceptably high delay in handling signals Recommended Action Memory problems or high CPU usage are generally at the root of signal congestion. 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). Use RTMT to check for memory leaks, causes of any CPU spikes, and determine whether the server has sufficient memory for the tasks expected of this server. Run server diagnostics to determine if the disk is bad, and examine/reconfigure the SDL trace settings in Unified Serviceability to ensure that trace settings are not contributing to the signal congestion. You can determine the level of fragmentation on the hard disk by issuing the File Fragmentation command from the CLI for the trace directories. After taking one or more of these corrective actions, monitor the situation and collect existing trace files. If the SignalCongestionExit alarm is not issued in a reasonable amount of time as deemed by your organization, or if the system is frequently triggering the SignalCongestionEntry alarm, contact the Cisco Technical Assistance Center (TAC) and supply the trace information you have collected. Error Message %UC_CALLMANAGER-5-SignalCongestionExit: %[Thread=String][AverageDelay=UInt] [EntryLatency=UInt][ExitLatency=UInt][SampleSize=UInt][TimeSpentInSignalCongestion=UInt] [NumberOfCallsRejected=UInt][TotalSignalCongestionExit=UInt][HighPriorityQueueDepth=Long] 5/24/26, 3:34 AM System Error Messages for Cisco Unified Communications Manager 15 - Cisco https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/err_msgs/15_x/ccmalarms15.html 268/343