HP B6191-90029 manual Sample Client Configuration File

Hardware Monitor Configuration Files

Client Configuration File

OR

/etc/opt/resmon/lbin/send_test_event

The program was created for HP Support Applications to ensure that the communication mechanism from the monitor to HP Support 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 (email, 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.)

The test event is #103 with a default severity of "INFORMATION". To test delivery to notification targets that by default only receive higher severity events (e.g. syslog or email to root, which receive "MAJOR_WARNING" or higher events only), you must edit the .clcfg file for the monitor to change the severity of event #103.

For more information on the command, see the manpage for send_test_event.

Sample Client Configuration File

The following is a sample of a client configuration (.clcfg) file.

#There are 4 types of entries in this file. HOST_ID, DEV_ID, EQ,

#CLCFG_VERSION. Each entry starts with the appropriate tag,

#followed by one or more colon separated fields. The number of fields and

#valid values for each field depends

#on the tag.

#

#Each entry in this file must be one line. Meaning, no returns can be

#put in the middle of a line. This may mean that the EQ entries will wrap.

#Text fields in the entries are case sensitive.

#

#Host ids that should be added to the event. This information will

#be added in the order the tags are listed

#Possible host ids are:

#host_model_num

#host_os_version

#host_fw_version

#host_serial_num

#host_sw_id

#host_ems_version

#host_stm_version

#Example:

#HOST_ID: host_ems_version : host_stm_version

HOST_ID:host_model_num:host_ems_version:host_stm_version

#Device ids that should be added to the event. This information will be

#added in the order the tags are listed

#NOTE: these are specific to this monitor

#Example:

#DEV_ID: dev_product : dev_qualifier

DEV_ID:dev_pdev:dev_inq_vendor:dev_inq_prod:dev_fw_version:dev_serial_num #DEV_ID:dev_pdev:dev_comp_tag2

#Event qualification entries for events generated by this monitor.

#NOTE: the event numbers are specific to this monitor.

#Example:

96 Chapter 5