Fujitsu M10-4 Service Manual page 71

Table 4-5 Predictive self-repairing messages
Output Displayed
EVENT-TIME: Thu Apr 19 10:48:39 JST 2012
PLATFORM: ORCL,SPARC64-X, CSN: PP115300MX, HOSTNAME:
4S-LGA12-D0
SOURCE: eft, REV: 1.16
EVENT-ID: fcbb42a5-47c3-c9c5-f0b0-f782d69afb01
DESC: The diagnosis engine encountered telemetry from the listed
devices for which it was unable to perform a diagnosis -
ereport.io.pciex.rc.epkt@chassis0/cpuboard0/chip0/hostbridge0/
pciexrc0 class and path are incompatible.
AUTO-RESPONSE: Error reports have been logged for examination.
IMPACT: Automated diagnosis and response for these events will
not occur.
REC-ACTION: Use 'fmadm faulty' to provide a more detailed view
of this event. Use 'fmdump -eV' to view the unexpected telemetry.
Please refer to the associated reference document at http://support.
oracle.com/msg/SUNOS-8000-J0 for the latest service procedures
and policies regarding this diagnosis.
Identifying the location of the chassis requiring maintenance
Execute the setlocator command to identify the location of the chassis requiring
maintenance by causing the CHECK LED on the operation panel and the CHECK
LED (locator) on the rear panel to blink.
1. Log in to the XSCF shell.
2. Execute the setlocator command to identify the location of the chassis
requiring maintenance, by causing the CHECK LED of the chassis to blink.
The CHECK LEDs on the operation and rear panels blink.
The chassis requiring maintenance in the following execution example is the
master chassis.
XSCF> setlocator blink
If the chassis requiring maintenance is not the master chassis, set "setlocator -b
bb_id blink".
For the locations of the CHECK LEDs and details on how to check them, see
Checking the LED Indications."
Description
EVENT-TIME: Time stamp of the diagnosis
PLATFORM: Description of the chassis in
which the error occurred
SOURCE: Information on the diagnosis
engine used to identify the error
EVENT-ID: Universally unique event ID for
this error
DESC: Basic description of the error
AUTO-RESPONSE: What the system has
done (if anything) to alleviate any
subsequent problems
IMPACT: Description of the assumed
impact of the failure
REC-ACTION: Brief description of the
corrective action the system administrator
should apply
Chapter 4 Preparation and Precautions for Maintenance
"2.4
57