GSP interface

[kapil sharma_1]

Hi,
The following is the output of sl command:
GSP> sl


SL

Select Chassis Code Buffer to be displayed:
Incoming, Activity, Error, Current boot or Last boot? (I/A/E/C/L) e
e

Set up filter options on this buffer? (Y/[N]) n
n

The first entry is the most recent Chassis Code
Type + CR and CR to go up (back in time),
Type - CR and CR to go down (forward in time),
Type Q/q CR to quit.


Log Entry # 0 :
SYSTEM NAME: uninitialized
DATE: 02/27/2006 TIME: 09:15:29
ALERT LEVEL: 14 = Fatal power or environmental problem prevents operation

SOURCE: 6 = platform
SOURCE DETAIL: 1 = cabinet SOURCE ID: FF
PROBLEM DETAIL: 1 = inlet overtemp

CALLER ACTIVITY: 3 = power on/off STATUS: F
CALLER SUBACTIVITY: 00 = unspecified
REPORTING ENTITY TYPE: 2 = power monitor REPORTING ENTITY ID: 00

0x002000E161FF300F 00000000 00000000 type 0 = Data Field Unused
0x582008E161FF300F 00006A01 1B090F1D type 11 = Timestamp 02/27/2006 09:15:29
Type CR for next entry, Q CR to quit.



Log Entry # 1 :
SYSTEM NAME: uninitialized
DATE: 02/26/2006 TIME: 17:36:45
ALERT LEVEL: 13 = System hang detected via timer popping

SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 4 = timeout

CALLER ACTIVITY: F = display_activity() update STATUS: 0
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX REPORTING ENTITY ID: 00

0x78E000D41100F000 00000003 00000000 type 15 = Activity Level/Timeout
0x58E008D41100F000 00006A01 1A11242D type 11 = Timestamp 02/26/2006 17:36:45
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 2 :
SYSTEM NAME: uninitialized
DATE: 02/26/2006 TIME: 17:36:49
ALERT LEVEL: 14 = Fatal power or environmental problem prevents operation

SOURCE: 6 = platform
SOURCE DETAIL: 1 = cabinet SOURCE ID: FF
PROBLEM DETAIL: 1 = inlet overtemp

CALLER ACTIVITY: 4 = monitor STATUS: F
CALLER SUBACTIVITY: 06 = temperature sensor
REPORTING ENTITY TYPE: 2 = power monitor REPORTING ENTITY ID: 00

0x002000E161FF406F 00000000 00000000 type 0 = Data Field Unused
0x582008E161FF406F 00006A01 1A112431 type 11 = Timestamp 02/26/2006 17:36:49
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 3 :
SYSTEM NAME: uninitialized
DATE: 11/23/2005 TIME: 12:08:14
ALERT LEVEL: 2 = Non-Urgent operator attention required

SOURCE: 3 = PDH
SOURCE DETAIL: 6 = interconnect medium SOURCE ID: 0
PROBLEM DETAIL: 3 = non-responding, may need GSP reset.

CALLER ACTIVITY: 2 = operation STATUS: 0
CALLER SUBACTIVITY: 02 = platform internal interconnect
REPORTING ENTITY TYPE: 1 = service processor REPORTING ENTITY ID: 00

0x5810082336002020 0000690A 170C080E type 11 = Timestamp 11/23/2005 12:08:14
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 4 :
SYSTEM NAME: uninitialized
DATE: 11/16/2005 TIME: 10:45:08
ALERT LEVEL: 2 = Non-Urgent operator attention required

SOURCE: 3 = PDH
SOURCE DETAIL: 6 = interconnect medium SOURCE ID: 0
PROBLEM DETAIL: 3 = non-responding, may need GSP reset.

CALLER ACTIVITY: 2 = operation STATUS: 0
CALLER SUBACTIVITY: 02 = platform internal interconnect
REPORTING ENTITY TYPE: 1 = service processor REPORTING ENTITY ID: 00

0x5810082336002020 0000690A 100A2D08 type 11 = Timestamp 11/16/2005 10:45:08
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry # 5 :
SYSTEM NAME: uninitialized
DATE: 06/13/2005 TIME: 08:15:19
ALERT LEVEL: 2 = Non-Urgent operator attention required

SOURCE: 3 = PDH
SOURCE DETAIL: 6 = interconnect medium SOURCE ID: 0
PROBLEM DETAIL: 3 = non-responding, may need GSP reset.

CALLER ACTIVITY: 2 = operation STATUS: 0
CALLER SUBACTIVITY: 02 = platform internal interconnect
REPORTING ENTITY TYPE: 1 = service processor REPORTING ENTITY ID: 00

0x5810082336002020 00006905 0D080F13 type 11 = Timestamp 06/13/2005 08:15:19
Type CR for next entry, - CR for previous entry, Q CR to quit.


This is the last log entry corresponding to your choice.



Log Entry # 5 :
SYSTEM NAME: uninitialized
DATE: 06/13/2005 TIME: 08:15:19
ALERT LEVEL: 2 = Non-Urgent operator attention required

SOURCE: 3 = PDH
SOURCE DETAIL: 6 = interconnect medium SOURCE ID: 0
PROBLEM DETAIL: 3 = non-responding, may need GSP reset.

CALLER ACTIVITY: 2 = operation STATUS: 0
CALLER SUBACTIVITY: 02 = platform internal interconnect
REPORTING ENTITY TYPE: 1 = service processor REPORTING ENTITY ID: 00

0x5810082336002020 00006905 0D080F13 type 11 = Timestamp 06/13/2005 08:15:19
Type CR for next entry, - CR for previous entry, Q CR to quit.

[kapil sharma_1]

The following is the output of ps and vfp command:

GSP> ps


PS

Power Monitor Status:
Firmware Revision : A
System Power state: On Power Switch : On
Temperature : Normal Selected fan state: Normal

Power supplies | Fan
# State Type | States
-----------------------------------------------------------
0 Normal Type 0 | Normal
1 Normal Type 0 | Normal
2 Normal Type 0 | Normal
3 - - | Normal
4 - - | Normal
5 - - | Normal
6 - - | Normal
7 - - | Normal


GSP> vfp


VFP

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

LEDs: RUN ATTENTION FAULT REMOTE POWER
OFF OFF OFF ON ON
LED State: Cannot Execute PDC.
Check Chassis and Console Logs for error messages.

platform operation 6203


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:
*****************************************

[Enrico P.]

Hi,


check

http://docs.hp.com/ja/2781/en/tools/l2/frontpanelleddecode_l2/allleds.htm

Cannot execute PDC. If more than one processor installed, the problem is most likely a failed system board. If only one processor installed, problem could be either the processor or system board.

I think you need to contact the HP support.

Enrico

[Michael Steele_2]

These servers have redundent power supplies.

You stated you recycled the power by pulling all the cables. Verify the cables are snug and tight.

Verify what you now have enough power to boot up. Get facilities involved and check your power nodes. Backtrack from the power node into the server and each power pack on the server.

Become aware of proper shutdown / halting commands, i.e., shutdown -h now, and graceful shutdown procedures.