The Guardian Service Processor (GSP) is an independent support processor for the system console. GSP provides services that facilitate the management of the host system. Its major features are:

• Always-on capability: The GSP is alive as long as the power cord is plugged in.
• User/password access control: Supports operator and administrator users
• Multiple access methods:

  Local Port

  use terminal or laptop computer for direct connect

  Remote/modem Port

  use dedicated modem RS-232 port and external modem

  LAN

  use telnet or web to access GSP LAN

• Mirrored console: the system console output stream is reflected to all of the connected console users, and any user can provide input.
• Display and/or logging of: The system console, System event logs (chassis codes), Virtual Front Panel (VFP), and system power and configuration status
• An independent, non-mirrored session: Available from local and modem ports for GSP connection (CSP) or OS login (SE).
• Power control, system reset, and TOC capabilities.

THE MIRRORED GSP SESSION:

Administrator-Only Commands:

RECOMMENDATION: Use the session for ASCII screen-oriented applications (SAM) or file transfer programs (ftp) from the local or modem ports. To use these applications from the LAN, telnet directly to the system for a private login.

The following severity (or alert) levels are defined:

0. No failure	6. Pending failure	11. (Reserved)
1. Information only	7. (Reserved)	12. Software Failure
2. Non-urgent attention req.	8. Performance Impaired	13. System hang
3. System blocked	9. (Reserved)	14. Power failure
4. Unexpected configuration	10. Loss of Functionality	15. Fatal HW failure
5. Environmental problem

The remote/modem port is configured via the CA command. The ER command enables/disables the port and gives the modem control over to the GSP or the OS. See the help on those commands for more details.

The GSP mirrors the system console to the GSP local, remote/modem, and LAN ports. One console output stream is reflected to all of the connected console users. If several different terminal types are used simultaneously by the users, some users may see strange results.

HP-UX example:
Applications which care about the terminal type (install, SAM, vi, etc.) running on HP-UX use three methods to determine the terminal type:

1. The application takes the terminal information from the OS. This value is set in the CA command and takes effect for all GSP ports.
2. The $TERM shell environment variable
3. The application directly queries the terminal (in this case, the write enabled terminal will establish the terminal type.)

MPE/iX Example:
MPE/iX only supports HPTERM terminal type. If the terminal type is set to VT100 there may be unpredictable results when some applications are run.

Applications which care about terminal type are of three categories:

1. Block mode applications using VPlus such as NMMGR.
2. Other screen oriented applications such as HPEdit.
3. Applications running under the MPE/iX Posix environment.

The application categories #1 and #2 generally get the terminal type by querying the terminal. The MPE/iX Posix applications will use the $TERM shell variable.

1. In the SO command, change individual users
2. In the DC command, choose \"Reset Security configuration\"
3. If all passwords have been forgotten, they can be reset by hitting the reset button on the back panel of the GSP. After the GSP reboots, the local console terminal will display a message for five seconds. Responding to this message in time will allow a local user to reset the passwords.

Note that the user information as well as the passwords are erased in methods 2 & 3.

Alerts with level 2 or greater will go into the Error Log. If an alert is acknowledged in the ALERT DISPLAY, that alert will not light the Attention LED. Any unacknowledged alert in the Error Log will light the Attention LED. To turn off the LED, read the Error Log. Since level 2 alerts can never activate the ALERT DISPLAY, they must always be acknowledged by reading the Error Log.

The setting in AC has no affect on the automatic early boot VFP. During boot, level 3 alerts and greater will always be displayed.

The default is level 13. Setting ASR for alert levels below 10 is strongly discouraged.

VT100 and HPTERM: Verify that the GSP setting in the CA command is correct and all mirrored consoles are of the same terminal type for proper operation.

To run an ASCII screen-oriented application (SAM) or a file transfer program (ftp), the console is not the recommended connection. On the local or remote/modem ports, it is recommended that the SE command be used to start a private system session, so that console output and mirroring do not disrupt the application. On the LAN, connecting directly via telnet or web to the system over the system LAN is recommended.

Other mirrored GSP users are placed in console mode when this command is executed. The CSP user returns to the mirrored GSP session after ending the CSP session.

More detailed help is not available for this command.

The user may reset all or a subset of the following parameters: IP configuration, modem configuration, paging configuration, command interface configuration, disable remote access, security configuration, session configuration. For example: setting the security configuration to default will erase all users and passwords.

For Display Logs, use the SL (Show Logs) command.

For Disable LAN, use the EL (Enable/disable LAN) command.

Please use:

ER : Enable/disable Remote console serial port modem access

The DR command has been replaced by the ER command. The ER command offers a selection of configurations for the remote console serial port modem, including disabling the port.

1. LOCKED-OUT -
   Lock out all dial-in access

2. GSP -
   Exclusive GSP access

3. SESSION -
   Modem controlled by OS; both dial-in and dial-out

Dial-in to the modem results in:

• Access denied under the mode: LOCKED-OUT
• A GSP login under the mode: GSP
• A session with the OS under the mode: SESSION (The OS must be properly configured to use the modem.)

Dial-out (paging) by the OS is allowed under the mode: SESSION. (The OS must be properly configured to use the modem.)

Paging by the GSP can be done under all modes. (Make sure that paging is enabled in the PG command.) GSP pages will wait until the modem is idle.

Translation from older versions of the GSP:

• Enable Remote = GSP
• Disable Remote = SESSION
• LOCKED-OUT was not available

To enable/disable LAN access, use the EL command.

GSP INACTIVITY TIMEOUT: up to (24x60) minutes - typically 60 minutes
This timeout prevents a user from inadvertently keeping the GSP locked in a GSP Command Interface mode preventing other users from looking at the console output. The GSP Command Interface inactivity timeout may not be deactivated.

The GSP Host Name set in this command is displayed at the GSP command interface prompt. Typically the DNS name for the LAN IP is entered. This field can be programmed to any useful name or phrase. For clarity, it is useful to enter: "GSPNAME-on-SYSTEM" as the GSP Host name, so both names show up in the prompt (limit 19 chars, no spaces allowed.) The web access port number is also set by this command.

Please use:

ER : Enable/disable Remote console serial port modem access

The legacy commands LR and UR have been replaced by the ER command. The ER command offers a selection of configurations for the remote console serial port modem, including configurations for dialing in and out.

More detailed help is not available for this command.

This command allows the user to switch the system power ON or OFF, or Power Cycle the machine. The user can have the action take place immediately, or after a specified delay.

Note this is roughly equivalent to turning the system power off at the front panel switch- there is no signal sent to the OS to bring the software down before power is turned off. To turn the system off properly, the operator must ensure that the OS is in the proper shutdown state before issuing this command, by using the proper OS commands.

If the modem is in use by either a dial-in connection to the GSP, a dial-in session to the OS, or a dial-out by the OS, all pages will queue up and wait until the modem is idle. Also, the modem presence in the CA command must be configured for \"always connected\" for paging to be possible.

More detailed help is not available for this command.

Please use:

This command causes the system to be reset through the RST signal.

Execution of this command irrecoverably halts all system processing and I/O activity and restarts the computer system. The effect of this command is very similar to cycling the system power- the OS is not notified, no dump is taken on the way down, etc.

This command is used to set the default display mode for chassis codes. It will affect the Virtual Front Panel (plus alerts), and the log viewer.

The GSP regularly checks the activity of the session and will close the connection with the system and return the port to mirroring if the timeout period has elapsed. The timeout period is set in the IT command.

On HP-UX, the SE command will work on the local and remote ports.

DEVICE FILES: The CA command settings must agree with the OS device settings for the session UARTS. HP-UX device files are:

• Local Session: /dev/ttyd0p4
• Remote Session: /dev/ttyd0p2

On MPE/iX, the SE command will only work on the connection to the remote/modem port. The CA command settings must agree with the parameters configured on the DTS User Port screen in NMMGR. An ldev must also be correctly configured in Sysgen for the I/O path to the session port.

The MPE/iX I/O path to the session port is 0/0/4/1.1

1. Incoming -
   All chassis codes as they come in except for activity updates codes from the OS.

2. Activity -
   All chassis codes of level 1 or greater

3. Error -
   All chassis codes of level 2 or greater

4. Current Boot -
   All chassis codes between "start of boot" and "boot complete"

5. Last Boot -
   The chassis codes from the previous boot

DIAL-BACK: If configured, when the user accesses the GSP via the modem port, the GSP will hang up and dial the user back. WThis will not work if "Modem Presence" is set to "not always connected" in the CA command.

MODE: Single/Multiple. If the mode is Single, the State will be changed to disabled after the first login.

USER'S STATE: Enabled/Disabled. A disabled user's login will not be accepted.

The GSP learns the system configuration through the chassis codes it receives from the system. Therefore, there will likely be a delay between any processor configuration change and what is displayed by this command. A more reliable way to get the processor configuration information is at the BCH prompt.

This command causes the system to be reset through the INIT (or TOC) signal.

Execution of this command irrecoverably halts all system processing and I/O activity and restarts the computer system. It is different from the RS command in that the processors are signaled to dump state on the way down.

Please use:

ER : Enable/disable Remote console serial port modem access

The legacy commands LR and UR have been replaced by the ER command. The ER command offers a selection of configurations for the remote console serial port modem, including configurations for dialing in and out.

There are two ways that the live display of chassis codes can be started:

1. LIVE MODE -
   Invoked from the VFP command at the GSP prompt. To exit, you must type Q to quit to the console.

2. EARLY BOOT MODE -
   When the boot sequence for the system begins, the live VFP is invoked automatically. When boot finishes, users are automatically switched to console mode.

More detailed help is not available for this command.

There is always one user listed for the local serial port. This is a default user name ("local user") if the local console client user didn't originate the GSP Command Interface session. If the local console operator typed CTRL-B, then the login name that the local operator typed is displayed instead.

• Parameters checksum
• I2C bus tests
• LAN connectivity test using "ping"
• Modem self-tests

Modem connections will be dropped. The XU command can be run from the LAN, WEB, or local ports. If the upgrade is successful, the GSP will reboot and come up using the new firmware.

If the upgrade fails, the GSP will return to the prompt with instructions on what went wrong, and what to do next.

Upgrading the GSP software and rebooting the GSP can be safely performed without affecting the operation of the server.

The version of GSP firmware is displayed at the top of the main help menu.