5.2.4 Event generation condition

A monitoring node can issue a JP1 event when its status changes.

As an event generation condition, you can specify the type of status change that will cause the node to issue a JP1 event. This JP1 event cannot be issued when the node status changes to Initial.

The issued JP1 event has event ID 00003FB0.

Details about this JP1 event are as follows. This information is taken from Chapter 3. JP1 Events in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

Table 5‒3: Details about event ID 00003FB0 (from the above manual)
Attribute type		Item	Attribute name	Contents
Basic		Source event server name	`SOURCESERVER`	The name of the event server that issued the JP1 event
Basic		Message	`MESSAGE`	`KAVB7900-I` message
Extended	Common information	Event level	`SEVERITY`	`Information`
		Product name	`PRODUCT_NAME`	`/HITACHI/JP1/IM/SCOPE`
		Object type	`OBJECT_TYPE`	`SERVICE`
		Object name	`OBJECT_NAME`	`IM_CS`
		Occurrence	`OCCURRENCE`	`STATUS_CHANGE`
	Program- specific information	Monitoring node ID	`MON_NODE_ID`	The ID of the monitoring node
		Monitoring node name	`MON_NODE_NAME`	The name of the monitoring node
		Monitoring node status^#1	`MON_NODE_STATUS`	The StatusID of the monitoring node
		Information about the JP1 event that triggered the status change^#2	`attribute-name`	The attribute value (basic attribute value prefixed with `JCS_B_` or extended attribute value prefixed with `JCS_E_`)

#1: The monitoring node status (E.MON_NODE_STATUS) is stored as one of the following numeric values, which is called the node's StatusID.

Value of StatusID (monitoring node status):

Emergency: 800, Alert: 700, Critical: 600, Error: 500,

Warning: 400, Normal: 300, Debug: 200, Initial: 100

For example, the JP1 event issued when the status of the monitoring node changes to Emergency has a monitoring node status (E.MON_NODE_STATUS) of 800.

#2: You cannot check this information from JP1/IM - View. Every item of information is stored as an attribute name combined with the attribute value. Therefore, when JP1 event 00003FB0 exceeds the maximum length of a JP1 event (10,000 bytes), only the portion within that limit is stored as information about the JP1 event that triggered the status change. Similarly, when the number of extended attributes exceeds 100, only the JP1 event information up to the 100th attribute is stored. Attributes are stored only if the attribute name is within 26 characters; if the attribute name exceeds 26 characters, the attribute is not saved.

Setting an automated action for a monitoring node

To execute an automated action when the status of a monitoring node changes:

In the Event-Issue Conditions page of the Properties dialog box for the selected monitoring node, select the node status that triggers the JP1 event.
Add an automated action condition for JP1 event 00003FB0 to the automated action definitions.

Information about the JP1 event resulting in a node status change is included in JP1 event 00003FB0, as shown in Information about the JP1 event that triggered the status change in the above table. For example, the original event message (B.MESSAGE) can be used as the attribute name E.JCS_B_MESSAGE with the automated action.

To Page Top