N-Class defective GSP cause for worry?

[Ralph Grothe]

Hello,

we have an N4000 that uniquely wasn't bought, nor leased from HP, but from some hardware broker.
Thus we haven't got any support by HP for this machine.
Albeit some more or less vital application is running on this box.
For almost one year now the OS (or the EMS dm_core_hw monitor) cannot communicate with the GSP.
All my attempts so far to reset the GSP (either physically by pressing the reset button, or by excercising the reset from the XD submenu in GSP, nor by the +resetGSP option to stty) haven't changed anything.
The red LED on the GSP board stays lit.
However, thus far the operation of OS and applications don't seem to be impaired by this, and there haven't been any panics neither.
But it still concerns me if there is any action (e.g. replacing the GSP board) required, or if these symptoms can safely be ignored.
Meanwhile I even deactivated the EMS monitoring of the GSP.

Rgds.
Ralph

[G. Vrijhoeven]

Hi Ralph,

I found some related issues that could provide more info:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=28357

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=57156

Regards,

Gideon

[Cheryl Griffin]

I would check the N4000 firmware, gsp and STM/EMS levels. Is everything up to date?

GSP Version
1. telnet into the GSP
2. logon to the GSP
3. Type ecf
4. Type b
5. Type he

GSP Rev A6696B PF_CCANGSPB0220
or
GSP Rev A6696A PF_CPREGSPA0112


PDC Firmware:
# cstm
map
sel dev
info
il

s700_800 11.11 N4000/rp7400 43.43 PDC Firmware Patch PHSS_30724


STM/EMS version:
# swlist -l product |egrep -e "diag|STM|EMS|Sup-Tool" |more

http://docs.hp.com/hpux/onlinedocs/diag/stm/stm_upd.htm#table