EMS Disk_em Errors

[Paul Stuhley]

Dose anyone know where to change the config
file for disk_em to bypass a device. I lost my notes.
paul s.
pstuhley@seeksystems.com

[Sandip Ghosh]

You can go to /etc/opt/resmon/lbin and try to change it over there.

Sandip

[Holger Knoppik]

Hi Paul, I think Sandip means the monconfig program, or check out the disk_em conf files at /var/stm/config/tools/monitor.
HTH,
RGDS, Holger

[Paul Stuhley]

I did find the directory but need to find the right syntax to enter into the config file

paul

[Christopher McCray_1]

Assuming your OS version is 11.00, here are two ways of doing this in a document I wrote up for my group after I had an issue regarding incompatability with EMS and one of my storage arrays. You can turn off the event or the hardware path in question.

I hope this is what you are looking for.

Chris

[Ross Martin]

Paul, I am an HP Response Engineer who works on EMS issues. The ITRC has a document 3100530009 which shows how to disable EMS HW monitors for a single instance and it uses the disk_em as an example.

You need to be on STM/EMS bundle A.26.00 or later to use this method. You can download the latest STM/EMS bundle from software.hp.com -> Networks and System Administration -> Support Tools for HPUX 9000 -> Try for Free

The latest version is A.29.00.

Hope this helps.

[Paul Stuhley]

I did not have a disabled_instances file so I created on, but when I do a check they still show up.
Dose anyone have a example of what the file looks like.

paul s.

[Christopher McCray_1]

Here you go!!

Enjoy and use only for the forces of good

Chris

[Ross Martin]

Don't have a file handy, but maybe the following will help:

In order to use the disabled_instances file, perform the following:

Run /etc/opt/resmon/lbin/moncheck to determine the names of instances you
would like to disable.

Run monconfig K)ill monitoring

With editor of your choice, Add/delete/modify instances
in /var/stm/data/tools/monitor/disabled_instances. You will need to add a line
for each disk or LUN.

Example:
/storage/events/disks/default/8_12.0.0

Run monconfig: Select the "E)nable Monitoring" command

Wait for monitoring to be re-enabled

Do a C)heck monitors
The resource class that you disabled should show up in the list with no
description of what to do with events. (ie. there are no monitoring requests)


=====================
Additional information:

The disabled_instances file is a text file with each fully qualified instance listed, one instance per line. In addition, wildcards can be used in the instance names to specify more than more instance. For example: /storage/events/disks/default/* could be used to specify all the instances associated with the default disk resource names.

For those instances listed in the disabled_instances file, no monitoring requests will show up in the list displayed by the monconfig "C)heck
monitoring" command.

NOTE: This does not mean that the monitor will stop polling the device. It just means that any events will not be forwarded to the log files, based on information in the *.sapcfg files.

In order to use the disabled_instances file, the user must perform the
following:

1. Run monconfig K)ill monitoring.

2. With editor of your choice, Add/delete/modify instances at
/var/stm/data/tools/monitor/disabled_instances.

3. Run monconfig; select the "E)nable Monitoring" command.

4. Wait for monitoring to be re-enabled.

5. Do a C)heck monitors.

The resource class that was disabled should show up in the list with no description of what to do with events. (ie. There are no monitoring requests.)

NOTE: The PSM (Peripheral Status Monitor) associated with the event monitor cannot be disabled via this technique. This ONLY disables the event monitor.

Hope this helps.

Ross