GSP Error message

[ss_hbti]

Dear All

I am having HP rp-5450 server , server shows attention LEd during shutdown and following error message appears at GSP prompt-

Alert Level 2 = Non-urgent operator attention required
Source:8 = I/O
Source Detail:2 = System bus adapter Source ID:7
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

[VK2COT]

Hello,

I have not seen the exact error like this before, but let me give it a try...

Chassis code to FRU error code analysis:

Alert Level: How the problem has affected
the system operation. In your case, alert level is not serious. It does not,
for example, prevent boot of the server.

Source: What major part of the system the
alert is referring to (platform, memory,
processor, and so on). In your case,
source 8 is I/O.

Source Detail: What sub-part of the system
the alert is referring to (cabinet fan,
DIMM, high voltage DC power, and so on).
In your case it is system bus adapter.
If Source Detail is 6, that is Disk.
In your case, it is a system bus adapter (2).

Source ID: Specific FRU referred to in
Source and Source Detail. In your case, it
is ID 7. You can check it through several
methods. Some examples:

ioscan
dos2ux /var/tombstones/ts99

or...

Run command "SL" at the Boot Console Handler
(BCH) Main Menu:

GSP> SL

The screen will display:

Which buffer are you interested in:
Incoming, Error, Current boot, Last boot? (I/A/E/C/L), type E, and press enter

For chassis logs generated by system firmware
(Reporting Entity Type 0), use the
chassis_code.codes file for chassis code
definitions. Each revision of system firmware
(Processor Dependent Code or PDC) has a
unique chassis_code.codes file. This file is
not part of the PF_Cxxxxx or PHSS_xxxxx
server firmware patches. The chassis_code.codes files appear in the
appendices of the Interpreting Chassis Logs
in Detail guide for definition and examples
of selftest chassis codes.

Problem Detail: Specific problem information (power off, functional failure, and so on).

If there are no hardware problems, then
a firmware upgrade of GSP and/or your hardware is advised.

Lot of useful alert codes are listed here:

http://docs.hp.com/en/diag/ems/dm_chassis.htm

In any case, you do not have serious problems
yet.

Cheers,

VK2COT

[Mridul Shrivastava]

This is an alert level 2 message and it clearly says Non-urgent operator attention required. Hence as such there is no fault and no action required. However you can do a hardware check using online diags like cstm to check everything is working fine.

[ss_hbti]

thanks for your response
Today morning we have booted the system , system has shown following errors and not able to boot -

Alert Level 12 = software failure
Source:1 = Processor
Source Detail:1 = Processor general Source ID:0
Problem Detail:0 = No problem detail
Caller Activity:B = System Panic Status:0
Caller Subactivity:00 = implementation dependent
Reporting Entity Type:E = HP-UX Reporting entity ID:0

0xA0E000C01100B000 00000000 000005E9 type20=major change in system state

Pl. help , system is not booting now.

[Dennis Handly]

If this is a software error and it is a HP-UX panic, what messages were on the console?
Have you talked to the Response Center?

[timber]

Under GSP Cli:
ss #show current CPU status
ps #show current Power&Fan status
of course call RC will be the best choice

[Roberto Arias]

Hi

where are you? vmunix is in memory? please give the step that you see the messages of GSP

regards

[ss_hbti]

I am getting these error messages before HP-UX boot.
these messages are displayed on console and also in GSP prompt.


GSP>ps & ss option is showing both CPU ok and power supply also ok.

[Matti_Kurkela]

Check the GSP firmware version and the system's PDC firmware version.

The L-class / rp54xx series went through quite a lot of GSP firmware versions. Some had known false alarms, and the early ones had a habit of being nonresponsive after a long uptime.

The GSP firmware version is displayed when you issue the GSP command HE (for HElp). It's on the first line of the main help menu.

The PDC firmware version can be ascertained using the STM diagnostics (cstm/mstm/xstm) or from the boot messages. The CL (Console Log) command of the GSP might allow you to see the firmware messages of the previous system startup, if the console has not been used much since then.

Here's a direct link to the PDC firmware patches:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=322777&prodTypeId=15351&prodSeriesId=2512033&swLang=13&taskId=135&swEnvOID=7

The GSP firmware patches seem to be a bit harder to find today. The L-class/rp54xx had two variations of GSPs: the older "A" revision (GSP firmware version A.xx.xx, grey cable at the back of the GSP card) and the newer "B" revision (GSP firmware version B.xx.xx, black cable).

The latest firmware for revision A GSP:
ftp://us-ffs.external.hp.com/archived_patches/firmware_patches/hp/cpu/PF_CPREGSPA0112.tar.gz
ftp://us-ffs.external.hp.com/archived_patches/firmware_patches/hp/cpu/PF_CPREGSPA0112.txt

The latest firmware for revision B GSP:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=2512037&swItem=pf-41402-1&prodNameId=86772&swEnvOID=7&swLang=13&taskId=135&mode=4&idx=1

Most likely the older L-class servers (rp5400 and rp5450) originally had revision A GSPs, but a broken revision A GSP may have been replaced with a revision B.

Read the patch release notes to find the upgrade procedure and any dependencies. In particular, the oldest revision B firmwares cannot be upgraded directly to the newest version: you must first upgrade to B.02.15 which has a special installation procedure.

MK