Sun Microsystems Netra 1290, Руководство администратора

Страница: 95 / 146

Chapter 5 Diagnostics 77
CODE EXAMPLE 5-5
shows an auto-diagnosis event message that appears on the
console. In this example, a single FRU is responsible for the hardware error. See
“Reviewing Auto-Diagnosis Event Messages” on page 81 for details on the AD
message contents.
Note – Contact your service provider when you see these auto-diagnosis messages.
Your service provider will review the auto-diagnosis information and initiate the
appropriate service action.
The output from the
showlogs
,
showboards
,
showcomponent
, and
showerrorbuffer
commands supplements the diagnosis information presented
in the event messages, and can be used for additional troubleshooting purposes.
See
“Obtaining Auto-Diagnosis and Recovery Information” on page 80 for details
on the diagnosis-related information displayed by these commands.
6. During the autorestoration process, POST reviews the component health status of
FRUs that were updated by the AD engine. POST uses this information and tries
to isolate the fault by deconfiguring (disabling) any FRUs from the domain that
have been determined to cause the hardware error. Even if POST cannot isolate
the fault, the system controller then automatically reboots the domain as part of
domain restoration.
Note –
To take advantage of the automatic recovery feature, make sure that the
OpenBoot PROM variable
hang-policy
is set to
reset
.
Automatic Recovery of a Hung System
The system controller automatically monitors systems for hangs when either of the
following occurs:
CODE EXAMPLE 5-5
Example of Auto-Diagnosis Event Message Displayed on the Console
[AD] Event: N1290.ASIC.AR.ADR_PERR.10473006
CSN: DomainID: A ADInfo: 1.SCAPP.17.0
Time: Fri Dec 12 09:30:20 PST 2003
FRU-List-Count: 2; FRU-PN: 5405564; FRU-SN: A08712; FRU-LOC: /N0/IB6
FRU-PN: 5404974; FRU-SN: 000274; FRU-LOC: /N0/RP2
Recommended-Action: Service action required