EMS Notification Value: "CRITICAL (5)"

[Fandi Kurnia]

Hello HP People,

I get CRITICAL log on HP RX 2620 Integrity. some of message log :
Jul 23 20:19:05 cardpro EMS [3723]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/system/events/ia64_corehw/core_hw" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 243990530 -r /system/events/ia64_corehw/core_hw -n 243990627 -a

Jul 24 20:34:56 cardpro EMS [3723]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/system/events/ia64_corehw/core_hw" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 243990530 -r /system/events/ia64_corehw/core_hw -n 243990628 -a

Jul 25 20:50:45 cardpro EMS [3723]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/system/events/ia64_corehw/core_hw" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 243990530 -r /system/events/ia64_corehw/core_hw -n 243990629 -a


need your solution here :

Fandi Kurnia
Junior System Administrator

[Dennis Handly]

Have you executed the stated command?
/opt/resmon/bin/resdata -R 243990530 \
-r /system/events/ia64_corehw/core_hw -n 243990629 -a

[Fandi Kurnia]

After I execute command

# /opt/resmon/bin/resdata -R 243990530 \
> -r /system/events/ia64_corehw/core_hw -n 243990629 -a

ARCHIVED MONITOR DATA:

Event Time..........: Sun Jul 25 20:50:45 2010
Severity............: CRITICAL
Monitor.............: ia64_corehw
Event #.............: 104011
System..............: cardpro

Summary:
Power Unit : Redundancy lost or not present.


Description of Error:

The number of Power supplies has gone from N+1 (redundant) to N
(non-redundant) if a Power supply was removed, or the number of Power
supplies is < N+1.

Probable Cause / Recommended Action:

The minimum number of power supplies required to power the unit is
currently installed and operating. There are no redundant I/O power
supplies available in case of failure. If redundancy is desired another
Power supply should be added.

For information on the sensor that generated this event, refer to FRU ID
in Event Details section.

Additional Event Data:
System IP Address...: 10.32.1.29
Event Id............: 0x4c4c413500000000
Monitor Version.....: B.01.00
Event Class.........: System
Client Configuration File...........:
/var/stm/config/tools/monitor/default_ia64_corehw.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.............: ia64 hp server rx2620
EMS Version.....................: A.04.20
STM Version.....................: C.58.00
System Serial Number............: SGH461100Y
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/ia64_corehw.htm#104011

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


Event Details :

Event Date .............: Fri Mar 26 18:02:41 2010
Sensor Number ..........: 0x4f
Sensor Type ............: Power Unit
Sensor Class ...........: Discrete (type 0Bh)
Sensor Reading/Offset...: 0x02 (Sensor Reading)
Event Type.............: Not Applicable
Entity ID ..............: 19
Generic Message.........:
Power Unit : Redundancy lost
Entity FRU Id Info......:
power unit / power domain (Sensor ID: Power Redundancy)

[Dennis Handly]

>Power Unit : Redundancy lost or not present.

Looks like you lost a power supply. Make sure it's plugged in.

[Prashanth.D.S]

Hi,

Looks like a false alarm actual issue was in the month of March but the alert is triggered in July.

Check MP logs to confirm if there is a actual fault.

MP:CM>ps

Best Regards,
Prashanth

[Torsten.]

Yes, please check

MP:CM> ps

for any failed status and the MP logs too.

Even a failed CPU fan can cause a power supply to be switched off.

[Torsten.]

And by the way, your version is Dec 2007, consider to update:

http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B6191AAE

[Cinoj]

As mentioned by Prashanth, the event is actually referring to an OLD event happened in MP during March. Check the event details and event date at the end of the event.

My suggestion:
Check the MP: CM> PS for any actual issue.
Check the System Event Log in MP to see if there is any intermittent issue.

If there is no Hardware issue identified in the above checking, consider upgrading the STM to the latest.

There is a workaround too.
Remove the file "/var/stm/logs/monitor/remindersel.dat" if exists. This will be automatically recreated whenever require.