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

GSP interface

 
kapil sharma_1
Occasional Advisor

GSP interface

Hi,
I am new to HPUX OS and haeving soem issue with it. We are running hpux 11 OS. I powered off the server during the weekend and now it is not coming up. I connected to the console , but can only get to GSP interface. I tried co command and nothing appears on the screen. I know I am not giving you sufficent information, but can anyone ask me the right questions to debug the issue?

Thanks
Kapil
23 REPLIES 23
Luk Vandenbussche
Honored Contributor

Re: GSP interface

Kapil,

go to CM
CM> PC, choose on
CM> ma (to go back)
MP> CO (and wait for any output)
Chan 007
Honored Contributor

Re: GSP interface

Kapil,

You need to get full priv to do that (I mean bump off the existing sessions),

press ^Ecf

then
your type CO --> for comsole

CL -->

help or ? will give your more help.

Better try CO and check what is the start of the system.

Chan
Enrico P.
Honored Contributor

Re: GSP interface

Hi,
what is the server model? Does it have the MP or GSP?


Enrico
Sivakumar TS
Honored Contributor

Re: GSP interface

Hello Kapil,

From the GSP prompt,

go to Command Mode by

MP>CM

and at

MP>CM>PS/PC depending on the server to Power ON the server.

Once powered ON

MP>CO --> to get the console of the server.

Regards,

Siva.
Nothing is Impossible !
kapil sharma_1
Occasional Advisor

Re: GSP interface

Hi,
The server model is: HP rp5405
The following is the output of commands:

Service Processor login:

Service Processor password:




Hewlett-Packard Guardian Service Processor

(c) Copyright Hewlett-Packard Company 1999-2002. All Rights Reserved.

System Name: uninitialized



*************************************************************************
GSP ACCESS IS NOT SECURE
No GSP users are currently configured and remote access is enabled.
Set up a user with a password (see SO command)
OR
Disable all types of remote access (see EL and ER commands)
*************************************************************************


GSP Host Name: uninitialized
GSP> cm


Unrecognized Command : Type HE for help on the available commands

GSP Host Name: uninitialized
GSP>

GSP Host Name: uninitialized
GSP> mp


Unrecognized Command : Type HE for help on the available commands

GSP Host Name: uninitialized
GSP>

GSP Host Name: uninitialized
GSP>

When i type co from gsp interface, it comes up with the folliwng screen:
GSP> co



CO

Leaving Guardian Service Processor Command Interface and entering
Console mode. Type Ctrl-B to reactivate the GSP Command Interface.

Any ideas?

kapil
Borislav Perkov
Respected Contributor

Re: GSP interface

Hi Kapil,
Are you Loging on the GSP?
Try to enter
Service Processor login: Admin
Service Processor password: Admin

which is default on every server.
Then try to go to main menu with MA command

Regards,
Borislav
Torsten.
Acclaimed Contributor

Re: GSP interface

After powering on, you should hear the fans running and see the system testing, e.g.

********** VIRTUAL FRONT PANEL **********
System Boot detected
*****************************************
LEDs: RUN ATTENTION FAULT REMOTE POWER
FLASH FLASH OFF ON ON
LED State: Running non-OS code. Non-critical error detected.
Check Chassis and Console Logs for error messages.

platform config 626F
processor slave rendezvous 1C17
processor test 1142
processor test 1100
processor test 1100
processor test 1100

Can you hear and see this?

Please post a

GSP> ps

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Enrico P.
Honored Contributor

Re: GSP interface

Ok,
you have an L-Class so your

Service Processor login:

Service Processor password:

are null (press Enter Key).

When you are in GSP prompt run the pc command:

GSP> pc

and power on the system

Also you can type "help" for a list of the command

GSP> help

Enrico
Jaime Bolanos Rojas.
Honored Contributor

Re: GSP interface

Kapil, the proble you are having is that you are typing the commands in Capital letters, they are not going to work like that.
Type them in lowercase and you will be able to see the output.

Regards,

Jaime
Work hard when the need comes out.
Enrico P.
Honored Contributor

Re: GSP interface

Also try to turn on the system with the power button on the front of the server and follow the boot in the console for any error.

Enrico
kapil sharma_1
Occasional Advisor

Re: GSP interface

Hi,
I tried the following comamnds:

GSP> vfp


VFP

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

LEDs: RUN ATTENTION FAULT REMOTE POWER
OFF FLASH OFF ON ON
LED State: No code is executing. Non-critical error detected.
Check Chassis and Console Logs for error messages.

platform power on/off 6300


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 Host Name: uninitialized

So the system looks ok, but I cannot still see any messages on the screen??

Thanks
kapil

Enrico P.
Honored Contributor

Re: GSP interface

Hi,
your RUN led is off, so I think your system is down.
Can you telnet on the system? If no:

Type rs from GSP prompt:

GSP> rs

and confirm with "yes"

Enrico
Torsten.
Acclaimed Contributor

Re: GSP interface

Did you only shut down the OS or really switched off the box last week?

In case you did *not* switched off you need to reset (GSP> rs) or power cycle the system.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
kapil sharma_1
Occasional Advisor

Re: GSP interface

Hi,
I tried to powercycle the box by switching off the machine (by disconnecting all power cables and reconnect them). I can see the following messages on console:
Leaving Guardian Service Processor Command Interface and entering
Console mode. Type Ctrl-B to reactivate the GSP Command Interface.

HP Guardian Service Processor
Firmware Revision B.02.20 Apr 14 2003,11:03:46
(c) Copyright Hewlett-Packard Company 1999-2002. All Rights Reserved.

Type Ctrl-B to activate the GSP Command Interface.

I don't know why it is not displaying any other messages?

Thanks
Kapil
Jaime Bolanos Rojas.
Honored Contributor

Re: GSP interface

Kapil, do this, when you are at the GSP> just type this command: rs

That is going to reboot your system and you can see all the messages on the server.

Jaime
Work hard when the need comes out.
kapil sharma_1
Occasional Advisor

Re: GSP interface

Hi,
I executed rs to reset the system, but still can't view any messages. Something might be seriouly wrong with my configuration:-(

kapil
Jaime Bolanos Rojas.
Honored Contributor

Re: GSP interface

Kapil, you might be facing a hardware problem instead of a software problem most likely, if your server is still under warranty I would recomend you to call HP for support on hardware.

Best Regards,

Jaime.
Work hard when the need comes out.
Sandy Chen
Honored Contributor

Re: GSP interface

Hi Kapil,

Can you attach result of SL command on GSP?

GSP> sl


SL

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

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

regards,
Sandy
I never think of the future. It comes soon enough.
mits
Respected Contributor

Re: GSP interface

I would suggest you will provide us the GSP PS command output and VFP command output at least. Then we can understand the current system status. Then someone can provide you more specific suggestion to resolve your problem. Most suspect is that you have not turned on the DC power. We do not know how you turned off the power. Was it just for DC power or AC power? Or did you use the front DC power switch to turn off the DC power? It is better you will describe how you turned on your system power step by step.
kapil sharma_1
Occasional Advisor

Re: GSP interface

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
Occasional Advisor

Re: GSP interface

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.
Honored Contributor

Re: GSP interface

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
Honored Contributor

Re: GSP interface

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.
Support Fatherhood - Stop Family Law