OVNM 5.3 - Operations Agent for NonStop Object Configuration Client Guide

Object Configuration Client: The Understanding 34
3-4 Monitoring
Monitoring is inactivated by default on the HP NonStop host when OCC is started. The OCC Monitoring
Gateway is responsible for the overall monitoring. When any object’s monitoring is started, OCC forwards the
appropriate commands to the OCC Monitoring Gateway, which further reads the information from the Objects
database and starts the monitoring process. The HP NonStop host will do the monitoring as per the checks
specified for the threshold configuration.
The initial monitoring status of the configuration can be specified using the Monitoring box in the Threshold
dialog box while creating a threshold configuration.
Figure 3-6 OCC Threshold Dialog Box with Monitoring Box
The objects can be in two different states. The two different states are as follows:
• Active
This option activates monitoring for the objects that are to be monitored at a particular time of the day.
OCC polls each configured object to check for any violations.
• Inactive
This option inactivates monitoring for the objects that are not to be monitored at present and OCC will
temporarily stop polling the configured objects for any violations. This is the default option.
First, the HP NonStop host checks for the value in the Monitoring box. It will proceed with monitoring only in case
the value has been set as Active. If the value in the Monitoring box is Inactive, it will skip monitoring for that
object and move on to the next one.
Next, it checks for the parameters like Poll Interval set in the Schedule dialog box when the threshold was
created. Depending on the values specified in this dialog box, it will proceed with the appropriate actions
assigned for that object.
Refer to the Scheduling section for more details on the various parameters in the Schedule dialog box.
NOTE:
Inactivating the monitoring is considered as a Pause in the monitoring process. This means that OCC
will stop issuing events for the objects in the Violation State and the database will not be modified. If at the
time of inactivation the object was in a violation state, the state after activation will be the same as before
inactivation, even though
the object could be in a normal state now. This situation will be in effect until the next
poll interval. This is applicable for inactivating at the object, configuration and system levels.
Object Configuration Client:
The Understanding