HPE 9000 and HPE e3000 Servers
cancel
Showing results for 
Search instead for 
Did you mean: 

how to check Chassis code

 
Nguyen Anh Tien
Honored Contributor

how to check Chassis code

This morning, on VFP pannel of my RP2450 the fauld LED was FLASH. then I checked /var/adm/syslog/sylog.log and dmes. The output look seem normal. Then i check GSP. and these are output
______________________________________________
GSP> vfp


VFP

This command activates the immediate display of the Virtual Front Panel.

LEDs: RUN ATTENTION FAULT REMOTE POWER
ON FLASH FLASH OFF ON
LED State: System Running. Unexpected Reboot. Non-critical Error Detected.
Check Chassis and Console Logs for error messages.

processor legacy PA HEX chassis-code F02F


Proceed with Live Mode of VFP? (Y/[N]) y
y


GSP Host Name: uninitialized
GSP>
********** VIRTUAL FRONT PANEL **********
VFP command executing...
Q/q: to quit Virtual Front Panel Display
->Choice:
*****************************************
processor display_activity() update 1F00
processor legacy PA HEX chassis-code FA2F
processor display_activity() update 1F00
processor legacy PA HEX chassis-code F02F
processor display_activity() update 1F00
processor legacy PA HEX chassis-code F02F
processor display_activity() update 1F00
==========================================
and the following are GSP log
=================



Log Entry # 2 :
SYSTEM NAME: uninitialized
DATE: 09/19/2004 TIME: 15:16:03
ALERT LEVEL: 2 = Non-Urgent operator attention required

SOURCE: 8 = I/O
SOURCE DETAIL: 2 = system bus adapter SOURCE ID: 6
PROBLEM DETAIL: 3 = function failure

CALLER ACTIVITY: 6 = machine check STATUS: 3
CALLER SUBACTIVITY: 34 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00

0x7000002382066343 00000000 00070200 type 14 = Problem Detail
0x5800082382066343 00006808 130F1003 type 11 = Timestamp 09/19/2004 15:16:03
Type CR for next entry, - CR for previous entry, Q CR to quit.
fq



Log Entry # 3 :
SYSTEM NAME: uninitialized
DATE: 09/19/2004 TIME: 15:16:03
ALERT LEVEL: 2 = Non-Urgent operator attention required

SOURCE: 8 = I/O
SOURCE DETAIL: 2 = system bus adapter SOURCE ID: 4
PROBLEM DETAIL: 3 = function failure

CALLER ACTIVITY: 6 = machine check STATUS: 3
CALLER SUBACTIVITY: 34 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00

=============
My question is that how do I analyse chassis-code(what is F02F meaning). and does I/0 have problem? (function failure)
HP is simple
2 REPLIES 2
melvyn burnard
Honored Contributor

Re: how to check Chassis code

F02F means you have a system that is running the OS, has very little run queue, 2 processors, so all should be aok.

This is the important bit:
LED State: System Running. Unexpected Reboot. Non-critical Error Detected.
Check Chassis and Console Logs for error messages.


Get a hardware call logged with your local HP Response Centre and have the logs checked, also check /etc/shutdownlog and see if you had a panic dump placed in /var/adm/crash. Also check the /var/tombstones directory and look in ts99.
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
Stefan Stechemesser
Honored Contributor

Re: how to check Chassis code

Hi,

I would also suggest to open a hardware call, because it seems that an HPMC (High Priority Machine Check) has happened. After a catastrophic failure detected by a CPU or the Memory/IO Controller, the HPMC is automatically initiated. During the HPMC, all CPU, IO and Memory Controller Registers are read and stored in the non volatile memory (NVM) on the System Board. The logs you provided, simply tells you that Registers from the I/O Controller on the Systemboard were read during the HPMC routine, but they do not tell us anything about the cause of the HPMC. I'm sure there are other GSP logs with higher alert level, because after the HPMC is processed, the machine usually crashes with a system panic to avoid data corruption.
During the bootup, the data stored in the NVM is automaticlly read out and stored to /var/tombstones/ts99.
The HP support should be able to analyze this file and hopefully the information is sufficient to determine a cause for the HPMC.

best regards

Stefan