Cisco MCS-7825-H3-IPC1 Service Guide - Page 169
Cisco CallManager System Performance
View all Cisco MCS-7825-H3-IPC1 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 169 highlights
Chapter 5 Cisco Unified Real-Time Monitoring Tool Tracing, PerfMon Counters, and Alerts Performance Monitoring in RTMT Cisco CallManager System Performance The Cisco CallManager System Performance object provides system performance information about Cisco Unified Communications Manager. Table 5-8 contains information about Cisco CallManager system performance counters. Table 5-8 Cisco CallManager System Performance Counters AverageExpectedDelay CallsRejectedDueToICTThrottling CallThrottlingGenericCounter3 CodeRedEntryExit CodeYellowEntryExit EngineeringCounter1 EngineeringCounter2 EngineeringCounter3 EngineeringCounter4 EngineeringCounter5 EngineeringCounter6 EngineeringCounter7 EngineeringCounter8 QueueSignalsPresent 1-High Counter Description This counter represents the current average expected delay before any incoming message gets handled. This counter represents the total number of calls that were rejected since the start of Cisco CallManager service due to Intercluster Trunk (ICT) call throttling. When the threshold limit of 140 calls per 5 seconds is met, the ICT will start throttling (rejecting) new calls. One cause for ICT call throttling occurs when calls across an ICT enter a route loop condition. This counter represents a generic counter that is used for call-throttling purpose. This counter indicates whether Cisco Unified Communications Manager has entered or exited a Code state (call-throttling mode). Valid values include 0 (Exit) and 1 (Entry). This counter indicates whether Cisco Unified Communications Manager has entered or exited a Code Yellow state (call-throttling mode). Valid values include 0 (Exit) and 1 (Entry). Do not use this counter unless directed by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes. Do not use this counter unless directed by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes. Do not use this counter unless directed by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes. Do not use this counter unless directed by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes. Do not use this counter unless directed by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes. Do not use this counter unless directed by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes. Do not use this counter unless directed by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes. Do not use this counter unless directed by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes. This counter indicates the number of high-priority signals in the Cisco Unified Communications Manager queue. High-priority signals include timeout events, internal Cisco Unified Communications Manager keepalives, certain gatekeeper events, and internal process creation, among other events. A large number of high-priority events will cause degraded performance on Cisco Unified Communications Manager and result in slow call connection or loss of dial tone. Use this counter in conjunction with the QueueSignalsProcessed 1-High counter to determine the processing delay on Cisco Unified Communications Manager. OL-22523-01 Cisco Unified Communications Manager Managed Services Guide 5-15