8.4.2 Managing JP1 events using JP1/Base

JP1 events are controlled by the JP1 event service and recorded in an event database unique to JP1/Base.

Figure 8‒8: Overview of JP1 event management

The information recorded in a JP1 event is categorized by attribute as follows:

Basic attributes (held by all JP1 events)
Extended attributes (optionally set by the program that issued the JP1 event, and consisting of common information and program-specific information)
- Common information (information in a format shared by all JP1 programs)
- Program-specific information (other information in a format specific to the program issuing the event)

To distinguish between attribute types, basic attribute names begin with B. (for example, B.ID), and extended attribute names begin with E. (for example, E.SEVERITY).

Information is recorded for each attribute type as follows:

Example: JP1 event generated when execution of an automated action is requested (partial only)

Basic attributes

Event ID (B.ID): 000020E0

Message (B.MESSAGE):

KAVB4430-I Execution of the action for an event was requested.

:

Extended attributes - Common information

Event ID (E.SEVERITY): Information
Product name (E.PRODUCT_NAME): /HITACHI/JP1/IM/JCAMAIN

:

Extended attributes - Program-specific information

Executing host (E.EXECHOST): jp1-manager

:

In this manner, events generated in the system are recorded as JP1 events.

For details about JP1 events, see Chapter 3. JP1 Events in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference. See also the description of JP1 events in the JP1/Base User's Guide.

Organization of this subsection

(1) Centrally managing events using JP1 events
(2) Using JP1 event forwarding to centralize event management
(3) Using JP1 events as historical and statistical information by CSV file output

(1) Centrally managing events using JP1 events

JP1/Base manages events occurring in the system as JP1 events.

Events being managed outside JP1, such as by log files and SNMP traps, can be converted into JP1 events and handled in JP1/Base.

By using JP1 events in this manner, events handled by a wide variety of products can be managed by JP1/Base in the same way as events issued by products in the JP1 series.

Events issued as JP1 events

JP1 events (issued by JP1 products)

The products in the JP1 series enable system operation management from a variety of angles. By managing the JP1 events that each product issues, you can comprehensively manage the events occurring in the system.

For details about the JP1 events issued by individual products in the JP1 series, see the relevant manual.
JP1 events (issued by commands)

JP1/Base provides commands for issuing JP1 events (jevsend and jevsendd). By placing these commands in a shell script or similar, users can use the issued JP1 events to monitor system operation. Since JP1/IM only monitors JP1 events that have an event level, specify the event level in the command arguments (for example -e SEVERITY=Error).

For details, see the chapter about commands in the JP1/Base User's Guide.
Events in JP1/SES format

JP1/Base can manage events in JP1/SES format (events that can be acquired by the programs JP1/SES and JP1/AJS provided in version 5 and earlier of the JP1 series.)

In its default state, JP1/IM cannot monitor events in the JP1/SES format. This is because JP1/IM uses the event level, an extended attribute, in monitoring events; events in the JP1/SES format have basic attributes only.

To allow JP1/IM to monitor events in the JP1/SES format, either set up an event acquisition filter to acquire JP1/SES format events, or use the extended functions provided by JP1/Base to enable extended attributes for JP1/SES-format events.

See 4.2 Filtering of JP1 events.

See the description of JP1/SES event conversion in the manual JP1/Base Function Reference.

JP1/SES-format events do not include any character code set. Therefore, to monitor JP1/SES-format events, the character code for JP1/SES-format events must be defined as a unified character code in the language environment of the whole system.
JP1 events (using the event issuing function)

JP1/Base provides functions that allow user application programs to issue JP1 events directly.

See the description of user-defined events in the manual JP1/Base Function Reference.

Events converted to JP1 events by the event converters

Log file information

The JP1/Base log file trapping function converts the information that application programs output to log files into JP1 events for management by JP1/Base.
Windows event log information

The JP1/Base event log trapping function converts the information output to the Windows event log into JP1 events for management by JP1/Base.
SNMP traps

The JP1/Base SNMP trap converter converts SNMP traps managed by HP NNM version 7.5 or earlier into JP1 events for management by JP1/Base.

See the chapter on setting the event converters in the JP1/Base User's Guide.

Note

For details about NNMi incident conversion in HP NNMi, see the manual Job Management Partner 1/Integrated Management - Event Gateway for Network Node Manager i Description, User's Guide and Reference.

To Page Top

(2) Using JP1 event forwarding to centralize event management

JP1/IM monitors the system by acquiring from JP1/Base the JP1 events recorded in the event databases on the managers.

Of the JP1 events generated at each host in the system, important events that need to be addresses can be forwarded to the JP1/IM manager by the event forwarding function of JP1/Base. In this manner, JP1/IM can centrally manage the events occurring in the system (important events needing management follow-up).

(a) Forwarding JP1 events

The JP1/Base event forwarding function forwards JP1 events from one host to another. By using this function, JP1/IM can forward JP1 events to a manager where they can be centrally managed.

To define which JP1 events to forward, use the forwarding settings file (forward) of the JP1/Base event service. This file is called a forwarding filter in JP1/IM.

Only important JP1 events needing management follow-up should be forwarded to a manager. Do not set up event forwarding to send all JP1 events that occur in the system. Under the default settings, JP1 events whose event level is Emergency, Alert, Critical, Error, or Warning are forwarded to higher-level managers according to the hierarchy defined in the configuration definition.

The following figure shows an example of how JP1 events are forwarded to higher-level managers.

Figure 8‒9: JP1 event forwarding

You can change the forwarding settings by editing the forwarding settings file directly on each host. Alternatively, by using the JP1/Base functionality for collecting and distributing definitions, you can distribute the new settings from a higher-level host in a batch operation.

(b) Retry setting for JP1 event forwarding

The JP1/Base event service can automatically retry forwarding a JP1 event if transmission fails because of a network error or because the destination event server has stopped. Enter this setting in the JP1/Base event server settings file (conf).

See the chapter on setting the event service environment in the JP1/Base User's Guide.

(c) Event forwarding according to configuration management

When you define the hierarchy of managers and agents using the JP1/Base configuration management functions, each host is automatically set up to forward JP1 events to the higher-level manager according to the resulting configuration definition. When you change a definition in the configuration definition file, the JP1 event forwarding settings are updated automatically on each host.

See 8.4.3 Managing the system hierarchy.

(d) Using the definition collection and distribution function

By using the definition collection and distribution function, you can distribute JP1 event forwarding settings from a higher-level host defined in the system hierarchy to lower-level hosts (for an overview of configuring a system hierarchy, see 8.4.3 Managing the system hierarchy). You can use this function to halt event forwarding from another host when you need to temporarily stop a host for maintenance, for example, or you do not want a flood of events sent from a host on which numerous errors have occurred. By distributing the settings from the manager using a JP1/Base command, you can update the forwarding settings file (forward) at all the lower-level hosts. The forwarding settings are reloaded at each host when distribution is successful, and events are forwarded thereafter based on the updated information.

See 8.4.5 Collecting and distributing definition information.

To Page Top

(3) Using JP1 events as historical and statistical information by CSV file output

You can check the JP1 events stored in an event database by outputting the database contents to a CSV file using the JP1/Base jevexport command.

JP1/IM manages the system operation by collecting important JP1 events that require urgent attention on a manager where they can be monitored from JP1/IM - View. Non-urgent JP1 events, on the other hand, are recorded in the event databases of their respective hosts, but are not forwarded to a manager or displayed in JP1/IM - View.

However, information about non-urgent JP1 events (indicating that a job has ended normally, for example) might occasionally be required in order to compile statistical information or an operating history. In this case, use the JP1/Base command jevexport to output the database contents to a CSV file.

For details about the jevexport command, see the chapter on commands in the JP1/Base User's Guide.

When you use the integrated monitoring database, you can output the JP1 events stored in the integrated monitoring database by using the JP1/IM jcoevtreport command.

For details about the jcoevtreport command, see jcoevtreport in Chapter 1. Commands in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

To Page Top