Skip to main content

Contents

  1. Preface
  2. Chapter 1 Before Starting Maintenance Work
    1.  1.1 Warning/Caution Indications
    2.  1.2 Labels/Tags
    3.  1.3 Safety Precautions
    4.  1.4 Precautions on Static Electricity
    5.  1.5 Other Precautions
    6.  1.6 Emergency Power Off
  3. Chapter 2 Understanding the System Components
    1.  2.1 Identifying the Names and Locations of Components
    2. Click 2.2 Checking the Memory Configuration Rules
    3. Click 2.3 Confirming the Functions of the Operation Panel
    4. Click 2.4 Checking the LED Indications
  4. Chapter 3 Types of Maintenance
    1.  3.1 Types of Maintenance Supported in the SPARC M10-1
    2.  3.2 Active Maintenance
    3.  3.3 System-stopped Maintenance (Inactive Maintenance)
  5. Chapter 4 Preparation and Precautions for Maintenance
    1. Click 4.1 Confirming the System Configuration
    2. Click 4.2 Troubleshooting
    3. Click 4.3 Maintenance Precautions
  6. Chapter 5 Preparations Required for Maintenance
    1.  5.1 Preparing Tools Required for Maintenance
    2.  5.2 Switching the Mode Switch to Service Mode
    3. Click 5.3 Checking the Operating Condition and Resource Usage Status
    4. Click 5.4 Enabling the Removal of an Internal Disk
    5. Click 5.5 Stopping the Entire System
    6. Click 5.6 Saving Setting Information and Configuration Information
    7.  5.7 Releasing a FRU from the System with the replacefru Command
    8. Click 5.8 Accessing a FRU
  7. Chapter 6 Understanding the Preparations for Restoring the System
    1. Click 6.1 Restoring the Chassis
    2.  6.2 Incorporating a FRU into the System with the replacefru Command
    3. Click 6.3 After Replacing the Motherboard Unit/PSU Backplane
    4.  6.4 Diagnosing a Replacement FRU
    5. Click 6.5 Restoring Setting Information and Configuration Information
    6.  6.6 Incorporating an Internal Disk
    7.  6.7 Checking the FRU Status after Maintenance
    8.  6.8 Returning the Mode Switch to Locked Mode
    9. Click 6.9 Starting the System
  8. Chapter 7 Maintenance Flow
    1.  7.1 Maintenance Workflow
    2. Click 7.2 FRU Replacement Workflow
    3. Click 7.3 FRU Installation Workflow
    4. Click 7.4 FRU Removal Workflow
  9. Chapter 8 Maintaining the PCI Express Cards
    1.  8.1 Before Maintaining a PCI Express Card
    2.  8.2 PCI Express Card Configuration
    3. Click 8.3 Removing a PCI Express Card
    4. Click 8.4 Installing a PCI Express Card
  10. Chapter 9 Maintaining the Internal Disks
    1.  9.1 Before Maintaining an Internal Disk
    2.  9.2 Configuration of the Internal Disks
    3.  9.3 Removing an Internal Disk
    4.  9.4 Installing an Internal Disk
  11. Chapter 10 Maintaining the HDD Backplane
    1.  10.1 Before Maintaining the HDD Backplane
    2.  10.2 HDD Backplane Location
    3. Click 10.3 Removing the HDD Backplane
    4. Click 10.4 Installing the HDD Backplane
  12. Chapter 11 Maintaining the Power Supply Units
    1.  11.1 Before Maintaining a Power Supply Unit
    2.  11.2 Configuration of the Power Supply Units
    3. Click 11.3 Removing a Power Supply Unit
    4. Click 11.4 Installing a Power Supply Unit
  13. Chapter 12 Maintaining the PSU Backplane
    1.  12.1 Before Maintaining the PSU Backplane
    2.  12.2 PSU Backplane Location
    3.  12.3 Precautions for Maintaining the PSU Backplane
    4. Click 12.4 Removing the PSU Backplane
    5. Click 12.5 Installing the PSU Backplane
  14. Chapter 13 Maintaining the Cable Kit
    1.  13.1 Before Maintaining the Cable Kit
    2.  13.2 Cable Kit Location
    3. Click 13.3 Removing the Cable Kit
    4. Click 13.4 Installing the Cable Kit
  15. Chapter 14 Maintaining the Operation Panel
    1.  14.1 Before Maintaining the Operation Panel
    2.  14.2 Operation Panel Location
    3. Click 14.3 Removing the Operation Panel
    4. Click 14.4 Installing the Operation Panel
  16. Chapter 15 Maintaining the Fan Units
    1.  15.1 Before Maintaining a Fan Unit
    2.  15.2 Configuration of the Fan Units
    3. Click 15.3 Removing a Fan Unit
    4. Click 15.4 Installing a Fan Unit
  17. Chapter 16 Maintaining the Motherboard Unit/Memory
    1.  16.1 Before Maintaining the Motherboard Unit/Memory
    2.  16.2 Motherboard Unit Location
    3.  16.3 Memory Locations
    4.  16.4 Precautions for Motherboard Unit Replacement
    5. Click 16.5 Removing the Motherboard Unit and Memory
    6. Click 16.6 Installing the Motherboard Unit and Memory
  18. Appendix A Component List
  19. Appendix B Component Specifications
    1.  B.1 Motherboard Unit
    2.  B.2 Power Supply Unit
    3.  B.3 Fan Unit
    4.  B.4 Internal Disk
    5.  B.5 PCI Express Card
    6.  B.6 Backplanes
    7.  B.7 Operation Panel
  20. Appendix C Oracle Solaris Troubleshooting Commands
    1.  C.1 iostat Command
    2.  C.2 prtdiag Command
    3.  C.3 prtconf Command
    4.  C.4 netstat Command
    5.  C.5 ping Command
    6.  C.6 ps Command
    7.  C.7 prstat Command
  21. Appendix D External Interface Specifications
    1. Click D.1 Serial Port
    2.  D.2 USB Port
    3.  D.3 SAS Port
    4.  D.4 RESET Switch
  22. Appendix E Removing the Lithium Battery
    1.  E.1 Location of the Lithium Battery
    2.  E.2 Removing the Lithium Battery

4.2.2 Identifying a failure


4.2.2 Identifying a failure
This section describes how to identify a failure. Use the flow described in "4.2.1 Confirming whether there is a failure" to determine the appropriate way of checking for a failure.
Checking the LED indications
Check the LEDs on the operation panel, rear panel, and each component to identify the FRU requiring maintenance. Check the status of a FRU from its LED before starting maintenance work on the FRU.
  1. Operation panel LEDs
    You can determine the status of the system by checking the LEDs on the operation panel. For details, see "2.4.1 Operation panel LEDs."
  2. Rear panel LED
    You can determine the status of the system by checking the CHECK LED on the rear panel of the chassis, which duplicates the CHECK LED on the operation panel. For details, see "2.4.2 LEDs on the rear panel (System locator)."
  3. LED of each FRU
    If an error occurs in the hardware in the chassis, you can determine the location of the error by checking the LED of the FRU that incorporates the failed hardware. For details, see "2.4.3 LEDs on each component."
    Note that some FRUs, such as memory, do not have mounted LEDs. To check the status of a FRU that does not have an LED, execute XSCF shell commands such as the showhardconf command from the maintenance terminal. For details, see "Checking the FRU status."
Checking error messages
Display error messages to check log information and an error overview.
You can use either of the following two methods to check the error messages:
  1. Checking error log information with the XSCF shell
    For details, see "12.1 Checking a Log Saved by the XSCF" in the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 System Operation and Administration Guide.
  2. Checking messages on Oracle Solaris
    For details, see "12.2 Checking Warning and Notification Messages" in the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 System Operation and Administration Guide.
Checking the FRU status
Execute XSCF firmware commands to determine the system hardware configuration and the status of each FRU.
showhardconf command
Execute the showhardconf command to check the FRU-related information.
  1. Log in to the XSCF shell.
  2. Execute the showhardconf command to check the FRU list.
    A failed component is indicated by an asterisk (*) at the beginning of the line.
XSCF> showhardconf
SPARC M10-1;
+ Serial:2101151008A; Operator_Panel_Switch:Locked;
+ System_Power:Off; System_Phase:Cabinet Power Off;
------------------------Omitted------------------------

PCI#1 Status:Normal; Name_Property:;
+ Vendor-ID:14e4; Device-ID:1648;
+ Subsystem_Vendor-ID:10cf; Subsystem-ID:13a0;
+ Model: LPe1250-F8-FJ;
+ Connection:PCIBOX#X07P;
* PCIBOX#X0DF Status:Faulted; Ver:0512 Serial:XCX0DF;
+ FRU-Part-Number:CF00541-0314 05 /501-6937-05;
IOB Status:Normal; Serial:XX00KA; Type:PCI-X;
+ FRU-Part-Number:CF00541-0316 03 /501-6938-05;
LINKBORAD Status:Faulted; Ver:0512 Serial:XCX0DF;
+ FRU-Part-Number:CF00541-0314 05 /501-6937-05;
PCI#0 Name_Property:fibre-channel;
+ Vendor-ID:14e4; Device-ID:1648;
+ Subsystem_Vendor-ID:10cf; Subsystem-ID:13a0;
+ Model: LPe1250-F8-FJ;
showstatus command
Execute the showstatus command to check the FRU status.
  1. Log in to the XSCF shell.
  2. Execute the showstatus command to check the status.
    A faulty FRU is indicated by an asterisk (*) at the beginning of the line.
XSCF> showstatus
MBU Status:Normal;
* MEM#0A Status:Faulted;
The FRU status is displayed after the "Status:" string.
Table 4-3 describes the FRU status.
Table 4-3  FRU status
Display Description
Normal The unit is in the normal state.
Faulted The unit is faulty and is not operating.
Degraded A part of the unit has failed or degraded, but the unit is running.
Deconfigured Due to the failure or degradation of another unit, the target unit and components of its underlying layer has been degraded, though there is no problem in them.
Maintenance Maintenance is being performed. The replacefru or addfru command is being executed.
Checking the status of a PCI expansion unit
If a PCI expansion unit is connected, execute the ioxadm command to check the status of the PCI expansion unit.
ioxadm command
Execute the ioxadm command to determine the environmental conditions (temperature, voltage, etc.) or LED indications of the PCI expansion unit.
  1. Log in to the XSCF shell.
  2. Execute the ioxadm command to check the environmental conditions of the specified PCI expansion unit.
    To specify a PCI expansion unit, enter the serial number of the PCI expansion unit after determining it with the ioxadm list command.
    The following example shows the environmental conditions for PCIBOX#2008. "2008" is the last four digits of the serial number of the PCI expansion unit.
XSCF> ioxadm env -te PCIBOX#2008
Location Sensor Value Resolution Units
PCIBOX#2008 AIRFLOW 180.000 0.000 CHM
PCIBOX#2008 P_CONSUMPTION 68.000 0.000 W
PCIBOX#2008/PSU#0 FAN 3936.000 0.000 RPM
PCIBOX#2008/PSU#1 FAN 3584.000 0.000 RPM
PCIBOX#2008/FAN#0 FAN 3374.000 0.000 RPM
PCIBOX#2008/FAN#1 FAN 3374.000 0.000 RPM
PCIBOX#2008/FAN#2 FAN 3374.000 0.000 RPM
PCIBOX#2008/IOBT T_INTAKE 26.000 0.000 C
PCIBOX#2008/IOBT T_PART_NO0 31.500 0.000 C
PCIBOX#2008/IOBT T_PART_NO1 30.750 0.000 C
PCIBOX#2008/IOBT T_PART_NO2 31.500 0.000 C
PCIBOX#2008/IOBT V_12_0V 12.069 0.000 V
PCIBOX#2008/IOBT V_3_3_NO0 3.293 0.000 V
PCIBOX#2008/IOBT V_3_3_NO1 3.295 0.000 V
PCIBOX#2008/IOBT V_3_3_NO2 3.291 0.000 V
PCIBOX#2008/IOBT V_3_3_NO3 3.300 0.000 V
PCIBOX#2008/IOBT V_1_8V 1.804 0.000 V
PCIBOX#2008/IOBT V_0_9V 0.900 0.000 V
Checking log information
Execute the showlogs command to check error log information.
  1. Log in to the XSCF shell.
  2. Execute the showlogs command to determine the error log information.
    The log information is listed in order of date, with the oldest appearing first.
    The following example shows that an Alarm occurred in PSU#1 at 12:45:31 on Oct 20, and the status changed to Warning at 15:45:31 on the same day.
XSCF> showlogs error
Date: Oct 20 12:45:31 JST 2012
Code: 00112233-445566778899aabbcc-8899aabbcceeff0011223344
Status: Alarm Occurred: Oct 20 12:45:31.000 JST 2012
FRU: /PSU#1
Msg: ACFAIL occurred (ACS=3)(FEP type = A1)
Date: Oct 20 15:45:31 JST 2012
Code: 00112233-445566778899aabbcc-8899aabbcceeff0011223344
Status: Warning Occurred: Oct 20 15:45:31.000 JST 2012
FRU: /PSU#1
Msg: ACFAIL occurred (ACS=3)(FEP type = A1)
Table 4-4 shows operands of the showlogs command and the log to be displayed.
Table 4-4  Operands of the showlogs command and the log to be displayed
Operand Description
error Lists the error log.
event Lists the event log.
power Lists the power log.
env Lists the temperature history.
monitor Lists the monitoring message log.
console Lists the console message log.
ipl Lists the IPL message log.
panic Lists the panic message log.
Checking the messages output by the predictive self-repairing tool
Check the messages output from the Oracle Solaris Fault Manager predictive self-repairing tool, running on Oracle Solaris. Oracle Solaris Fault Manager supports the following functions:
  1. Receives telemetry information about errors.
  2. Performs troubleshooting.
  3. Disables the FRUs that have experienced errors.
  4. Turns on the LED of a FRU that has experienced an error and displays the details in a system console message.
Table 4-5 lists typical messages that are generated if an error occurs. These messages indicate that the fault has already been diagnosed. If corrective actions can be taken by the system, this indicates that they 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.
Table 4-5  Predictive self-repairing messages
Output displayed Description
EVENT-TIME: Thu Apr 19 10:48:39 JST 2012 EVENT-TIME: Time stamp of the diagnosis
PLATFORM: ORCL,SPARC64-X, CSN: PP115300MX, HOSTNAME: 4S-LGA12-D0 PLATFORM: Description of the chassis in which the error occurred
SOURCE: eft, REV: 1.16 SOURCE: Information on the diagnosis engine used to identify the error
EVENT-ID: fcbb42a5-47c3-c9c5-f0b0-f782d69afb01 EVENT-ID: Universally unique event ID for this error
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. DESC: Basic description of the error
AUTO-RESPONSE: Error reports have been logged for examination. AUTO-RESPONSE: What the system has done (if anything) to alleviate any subsequent problems
IMPACT: Automated diagnosis and response for these events will not occur. IMPACT: Description of the assumed impact of the failure
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. REC-ACTION: Brief description of the corrective action the system administrator should apply
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 blink the CHECK LED of the chassis requiring maintenance, and determine its location.
    The CHECK LEDs on the operation and rear panels blink.
XSCF> setlocator blink
  1. For details on where to find and how to check the CHECK LEDs, see "2.4 Checking the LED Indications."

Top of Page