Table3-3 Predictiveself-repairin g messages
OutputDisplayed Description
Nov1 16:30:20 dt88-292 EVENT-TIME:Tue
Nov1 16:30:20 PST 2005
EVENT-TIME:Time stamp for the
diagnosis
Nov1 16:30:20 dt88-292 PLATFORM:
ORCL,SPARC64-X,CSN:-,HOSTNAME :dt88-292
PLATFORM: Description of the
chassisin which the error occurred
Nov1 16:30:20 dt88-292 SOURCE:eft, REV:1.13 SOURCE:Informationregarding
thediagnos isen gine used to
identifythe error
Nov1 16:30:20 dt 88-292 EVENT-ID:
afc7e660-d609-4b2f-86b8-ae7c6b8d50c4
EVENT-ID:Universally unique
eventID for th is error
Nov1 16:30:20 dt88-292 DESC:
Nov1 16:30:20 dt88-292 A problem was detected in
thePCI Express subsystem
DESC:Basic descript ion of the error
Nov1 16:30:20 dt88-292 Refer to http://support.
oracle.com/msg/SUN4-8000-0Yfor more information.
Website:Where to find specific
informationand countermeasures
forthis error
Nov1 16:30:20 dt88-292 AUTO-RESPONSE:
Oneor more device inst ances may be disabled.
AUTO-RESPONSE:What the
systemhas done (if anything) to
alleviateany subseq uent problems
Nov1 16:30:20 dt88-292 IMPACT:Loss of services
providedby the d evice instances associated with this
fault.
IMPACT:Description of the
assumedimpact of the failure
3.3.6 Checking the messages output by the predictiveself-repairing toolCheckthe messages output from the Oracle Solaris Fault Manager predictive
self-repairingtool, running on Oracle Solaris. Oracle Solaris Fault Manager has the
following functions:
■Receivestelemetry information about errors.
■Performstroubleshooting
■Disablesthe components that have experienced errors.
■Turnson the LED of a component that has experienced an error and displays the
detailsin the system c onsole message.
Table3-3 lists typical messages that are generated if an error occurs. These messages
indicatethat the fault has already been diagnosed. If there are corrective actions that
can bet aken by the system,t hey have already been taken. In addition, if the system is
running, corrective actions continue to be applied.
Messages are displayed on the console and are recorded in the /var/adm/messages
file.
Chapter3 Troubleshooting 39