GSP/MP Login Credential Unknown

[Lemon123]

Hi,

I am supporting remote Customers which is far away from my office. My HPUX system is hung and I need to reset the server via the GSP/MP. However, I have no information for that after the previous vendor passed to us. How can I obtain the GSP ID and Password without assign HP CE to go onsite or press the button?

There are many servers having the same issue which has GSP/MP in the system but no login information.

Thank You

[Jeeshan]

other than your mentioned way, there is no way to obtain MP information.

you may need to go to on site and connect through serial cable or you may reset the MP.

[Torsten.]

A password in general would not make so much sense if there are several ways to work around ... you need physical access to the server (and console) to press the button and reset the values.

[Dennis Handly]

Wouldn't resetting the GSP work?
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1245494
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1224794
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1217917
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1198839
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1168824
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1158493

[Torsten.]

Note, the command

#stty +resetGSP < /dev/GSPdiag1

does only work on certain models, not all.

[Bill Hassell · Accepted solution]

You have a new project: Every server must be setup for GSP/MP access. The previous vendor was remiss in not setting (or documenting) the GSP/MP login. Without this capability, remote system administration is impossible when hangs or hardware issues are encountered. And in the future, no servers are allowed to be installed without a checklist that includes setting up (and testing) access to the GSP/MP ports. I would strongly recommend that there be a completely separate subnet created for GSP/MP ports (as well as other devices such as SANs, network appliances, tape changers, etc) at each remote site. This subnet is kept separate because the maintenance ports on all machines are inherently unsecure. If security is ever breached on these ports, the hacker can turn off the power or crash and reboot these boxes at will.