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

Guardian Service Processor

Go to solution
Jim Roland
Occasional Visitor

Guardian Service Processor

I have an HP 9000 L1000 and the console terminal is running CDE. How do I get to the GSP?
Steve Steel
Honored Contributor

Re: Guardian Service Processor


telnet should work

Steve Steel
If you want truly to understand something, try to change it. (Kurt Lewin)
G. Vrijhoeven
Honored Contributor

Re: Guardian Service Processor

Hi Jim,

If you have console access you should be able to use the combination to access the gsp. You can configure it to listen on an ip-address.

You could check this link for more info:



Joshua Scott
Honored Contributor

Re: Guardian Service Processor

if you have a regular (700/96 or similar) terminal, or a pc/laptop with a serial port, just plug into the serial port labeled 'console' on the 3 port cable.

if you use a PC, make sure the terminal emulation software (hyperterm or teraterm, etc.) is set to:
9600 baud
8 data bits
1 stop bit
no parity
VT100 emulation

the LC command in the GSP should set up the network connection, then all you should have to do is hook the lan console port to you network, and telnet to the IP address.

What are the chances...
Honored Contributor

Re: Guardian Service Processor

There is a way to access the GSP through the OS, although it is not supported by HP due to security concerns.

On the system, the GSP internal port should be /dev/tty1p0.

# cd /dev
# mknod tty1p0 c 1 0x010000

The internal port can be accessed via terminal emulators such as cu. To use cu, you need to edit the following:

1) Enter the following in /usr/lib/uucp/Systems (The spelling looks unusual, but it needs to be exactly as shown):
gspiport Any;5 gspiport,f900 - ''''\r\d\r\d\r ogin:-BREAK-ogin: uucp asswrd: uucp-BREAK-ogin: uucp asswrd: uucp

2) Now edit /usr/lib/uucp/Devices to include the following:
gspiport tty1p0 - 9600 direct

Now access the GSP with the â cuâ command:
# cu â l /dev/tty1p0

To terminate the cu session, use "~." (tilde dot return).

CAUTION Securing the /dev/tty1p0 device file with root capabilities will not prevent non-root users from accessing the GSP internal port. This is due to the fact that cu and kermit carry root access and run with the sticky bit enabled. To secure the internal port from unauthorized use, be sure to remove the /dev/tty1p0 file after using
Was this helpful? Like this post by giving me a thumbs up below!