Hitachi

JP1 Version 12 JP1/Performance Management User's Guide


6.6.5 Checking alarm application status

In the message area of the Agents tree and in the Alarm Application Status window, you can determine if alarm information has been applied to monitoring agents. If no alarm information has been applied, it is possible that the targets are not being monitored correctly. In such a case, re-apply the alarm information from the Alarm Application Status window.

The alarm information discussed here includes the results of alarm-related operations, such as binding and unbinding monitoring agents, updating bound alarm definitions, and updating action definitions. If you have performed these operations, we recommend that you check the alarm application status. For details, see 6.6.5(1) Timing of checking alarm application status.

You can also use the following commands to check alarm application status and apply alarm information:

  1. Log on to PFM - Web Console from the monitoring console web browser.

    You must log on as a user with administrator user permissions.

    In a multiple-monitoring configuration, log on to the primary system.

  2. In the navigation frame of the main window, select the Agents tab.

  3. Check if the message Application of alarm information is not complete is displayed in the navigation frame of the Agents window.

    • If this message is not displayed

      Alarm information has been applied. There is no need to proceed to the steps described below.

    • If this message is displayed

      Wait a while, and then click Refresh. If the message is still displayed, perform the steps below.

  4. Click the message to display the Alarm Application Status window.

    You can also display this window by clicking Alarm Application Status in the method frame.

  5. If there are services awaiting application of alarm information, wait about five minutes, and then click Refresh to see if the message Services waiting for application do not exist is displayed.

  6. Check the Application status, Incompatible, and Inactive tabs.

    The monitoring agent's services to which the results of alarm-related operations have not been applied are displayed. Take the corrective action according to the status of the service as described in the following table.

    Table 6‒11: Corrective action according to alarm application status (web browser)

    Tab

    Application status

    Description

    Corrective action

    Application status

    Failed

    Application of alarm information has failed or the application processing timed out.

    Click the Apply to All or Apply button to re-apply alarm information.#

    Uncertain

    Alarm information application status is unknown.

    Take the appropriate corrective action according to the cause of the error. For details, see 6.9.4(4) Scenarios where application status becomes Uncertain.

    Incompatible

    Incompatible

    Application of alarm information has failed or the application processing timed out. In addition, the version of the service does not support the application processing on the Application status tab.

    Restart the displayed Action Handler service.

    Inactive

    Inactive

    Alarm information cannot be applied because the service is stopped.

    Take the corrective action according to the displayed message. If the service's inactivity is not a problem, no action is needed.

    #

    If alarm information is being applied to many services at the same time, the monitoring manager's processing speed might become slow.

    Note that alarm information cannot be applied while the jpctool config sync or jpctool config alarmsync command is running.

    If alarm information is still not being applied after taking these corrective actions, check the following:

    • A target service is not running in standalone mode.

    • A target service is busy.

    • A connection-target PFM - Manager's host name is invalid.

    • In a multiple-monitoring environment, the primary and secondary systems are reversed.

  7. Re-display the Alarm Application Status window or click Refresh to display the most recent alarm application status and verify that no more services are displayed in the window.

Organization of this subsection

(1) Timing of checking alarm application status

When an alarm-related operation is performed, its results (alarm information) are applied to monitoring agents. If application of alarm information has not been completed, the target might not be being monitored correctly. Therefore, we recommend that you check the alarm application status after you have performed operations.

The following table describes the operations that should trigger checking of alarm application status.

Table 6‒12: Timing of checking alarm application status

No.

Classification

Operation

1

Updating binding information

The following operations are performed on monitoring agents:

  • Binding

  • Unbinding

2

Updating alarm definitions

The following operations are performed on the alarms contained in bound alarm tables:

  • Addition

  • Editing

  • Deletion

  • Changing active settings

3

Updating action definitions

LOCAL is specified for the action handler and the following operations are performed:

  • Binding to monitoring agents

  • Unbinding from monitoring agents

  • Changing action definitions for the alarms that are contained in bound alarm tables

A remote action is set for the action handler and the following operation is performed:

  • Updating of action definitions (including when alarms are not bound to monitoring agents)

4

Manually applying alarm information

The following operations are performed on a monitoring agent or handler subject to operations described in 1 to 3:

  • Executing the jpctool config sync command

  • Executing the jpctool config alarmsync command

  • Applying alarm information in the Alarm Application Status window

5

Starting a monitoring agent or action handler to which alarms are to be applied

The following operations are performed on a monitoring agent or handler subject to operations described in 1 to 4:

  • Starting services

  • Restoring from standalone mode to normal mode