Hitachi

JP1 Version 12 JP1/Performance Management Planning and Configuration Guide


2.4.4 Examining alarm table binding methods

To perform monitoring that uses alarms with Performance Management, you must associate a monitoring agent with an alarm table. An alarm table is a consolidated group of several alarms. This association is known as binding.

The monitoring agent evaluates condition expressions for all alarms included in the bound alarm table and notifies an alarm to PFM - Web Console, according to the specified alarm definition. Normally, alarms are notified when an evaluation determines that a condition has been changed.

If you add a new alarm to an alarm table that is already bound to the monitoring agent, or if you change an existing alarm's definition, the new definition is automatically used to perform evaluations.

Alarm tables are bound as follows:

If you bind multiple alarm tables to a monitoring agent, different alarm conditions can be set for each agent. That is, you can use different combinations of alarm tables for each monitoring agent. For example, you can create a separate alarm table for each type of monitoring, such as database cache monitoring, CPU usage monitoring, or process monitoring. After creating a separate table, you can then bind a monitoring agent with a combination of alarm tables for database cache and process monitoring, or bind another agent with a combination of alarm tables for CPU usage and process monitoring.

If you have multiple monitoring agents, you can bind a common alarm table to all of the monitoring agents, as well as add another alarm table to a specific monitoring agent.

Figure 2‒12: Example of binding multiple alarm tables

[Figure]

You can set the binding method of the alarm table in PFM - Manager. You must be using version 09-00 or later of PFM - Manager and PFM - Web Console to bind multiple alarm tables to one monitoring agent. To bind multiple alarm tables to a monitoring agent, PFM - Agent must be 08-00 or later, and PFM - Base must be 09-00 or later. To bind an alarm table to a monitoring agent for PFM - RM, the Performance Management product must be 09-00 or later. For details about how to configure the binding method of the alarm table, for Windows see 4.4.4 Configuring the functionality for binding multiple alarm tables, and for UNIX see 5.4.4 Configuring the functionality for binding multiple alarm tables.

You can bind an alarm table (or alarm tables) to monitoring agents as follows:

With manual alarm bind, alarm monitoring is initiated when the alarm table is bound to the monitoring agents. Any errors that occur between the start of the monitoring agent service and the binding of the alarm table do not get detected. Furthermore, you need to bind the alarm table to each one of the monitoring agents one by one.

With auto alarm bind, the alarm table is automatically bound to the monitoring agents when the monitoring agent service starts, after which alarm monitoring is initiated. On the other hand, if you include an additional monitoring agent for which auto alarm bind has already been configured, the alarm table is automatically bound to the added monitoring agent at the moment the monitoring agent starts.

Note

To use auto alarm bind, you have to enable the functionality for binding multiple alarm tables in advance.

To use auto alarm bind, both the PFM - Manager version and the PFM - Web Console version must be 11-50 or later. If you want to use auto alarm bind with PFM - Manager 11-50 or later and PFM - Web Console earlier than 11-50, you need to directly edit the configuration file to configure auto alarm bind.

For details about how to configure the auto alarm bind function, see 4.1.4 (11) Configuring the auto alarm bind function for Windows and 5.1.4 (12) Configuring the auto alarm bind function for UNIX. For details about the auto alarm bind function, see the section describing auto alarm bind in the JP1/Performance Management User's Guide.