Hitachi

JP1 Version 12 JP1/Integrated Management 2 - Manager Overview and System Design Guide


8.4.8 JP1/Base health check function

The JP1/Base health check function monitors JP1/Base processes for hangups#, abnormal termination, and other problems, and issues a message or JP1 event to report the error and prompt the operator to take recovery action. By using this function, JP1/IM can check whether the instances of JP1/Base in the JP1/IM system are operating normally. The health check function is disabled by default. Enable the function by changing the setting in the common definition information.

#: Hangups are caused by a deadlock or infinite loop, and mean that the process can no longer accept processing requests.

This subsection gives an overview of the JP1/Base health check function. For details about how the function works and how to set it up, see the chapter on setting the health check function in the JP1/Base User's Guide.

Broadly classified, the JP1/Base health check function has two roles:

Depending on the JP1/Base version, this functionality might not be supported. For details, see the JP1/Base User's Guide.

Organization of this subsection

(1) Monitoring the status of JP1/Base processes on the local host

By enabling the health check function, you can detect hangups and abnormal terminations in JP1/Base processes on the local host. This information is registered in the operating system's log (the Windows event log or UNIX syslog) as message information, or in the event database as JP1 events, depending on how JP1/Base is set up.

The figure below shows how JP1/Base processes are monitored on the local host.

Figure 8‒20: Monitoring the status of JP1/Base processes on the local host

[Figure]

By recording errors that affect JP1/Base as JP1 events in the event database, you can use JP1/IM to monitor JP1/Base for errors.

The health check function is unable to monitor the status of other processes if the function itself hangs or terminates abnormally. Also, JP1 events cannot be registered if an error occurs in the event service.

To avoid this type of situation, the health check function and the event service must be monitored by the health check function of JP1/Base on a remote host.

(2) Monitoring the status of JP1/Base processes on remote hosts

The JP1/Base health check function can monitor the status of the JP1/Base health check function and the event service on remote hosts, as well as the JP1/Base processes on the local host. Thus, you can prevent situations in which errors in JP1/Base processes are overlooked because of an error in the health check function, or JP1 events are not registered because of an error in the event service.

If you are using JP1/Base version 09-00 or later, you can suppress monitoring when the monitoring target stops normally. For details, see the JP1/Base User's Guide.

The figure below shows how JP1/Base processes are monitored on remote hosts.

Figure 8‒21: Monitoring the status of JP1/Base processes on remote hosts

[Figure]

The above figure shows a configuration in which the health check functions and event services of HostB and HostC are monitored from HostA. When an error occurs in the health check function on HostB, HostA detects the error and records the particulars in its own OS log or event database. When an error occurs in the event service on HostC, HostA detects the error and records the particulars in its own OS log or event database#.

#: In this situation, JP1 events cannot be registered in the event database on HostC. However, log information can still be registered in the OS log provided that the health check function is working normally.

In this manner, JP1/Base detects errors in JP1/Base processes.