How to disable part of EMS Monitoring?

[Sandip Ghosh]

OS - HP-UX 10.20
EMS Version : A.03.20
STM Version : A.29.00

I need to disable the monitor for the UPS, dm_ups, temporarily. Is there any way to disable the monitor except "delete a monitor" option in the monconfig?

Thanks in advance,
Sandip

[S.K. Chan · Accepted solution]

You would have to delete it from "monconfig" and later add it back.
To disable
==========
# cd /etc/opt/resmon/lbin
# ./monconfig.
==> Use "d" to delete all dm_ups monitoring. You'll be prompted to enter the number from the output when you enter "d".
==> With ./monconfig still running, continue ..
# cd /var/stm/config/tools/monitor
# mv dm_ups.psmcfg dm_ups.psmcfg.org
==> Rename the config file.

Back to monconfig window, enter "c" (check) to make sure dm_ups is not longer being monitored.

# mv dm_ups.sapcfg dm_ups.sapcfg.org
==> Rename another config file.
# ps -ef|grep dm_ups
# kill
==> Kill it.
# cd /var/stm/data/tools/monitor
# rm dm_ups.hwa
==> Remove the dm_ups.hwa file.

Later to enable it back
=======================
# cd /etc/opt/resmon/lbin
# ./monconfig
==> Enter "a" to add dm_ups back.

Rename dm_ups.psmcfg.org and dm_ups.sapcfg.org back to it's original name.

In "monconfig" check it with "c" and also check the process. It should be started up.

[Helen French]

Just curious - why do you want to do this? any message in syslog.log?

[Sandip Ghosh]

Superb SK!!!
It works fine.

Shiju,

Actually what happens, after installing the HP Powertrust MRII UPS , everyday I found that in a particular time the /var filesystem is filling up and it is getting cleaned automatically. Initially I thought it is happening through some application and I was trying to catch the process who is writing the process. If you could remember I had opened a thread also regarding this. After that I found that EMS is trying to dump something. After doing some investigation I found out that it is coming from the UPS monitoring (dm_ups). That is why I need to disable the dm_ups.

Interestingly, the same configuration is working with the old powertrust UPS. Do you know anything needs to be changed for the new Powertrust MRII UPS? Anyway, I have opened a call with HP also regarding this.

Sandip

[Christopher McCray_1]

Hello,

You can make use of the /var/stm/data/tools/monitor/disabled_instances file to accomplish this.

Here is a cut and paste of the instructions given to me by the response center:

Disable an EMS hardware monitor for a single instance
-----------------------------------------------------

EMS now reads a file /var/stm/data/tools/monitor/disabled_instances to determine which hardware paths should be ignored.

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.

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

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

2.Run monconfig K)ill monitoring

3.With editor of your choice, Add/delete/modify instances at /var/stm/data/tools/monitor/disabled_instances.
Example:/storage/events/disks/default/8_12.0.0

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

5.Wait for monitoring to be re-enabled

6.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.)

Hope this helps

Chris

[Sandip Ghosh]

Yes Chris,

It is there in the EMS help file. It looked complecated to me. In my scenario, I think, it will first try to start the monitor and the it will stop the monitor since it is mentioned in the disable_monitor file. And if it try to start the monitor I will get the problem before it disable the monitor by the next monitoring request. So, in my case SK's suggestion is more appropriate.

Sandip

[Helen French]

Sandip,

Yes, I do remember the old thread regarding the case you mentioned. But the reason I was asking is that, recently I read a TKB document saying the same type of problem with the same EMS version installed. It says the message keeps coming because of an installed patch on the system - PHCO_19031 (on 10.20) OR PHCO_19040 (on 11.0). What happens is that this patch adds an older filesets to the EMS installed version. I will search for that document and will post if I could find that.

The solution is to uninstall this patch with swremove!

[Helen French]

This is the document, may be helpful (TKB#KBRC00004745):
http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000063208033

[Sandip Ghosh]

Shiju,

Unfortunately I do not have that patch, PHCO_19031, installed in my system. Do you know any specific configuration is there for PowerTrust MRII installation/configuration?

Sandip

[Helen French]

Sorry, if it didn't help. I don't have any detail about the configuration for this particular UPS. I found these two documents by doing a search. may be helpful for you:
http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062922857
http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062922413