Hitachi

JP1 Version 12 JP1/Integrated Management 2 - Manager Configuration Guide


6.9.3 Example of creating a general monitoring object (HiRDB monitoring)

This subsection explains how to create and set up a monitoring object for monitoring HiRDB version 6. This example uses the message log events (JP1/SES event: 0x00010C03) that are output by HiRDB as the status change condition for the monitoring object.

Note

HiRDB version 07-02 or later can issue JP1 events, not JP1/SES events (the output settings are required at HiRDB). In this case, use the system-monitoring object provided by Central Scope to create a monitoring object for HiRDB.

Organization of this subsection

(1) Creating a monitoring object (HiRDB monitoring)

To create a monitoring object:

  1. From the Monitoring Tree window, choose Options, and then Edit Tree.

    The Monitoring Tree (Editing) window appears.

  2. From the File menu, choose Open Tree.

    Open the monitoring tree to which the monitoring object for HiRDB is to be added

  3. In the tree area, select the location where the monitoring object for HiRDB is to be added.

  4. From the Edit menu, choose Create New Monitoring Node.

    The Create New Monitoring Node window appears.

    Figure 6‒20: Create New Monitoring Node window

    [Figure]

    The settings in the Create New Monitoring Node window are as follows.

    Table 6‒10: Settings in the Create New Monitoring Node window

    Item

    Setting

    Monitoring node name

    Enter any name.

    We recommend that you assign a name that is easy to manage. This example enters HiRDB Monitoring.

    Monitoring node type

    Select the Monitoring object radio button, and select User Monitoring Object from the list box.

  5. Click the OK button.

    The monitoring object HiRDB Monitoring is added to the monitoring tree.

(2) Setting up the monitoring object (HiRDB monitoring)

(a) Setting the basic information for the monitoring object

To set the basic information for the monitoring object:

  1. Select the newly created monitoring object.

  2. From the Edit menu, choose Properties.

    The Properties window appears.

  3. Choose the Basic Information page.

    Figure 6‒21: Basic Information page

    [Figure]

    The settings on the Basic Information page are as follows.

    Table 6‒11: Settings on the Basic Information page

    Item

    Setting

    Monitoring node attribute name

    Enter any name.

    We recommend that you assign a name that is easy to remember, such as a host name.

    Monitoring node attribute value

    Enter any value. This is the value for the name entered in Monitoring node attribute name.

    If you entered a host name in Monitoring node attribute name, enter a value such as the host name displayed by the hostname command, or a value that is easily associated with the product. This example enters dbserver as a value that is easily associated with HiRDB.

    Note: You can specify the monitoring node basic information specified here as the search condition when you search for a monitoring node. The basic information has no effect on monitoring object status change.

  4. Click the Add button.

    The basic information is set for the monitoring object.

(b) Setting the status change condition for the monitoring object

To set the status change condition for the monitoring object:

  1. Select the newly created monitoring object.

  2. From the Edit menu, choose Properties.

    The Properties window appears.

  3. Choose the Status-Change Condition page.

    Figure 6‒22: Status-Change Condition page

    [Figure]

  4. Click the Add button.

    The Status-Change Condition Settings window appears.

    Figure 6‒23: Status-Change Condition Settings window

    [Figure]

    The settings in the Status-Change Condition Settings window are as follows.

    Table 6‒12: Settings in the Status-Change Condition Settings window

    Item

    Setting

    Condition name

    Specify a name for the condition.

    Status

    From the list box, select the status to which the monitoring object is to change when an event is received.

    Common condition

    Specify information needed to identify the event or the product that caused the event.

    The details are provided below.

    Individual conditions

    Specify information needed to identify the location where the event occurred.

    The details are provided below.

  5. After you have entered a condition name, status, common condition, and individual condition, click the OK button.

Specifying the common condition:

For the common condition, specify the information needed to identify the event or the product that caused the event.

To specify the common condition:

  1. Click the Set Common Condition button.

    The Common Condition Settings window appears.

  2. Click the Add button.

    The Common Condition Detailed Settings window appears.

    Figure 6‒24: Common Condition Detailed Settings window

    [Figure]

    The settings in the Common Condition Detailed Settings window are as follows.

    Table 6‒13: Settings in the Common Condition Detailed Settings window

    Item

    Setting

    Common condition name

    Specify a name for the common condition.

    Message

    Specify the message for the JP1 event (in this example, a JP1/SES event).

    Specify this information if you want to monitor only a specific message. In the case of HiRDB, specify a JP1/SES event message that is issued by HiRDB.

    For example, if you enter KFPS01222-I and select Match prefix, you can monitor only the HiRDB log swap messages.

    Event ID

    Specify the event ID of the JP1 event (in this example a JP1/SES event) to be monitored.

    For a product that issues JP1/SES events such as HiRDB, specify the basic code of JP1/SES events (00010C03).

  3. Click the OK button.

    The Common Condition Settings window is displayed again.

  4. Click the Close button.

    The Status-Change Condition Settings window is displayed again.

  5. Select the created common condition.

    The created common condition is added to the list box. Select the created common condition.

Specifying the individual conditions:

In individual conditions, specify conditions needed to identify the location where the event occurred, such as the name of the host resulting in a failure.

To specify the individual conditions:

  1. Enter the name and value of an attribute and then click the Add button.

    The individual condition is added. Repeat this step as many times as there are individual conditions to be added.

    The settings for individual conditions are as follows.

    Table 6‒14: Settings for individual conditions

    Attribute name

    Attribute value

    Description

    B.SOURCESERVER

    dbserver

    For the attribute name, enter B.SOURCESERVER to narrow down the source of the event (host) that is to be reported.

    For the attribute value, enter the name of the host where the HiRDB system manager is running.

    B.MESSAGE

    HiRDB-server-name

    If product-specific message information is output as event information, use that message information for narrowing.

    This is because the message might contain information that identifies the location where the event occurred (such as a message log event issued by HiRDB).

    If you want to identify the location of the event on the basis of information in the message, enter B.MESSAGE as the attribute name and a keyword that can be narrowed down as the attribute value.

    For example, log swap messages of HiRDB contain a HiRDB server name. If you specify B.MESSAGE as the attribute name and HiRDB-server-name as the attribute value, and select Regular expression from the list box, you can monitor only those log swaps that occur at a specific HiRDB server.

    If you specify B.MESSAGE, make sure that no message that is not monitored satisfies the conditions.

    Note that detailed information for JP1/SES events cannot be specified in the status change conditions.

(c) Updating the edited monitoring tree

To update the edited monitoring tree in order to use it:

  1. In the Monitoring Tree (Editing) window, from the File menu, choose Update Server Tree.

    The HiRDB monitoring node is added to the monitoring object database of Central Scope.