Use this Knowledge Script to monitor call throttling and signal processing queues for a Communications Manager. This script raises an event if a threshold is exceeded. In addition, this script generates data streams for the following metrics:
Low, normal, and high priority signals that are processed and in queue
Calls rejected due to throttling
Throttled SCCP (Skinny Client Control Protocol) devices
Number of times the Communications Manager went into a throttling state
Average amount of expected delay
Throttling refers to an internal process within Communications Manager that prevents it from being inundated with heavy call traffic.
This script is a member of the CiscoCM recommended Knowledge Script Group. For more information, see Section 4.57, Recommended Knowledge Script Group.
CiscoCM_CallProcessor
By default, this script runs every five minutes.
If you are running this script as part of the Recommended KSG, do not change the schedule. The schedules for the recommended scripts are staggered so as to lessen the impact on CPU utilization when you run the KSG.
Set the following parameters as needed:
|
Parameter |
How to Set It |
|---|---|
|
General Settings |
|
|
Job Failure Notification |
|
|
Event severity when job fails |
Set the event severity level, from 1 to 40, to indicate the importance of the failure of the CCM_SystemPerformance job. The default is 5. |
|
Event Notification |
|
|
Raise event if call throttling warning (Code Yellow) state entered? |
Select Yes to raise an event if Communications Manager enters a Code Yellow call throttling warning state. The default is Yes. |
|
Event severity when call throttling warning (Code Yellow) state entered |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which Communications Manager enters a Code Yellow call throttling state. The default is 10. |
|
Raise event if severe (Code Red) call throttling state entered? |
Select Yes to raise an event if Communications Manager enters a severe (Code Red) call throttling state. The default is Yes. |
|
Event severity when severe (Code Red) call-throttling state entered |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which Communications Manager enters a severe (Code Red) call-throttling state. The default is 5. |
|
Monitor High Priority Signals in Queue |
|
|
Event Notification |
|
|
Raise event if high priority signals in queue exceed threshold? |
Select Yes to raise an event if the number of high-priority signals in queue exceeds the threshold you set. The default is Yes. |
|
Threshold - Maximum high priority signals in queue |
Specify the maximum number of high-priority signals that must be in queue before an event is raised. The default is 500 signals. |
|
Event severity when high priority signals in queue exceed threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the number of high-priority signals in queue exceeds the threshold you set. The default is 5. |
|
Data Collection |
|
|
Collect data for high priority signals in queue? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the number of high-priority signals in queue at each script iteration. The default is unselected. |
|
Monitor High Priority Signals Processed |
|
|
Data Collection |
|
|
Collect data for high priority signals processed? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the number of high-priority signals that were recently processed at each script iteration. The default is unselected. |
|
Monitor Normal Priority Signals in Queue |
|
|
Event Notification |
|
|
Raise event if normal priority signals in queue exceed threshold? |
Select Yes to raise an event if the number of normal priority signals in queue exceeds the threshold you set. The default is Yes. |
|
Threshold - Maximum normal priority signals in queue |
Specify the maximum number of normal-priority signals that must be in queue before an event is raised. The default is 1000 signals. |
|
Event severity when normal priority signals in queue exceed threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the number of normal-priority signals in queue exceeds the threshold you set. The default is 5. |
|
Data Collection |
|
|
Collect data for normal priority signals? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the number of normal-priority signals in queue at each script iteration. The default is unselected. |
|
Monitor Normal Priority Signals Processed |
|
|
Data Collection |
|
|
Collect data for normal priority signals processed? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the number of normal-priority signals that were recently processed at each script iteration. The default is unselected. |
|
Monitor Low Priority Signals in Queue |
|
|
Event Notification |
|
|
Raise event if low priority signals in queue exceed threshold? |
Select Yes to raise an event if the number of low-priority signals in queue exceeds the threshold you set. The default is Yes. |
|
Threshold - Maximum low priority signals in queue |
Specify the maximum number of low-priority signals that must be in queue before an event is raised. The default is 1000 signals. |
|
Event severity when low priority signals in queue exceed threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the number of low-priority signals in queue exceeds the threshold you set. The default is 15. |
|
Data Collection |
|
|
Collect data for low priority signals in queue? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the number of low-priority signals in queue at each script iteration. The default is unselected. |
|
Monitor Low Priority Signals Processed |
|
|
Data Collection |
|
|
Collect data for low priority signals processed? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the number of low-priority signals that were recently processed at each script iteration.The default is unselected. |
|
Monitor Rejected Calls |
|
|
Event Notification |
|
|
Raise event if rejected calls exceed threshold? |
Select Yes to raise an event if the number of rejected calls exceeds the threshold you set. The default is Yes. |
|
Threshold - Maximum rejected calls |
Specify the maximum number of calls that must be rejected before an event is raised. The default is 10 calls. |
|
Event severity when rejected calls exceed threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the number of rejected calls exceeds the threshold you set. The default is 5. |
|
Data Collection |
|
|
Collect data for rejected calls? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the number of calls rejected during the monitoring period. The default is unselected. |
|
Monitor Throttled SCCP Devices |
|
|
Event Notification |
|
|
Raise event if throttled SCCP devices exceed threshold? |
Select Yes to raise an event if the number of throttled SCCP devices exceeds the threshold you set. The default is Yes. |
|
Threshold - Maximum throttled SCCP devices |
Specify the maximum number of SCCP devices that must be throttled before an event is raised. The default is 10 devices. |
|
Event severity when throttled SCCP devices exceed threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the number of throttled SCCP devices exceeds the threshold you set. The default is 5. |
|
Data Collection |
|
|
Collect data for throttled SCCP devices? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the number of SCCP devices throttled during the monitoring period. The default is unselected. |
|
Monitor Call-Throttling |
|
|
Event Notification |
|
|
Raise event if number of times in call-throttling mode exceeds threshold? |
Select Yes to raise an event if the number of times Communications Manager entered a call-throttling state exceeds the threshold you set. The default is Yes. |
|
Threshold - Maximum number of times in call-throttling mode |
Specify the maximum number of times Communications Manager must enter a call-throttling state before an event is raised. The default is 0 times. |
|
Event severity when number of times in call-throttling mode exceeds threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the number of times Communications Manager entered a call-throttling state exceeds the threshold you set. The default is 15. |
|
Data Collection |
|
|
Collect data for number of times in call-throttling mode? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the number of times Communications Manager entered a call-throttling state during the monitoring period. The default is unselected. |
|
Monitor Average Expected Delay |
|
|
Event Notification |
|
|
Raise event if average expected delay exceeds threshold? |
Select Yes to raise an event if the average amount of time it takes Communications Manager to handle incoming messages exceeds the threshold. The default is Yes. |
|
Threshold - Maximum average expected delay |
Specify the maximum amount of average delay Communications Manager can expect before an event is raised. The default is 2 seconds. |
|
Event severity when average expected delay exceeds threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the average amount of expected delay exceeds the threshold you set. The default is 15. |
|
Data Collection |
|
|
Collect data for average expected delay? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the average amount of expected delay. The default is unselected. |