HPE 9000 and HPE e3000 Servers
1825512 Members
1975 Online
109681 Solutions
New Discussion юеВ

GSP Correct logout sequence

 
Joan Blais
Frequent Advisor

GSP Correct logout sequence

I've been receiving numerous EMS alerts stating that the service processor is not responding on N4000 servers. I've checked the status through the GSP XD I2C access test and it always passes. The firmware version is B.02.04. The login sequence used is to telnet to the GSP, then login. I enter at a read only screen. From there I enter ^Ecf. At the console prompt I enter ^b to reach the GSP prompt. To exit I enter co returning to the console. From there I enter ^] to reach the telnet prompt, then c to close. Is this the correct logout sequence?
13 REPLIES 13
Sachin Patel
Honored Contributor

Re: GSP Correct logout sequence

Hi Joan,
I uses co at gsp> prompt to get out from gsp menu.

Sachin
Is photography a hobby or another way to spend $
Joan Blais
Frequent Advisor

Re: GSP Correct logout sequence

I don't have a problem getting out, however the EMS notifications are stating that the GSP is not responding. I'm wondering if I am not logging out correctly, causing the EMS notifications.
Christopher McCray_1
Honored Contributor

Re: GSP Correct logout sequence

Hello,

If the EMS messages you are getting are what I think they are, does the message continue on as to how to reset the GSP? Somenthing like executing the following command:

# stty +resetGSP < GSPdiag

I can't recall the particular error, but that is what I'm looking for.

Can you post the EMS message by chance?

Chris
It wasn't me!!!!
Joan Blais
Frequent Advisor

Re: GSP Correct logout sequence

CURRENT MONITOR DATA:Event Time..........: Tue Apr 9 16:14:05 2002
Severity............: SERIOUS
Monitor.............: dm_core_hw
Event #.............: 32
System..............: usunx26.reebok.com
Summary: Service processor not responding
Description of Error: The operating system is unable to communicate
with the service processor.
Probable Cause / Recommended Action:
The support bus which connects the system processors,
the service processor and the Power Monitor or
Platform Monitor may have become hung.
(The support bus can be tested by issuing the service processor command
"XD", and selecting the I2C access test).
To reset the bus, issue the service processor command "XD" and then
select "R", use the HP-UX command `stty +resetGSP or press the service processor reset button.
If this solves the problem
(if the I2C access test now works) and the system is an N-Class,
rp7400, L-Class, rp5400, rp5430, rp5450 or rp5470, check the service
processor firmware revision using the service processor command "HE". If the service processor firmware version is less than A.01.09,
schedule an update of the service processor firmware to version
A.01.09 or a more recent version to prevent a reoccurrence of this
problem.

There could be a problem with the service processor.
Verify that the service processor appears to be operating normally.
This can be done by typing a B at the console and verifying
that the service processor responds to commands. If the service
processor has failed, contact your HP support representative to check
the core I/O board.

There could be a problem with the system board.
Contact your HP support representative to check the system board if
necessary.

Additional Event Data:
System IP Address...: 10.101.202.126
Event Id............: 0x3cb34b8d00000000
Monitor Version.....: B.01.00
Event Class.........: System
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_core_hw.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 2
Associated OS error log entry id(s):
0x3cb34b8d00000000
Additional System Data:
System Model Number.............: 9000/800/N4000-75
OS Version......................: B.11.00
STM Version.....................: A.29.00
EMS Version.....................: A.03.20

Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_core_hw.htm#32
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-
FRU Physical Location: 0xffffffffffffff00
FRU Source = 0 (unknown, no source stated)
Source Detail = 0 (unknown, no source stated)
Christopher McCray_1
Honored Contributor

Re: GSP Correct logout sequence

Hello again,

Yes, this is the exact error I have had in the past.

Run the stty command:

# stty ++resetGSP
The output should read that the GSP was successfully reset. Do what the message says and ensure the firmware version meets the requirments or better in the message. In my case, after running the above command, I won't see it again (or at least for a long time)

Regards,
Chris
It wasn't me!!!!
Joan Blais
Frequent Advisor

Re: GSP Correct logout sequence

I've run the "stty" comands several times. I've also reset the GSP by using the "XD" R command. This will clear it until one of my admins logs in. Is there a reason why this keeps happening?
Victor_5
Trusted Contributor

Re: GSP Correct logout sequence

Check with HP, maybe you need install patch for EMS or upgrade your firmware.

Joan Blais
Frequent Advisor

Re: GSP Correct logout sequence

Thanks, I'll give HP a call.

Re: GSP Correct logout sequence

These GSP messages are mainly linked to GSP firmware. A reset of the GSP will fix the problem temporarily. The GSP can be reset while the system is running with no impact on the system up or down. A firmware upgrade to the latest version should fix this problem. I believe it is version A.11 but dont qoute me on that. Your HP service rep can update it for you or it is also customer updatable.
Jeff Schussele
Honored Contributor

Re: GSP Correct logout sequence

Guys - HP guys in particular,

This where HP EMS / GSP interoperability - or more truly lack of knowledge thereof - really irks me.
Tell me why can't EMS just inquire what the heck is there firmware-wise & flat-out state - UPGRADE!
Is this TRULY something that CAN'T be interrogated while the system is up & if it can WHY doesn't EMS do so?
And more basically why would that level of EMS even swinstall if requirements GSP-wise weren't met?!?!
I'm no engineer here - but this doesn't appear like rocket science to this lowly ole SA.
I've had CEs replace SPs in the past only to finally "discover" these lovely incompatibities. Nothing brightens my day MORE than explaining "unnecessary" downtime to mgmnt ;~)

Rgds,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
Joan Blais
Frequent Advisor

Re: GSP Correct logout sequence

Amen, I feel your pain. The firmware was upgraded back in Nov, 01. It must be time to upgrade again.
hpuxrox
Respected Contributor

Re: GSP Correct logout sequence

Try reseting the GSP. The switch is located on the back of the N-Class. Its a small pin hole you can use a paperclip or something to reset.
Joan Blais
Frequent Advisor

Re: GSP Correct logout sequence