
ALERT LEVEL: 6=Boot possible, pending failure or environmental problem - action required
SOURCE: 6=platform - SOURCE DETAIL: 3=cabinet fan
PROBLEM DETAIL: 4=fan failure
GSP> co
CO
You are now leaving the Guardian Service Processor Command Interface
and returning to the console mode. Type Ctrl B to reactivate it.
Main Menu: Enter command or menu >
Key FRU Identification Fields for Error Chassis Logs
The following fields are 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., fan #4).
Problem Detail: Specific problem information (i.e, power off, functional failure, etc.).
Timestamp: When the problem occurred.
The above sample system alert message shows the following:
1. The problem does not affect booting of the system.
2. The problem is with fan #4.
3. The problem is a fan failure.
4. The fan failed on April 15, 1999 at 9:29 PM.
In this example, fan #4 should be replaced to correct the problem.
Interpreting Chassis Logs Using the chassis_code.codes File
For chassis logs generated by system firmware (Reporting Entity Type 0), use the
chassis_code.codes file for chassis code definitions. Each revision of system firmware (AKA
Processor Dependent Code or PDC) has a unique chassis_code.codes file. This file is not part of
either the PF_Cxxxxx or PHSS_xxxxx server firmware patches. The chassis_code.codes files
appear in the appendices of the Interpreting Chassis Logs in Detail guide.
The definition of a PDC reported chassis code is determined by locating either the last four digits
of a chassis log or the last three digits of a selftest chassis code in the appropriate
chassis_code.codes file. Refer to the Interpreting Chassis Logs in Detail guide for definition and
examples of selftest chassis codes.
NOTE: Be sure to use the appropriate appendix as the PDC for rp5400/rp5450 is different than
PDC for rp5470. Using the wrong appendix may result in a mis-interpretation of the chassis code.
To quickly learn the definition of a PDC reported chassis code, follow these four steps:
1. Determine either the last 4 digits of the hex chassis code or the last 3 digits of the selftest
chassis code.
2. Go to the appropriate appendix in the Interpreting Chassis Logs in Detail guide.
3. Locate the chassis code that matches the last 3 or 4 digits. If viewing via web browser or
Adobe Acrobat, use the FIND feature to locate the chassis code.
4. Take action as appropriate.
Chassis Code to FRU Decode 81
Comentarios a estos manuales