GSP Error

[Sritharan]

Hi,
Check the attachment

And the problem occured again yesterday.

What can I do to avoid this problem to occured again?

Thanks for your help

[S.K. Chan]

If you look at the EMS message carefully, it pretty much tells you what to do. Generally the error is saying your "GSP (Guardian Service Processor) is having problem. First thing you need to do is see if you can get into GSP. Do this ..

On your system console or remote console, enter CTRL-B, that will bring you to a login and password prompt for GSP, if you don't have it set just press enter for both. At this point you should be able to see the GSP prompt which looks like this ..

GSP>

If that does not work, try resetting GSP as suggested in the message.

# stty +resetGSP < /dev/GSPdiag1

and do the CTRL-B again, if this still does not work it's time to call HP for possible hardware replacement (system board, as mentioned in the message).

[Sritharan]

Hi,
Thanks Chan

I had done that but the same problem have occured twice on the same server.

I did the same solution,so my concern now is a permanent solution for this problem. Do you I have to call HP represetative to check the board ???

Thanks again

[S.K. Chan]

Yes I would do that if I were you.

[T G Manikandan]

Hello,
check your GSP firmware version.A firmware upgrade should do fine.It is good to call the HP person but here is some more information to you.

Just check this link for the same problem as yours

http://bizforums.itrc.hp.com/cm/QuestionAnswer/1,,0x2f52d20fd34bd61190010090279cd0f9,00.html

I just browsed to get this info

Based on HP-UX patch PHKL_22469:
(SR: 8606136107 CR: JAGad05237)
Due to reporting of some errors such as GSP not responding,
the OS used to continually log such events without making
any distinction as to whether this is a continuation of the
older problem or is a new instance of the same. Due to
this, syslog used to be flooded by such messages leading to
some messages not getting logged due to overflowing of the
log. As a result, there was a possibility of critical
messages not getting logged. This problem not only
manifests itself in the GSP not responding but also in other
events like overtemp reporting, power monitor fail, etc.

Resolution:
Since this is a problem occuring in multiple events, there
was a need for a generic solution for the same. The
solution which has been implemented incorporates both time
based and counter based resetting of counters used to keep
track of the occurences of each individual event. The time
based resetting mechanism resets the counter if the previous
instance of the error logged is greater than 5 minutes old.
The counter based resetting mechanism resets the counter
once per every 32768 occurrences (event is logged at
0,32768, 65536,...) of that event.




http://bizforums.itrc.hp.com/cm/QuestionAnswer/1,,0xa60ccb60e503d6118ff40090279cd0f9,00.html

Thanks

[Christopher Meenan]

The Problem with your GSP can be fixed by a firmware upgrade to the GSP itself. I believe that the current level that addresses that problem is A.01.10. The problem is regarding the communication bus between the GSP and the Host. On older firmware rev's, when the bus gets busy it reports as failing to communicate and a possible error. As you can tell when you test the gsp yourself, there is no REAL error. More current versions of EMS actually tell you to do this exact thing!

You can have your HP support person upgrade the firmware or do it yourself. It is very easy and the problems will go away forever!