Use this Knowledge Script to monitor the status of a trunk group. This script raises an event if a monitored value exceeds the threshold you set. In addition, this script generates data streams for the following statistics:
Total number of hours all trunks are busy with calls
Percentage of time all trunks are simultaneously in use
Calls in queue
Calls not in queue
Out-of-service trunks
NOTE:If you bypass SNMP to discover a call manager (by selecting the Discover using manual configuration? parameter), this script is not available.
AvayaCM Trunk Group object
By default, this script runs every hour because the SNMP data it monitors is updated only once an hour. If you change the schedule to a shorter interval, you may receive SNMP request errors until the SNMP data is repopulated.
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 TrunkGroupUsage job. The default is 5. |
|
Enable use of SNMP GETBulk operations? |
Select Yes to allow this Knowledge Script to access Communication Manager MIBs using GETNext and GETBulk SNMP requests, as appropriate. The default is Yes. Deselect the check box to allow the Knowledge Script to use only GETNext requests. Not all MIB tables are extensive enough to need a GETBulk request. A GETBulk request is faster, but more CPU-intensive than a GETNext request. |
|
Number of rows to request for each GETBulk operation |
Specify the number of rows from the MIB table to return in a GETBulk request. The default is 10 rows. The number of rows determines how fast the MIB data is returned. If the CPU usage is too high, you can reduce the number of rows per GETBulk request or deselect the Enable use of SNMP GETBulk requests? parameter. |
|
Interval to pause between GETBulk operations |
Specify the number of milliseconds to wait between GETBulk requests. The default is 100 milliseconds. The length of the delay can help manage CPU usage and the speed of SNMP requests. For example, a one-row GETBUlk with a 100-millisecond delay between requests executes more slowly and uses less CPU than a GETNext request. |
|
Monitor Total Time Trunks Busy with Calls |
|
|
Event Notification |
|
|
Raise event if total hours trunks busy with calls exceeds threshold? |
Select Yes to raise an event if the total number of hours that all trunks are busy with calls exceeds the threshold you set. The default is Yes. |
|
Threshold - Maximum total hours trunks busy with calls |
Specify the highest number of hours that all trunks can be busy with calls before an event is raised. The default is 1 hour. |
|
Event severity when total hours trunks busy with calls exceeds threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the total number of hours that all trunks are busy with calls exceeds the threshold. The default is 15. |
|
Data Collection |
|
|
Collect data for total hours trunks busy with calls? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the total number of hours that all trunks were busy with calls during the monitoring period. The default is Yes. |
|
Monitor Calls Queued |
|
|
Event Notification |
|
|
Raise event if number of calls queued exceeds threshold? |
Select Yes to raise an event if the number of calls in queue exceeds the threshold you set. The default is Yes. |
|
Threshold - Maximum calls queued |
Specify the maximum number of calls that can be in queue before an event is raised. The default is 10 calls. |
|
Event severity when number of calls queued exceeds threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the number of calls in queue exceeds the threshold. The default is 15. |
|
Data Collection |
|
|
Collect data for calls queued? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the number of calls in queue during the monitoring period. The default is Yes. |
|
Monitor Calls Not Queued |
|
|
Event Notification |
|
|
Raise event if number of calls not queued exceeds threshold? |
Select Yes to raise an event if the number of calls not in queue exceeds the threshold you set. The default is Yes. Calls not in queue are calls that were offered to the trunk group when the queue was full. |
|
Threshold - Maximum calls not queued |
Specify the maximum number of calls that can be not queued before an event is raised. The default is 5 calls. |
|
Event severity when number of calls not queued exceeds threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the number of calls not queued exceeds the threshold. The default is 15. |
|
Data Collection |
|
|
Collect data for calls not queued? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the number of calls not queued during the monitoring period. The default is unselected. |
|
Monitor Trunks Out of Service |
|
|
Event Notification |
|
|
Raise event if number of trunks out of service exceeds threshold? |
Select Yes to raise an event if the number of out-of-service trunks exceeds the threshold you set. The default is Yes. |
|
Threshold - Maximum trunks out of service |
Specify the maximum number of trunks that can be out of service before an event is raised. The default is 1 trunk. |
|
Event severity when number of trunks out of service exceeds threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the number of out-of-service trunks exceeds the threshold. The default is 15. |
|
Data Collection |
|
|
Collect data for trunks out of service? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the number of trunks that were out of service during the monitoring period. The default is Yes. |
|
Monitor Percent Time Trunks in Use |
|
|
Event Notification |
|
|
Raise event if percent of time all trunks simultaneously in use exceeds threshold? |
Select Yes to raise an event if the percentage of time that all trunks are simultaneously in use exceeds the threshold you set. The default is Yes. |
|
Threshold - Maximum percent of time all trunks simultaneously in use |
Specify the highest percentage of time that all trunks can be simultaneously in use before an event is raised. The default is 1%. |
|
Event severity when percent of time all trunks simultaneously in use exceeds threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the percentage of time that all trunks are simultaneously in use exceeds the threshold. The default is 15. |
|
Data Collection |
|
|
Collect data for percent of time all trunks simultaneously in use? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the percentage of time that all trunks were simultaneously in use during the monitoring period. The default is Yes. |