Use this Knowledge Script to monitor the status of H.248 media gateways, including the following items:
Major alarms
Minor alarms
Warning alarms
Status of H.248 (server to gateway) link
This script raises an event if a threshold is exceeded. In addition, this script generates data streams for each monitored value.
NOTE:If you bypass SNMP to discover a call manager (by selecting the Discover using manual configuration? parameter), this script is not available.
AvayaCM H.248 Media Gateway object
By default, this script runs every 5 minutes.
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 H248GatewayStatus 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 Major Alarms |
|
Event Notification |
|
Raise event if number of major alarms exceeds threshold? |
Select Yes to raise an event if the number of major alarms exceeds the threshold you set. The default is Yes. |
Threshold - Maximum major alarms |
Specify the highest number of major alarms that can occur before an event is raised. The default is 1 alarm. |
Event severity when number of major alarms exceeds threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the number of major alarms exceeds the threshold. The default is 5. |
Data Collection |
|
Collect data for major alarms? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the number of major alarms that occurred during the monitoring period. The default is Yes. |
Monitor Minor Alarms |
|
Event Notification |
|
Raise event if number of minor alarms exceeds threshold? |
Select Yes to raise an event if the number of minor alarms exceeds the threshold you set. The default is Yes. |
Threshold - Maximum minor alarms |
Specify the highest number of minor alarms that can occur before an event is raised. The default is 5 alarms. |
Event severity when number of minor alarms exceeds threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the number of minor alarms exceeds the threshold. The default is 10. |
Data Collection |
|
Collect data for minor alarms? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the number of minor alarms that occurred during the monitoring period. The default is Yes. |
Monitor Warning Alarms |
|
Event Notification |
|
Raise event if number of warning alarms exceeds threshold? |
Select Yes to raise an event if the number of warning alarms exceeds the threshold you set. The default is Yes. |
Threshold - Maximum warning alarms |
Specify the highest number of warning alarms that can occur before an event is raised. The default is 10 alarms. |
Event severity when number of warning alarms exceeds threshold |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the number of warning alarms exceeds the threshold. The default is 15. |
Data Collection |
|
Collect data for warning alarms? |
Select Yes to collect data for charts and reports. If enabled, data collection returns the number of warning alarms that occurred during the monitoring period. The default is unselected. |
Monitor H.248 Link Status |
|
Event Notification |
|
Raise event if H.248 link is down? |
Select Yes to raise an event if the H.248 link is unavailable. The default is Yes. |
Event severity when H.248 link is down |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the H.248 link is unavailable. |
Data Collection |
|
Collect data for link status? |
Select Yes to collect data for charts and reports. If enabled, data collection returns 0 if the link is up or 1 if the link is down. The default is Yes. |