If probelm is serious

[Slawek Ksiazek]

Last time i see in my syslogd.log following infrmation:

Sep 20 13:39:01 nc041226 EMS [2537]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/system/events/ipmi_fpl/ipmi_fpl" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 166264835 -r /system/events/ipmi_fpl/ipmi_fpl -n 166264833 -a
Sep 20 13:39:01 nc041226 EMS [2537]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/system/events/ipmi_fpl/ipmi_fpl" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 166264835 -r /system/events/ipmi_fpl/ipmi_fpl -n 166264834 -a


and

CURRENT MONITOR DATA:

Event Time..........: Sat Sep 20 13:39:01 2008
Severity............: CRITICAL
Monitor.............: fpl_em
Event #.............: 292
System..............: nc041226.kraklab.pl.ibm.com

Summary:
Machine Check initiated


Description of Error:

A Machine Check has been initiated

Probable Cause / Recommended Action:


A Machine Check has occurred.

Analyze cause of Machine Check using diag's and EFI tools.


Additional Event Data:
System IP Address...: 9.167.41.226
Event Id............: 0x48d5515500000003
Monitor Version.....: A.01.00
Event Class.........: System
Client Configuration File...........:
/var/stm/config/tools/monitor/default_fpl_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.............: ia64 hp server rx7640
EMS Version.....................: A.04.20
STM Version.....................: C.58.00
System Serial Number............: USE48223V7
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/fpl_em.htm#292

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


IPMI event hex: 0xf480009810e00000 0x000000000000000b
Time Stamp: Sat Sep 20 19:26:32 2008
Event keyword: MC_INITIATED
Alert level name: Fatal
Reporting vers: 1
Data field type: Major change in system state
Decoded data field: System State = 11(HPMC or MCA)
State Change Event = 0(At BIB)
LED Command Valid = 0(LED state is not updated)
LED Run = 0(off (default))
LED Attention = 0(reserved)
LED Stopped = 0(off (default))
Reporting entity ID: 16 ( Cab 0 Cell 1 CPU 0 )
Reporting entity Full Name: System Firmware
IPMI Event ID : 152 (0x98)


what you think about this?Thanks


Slawek

[Slawek Ksiazek]

and aslo this

# r /system/events/ipmi_fpl/ipmi_fpl -n 166264833 -a <

ARCHIVED MONITOR DATA:

Event Time..........: Sat Sep 20 13:39:01 2008
Severity............: CRITICAL
Monitor.............: fpl_em
Event #.............: 267
System..............: nc041226.kraklab.pl.ibm.com

Summary:
INIT initiated


Description of Error:

This is the equivalent of a TOC event in the PA RISC Architecture. On IPF
systems, this event is called an INIT.
This event can be triggered by the "tc" command from the MP, or from the button
labeled "TOC" :wor "Transfer of Control" on the Management card or bezel of the
system. There are also other causes of an INIT generated by software.
Data: Local CPU Number

Probable Cause / Recommended Action:


Software has requested an INIT or the INIT button has been pressed.

No action is required.


Additional Event Data:
System IP Address...: 9.167.41.226
Event Id............: 0x48d5515500000000
Monitor Version.....: A.01.00
Event Class.........: System
Client Configuration File...........:
/var/stm/config/tools/monitor/default_fpl_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.............: ia64 hp server rx7640
EMS Version.....................: A.04.20
STM Version.....................: C.58.00
System Serial Number............: USE48223V7
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/fpl_em.htm#267

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


IPMI event hex: 0xf680007913e00000 0x000000000000000b
Time Stamp: Sat Sep 20 19:26:02 2008
Event keyword: INIT_INITIATED
Alert level name: Fatal
Reporting vers: 1
Data field type: Implementation dependent data field
Decoded data field:
Reporting entity ID: 19 ( Cab 0 Cell 1 CPU 3 )
Reporting entity Full Name: System Firmware
IPMI Event ID : 121 (0x79)


Slawek

[Kenan Erdey · Accepted solution]

Hi,

it says TOC signal was send. so there must be log in /var/adm/crash. if someone didn't push the TOC button in front of the server, it may be a hardware problem. Open a call to HP.

Kenan.