Use this Knowledge Script to access the Host Resource MIB to monitor the status of a device and the number of errors that have occurred since the last iteration of the script. This script raises an event if a device is down or if errors occur. In addition, this script generates datastreams for device status and the number of errors.
NOTE:This script retrieves the error count from the DeviceErrors field of the Host Resource MIB.
NetworkDevice Host Device
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 Host_DeviceStatus job. The default is 5. |
|
Event severity when job returns warnings |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the job completes with warnings. The default is 25. |
|
Event severity when monitoring fails |
Set the event severity level, from 1 to 40, to indicate the importance of an event that is raised when monitoring fails. The default is 25. |
|
SNMP Settings |
|
|
SNMP timeout |
Specify the length of time in milliseconds that the job should wait for the SNMP response from the monitored network device before timing out and raising a failure event. The default is 2000 milliseconds. |
|
SNMP retries |
Specify the number of times the job should attempt to get the SNMP response from the monitored network device. The default is 1 attempt. |
|
Raise event if device is down? |
Select Yes to raise an event if the monitored device is down. The default is Yes. |
|
Event severity when device is down |
Set the severity level, between 1 and 40, to indicate the importance of an event in which the monitored device is down. The default is 10. |
|
Collect data for device status? |
Select Yes to collect data for charts, graphs, and reports. When enabled, data collection returns 100 if the device is up or 0 if the device is down. The default is No. |
|
Raise event if device errors occur? |
Select Yes to raise an event if errors occurred since the last iteration of the script. The default is Yes. |
|
Event severity when device errors occur |
Set the severity level, between 1 and 40, to indicate the importance of an event in which errors occurred since the last iteration of the script. The default is 10. |
|
Collect data for device errors? |
Select Yes to collect data for charts, graphs, and reports. When enabled, data collection returns a datastream for the number of errors that have occurred since the last iteration of the script. The default is No. |
|
Raise one-time events? |
Select Yes to raise an event for all one-time events. If you set this parameter to Yes, then AppManager raises an event when a particular performance counter cannot be found in an iteration. For example, if this script does not find a particular performance counter in the first iteration, AppManager raises an event on the first iteration and does not raise further events for consecutive failures. This script raises further one-time events only on the iteration when there are failure events following successful retrieval of the performance counters. If you do not want to see such one-time events, set this parameter to No. |