HP L1000 - 9000 - 0 MB RAM, User Manual

Page: 109 / 231

Chapter 6
Troubleshooting
Chassis Code to FRU Decode
95
Interpreting System Alerts
Do one of the following:
1. No response: the alert will time out and the system will continue operating.
2. A - Responding with the letter A will inform the Service Processor that you have seen the entry. The
system will continue to operate.
3. X - Responding with the letter X will inform the Service Processor to disable all future alert messages.
This can be re-enabled with a Service Processor command.
Sample System Alert
*************************SYSTEM ALERT***************************************
ALERT LEVEL: 6=Boot possible, pending failure or environmental problem - action required
PROBLEM DETAIL: 4=fan failure - SOURCE ID: 04
SYSTEM NAME: fesrhapgsp
MODEL NAME: MODEL STRING: S/N:
SPU POWER: ON
ACTIVITY/COMPLETION LEVEL: 0%
SYSTEM BOOT IS PENDING
LEDs: RUN ATTENTION FAULT REMOTE
FLASH OFF OFF ON
CALLER ACTIVITY: 4=monitor - CALLER SUBACTIVITY: 05=fan
REPORTING ENTITY TYPE: 2=power monitor - REPORTING ENTITY ID: 00
SOURCE: 6=platform - SOURCE DETAIL: 3=cabinet fan
0x002008646304405F 00000000 00000000 - type 0 = Data Field Unused
0x582008646304405F 00006303 0F151D08 - type 11 = Timestamp 04/15/1999 21:29:08
A: ack read of this entry - X: Disable all future alert messages
Anything else skip redisplay the log entry
->Choice:a
Key FRU Identification Fields for System Alerts
The following fields are used for FRU identification.
Alert Level: How the problem has affected the system operation.
Source: What major part of the system the alert is referring to (i.e, platform,
memory, processor, etc...).
Source Detail: What sub-part of the system the alert is referring to (i.e, cabinet fan,
DIMM, high voltage DC power, etc...).
Source ID: Specific FRU referred to in Source and Source Detail (i.e, cabinet fan #4).
Problem Detail: Specific problem information (i.e, power off, functional failure, etc...).
Timestamp: When the problem occurred.
The above sample system alert shows the following:
1. The problem does not affect system boot.
2. The problem is with platform cabinet fan #4.
3. The problem is a fan failure. Replace fan #4 to correct the problem.
4. The fan failed on April 15, 1999 at 9:29 PM.