EMS Event Notification

Nabil Boussetta — Mon, 22 Aug 2005 07:24:49 GMT

i have an rp8400 server under hp-ux11i v1.
i have found the following notification on the syslog file.

Aug 15 14:28:01 CENTRAL2 EMS [2578]: ------ EMS Event Notification ------ Value: "MAJORWARNING (3)" for Resource: "/system/events/chassis/chassis_log" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 168951810 -r /system/events/chassis/chassis_log -n 168951813 -a

execution of the CMD /opt/resmon/bin/resdata -R 168951810 ... gives the following

$ /opt/resmon/bin/resdata -R 168951810 -r /system/events/chassis/chassis_log -n 168951813 -a

CURRENT MONITOR DATA:

Event Time..........: Mon Aug 15 14:28:01 2005
Severity............: MAJORWARNING
Monitor.............: dm_chassis
Event #.............: 5
System..............: CENTRAL2

Summary:
Boot possible pending failure - action required (e.g. boot disk error rate
above threshold, power failure, overtemp medium).

Description of Error:
The first encoded field of this chassis log was not found in the internal
chassis code table. Therefore, no description text is available for this
chassis log. Enter the "details" key to view the fully decoded chassis
log.
Probable Cause / Recommended Action:

Cause:
The first encoded field (0x582008694102401f) of this chassis log was
not found in the internal chassis code table. This chassis code may
have been added since the monitor was last changed.

Action:
Possible ways to decode this chassis code:
1) Load a more current version of the OnlineDiag software depot
(Support Tools). Installing this depot automatically installs
the EMS hardware monitors (if you have modified the default
settings, additional configuration may be required.) Almost
all chassis codes for a computer system should be supported in
the dm_chassis monitor in the first diagnostic release that
appears after the computer system has been released. The EML
monitor release notes for the diagnostic release may have more
information.
2) Contact HP support. They may have access to a more current
set of chassis codes, for example, through a chassis code
decoder program.

Additional Event Data:
System IP Address...: 172.20.0.103
System IP Address...: 10.0.0.2
Event Id............: 0x4300986100000000
Monitor Version.....: A.01.00
Event Class.........: System
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_chassis.clcfg
Client Configuration File Version...: A.02.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
None
Additional System Data:
System Model Number.............: 9000/800/S16K-A
EMS Version.....................: A.04.00
STM Version.....................: A.41.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_chassis.htm#5

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

Chassis Log Timestamp : 08/15/2005 12:05:18
Chassis Code Encoded Field : 0x582008694102401f
Alert Level : 6 (Boot possible pending failure - action required
(e.g. boot disk error rate above threshold, power failure, overtemp
medium).)
Source FRU : 4 (power entity)
Source FRU Detail : 1 (AC mains)
Source ID : 2 (platform dependent)
Event Detail : 9 (power off)
Caller Activity : 4 (monitor)
Caller Subactivity : 1 (AC main)
Activity Status : 15 (implementation dependent)
Reporting Entity Type : 2 (power monitor)
Reporting Entity ID : 0
Data Type : 11 (timestamp)
Message ID : 0 (not associated with other log entries)
Chassis Log Timestamp : 08/15/2005 12:05:18

is there a serious problem ? what should i do ?

Re: EMS Event Notification

Nabil Boussetta — Mon, 22 Aug 2005 07:26:31 GMT

topic Re: EMS Event Notification in Insight Remote Support

EMS Event Notification

Re: EMS Event Notification