5.2.2 Statuses of monitoring nodes
The status of monitoring objects and groups is managed on the basis of the JP1 events generated in the particular object.
A monitoring node has two different types of statuses:
-
Status
The events occurring on a monitoring node are managed according to the status of the node.
Node statuses, in order of priority, are Emergency, Alert, Critical, Error, Warning, Normal, Debug, and Initial.
For example, if an error occurs on a node, resulting in a JP1 event of Emergency level, the Central Scope manages the event according to the current status of the node.
-
Monitoring status
Information that determines whether to monitor the node status.
There are two monitoring statuses: Monitor and Do not monitor.
When Monitor is set for a node, the status of the node changes when a JP1 event matching the monitoring conditions is received. Statuses are color-coded in the Monitoring Tree window and Visual Monitoring window.
When Do not monitor is set for a node, the status of the node does not change even when a JP1 event is received from the node. The node is grayed out in the Monitoring Tree window and Visual Monitoring window.
A node has Initial status when monitoring begins. This means that the Central Scope does not yet have any information about the status of the node.
If Monitor is set for an object and a JP1 event of Emergency level occurs because of a failure, for example, the status of the object changes on receipt of the JP1 event by JP1/IM - Manager. Whether a status change occurs in an object is determined by a status change condition.
When the status of an object changes, its new status is passed in succession to each of the higher-level groups in the monitoring tree. If the new status has higher priority than the status of the receiving group, or if the status of the lower-level node satisfies the status change condition of the receiving group, the status of that group changes.
If Do not monitor is set for an object, the status of the monitoring node does not change, even when a JP1 event is received because of an error on the node. If the object's monitoring status is changed to Monitor, the status of the node will change according to JP1 events subsequently received from the object. Do not monitor is the default status for an automatically generated monitoring tree.
- Organization of this subsection
(1) Behavior when changing the status of a monitoring node manually
You can change the status of a monitoring node manually. The statuses that can be set, and the status change behavior, differ according to whether the monitoring node consists of monitoring objects or monitoring groups.
Monitoring node type |
Specifiable statuses and status change behavior |
---|---|
Monitoring object |
You can change the node status to Emergency, Alert, Critical, Error, Warning, Normal, Debug, or Initial#1. When the node status changes, the new information is relayed upward through the tree, and the status of each higher-level monitoring group changes to the status that has highest priority among the statuses of the lower-level monitoring nodes. |
Monitoring group |
You can change the node status to Initial#1 only. When the node status changes, the new information is relayed upward through the tree, and the status of each higher-level monitoring group changes to the status that has highest priority among the statuses of the lower-level monitoring nodes (same behavior as for a monitoring object). The status of all lower-level monitoring nodes changes to Initial. |
#1: Manually changing the status of a monitoring node deletes the status change events logged for that node (see 5.7.2 Searching for status change events).
#2: The status of a monitoring group changes to the highest status among the lower-level nodes. However, when a status change condition is set for a group, that condition takes precedence.
You can change a node status manually using the GUI or the jcschstat command (for the command syntax, see jcschstat in Chapter 1. Commands in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
When you change a node's monitoring status to Do not monitor, the monitoring status of all lower-level nodes is reset to Do not monitor. The node itself and all lower-level nodes revert to Initial status. Similarly, when you change a node's monitoring status to Monitor, all lower-level nodes also change to Monitor.
When a higher-level node has been reset to Do not monitor, you cannot change the lower-level nodes back to Monitor status. To change a lower-level node back to Monitor status, you must change the higher-level node from Do not monitor to Monitor again.