HP 9000 rp5400 Servers - Manual (Page 77)

Table 6-2 Chassis Log Error to FRU Decoder (continued)
Chassis Log Field Values and Descriptions from Log Entry
Action to Take FRU Problem
Detail Source ID Source Detail Source
Isolate to failing DIMM
using BCH (IN, ME) and
ODE memory diagnostic. Memory
DIMM N/A N/A 4 - SIMM or DIMM 7 - Memory
Use BCH commands and
ODE diagnostics to check
disk subsystem. Disk
Subsystem Various
Values N/A 6 - Disk 8 - I/O
Power Supply Failure Example
GSP> sl
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 to escape.
Log Entry # 0 :
ALERT LEVEL: 6=Boot possible, pending failure or environmental problem - action required
REPORTING ENTITY TYPE: 2=power monitor - REPORTING ENTITY ID: 00
CALLER ACTIVITY: 4=monitor - CALLER SUBACTIVITY: 04=low voltage power supply
SOURCE: 4=power - SOURCE DETAIL: 4=high voltage DC power - SOURCE ID: 02
PROBLEM DETAIL: A=unexpected - ACTIVITY STATUS: F
Data 0 : Low=00000000 : High=00000000 - type 0 = Data Field Unused
Data 1 : Low=0F152A28 : High=00006303 - type 11 - Timestamp 04/15/1999 21:42:40
Problem Analysis
1. Find the Source value. In this example, it is SOURCE: 4=power.
Use the Power row of the Error Chassis Log-to-FRU Decoder table.
2. Find the Source Detail value. In this example, it is SOURCE DETAIL: 4=high voltage DC power.
Use the High Voltage DC Power row of the table.
3. Find the Source ID value. In this example, it is SOURCE ID: 02.
The failing power supply is Power Supply #2.
4. The Problem Detail for this row is not applicable.
5. The FRU column of the table identifies the FRU as the Power Supply.
The correct action would be to replace Power Supply #2, located in the front of the system.
Processor Failure Example
Log Entry # 1 :
ALERT LEVEL: 6=Boot possible, pending failure or environmental problem - action required
REPORTING ENTITY TYPE: 0=system firmware - REPORTING ENTITY ID: 01
CALLER ACTIVITY: 1=test - CALLER SUBACTIVITY: 62=implementation dependent
SOURCE: 1=processor - SOURCE DETAIL: 1=processor general - SOURCE ID: 00
PROBLEM DETAIL: 3=functional failure - ACTIVITY STATUS: 0
Data 0 : Low=00000003 : High=F7000000 - type 0 = Data Field Unused
Data 1 : Low=0F160920 : High=00006303 - type 11 - Timestamp 04/15/1999 22:09:32
Chassis Code to FRU Decode 77