Mulitiple-View (Predictive-Enabled) Monitors

In June 2000, the platform for EMS Hardware Monitor platform was enhanced to support the Multiple-View (Predictive-enabled) feature. In each diagnostic release, individual monitors have been enhanced to support this feature.

• June 2001 Release
• March 2001 Release
• December 2000 Release
• September 2000 Release
• June 2000 Release

Other monitors are planned to become Multiple-View Enabled in future releases.

For more information, see the sections below:

• What Are Multiple-View (Predictive-Enabled) Monitors?.
• Clients: Targets for Events
• Client Configuration File (*.clcfg)
• Verifying Monitors with a Test Event

June 2001 Release

Release March 2001

Release December 2000

Release September 2000

Release June 2000

Note 1: This monitor is not supported on HP-UX 10.20.

What Are Multiple-View (Predictive-Enabled) Monitors?

In June 2000 and later releases of the diagnostics, the EMS Hardware Monitors were enhanced to support Multiple-View (Predictive-enabled) EMS hardware monitors. The change is transparent to most customers.

The immediate purpose of this change is to enable Predictive Support to work with hardware monitors. There will also be long-term benefits to all customers, as well.

Following is a brief explanation. For more details, refer to the "EMS Hardware Monitors User's Guide", available at Diagnostics HOME

Clients: Targets for Events

When a hardware monitor detects an event, it can send an event message to one or more targets ("clients").

                                        target 1
                                       /
                                      /
event ---> monitor ---> event message -----> target 2
                                      \
                                       \
                                       target 3

Previously, EMS hardware monitors generated events in the same way for all targets. The problem is that different targets, such as Predictive Support, may have different requirements for events.

As of the June 2000 release (IPR 0006), certain monitors allow event reporting to be tailored for different targets. This "Multiple-View" ("Predictive-enabled") feature will be added to most hardware monitors in future releases.

Client Configuration File (*.clcfg)

With Multiple-View hardware monitors, you can create a different Client Configuration File (*.clcfg) for each target. In this file, you can specify:

• The text to be included in event messages.
• "Qualification requirements": the time or value thresholds a problem must meet in order to generate an event. For example, the default time threshold might be to send an event if the problem is seen 6 times in 24 hours. However, Predictive may want to see the event 3 times in 24 hours. Another example: the default value threshold might be to send the event when the value associated with the problem is >= 80, but Predictive may want to see the event when the value is >= 70.
• Events to be enabled/disabled for a given target. For example event 1 may be enabled for target #1, but disabled for target #2.
• Severity level for an event sent to a given target. For example, event 3 may have a severity level of CRITICAL for target #1, but a severity level of MAJOR_WARNING for target #2.

The default Client Configuration File (*.clcfg) is:

/var/stm/config/tools/monitor/default_MONITOR_NAME.clcfg

For example:

/var/stm/config/tools/monitor/default_disk_em.clcfg

The Client Configuration File for Predictive Support client would be :

/var/stm/config/tools/monitor/predictive_MONITOR_NAME.clcfg

For example,

/var/stm/config/tools/monitor/predictive_disk_em.clcfg

Verifying Monitors with a Test Event

As of the June 2000 release of the diagnostics, a standalone program is available to cause multiple-view (Predictive-enabled) EMS hardware monitors to generate a test event:

/opt/resmon/bin/send_test_event
       OR
/etc/opt/resmon/lbin/send_test_event

The program was created for Predictive Support to ensure that the communication mechanism from the monitor to Predictive is working. However, it can be used by customers to ensure the same thing: that the communication mechanisms from the monitor to their notification method (e-mail, event log, SNMP trap, etc) are working.

The program will not work with monitors that have not been updated to be multiple-view. In the long term, all monitors are planned to be updated to be multiple-view.

Before the send_test_event program can be run, the monitors must be enabled and configured. (That is, when you run monconfig, it should say that monitoring is enabled and when you do a "Check", the requests show up.)

For more information on the command, see Verifying EMS Hardware Monitors. Also see the man page for send_test_events.

Top of Page / Diagnostics HOME