Generic Monitor (default settings for all monitors)

Monitor Description | Configuration Files

Monitor Description
This page lists the default settings common to all EMS Hardware Monitors.
Note that some configuration settings are handled differently by the multiple-view (Predictive-enabled) hardware monitors, first introduced in the June 2000 release (IPR0006).

Release History

June 2000 Release: Multiple-view (Predictive-enabled) monitors first supported
February 1999 Release: Initial release for the first set of monitors

Supported Products

-

Special Requirements

-

Resource Path

Event monitoring: /___/events/___/___
Status monitoring: /___/status/___/___

Monitor Name

/usr/sbin/stm/uut/bin/tools/monitor/MONITOR_NAME

PSM State Control

For most monitors, the set_fixed utility must be used to return a hardware resource to the UP state following a failure. Most monitors do not support automatic state control.

You can tell whether a monitor requires the use of the set_fixed utility by looking in the .psmcfg file for the monitor. If either of the following lines occurs in the file, then the monitor does its own state handling and does not require the use of set_fixed:
MONITOR_STATE_HANDLING  UP_STATE_CONTROL
MONITOR_STATE_HANDLING  ALL_STATE_CONTROL
Event History File
By default, monitors keep event history in memory; they do not keep an event history file. Therefore, if the monitor is disabled or rebooted, event history is not saved.
Configuration Files

Startup Configuration File (.sapcfg)

File name: /var/stm/config/tools/monitor/MONITOR_NAME.sapcfg

By default, messages regarding Major Warning, Serious and Critical events are:

Written to /var/adm/syslog/syslog.log (SYSLOG)

Sent to EMAIL address root

(On releases prior to June 1999, messages were also sent to the console by default.)

All events are also stored in /var/opt/resmon/log/event.log (TEXTLOG).
Monitor Configuration File (.cfg)

File name: /var/stm/config/tools/monitor/MONITOR_NAME.cfg

The defaults shown below are for all monitors and are set in the file /var/stm/config/tools/monitor/Global.cfg. If a different default is used by a monitor, it is set in the monitor's own .cfg file.

Default settings:

Setting Name Before Multiple-view Release After Multiple-view Release

POLLING_INTERVAL 60 minutes 60 minutes

REPEAT_FREQUENCY 1440 minutes (1 day) Replaced by "Suppression Time" in the .clcfg file.

SEVERITY_ACTION Notify for all levels See the .clcfg file for specific event info.

The min. polling interval is 1 minute with a max. of 1440 minutes. If the user tries to set a value outside these, they will get the default value of 60.

Do Not set the value at zero(0).

Note: Multiple-view (Predictive-enabled) hardware monitors no longer use the the Monitor Configuration file (.cfg) to set the Repeat Frequency and Severity Action. These settings are made instead in the the Default Client Configuration files (.clcfg) described below.

Default Client Configuration File (.clcfg)

File name: /var/stm/config/tools/monitor/default_MONITOR_NAME.clcfg

If a monitor is Multiple-view (Predictive-enabled), it uses a client-configuration file (*.clcfg) to control the text sent in text messages to specific targets (for example, to Predictive Support). Client-configuration files can be used to control the text sent in text messages to specific targets (for example, to Predictive Support). The default_MONITOR_NAME.clcfg applies to messages sent to all targets. Specific .clcfg files (for example, predictive_disk_em.clcfg) are used to control the text sent to specific targets (in this example, to Predictive Support).

HOST_ID tags in the .clcfg files control the System Information, which is reported under the "Additional System Data" label in the event messages.

If a HOST_ID tag is enabled in the *.clcfg file, then the corresponding information will appear in the event message.

HOST_ID tag Default Description Text label

host_sw_id Off System software ID System Software ID:

host_serial_num Off System Serial number System Serial Number:

host_model_num On System model string System Model Number:

host_os_version On System OS version OS Version:

host_fw_version Off PDC FW revision System FW Version:

host_stm_version On Version of Support Tools Manager STM Version:

host_ems_version On Version of Event Monitoring Service EMS Version:

host_orig_
product_num Off Original system product number System Original Product Number:

host_curr_
product_num Off Current system product number System Current Product Number:

DEV_ID tags in the .clcfg files control the Monitor-specific information, which is reported under the "Component Data" label in the event messages.

If a DEV_ID tag is enabled in the *.clcfg file, then the corresponding information will appear in the event message.

For the list of monitor-specific fields, see the data sheet for the individual monitor.

EQ tags are Event Qualification entries for events generated a particular monitor. Examples of common entries for all monitors with .clcfg files are as follows:

EQ : event_number : severity : enable flag : Suppression Time : time window : threshold : value threshold 1 : operator 1 : operator 2 : value threshold 2

Text Label Descriptions and Available Values

event_number : A unique number given to each event for an individual monitor.

severity : The severity of the event. Valid values are:

CRITICAL

SERIOUS

MAJOR_WARNING

MINOR_WARNING

INFORMATION

enable flag :
Whether the event is enabled. Valid values are:

TRUE - event is enabled

FALSE - event is not enabled

Suppression Time : Time, in minutes, to suppress generation and trending for this event after generating the event. Valid values are:

NOT_USED - Never suppress the event

1 - maxint - number of minutes to suppress

NOTE: Suppression Time in the .clcfg file replaced the Repeat Frequency from the .cfg file in some monitors.

time window:
Amount of time, in minutes, event must be seen to qualify event. Valid values are:

NOT_USED - time window thresholding not used

ANY - time window thresholding used but no time window specified

1-maxint - time need to see threshold events to qualify

threshold :
Number of times in time window event must be seen to qualify event. Valid values are:

1-maxint

NOTE: To configure an event to always be generated every time an event is seen, the threshold should be set to 1 and the time window should be set to "ANY".

value threshold X, operator X : Value thresholds to qualify event. Valid values for value threshold depend on the type of value associated with the event. However, predefined value of "NONE" means this value threshold is not used.
Valid values for operator X are:

NO_OP - this operator not used

>, < , >=, <=,==, !=.

These values are used to qualify the event using the following logic: value threshold 1 operator 1 value operator 2 value threshold 2.

For example, if the value is an integer and want to qualify event "if value is between 60 and 70," inclusive, the entry would be:

60 : <= : <= 70.

If the value is an integer and want to qualify event "if value is > 70," the entry would be :

NONE : NO_OP : > : 70.

PSM Configuration File (.psmcfg)

File name: /var/stm/config/tools/monitor/MONITOR_NAME.psmcfg

Default settings:

MONITOR_RESOURCE_NAME /___/___/___/___

PSM_RESOURCE_NAME /___/___/___/___

MONITOR_STATE_HANDLING NO_UP_CONTROL. Requires the use of set_fixed to set UP state.

DOWN_SEVERITY_THRESHOLD Serious and Critical map to DOWN

Top of Page

/ Diagnostics HOME

URL: http://docs.hp.com/hpux/onlinedocs/diag/ems/emd_generic.htm
Last updated: Fri May 11 11:24:15 PDT 2001

Setting Name	Before Multiple-view Release	After Multiple-view Release
POLLING_INTERVAL	60 minutes	60 minutes
REPEAT_FREQUENCY	1440 minutes (1 day)	Replaced by "Suppression Time" in the .clcfg file.
SEVERITY_ACTION	Notify for all levels	See the .clcfg file for specific event info.

HOST_ID tag	Default	Description	Text label
host_sw_id	Off	System software ID	System Software ID:
host_serial_num	Off	System Serial number	System Serial Number:
host_model_num	On	System model string	System Model Number:
host_os_version	On	System OS version	OS Version:
host_fw_version	Off	PDC FW revision	System FW Version:
host_stm_version	On	Version of Support Tools Manager	STM Version:
host_ems_version	On	Version of Event Monitoring Service	EMS Version:
host_orig_ product_num	Off	Original system product number	System Original Product Number:
host_curr_ product_num	Off	Current system product number	System Current Product Number:

Text Label	Descriptions and Available Values
event_number :	A unique number given to each event for an individual monitor.
severity :	The severity of the event. Valid values are: CRITICAL SERIOUS MAJOR_WARNING MINOR_WARNING INFORMATION
enable flag :	Whether the event is enabled. Valid values are: TRUE - event is enabled FALSE - event is not enabled
Suppression Time :	Time, in minutes, to suppress generation and trending for this event after generating the event. Valid values are: NOT_USED - Never suppress the event 1 - maxint - number of minutes to suppress NOTE: Suppression Time in the .clcfg file replaced the Repeat Frequency from the .cfg file in some monitors.
time window:	Amount of time, in minutes, event must be seen to qualify event. Valid values are: NOT_USED - time window thresholding not used ANY - time window thresholding used but no time window specified 1-maxint - time need to see threshold events to qualify
threshold :	Number of times in time window event must be seen to qualify event. Valid values are: 1-maxint NOTE: To configure an event to always be generated every time an event is seen, the threshold should be set to 1 and the time window should be set to "ANY".
value threshold X, operator X :	Value thresholds to qualify event. Valid values for value threshold depend on the type of value associated with the event. However, predefined value of "NONE" means this value threshold is not used. Valid values for operator X are: NO_OP - this operator not used >, < , >=, <=,==, !=. These values are used to qualify the event using the following logic: value threshold 1 operator 1 value operator 2 value threshold 2. For example, if the value is an integer and want to qualify event "if value is between 60 and 70," inclusive, the entry would be: 60 : <= : <= 70. If the value is an integer and want to qualify event "if value is > 70," the entry would be : NONE : NO_OP : > : 70.

MONITOR_RESOURCE_NAME	/___/___/___/___
PSM_RESOURCE_NAME	/___/___/___/___
MONITOR_STATE_HANDLING	NO_UP_CONTROL. Requires the use of set_fixed to set UP state.
DOWN_SEVERITY_THRESHOLD	Serious and Critical map to DOWN