1837232 Members
2131 Online
110115 Solutions
New Discussion

EMS

 
SOLVED
Go to solution
castro_2
Regular Advisor

EMS

I have in state DOWN, I put in /var/stm/data/tools/monitor/disabled_instances
/adapters/status/FC_adapter/*
/adapters/status/TL_adapter/*
But still send me alarms.

/storage/status/disks/default/8_0.3.0 UP TRUE
/storage/status/disks/default/8_0.5.0 UP TRUE
/storage/status/disks/default/8_0.6.0 UP TRUE
/storage/status/disks/default/10_0.3.0 UP TRUE
/storage/status/disks/default/10_0.5.0 UP TRUE
/storage/status/disks/default/10_0.6.0 UP TRUE
/storage/status/disks/default/10_12_5.2.0 UP TRUE
/adapters/status/FC_adapter/8_12 DOWN TRUE
/adapters/status/FC_adapter/8_12.8 DOWN TRUE
/adapters/status/TL_adapter/8_12.8 DOWN TRUE
/system/status/core_hw/core_hw UP TRUE
/system/status/memory/49 UP TRUE
/storage/status/tapes/SCSI_tape/10_12_5.0.0 UP TRUE
/system/status/system_status/ui_host/sarsau12 UP TRUE

Thanks
5 REPLIES 5
Stefan Farrelly
Honored Contributor

Re: EMS

Have you followed all the steps ? rebooted after changing this file to restart th diags and run monconfig to enable monitoring to make it take effect ?
Im from Palmerston North, New Zealand, but somehow ended up in London...
Fabio Ettore
Honored Contributor

Re: EMS

Hi castro,

as described into /var/stm/data/tools/monitor/disabled_instances:

............
# When changes are made to this file, the user should run monconfig and
# enable monitoring to make changes in this file take effect.
#
# NOTE: entries in this file do NOT cause a monitor to stop polling an
# instance or stop the PSM monitor from marking an instance as DOWN, it
# just stops the notification of events based on entries in the *.sapcfg
# files for this instance.

Anyway a procedure to disable instances is described perfectly to the end of doc KBRC00008971. You find it into 'search technical knowledge base' from ITRC home page and then select 'search by Doc.ID' inserting KBRC00008971.

I hope this helps you.

Best regards,
Ettore
WISH? IMPROVEMENT!
castro_2
Regular Advisor

Re: EMS

Before I used the procedure KBRC00008971 to disable instances.
But still send me alarms. The problem can be by It has more than 1 instance in file disabled_instances?
Thanks
Fabio Ettore
Honored Contributor
Solution

Re: EMS

Hi,

it should not be a problem.
What do you see if launch

# /etc/opt/resmon/lbin/monconfig

and then select

(C)heck detailed monitoring status

(just type c to select)

?

This output should not show instances into disable_instances file.

Otherwise if it shows that instance yet, problem could be that disable_instances file isn't used. In this instance you should

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

2. 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

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 you disabled should show up in the list with no
description of what to do with events. (ie. there are no monitoring requests)

I hope this solves your problem.

Best Regards,
Ettore
WISH? IMPROVEMENT!
castro_2
Regular Advisor

Re: EMS

El problem events y not status
/storage/events/tapes/SCSI_tape/8_16_5.3.0
/storage/status/tapes/SCSI_tape/8_16_5.3.0
Thanks
Regards