Disabling EMS alarms for HITACHI pseudo devices

[Ralph Grothe]

Hi,

the EMS generated email notification, which in general is very appreciated, is pestering with daily alerts for the bogus pseudo disk our Hitachi disk subsystem obviously uses for internal meta data.
Btw, I'm not administering our disk subsystems, and don't know much about them.

Attached you may find the current resmon configuration of the server that emits the alarms (with notification mail address substituted by bogus address to guard against spam flood).

Also included is one such EMS notification for one of 16 pseudo disks.

Then the last output is an ioscan over the HW path where the pseudo disks are attached to, as well as a loop of diskinfos over the disks in order to show that they got no valid size nor ID.

I would be grateful to find someone who could tell how to just disable alerts for these disks without disabling disk monitoring altogether.

Rgds.
Ralph

P.S. Please excuse the \n\r line endings, but ITRC had forced me to move from Mozilla to IE and thus I have to copy attachments from Unix to Windoze

[T G Manikandan]

Run etc/opt/resmon/lbin/monconfig

and stop the ipfcorehw_hitachi

[Ralph Grothe]

T.G.,

would this inadvertently also disable monitoring or alarm generation of all the real, and being used, disks from the Hitachi subsystem?
That was what I clearly would like to avoid.

[Stefan Farrelly]

Hi Ralph,

Im not sure you can disable events for just one path/device, but you can possibly turn of the event being logged for that device. Check out; /var/stm/config/tools/monitor

for example, in this dir in the file default_dm_stape.clcfg you can see all the different event numbers listed to scsi tapes, if you are receiving only 1 unique event number for your troublesome device you can simply edit this file and turn it off - then restart the diags. Im trying to recall where you can stop monitoring for one device/path, I think ive done it once before, I will keep trying to recall.

I also remember problems like this with HDS devices. We had to uprade to the latest diags first - didnt help, then I think HDS found a firmware issue with their drives and updated them, and this stopped the diag messages. Get onto HDS about it - it shouldnt be happening.

Cheers,

Stefan

[V.Tamilvanan · Accepted solution]

Hi,

How can I disable a EMS HW monitor for a single instance?
A user asks: "I have a disk that is reporting an error. It will be several days until we can replace this disk. I would like to stop the reporting of the error message to the logs until we get the disk replaced. Is this possible?"

The startmon_client program now reads the file /var/stm/data/tools/monitor/disabled_instances. The above file is read before the *.sapcfg file is read and so there is no startup of the monitor for the specific instance listed in the disabled_instances file.

The format of the disabled_instances file is a text file, with each fully qualified instances 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 instance 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:
Add/delete/modify instances in the disabled_instances file
Run monconfig
Select the "E)nable Monitoring" command
Wait for monitoring to be re-enabled

[Ralph Grothe]

Sorry, for my late response.
Almost forgot this thread.

Tamil, the disabled_instances did exactly what I was looking for.