3.16 Host_CPULoaded

Use this Knowledge Script to access the Host Resource MIB to monitor CPU usage on a host device. This script raises an event if CPU usage exceeds the threshold that you set. In addition, this script generates a datastream for percentage of CPU usage during the monitoring period.

NOTE:For a Nortel CS1000 version 4.5 Call Server, this script monitors call capacity usage rather than CPU usage. In version 4.5 devices, the MIB value for the CPU processor load represents call capacity usage.

3.16.1 Resource Object

NetworkDevice Host Processor

3.16.2 Default Schedule

By default, this script runs every 5 minutes.

3.16.3 Setting Parameter Values

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_CPULoaded 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.

Collect data for CPU utilization for each processor?

Select Yes to collect data for charts, graphs, and reports. When enabled, data collection returns the overall CPU usage percentage for each processor. The default is No.

Collect data for average CPU utilization across all processor?

Select Yes to collect data for charts, graphs, and reports. When enabled, data collection returns the average CPU usage percentage across all processors. The default is No.

Threshold - Maximum CPU utilization for individual processor

Specify the maximum CPU usage that must occur for each processor before an event is raised. The default is 50%.

Event severity when individual CPU utilization exceeds threshold (0 for no event)

Set the event severity level, from 1 to 40, to indicate the importance of an event in which CPU usage exceeds the threshold for each processor. If you do not want to raise an event, set the severity level to 0. The default is 10.

Raise event if average CPU utilization exceeds threshold?

Select Yes to raise an event if the average CPU usage across all the processors exceeds the threshold. The default is No.

Event severity when average CPU utilization exceeds threshold (0 for no event)

Set the event severity level, from 1 to 40, to indicate the importance of an event in which average CPU usage exceeds the threshold. If you do not want to raise an event, set the severity level to 0. The default is 10.

Threshold-Maximum average CPU utilization

Specify the maximum average CPU usage that must occur across all processors before an event is raised. The default is 50%.

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.