Linux Service Aid "Diagela; Using The Srn List; Service Request Number; Source Of Srn - IBM JS20 - BladeCenter - 8842 Maintenance And Troubleshooting Manual

Linux service aid "diagela"

The following is an example of the diagela output that is automatically run by the
Linux service aid tool kit that has been applied to the system. See "Service aids
and the Linux system error log" on page 40 for more information about these tools.
The Linux service aids for hardware diagnostics are separate from the operating
system installation and are available for download from the following Web site:
http://techsupport.services.ibm.com/server/lopdiags
This service aid tool kit provides the key tools required to take advantage of the
inherent JS20 hardware reliability, availability, and serviceability (RAS) functions.
Use the SRN table to determine the description of the problem and the action plan
for the SRN provided by the diagela application. For example:

Using the SRN list

The service request number (SRN) list is in numerical sequence. The SRNs listed
in the following tables are for all systems and devices for which this version of the
diagnostic programs can produce an SRN. The columns in the table are defined as
follows:

Service request number

Usually a six-digit number (9333 uses four digits) representing a specific failure of a
specific function.

Source of SRN

SRN source codes identify the program or procedure that produced the SRN:
A
B
C
D
E
F
G
H
K

Failing Function Codes

These numbers represent functional areas of the system unit. The "Failing Function
Codes (FFCs)" on page 141 identify the FRU that contains this function for each
specific system unit.
diagela: 02/19/2004 18:10:23
diagela: Automatic Error Log Analysis has detected a problem.
diagela:
diagela: The Service Request Number(s) /Probable Cause(s)
diagela: (causes are listed in descending order of probability):
diagela:
diagela: A01-020: CPU internal cache or cache controller error
diagela: Analysis of /var/log/platform sequence number: 3
The SRN is from a progress code (i.e., 101-254E)
The SRN is from a MAP callout.
The SRN was due to a missing resource at configuration time.
The SRN is from a diagnostic test after complete isolation testing.
The SRN is from a POST failure.
The SRN is from a diagnostic test after partial isolation testing.
The SRN is from the Error Log Analysis program.
The SRN is from a diagnostic message after an 888 sequence.
The SRN is from off-line diagnostics.
Chapter 10. Symptom-to-FRU index
109