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

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

Chapter 5 Diagnostics 81
Reviewing Auto-Diagnosis Event Messages
Autodiagnosis
[AD]
and domain
[DOM]
event messages are displayed on the
console and also in the following:
■
The
/var/adm/messages
file, provided that you have set up the event reporting
appropriately, as described in Chapter 3 .
■
The
showlogs
command output, which displays the event messages logged on
the console.
In servers with enhanced-memory system controllers (SC V2s), log messages are
maintained in a persistent buffer. You can selectively view certain types of log
messages according to message type, such as fault event messages, by using the
showlogs -p -f
filter command. For details, see the
showlogs
command
description in the Sun Fire Entry-Level Midrange System Controller Command
Reference Manual.
The
[AD]
or
[DOM]
event messages (see
CODE EXAMPLE 5-5
,
CODE EXAMPLE 5-8
,
CODE EXAMPLE 5-9
, and
CODE EXAMPLE 5-10
) include the following information:
■
[AD]
or
[DOM]
–
AD
indicates that the system controller application (
ScApp)
or
POST automatic diagnosis engine generated the event message.
DOM
indicates that
the Solaris Operating System on the affected domain generated the automatic
diagnosis event message.
■
Event
– An alphanumeric text string that identifies the platform and event-
specific information used by your service provider.
■
CSN
– Chassis serial number, which identifies your Netra 1290 server.
■
DomainID
– The domain affected by the hardware error. The Netra 1290 server is
always Domain A .
■
ADInfo
– The version of the autodiagnosis message, the name of the diagnosis
engine (SCAPP or SF-SOLARIS_DE), and the autodiagnosis engine version. For
domain diagnosis events, the diagnosis engine is the Solaris Operating System
(SF-SOLARIS-DE) and the version of the diagnosis engine is the version of the
Solaris Operating System in use.
■
Time
– The day of the week, month, date, time (hours, minutes, and seconds),
time zone, and year of the autodiagnosis.
■
FRU-List-Count
– The number of components (FRUs) involved with the error
and the following FRU data:
■
If a single component is implicated, the FRU part number, serial number, and
location are displayed, as
CODE EXAMPLE 5-5
shows.
■
If multiple components are implicated, the FRU part number, serial number,
and location for each component involved is reported, as
CODE EXAMPLE 5-9
shows.
Be aware that not all the FRUs listed are necessarily faulty. The fault may
reside in a subset of the components identified.