The Guardian Service Processor (GSP) is a new console subsystem
on N4000, all L-Class models, the new A-Class machines (the A400
and A500), Superdome systems, and all new servers introduced starting
with the N-Class. The GSP console driver, the software component
of the GSP, provides the following features on HP-UX:
- Local console
port
provides system console while HP-UX is running.
- Remote session port
establishes an HP-UX login session on the remote
console.
- Local session port
establishes an HP-UX login session on the local
console.
- Internal console port
supports firmware upgrade and diagnostics on GSP.
- UPS port
establishes a communication channel between the
UPS daemon and UPS.
SAM provides configuration support (that is, modem and UPS connections)
over the GSP serial ports. The insf(1M) and mksf(1M) commands
create device files for the GSP serial ports.
The following commands have been changed to provide additional support
for the GSP console:
ttytype can determine the ID of the terminal connected to the
local console port.
stty supports status query and reset function of the GSP.
The GSP console driver is based on the existing built-in serial
port driver (asio0). Every serial port on the GSP adheres strictly to the termio feature set; these features are described in the termio(7) and modem(7) manpages.
GSP Logging Capabilities |
 |
The introduction of GSP to the above platforms dramatically
changes the way chassis operations and diagnostic evaluations are
performed on a running system.
The new subsystem requires HP-UX to provide more information
than was provided on previous platforms. HP-UX will continue to
output the same chassis-codes and forward-progress indicators that
have been provided in previous releases. On the above and subsequent
systems, however, the codes are displayed on the Virtual Front Panel
(VFP) of the system. Most of the existing four-hex digit chassis
codes are enclosed in GSP-specific encoding.
The GSP subsystem interprets various forms of logging information
from both firmware and software.
Several new software events will be logged, including:
"Boot Complete" indicator
Periodic heartbeat, with:
timeout value (a time-limit within
which another event must be logged before the system is declared "dead")
activity level indicating system usage
In addition to existing four-hex digit chassis codes, the
following information is sent with each event:
Printable version
