EMS reporting

[Richard_115]

how do I stop EMS from reporting or collecting information on a particular hardware like HPARRAY that I have disconnected ? Is there a config file where I can do that ????

Thanks
Richard

[spex]

Hi Richard,

# /etc/opt/resmon/lbin/monconfig

PCS

[Chan 007 · Accepted solution]

Richard,

You need to edit the following file and add or remove

/var/stm/data/tools/monitor/disabled_instances

restart the EMS

Chan

[Richard_115]

I did that... but each time I disable and enable monitoring, it still sends me the same error that the device is unavailable ... thats after some minutes...

[Richard_115]

Chan

What am I supposed to do in this file ??? I have opened it and it seems empty... any advise ?

[Andrew Merritt_2]

Hi Richard,
Does the hardware still show up in 'ioscan'? Have you tried rerunning ioscan without the -k option, to rescan what's actually attached? Was the hardware removed in accordance with the instructions (I don't know if hparray can be removed without shutting down, for example)?

What problems are you actually seeing? If it's EMS events, which ones and how often?
What version of the OnlineDiags is installed?

Andrew

(Reposted from the other thread you started, so that can be closed)

[Chan 007]

Richard,

Depends which alert you are disbaling, if you want to disbale a tape of HP

the follow the following

ioscan -kfnCtape |grep "HP" |awk '{print ":storage:events:tapes:default:"$3}' |tr '/' '_' |tr ':' '/'

The output will be something like

/storage/events/tapes/default/10_12_5.0.0

Just append that line to the file I mentioned earlier, then restart the ems

Once done it, just do the following

/etc/opt/resmon/lbin/moncheck

this will give Critical but No warning

Chan

[Andrew Merritt_2]

Richard,
What's the actual message you are getting?

If we're talking about a temporary situation until the system can be rebooted and the hardware rescanned, then yes, using disabled_instances is a way to suppress the events. (Though you should check after the reboot that the path in disabled_instances doesn't now refer to a valid hparray device if you have more than one.)

Chan 007:
this will give Critical but No warning

If you mean that you will still get Critical level events for paths that have an entry in disabled_instances, then I'm afraid you are mistaken. If you mean something else, please explain.

Andrew

[Richard_115]

All

The error I am getting is as follows:

Summary:
Disk Array at hardware path :
Array at hardware path 0/5/0/0.8.0.5.0.0.0, path 1/12/0/0.8.0.4.0.0.0: The primary battery has failed.

Now I have done what chan has recomended. I have disabled and enabled monitoring. I am waiting to see that it works or not.

[Andrew Merritt_2]

That's Event 22 from fc60mon, I think?


The following questions may help to get to the root cause, which in general is best :-)

What state is the FC60 in, is it physically attached to the system? Is the battery OK?

What version of the OnlineDiags do you have? (You can see this in the EMS message, as "STM Version", or when you run STM.)

What does ioscan show for 0/5/0/0.8.0.5.0.0.0, and 1/12/0/0.8.0.4.0.0.0?

If you really just want to suppress the errors, and you're still having problems doing that, the disabled_instances entry should be the same as near the beginning of the EMS event (before the bit you pasted), something like:

/storage/events/disk_arrays/FC60/000E00A0B8091236

Hope this helps,
Andrew

[Michael Steele_2]

Dear Richard:

export display
sam
resource management
event monitoring service
select HPARRAY
actions menu > remove

Tally Ho

[Andrew Merritt_2]

Sorry, Michael, that doesn't address Richard's question at all.

The EMS section under Resource Monitoring is for monitoring the status of devices. It does not deal with the EMS HW monitors, which report events relating to errors and other incidents.

Andrew