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 Notes Regarding 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 Confirming the Functions of the Operation Panel
    3. Click 2.3 Checking the LED Indications
    4. Click 2.4 Confirming the Types of Cable
  4. Chapter 3 Types of Maintenance
    1. Click 3.1 Types of Maintenance Supported for the Crossbar Box
    2.  3.2 Active Maintenance
    3.  3.3 Inactive Maintenance
    4.  3.4 System-Stopped 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 Enabling the Removal of a FRU Requiring Maintenance
    1.  5.1 Preparing Tools Required for Maintenance
    2. Click 5.2 Releasing the Chassis for a Connecting Physical Partition From the System
    3.  5.3 Saving XSCF Setting Information
    4. Click 5.4 Releasing FRUs of the Crossbar Box From the System With the replacefru Command
    5. Click 5.5 Accessing a FRU
  7. Chapter 6 Restoring the System
    1. Click 6.1 Restoring the Chassis
    2. Click 6.2 Incorporating the FRUs of the Crossbar Box Into the System With the replacefru Command
    3. Click 6.3 Diagnosing a Replacement FRU
    4.  6.4 Restoring XSCF Setting Information
    5.  6.5 Incorporating a Chassis Into a Physical Partition
    6.  6.6 Returning the Mode Switch to Locked Mode
    7.  6.7 Powering On the Physical Partition Requiring Maintenance
    8. Click 6.8 Starting the Entire System
  8. Chapter 7 Maintenance Flow
    1.  7.1 Maintenance Workflow
    2.  7.2 Active Maintenance Flow
    3.  7.3 Inactive Maintenance Flow
    4. Click 7.4 System-Stopped Maintenance Flow
  9. Chapter 8 Maintaining the XSCF Unit
    1.  8.1 Before Maintaining an XSCF Unit
    2.  8.2 Location of the XSCF Unit
    3.  8.3 Maintenance Precautions
    4.  8.4 Removing the XSCF Unit
    5.  8.5 Switching the microSD Card
    6.  8.6 Installing the XSCF Unit
    7.  8.7 Checking the XCP Firmware Version
  10. Chapter 9 Maintaining the XSCF BB Control Cables
    1.  9.1 Before Maintaining an XSCF BB Control Cable
    2.  9.2 Configuration of the XSCF BB Control Ports
    3.  9.3 Removing an XSCF BB Control Cable
    4.  9.4 Installing an XSCF BB Control Cable
  11. Chapter 10 Maintaining the XSCF DUAL Control Cables
    1.  10.1 Before Maintaining an XSCF DUAL Control Cable
    2.  10.2 Configuration of the XSCF DUAL Control Ports
    3.  10.3 Removing an XSCF DUAL Control Cable
    4.  10.4 Installing an XSCF DUAL Control Cable
  12. Chapter 11 Maintaining the Crossbar Cables (Optical)
    1.  11.1 Before Maintaining a Crossbar Cable (Optical)
    2.  11.2 Configuration of Connection Ports for Crossbar Cables (Optical)
    3.  11.3 Removing a Crossbar Cable (Optical)
    4.  11.4 Installing a Crossbar Cable (Optical)
  13. Chapter 12 Maintaining the Crossbar Units
    1.  12.1 Before Maintaining a Crossbar Unit
    2.  12.2 Configuration of the Crossbar Units
    3.  12.3 Removing a Crossbar Unit
    4.  12.4 Installing a Crossbar Unit
  14. Chapter 13 Maintaining the Power Supply Units
    1.  13.1 Before Maintaining a Power Supply Unit
    2.  13.2 Configuration of the Power Supply Units
    3.  13.3 Removing a Power Supply Unit
    4.  13.4 Installing a Power Supply Unit
  15. Chapter 14 Maintaining the XSCF Interface Unit
    1.  14.1 Before Maintaining an XSCF Interface Unit
    2.  14.2 Location of the XSCF Interface Unit
    3.  14.3 Maintenance Precautions
    4.  14.4 Removing the XSCF Interface Unit
    5.  14.5 Installing the XSCF Interface Unit
  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 Fan Backplane
    1.  16.1 Before Maintaining a Fan Backplane
    2.  16.2 Configuration of the Fan Backplane
    3. Click 16.3 Removing the Fan Backplane
    4. Click 16.4 Installing the Fan Backplane
  18. Chapter 17 Maintaining the Operation Panel
    1.  17.1 Before Maintaining the Operation Panel
    2.  17.2 Location of the Operation Panel
    3.  17.3 Maintenance Precautions
    4. Click 17.4 Removing the Operation Panel
    5. Click 17.5 Installing the Operation Panel
  19. Chapter 18 Maintaining the Cable Kit
    1.  18.1 Before Maintaining a Cable Kit
    2. Click 18.2 Configuration of the Cable Kit
    3. Click 18.3 Removing the Cable Kit
    4. Click 18.4 Installing the Cable Kit
  20. Chapter 19 Maintaining the Crossbar Backplane Unit
    1.  19.1 Before Maintaining a Crossbar Backplane Unit
    2.  19.2 Location of the Crossbar Backplane Unit
    3.  19.3 Removing the Crossbar Backplane Unit
    4.  19.4 Installing the Crossbar Backplane Unit
  21. Chapter 20 Maintaining the Dedicated Power Distribution Unit Mounted on the Rack for Expanded Connection
    1.  20.1 Before Maintaining a Dedicated Power Distribution Unit
    2. Click 20.2 Configuration of the Dedicated Power Distribution Unit
    3. Click 20.3 Removing the Dedicated Power Distribution Unit
    4.  20.4 Installing the Dedicated Power Distribution Unit
  22. Appendix A Component List
  23. Appendix B Component Specifications
    1.  B.1 Crossbar Unit
    2.  B.2 XSCF Unit
    3.  B.3 XSCF Interface Unit
    4.  B.4 Power Supply Unit
    5.  B.5 Fan Unit
    6.  B.6 Various Backplanes
    7.  B.7 Operation Panel
  24. Appendix C External Interface Specifications
    1. Click C.1 Serial Port
    2.  C.2 USB Port
    3.  C.3 RESET Switch
  25. Appendix D Removing the Lithium Battery
    1.  D.1 Location of the Lithium Battery
    2.  D.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 troubleshooting flow described in "4.2.1 Determining the Causes of Failures" 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.3.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.3.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.3.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" below.
Checking Error Messages
Display error messages to check the log information and obtain an error overview.
You can use either of the following two methods to check the error messages:
  1. Checking error log information using 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 with 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 information on the FRU list.
  1. Log in to the XSCF shell.
  2. Execute the showhardconf command to check the FRU list.
    A faulty FRU is indicated by an asterisk (*) at the beginning of the line.
    The following example shows execution on the SPARC M10-4S.
XSCF> showhardconf
SPARC M10-4S;
+ Serial:2081230011; Operator_Panel_Switch:Locked;
+ System_Power:On; System_Phase:Cabinet Power On;
Partition#0 PPAR_Status:Powered Off;
Partition#1 PPAR_Status:Initialization Phase;
BB#00 Status:Normal; Role:Slave; Ver:2003h; Serial:2081231002;
+ FRU-Part-Number:CA07361-D202 A1 ;
+ Power_Supply_System:Single;
+ Memory_Size:256 GB;
------------------------Omitted------------------------

XBBOX#80 Status:Normal; Role:Master; Ver:0101h; Serial:7867000297;
+ FRU-Part-Number:CA07361-D011 A0 /NOT-FIXD-01 ;
+ Power_Supply_System:Single;
XBU#0 Status:Normal; Serial:PP0629L068
+ FRU-Part-Number:CA20393-B50X A2 ;
+ Type: A ;
* CBL#L0 Status:Degraded;
+ FRU-Part-Number:2123628-2 ; Ver:3820h;
+ Type:Optic; Length: 3;
+ FRU-Part-Number:2123628-2 ; Ver:3820h;
+ Type:Optic; Length: 3;
------------------------Omitted----------------------
- 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
XBBOX#80;
* PSU#0 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 with them.
Maintenance Maintenance is being performed. The replacefru, addfru, or initbb command is being executed.
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 check the log information.
    The log information is listed in order of date, with the oldest appearing first.
    The following example shows that an Alarm status occurred in PSU#1 at 12:45:31 on Oct 20, and the Alarm status changed to a Warning status 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 what log information each operand of the showlogs command can display.
Table 4-4  showlogs Command Operands and the Logs 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 has 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 there are corrective actions that can be taken by the system, 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 regarding 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.
  1. The chassis requiring maintenance in the following execution example is the master chassis.
XSCF> setlocator blink
  1. If the chassis requiring maintenance is not the master chassis, set "setlocator -b bb_id blink".
  1. For details on where to find and how to check the CHECK LEDs, see "2.3 Checking the LED Indications."

Top of Page