FES Prelude Training
Guardian Service Processor
"Guardiaii" Service Processor Overview
* Overview of Capabilities
* Block Diagram - how does it work?
* Review New Commands
* GSP and Chassis Codes
* Error Conditions and Troubleshooting.
Overview of GSP Capabilities
•Similarity to AP:
- Provides connection point for local and remote console access
- Console Mirroring between Remote and Local Console
- Ability to do RESET and TOC
- Monitor Boot Progress (enhanced)
Overview of GSP Capabilities
• Addition or enhancement to AP:
- Access via LAN
- Provides remote system management features (new)
- Maintains logging information (expanded)
- System Alert Notification (formerly VFP)
- User and Administrator Security (new)
- Internal Port (new)
- Firmware Update over network
- Alphanumeric Paging (Phase V)
- Web Access (coming Phase V) (like Prospero)
- Web Access (first release) via Prospero (with VT100 firmware)
GSP via AP
GSP
Modem Access
Yes
Lan Access
Yes
Web Access
Yes
Console Mirror
Yes
Access Control
Yes
Front Panel Display Yes
System Reset
Yes
Power Control
Yes
HardWare Log
Yes
Multiple Account
Yes
AP
Yes
No
No
Yes
Yes
Yes
Yes
No
No
No
SP Console Access
•Local Console(always active)
•Mirroring at Local/Remote console à la access port.
•Mirrors BCH/OS/almost anything from console.
•Remote Console(mirror(s) of local console)
-over RS-232 modem
-over LAN [new]
-over modem PPP [new] (Phase V)
SP System Remote Management
Features
* System Reset
* Power Management and Control
- Power up and Down
- Display Status of fans, ambient temperature, etc.
- Display Installed / responsive processors (maybe not)
* Automatic Restart (TC) based on specified alert levels.
* Digital Paging based on specified events (Phase V)
SP Logging Features
* Console Logs - Contains Console Activity
* Event Logs - Contains Chassis Codes
SP Consloe Logs
• ASCH log of everything that transpired on the
console including GSP handler, boot console
handler (BCH) messages, and 0/S generated
messages. (20KB - about 20 pages)
SP Event Logs - Contains
Chassis Codes
- Incoming log-(contains the most events)
- Activity Logs (One is always active - subset of
incoming log)
- Current
- Current Boot
- Prior Boot
- Error Log (contains the fewest events)
SP Incoming log
•Contains almost all chassis codes.
• Circular Queue
•Not that useful for troubleshooting.
•Mostly a data structure for the benefit of GSP
frimware
SP Activity logs
•Should be always logging to one of these three logs.
(after boot_start)
•Does not contain Alert level 0 log entries.
• There are 3 Separate Activity Logs
-Current Activity Log-circular buffer (200 events)
-Current and prior Boot logs-linear buffers(800 events)
•Visible via the SL command with various filtering
options
SP Boot logs
•Logs all chassis codes with alert level>0.
•Starts with “Boot Start” Chassis Code from PDC
•Ends with “Boot Complete” Chassis Code from O/S
•Entire boot log gets sent to O/S at Boot Complete
•Two Boot Logs-one for current boot,one for prior boot.
•Can read either Boot Log from GSP Handler
SLcommand.
SP Current Activity log
•Contains ALL recent Events(chassis codes)
•Circular buffer with 200 Events
•Visible via the SL command with various filtering
options
•Most useful to look at MOST RECENT activity
SP Error log
•Contains all chassis codes with Cricular Queue
•Contains all chassis codes with>=2 severity
•Visible via the SL command with various filtering
options
•Use to look for errors.
Error Log Example (SL command)
Log Entry # 5:
SYSTEM NAME: fespresas
DATE: 05/05/1999 TIME: 10:10:00
ALERT LEVEL: 6 = Boot possible, pending failure - action required
SOURCE: 6 = platform
SOURCE DETAIL: 3 cabinet fan SOURCE ID: 0
PROBLEM DETAIL: 4 fan failure
CALLER ACTIVITY: 4 monitor STATUS: F
CALLER SUBACTIVITY: 05 = fan
REPORTING ENTITY TYPE: 2 = power monitor REPORTING ENTITY ID: 00
0x002008646300405F 00000000 00000000 type 0 = Data Field Unused
0x582008646300405F 00006304 050A0A00 type 11 = Timestamp 05/05/1999 10:10:00
Type CR for previous entry, + CR for next entry, Q CR to escape.
SP Event Logs Summary
Log T ype
Incoming Log
Current Boot
Activity Log
Previous Boot
Activity Log
Cruuent Activity
Log
Error Log
Alert
Contains
T ype of Log Leverl of
Events
Every Log
Circular
All
Entry received
(0-15)
by SAS
Chassis Codes
Linear
>0
since start of
1-15
current boot
Chassis Codes
Linear
>0
prior boot
1-15
Circular
>0
Recent Events
1-15
Circular
2-15
Recent Events
Size
600 Log
Entries
800 Log
Entries
800 Log
Entries
200 Log
Entries
200 Log
Entries
Alert Notification(Virtual Front
Panel)(new)
•Two modes
- LIVE mode (VFP command)
- ALERT MODE with configurable 'alert threshold' (AC
command)
•What all does it show?
Virtual Front Panel (live)
GSP> vfp
VFP
This command activates the immediate display of the Virtual Front Panel.
Please, confirm : (Y/ [NI ) y
y
GSP Host Name:
fespresas
GSP>
* * * * * * * * * * * VIRTUAL FRONT PANEL * * * * * * * * * * * * *
VFP command executing...
Q/q: to quit Virtual Front Panel Display
->Choice:
***************************************
processor
display-activity update 10F1
processor
display-activity update I0F0
VFP Example
processor
display_activity() update 10F1
processor
display_activity() update 10F0
* * * * * * * * * * * * * * * LIVE VFP : SYSTEM ALERT* * * * * * * * * * * * *
SYSTEM NAME: fespresas
DATE:05/05/1999 TIME: 10:10:00
ALERT LEVEL: 6= Boot possible, pending failure - action required
REASON FOR ALERT
SOURCE : 6 = platform
SOURCE DETAIL: 3 = cabinet fan SOURCE ID: 0
FROBLEM DETAIL: 4 = fan failure
LEDs : RUN
FLASH
ATTENTION
OFF
OFF
FAULT
ON
REMOTE
ON
0x002008646300405F 00000000 00000000
type. 0 = Data Field Unused
0x5820086463004057 00006304 050A0A00 type. 11 =Timestamp 05/05/1999 10:10:00
A/a: ack read of this entry - Q/q: quit Virtual Front Panel Display
Anything else display the log entry
>Choice: Timeout!
*********************************
processor
display-activity() update 10F0
processor
display-activity() update 10F1
POWER
-
SP Administration/Security (new)
•AP had a single password.
•SP allows configuration of 2 types of logons
- Administrators
- Operators
•Administrator can access all commands - add/create users
•Operator can access a subset of commands
- can reboot system
- cannot change SP configuration
• 0"Internal Port' always has Administrator Capability
Internal Port(new)
•Purpose: Allows a root user to access SP functionality, i.e. in
case the SP password is forgotten. (back door)
•Separate port from the system to the GSP Handler.
•Always has ADMINISTRATOR capability - no password!
- Access must be protected by HP-UX operating system.
•Use the HP-UX cu command to access the internal port. (#cu
-1 /dev/tty 1p0) (maybe /dev/tty(something else)p0 on Half Dome)
Firmware Update(over lAN)
•New command “XU” does this
•Must be done from LOCAL or INTERNAL port
- Disconnects LAN connected clients
-Can be used with Prospero(Web Console)
•Use FTP protocol
•Requires ip address of FTP Host,and the directory to be
accessed.
Firmware Update Example
•GSP>XU
XU
This command activates the upgrade mode.All connections will be closed,the
network will be stopped , the session will be aborted and the modem connection
will be dropped.
Please,confirm your intention to activate the upgrade mode(Y/[N]) : y
Enter source system IP address :15.8.149.21
Enter file path :/sasDepot/current
Do you wish to use the default login : anonymous /[email protected] (Y/[N]) : y
GSP firmware upgrade in progress
GSP firmware upgrade complete - GSP will now reset
Firmware Update (ftp process)
•A look at the current FTP site.
Ftp> cd sasDepot
250 CWD command successful
ftp> cd current
250 CWD command successful.
ftp>dir
200 PORT command successful.’150 Opening ASCII mode data connection for /usr/bin/ls.
Total 20320
-rw-r----- 1 ftp
other
1265480 Mar 25 16:45 APPLICATION.ROM
-rw-r----- 1 ftp
other
131072 Mar 25 16:45 BOOTSTRP.ROM
-rw-r----- 1 ftp
other
22598 Mar 25 16:45 readme
-rw-r----- 1 ftp
other
128 Mar 25 16:45 upgrade.cnf
-rw-r----- 1 ftp
other
5015981Mar 25 16:45 vxWords_rom
-rw-r----- 1 ftp
other
3916905Mar 25 16:45 vxWorks_rom.hex
GSP Command Set
GSP>
HE
Hardware Revision 7 Revision X.17.12 Apr 28 1999,18:06:22
AC : Alert Display Configuration
PC : Remote Power Control
AR : Config.Automatic System Restart PS : Power Management Module Status
CA : Configure serial port parameters
RP : Reset password configuration
CE : Log repair info in history buffer
RS : System reset through RST signal
CL : Display console history
SDM: Set Display Mode (hex or text)
CO : Return to Console Mode
SE : Activate a system session
DC : Default con figuration
SL : Display SPU status logs
DI : Disconnect remote or LAN console SO : Security options $ access control
DR : Disable remote or LAN console
SS : System’s processor status
ER : Enable remote or LAN console
TC : System reset through INIT signal
HE : Display the available commands
TE : Sends a message to other terminals
IT : Modify GSP inactivity timeouts
VEP: Activates Alert Log Display
LC : Configure LAN console status
WHO: Display list of GSP connected users
LS : Display LAN console status
XD : GSP Diagnostics and Reset
MR : Modem Reset
XU : Upgrade the GSP Fremware
MS : Modem Status
GSP Host Name: fespresas
GSP>
HP-UX Device Files(1)
•Console Path: /dev/console (/dev/GSPdiag())
- /dev/console baud rate is mot applicable.
•UPS Path: - /dev/tty0p1
- configure with SAM (straight through) up to 9600 Baud
•Local Console Session Path /dev/ttyd1p1
-configure with SAM
-must be BELL protocol-max speed 38400 baud
•Remote Console Session Path /dev/ttyd0p2
-configure with SAM
-if remote disabled - direct device file,CCITT,or BELL
-if remote enabled - CCITT or BELL,but must match configuration in CA
command - max 38400 baud
HP-UX Device Files(2)
• Internal Port: /dev/tty1p0 (/dev/GSPdiag1)
• Supports both direct device file and BELL modem device files.
• Cannot be configured with SAM.BAUD rate is not applicable,since
this only applies to GETTY driver.Cu and kermit can be used to access
this page.(see cu configuration on next page)
• If you need to add the device file for the Internal Port ,use
something like:#mknod tty1p0 c1 0x010000
Accessing Internal Port via cu
•/usr/lib/uucp/Systems needs this entry:
gspiport Any;5 gspiport,f 9600 - “ ” \r\d\r\d\r ogin:BREAK-ogin: uucp asswrd: uucp-BREAK-ogin:uucp
asswrd:uucp
•/usr/lib/uucp/Devices needs this entry:
gspiport tty1p0 - 9600 direct
•cu -1/dev/tty1p0
•No SAM support for this
Timestamps
• GSP adds timestamps from its own internal clock to any log
entries that do not already contain timestamps.
• GSP clock is not battery backed up.
• GSP clock can lose 8 minutes per day.
• GSP clock is synced from system clock by PDC at boot(GMT)
• Synced by HP-UX at initial boot (GMT)
• After IPR 9906,diagmond will update GSP clock once an hour
(Local time in 9906-GMT time in 9909)
GSP and it’s internal Clock
• The GSP’s Internal Clock reverts to Jan 1,1970
When GSP is reset.This happens when:
-Housekeeping Power is first applied
-GSP Firmware Update is done
-XD command (Reset option)
-GSP RESET button on the rear of the Core I/O.
Problems Accessing Internal Port
• Check/usr/lib/uucp/Systems for an entry as follows:
gspiport Any;5 gspiport,f 9600 - “ ” \r\d\r\d\r ogin:BREAK-ogin: uucp asswrd: uucp-BREAK-ogin:uucp
asswrd:uucp
•Check/usr/lib/uucp/Devices for an entry as follows:
gspiport tty1p0 - 9600 direct
•Make sure that/dev/tty1p0 exists…if not ,do a mknod
for the device.
•NO SAM support for Internal Port.
Looking at Error Logs
• SL Command Example (1 of 3)
SL
Which buffer are you interested in:
Incoming,Activity,Error,Current boot or Last boot ?(I/A/E/C/L) e
e
Do you want to set up filter options on this buffer ? (Y/[N]) n
n
Type + CR and CR to go up (back in time),
Type - CR and CR to go down (forward in time),
Type Q CR to escape.
Looking at Error Logs
• SL Command Example (2 of 3)
Log Entry # 0 :
SYSTEM NAME: fespresas
DATE: 05/05/1999 TIME: 17:17:21
ALERT LEVEL: 15 = Fatal hardware or configuration problem prevents
SOURCE: 8= I/O
SOURCE DETAIL: 6= disk SOURCE ID: 0
PROBLEM DETAIL: 3= functional failure
CALLER ACTIVITY: 1= test
STATUS: 0
CALLER SUBACTIVITY: 48= implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 03
0x000038F386001480 00000000 00000000 type 0 = Data Field Unused
0x580038F386001480 00006304 05111115 type 11 = Timestamp 05/05/1999 17:17:21
Type CR for next entry, Q CR to escape.
Looking at Error Logs
• SL Command Example (3 of 3)
Log Entry # 5:
SYSTEM NAME: fespresas
DATE: 05/05/1999 TIME: 10:10:00
ALERT LEVEL: 6 = Boot possible, pending failure - action required
SOURCE: 6 = platform
SOURCE DETAIL: 3 cabinet fan SOURCE ID: 0
PROBLEM DETAIL: 4 fan failure
CALLER ACTIVITY: 4 monitor STATUS: F
CALLER SUBACTIVITY: 05 = fan
REPORTING ENTITY TYPE: 2 = power monitor REPORTING ENTITY ID: 00
0x002008646300405F 00000000 00000000 type 0 = Data Field Unused
0x582008646300405F 00006304 050A0A00 type 11 = Timestamp 05/05/1999 10:10:00
Type CR fornext entry, - CR for previous entry, Q CR to escape.