resdata --> EMS Event Notification

[Nikee Reddy]

Hello,

The usage of the resdata command is as follows:

USAGE: resdata -r resource_name -R request_id -a|-m|-u

Here my questions are:
1. How can I found out the request_id (-R) for a perticular resource?

2. Also please let me know how can I find out the resource_names available in the system?

Thanks,
Nikee

[Kent Ostby]

Nikee --

These questions can probably be answered in the EMS manual online at docs.hp.com:

http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B7609-90022/B7609-90022_top.html&con=/hpux/onlinedocs/B7609-90022/00/00/41-con.html&toc=/hpux/onlinedocs/B7609-90022/00/00/41-toc.html&searchterms=resdata&queryid=20040804-102346

Best regards,

Kent M. Ostby

[Thayanidhi]

Hi,
After any event you see a message in the syslog with request-id. Also the syntax is given in the message. You may not use this command unless there is an event.

TT

[RAC_1]

man resls

resls / will give you resource names.
The id is in EMS message itself.

Anil

[john kingsley]

set_fixed -l
Will give you a quick list of all of the resources on the system that are being monitored.

[Andrew Merritt_2]

What do you want to do with the resdata command?

By default, all the events from the EMS HW Monitors are logged in /var/opt/resmon/log/event.log.

In syslog.log, you get notifications that include the full 'resdata' command. I'm not sure what you'd want to run resdata for otherwise, but I'm interested to learn.

[Nikee Reddy]

Hello Andrew,

I have found the following command and the error in the syslog file:

Command:
resdata -R 264896546 -r /storage/events/disks/default/14_8_1_0.97.4.19.0.0.3 -a

Error:
Summary:
Disk at hardware path 14/8/1/0.97.4.19.0.0.3 : Device connectivity or hardware failure

Additional Event Data:
System IP Address...: 198.102.24.126
Event Id............: 0x4111529f00000000
Monitor Version.....: B.01.00
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_disk_em.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
None
Additional System Data:
System Model Number.............: 9000/800
OS Version......................: B.11.00
STM Version.....................: A.25.00
EMS Version.....................: A.03.20


The following are the EMS process on the host:
root@pluto:/root# ps -ef | grep res
root 3922 1 0 Jul 11 ? 3:51 /etc/opt/resmon/lbin/p_client
root 2620 1 0 Jul 11 ? 0:00 /etc/opt/resmon/lbin/emsagent
root 3972 1589 0 Jul 11 ? 0:02 /etc/opt/resmon/lbin/registrar



root@pluto:/root# ps -ef | grep stm
root 6465 1 0 Jul 11 ? 0:01 /usr/sbin/stm/uut/bin/tools/monitor/dm_memory
root 2286 1 0 Jul 11 ? 3:50 /usr/sbin/stm/uut/bin/sys/diagmond
root 5818 1 0 Jul 11 ? 0:04 /usr/sbin/stm/uut/bin/tools/monitor/dm_FCMS_adapter
root 4042 1 0 Jul 11 ? 12:54 /usr/sbin/stm/uut/bin/tools/monitor/disk_em
root 23678 23337 3 09:55:14 ttyp0 0:00 grep stm
root 6655 1 0 Jul 11 ? 8:43 /usr/sbin/stm/uut/bin/tools/monitor/sysstat_em
root 6301 1 0 Jul 11 ? 0:15 /usr/sbin/stm/uut/bin/tools/monitor/dm_core_hw
root 5984 1 0 Jul 11 ? 0:06 /usr/sbin/stm/uut/bin/tools/monitor/dm_TL_adapter
root 6506 1 0 Jul 11 ? 0:10 /usr/sbin/stm/uut/bin/tools/monitor/dm_stape


Can you please also tell me how to stop and how to start these different processes?

Under sam ==> Resource Management ==> Event Monitoring Service " There are no Monitoring requests "

Inspite of this, how come the above processes started?

I really appreciate your response.

Thanks,
Nikee

[Andrew Merritt_2 · Accepted solution]

disk_em and the other processes are part of the OnlineDiags and the EMS Hardware Monitors. They are used by the Resource Management in SAM, but are not themselves administered under SAM.

They are started automatically by the start up scripts, and can be modified (though there's not many good reasons to do so) by '/etc/opt/resmon/lbin/monconfig'

You do have an old version of OnlineDiags installed; A.25.00 (from the event text) is over 3 years old. I'd recommend upgrading to the latest version, A.44.00 and the latest patch for that release, PHSS_30890.

See http://www.docs.hp.com/hpux/onlinedocs/diag/stm/stm_upd.htm#table for the versions.

See http://www.docs.hp.com/hpux/diag/index.html#EMS%20Hardware%20Monitors%20%28for%20HP%209000%29 for more about the OnlineDiags.

You'll find the full text of the event in event.log, as well as other of lower severity that don't get logged to syslog.

[Sanjay_6]

/opt/resmon/bin/et_fixed -l will give a list of all the resources being monitored by the system.

The request id for q particular event is mentioned in the syslog log on the system.

Hope this helps.

Regds