Remove Monitor Class from EMS

[Tony Scully_2]

Hi,

I need to remove a monitor from EMS as we no loger use that particular type of hardware. monconfig does not seem to allow me to do this, and I don't think this is appropriate for disabled_instances (which I think is for individual paths). Can I just delete or change the monitor config files directly and restart the monitoring?

It's an FC60 arrray (so fc60mon is affected).

TIA
Tony

[Steven E. Protter]

Shalom Tony,

Try entering EMS configuration as root user via sam.

This should permit you to stop monitoring on any type of hardware.

SEP

[Tony Scully_2]

Hi Stephen,

Weirdly I don't get a list of monitors under SAM->Resource Management->Event Monitoring but if I run monconfig I do, and we are getting alerts....

Any ideas?

Tony

[Nikolay Kuznetsov]

1. What is the output of:
set_fixed -l
2. Then
resls /storage/events/disk_arrays/FC60
resls /storage/status/disk_arrays/FC60
3. Try restart EMS. If the hardware is not available you should not receive events.

[Tim Nelson]

Unless it has changed SAM only lets you create or delete extra services not the basics.

/etc/opt/resmon/lbin/monconfig will work. Add, edit, delete....

(S)how monitoring requests configured via monconfig
(C)heck detailed monitoring status
(L)ist descriptions of available monitors
(A)dd a monitoring request
(D)elete a monitoring request
(M)odify an existing monitoring request
(E)nable Monitoring
(K)ill (disable) monitoring
(H)elp
(Q)uit
Enter selection: [s]

[Ivan Krastev]

See kb doc KBQA00000261 - 'EMS : HOW TO DISABLE A HARDWARE DEVICE FROM BEING MONITORED' - http://www8.itrc.hp.com/service/cki/docDisplay.do?docLocale=en&docId=emr_na-c00991671-2


regards,
ivan

[Andrew Merritt_2]

Hi Tony,
What do you mean by removing the monitor from EMS? Where are you seeing it listed?

If you have no FC60 hardware, fc60mon should not be running. Or do you mean the FC60 is still attached, but not used?

If the latter case, what's the problem you're actually getting from the monitor running?

(Please ignore the first response, the HW monitors are not configured from SAM, no matter how many times SEP says they are.)

Andrew

[Tony Scully_2]

Guys,

Thanks for the replies. If I look in monconfig I can see the fcmonitor is there, as part of a bigget event monitor -- I can only delete the whole monitor, or modify the individual classes, not remove them. Unless I am being stupid of course!
I don't want to add to the disabled instace file, becasue it's not a disabled instance - the FC60 has gone and is not coming back.

Here's the message we get:



Notification Time: Wed Oct 31 18:34:29 2007
sent Event Monitor notification information:
/storage/events/disk_arrays/FC60/AM60Srvr is >= 3.
Its current value is MAJORWARNING(3).


Event data from monitor:
Event Time..........: Wed Oct 31 18:34:29 2007
Severity............: MAJORWARNING
Monitor.............: fc60mon
Event #.............: 4
System..............: hpmagpie

Summary:
Disk Array at hardware path :
Array at hardware path Unknown, path Unknown: The computer can not connect to the AM60Srvr.
The status on the disk array is not currently available.


Description of Error:

This event message is displayed when a connection cannot be made to the AM60Srvr. The resource monitor will continue to attempt to connect to the AM60Srvr at regular polling intervals. When the AM60Srvr is restored, the connection will succeed and normal operation will continue. Until the AM60Srvr is operating normally, it is not possible to obtain the current status of any of the disk arrays.

Probable Cause / Recommended Action:

Restart AM60Srvr, or if still running, stop and restart the AM60Srvr.
Possible Causes Include:
1. The AM60Srvr is not running.
2. The wrong version of the AM60Srvr is running.
3. The correct AM60Srvr is running, but is hung.
4. Restart AM60Srvr using the command /opt/hparray/bin/AM60Srvr, or if still running,
5. Stop (kill -9 pid; pid - process if of AM60Srvr) and restart the AM60Srvr.

Additional Event Data:
System IP Address...:
Event Id............: 0x4728cab500000000
Monitor Version.....: B.01.02
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_fc60mon.clcfg
Client Configuration File Version...: A.01.01
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
None
Additional System Data:
System Model Number.............: 9000/800/N4000-55
EMS Version.....................: A.03.20
STM Version.....................: A.44.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/fc60mon.htm#4
v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v


Product/Device Data:
Logger ID.........: (not available/applicable)
Product Identifier: (not available/applicable)
Product Qualifier.: (not available/applicable)
SCSI Target ID....: (not available/applicable)
SCSI LUN..........: (not available/applicable)

[Andrew Merritt_2]

Tony,
Thanks for the update. Just to check, you've physically removed the FC60 from the system, and now you're getting EMS events (which are saying that the FC60 is unreachable); is that correct?

I think I've seen this before; unfortunately I can't remember what needs to be done to stop it. I've a feeling there are some steps that should be followed when removing an FC60. Removing the AM60Srvr software might clear this.

Using disabled_instances is one way to deal with the symptom; it would stop the generation of the EMS events for FC60. Don't get too hung up on the name of the file; it's a list of devices for which EMS Events have been disabled. Assuming you don't have any FC60s left on the system, I think the entry to put in the disabled_instances file would be:

/storage/events/disk_arrays/FC60/AM60Srvr

Andrew

[Tony Scully_2]

Andrew,

Thanks -- There's no FC60 array attached now, but I've only just started working on these servers, so don't know when (or how) it was removed.

It's probably sensible to remove the ARM server software anyway, and I will try putting the fc60mon in the disabled instances file -- I was under the (false) impression that you have to put the h/ware path in that file.

I'll get this done in the next few days, then assign points if required.

Cheers,
Tony