HP-UX 11i June 2002 Release Notes

Workstation/Server Specific Information

Service Processor (GSP or MP)

Chapter 5

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 are now logged, including:

•“Boot Complete” indicator

• Timestamp

• 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

• Minimal LED control

In addition to existing four-hex digit chassis codes, the following information is sent with

each event:

• Alert level

• CPU number

NOTE The GSP will not store codes of alert level 0 after PDC's “boot complete” code. All

incoming codes will display on the VFP, but level 0's will not be stored for later retrieval.

This is so the log won't fill up with heartbeat entries.

PDC_CHASSIS, the old firmware call for old-style, four-hex digit chassis codes, always

produces codes of alert level 0. In order to create new-style chassis codes, the PAT_ call

for CHASSIS must be used.