Skip to main content

Contents

  1. Preface
  2. Chapter 1 Before Starting Maintenance Work
    1.  1.1 Warning/Caution Indications
    2. Click 1.2 Labels
    3.  1.3 RFID Tag
    4.  1.4 Safety Precautions
    5.  1.5 Precautions on Static Electricity
    6.  1.6 Other Precautions
    7.  1.7 Emergency Power-Off
    8.  1.8 Tools Required for Maintenance
  3. Chapter 2 Understanding the System Units
    1. Click 2.1 Understanding the Names and Locations of the Units
    2. Click 2.2 Checking the Memory Configuration Rules
    3. Click 2.3 Understanding the OPNL Functions
    4. Click 2.4 Understanding the LED Indications
    5. Click 2.5 Understanding the Types of Cable
  4. Chapter 3 Understanding the Types of Maintenance
    1.  3.1 Types of Maintenance
    2. Click 3.2 Types of Maintenance Applicable to the SPARC M12-2
    3. Click 3.3 Types of Maintenance Applicable to the SPARC M12-2S (1BB Configuration)
    4. Click 3.4 Types of Maintenance Applicable to the SPARC M12-2S (Multiple-BB Configuration)
  5. Chapter 4 FRU Replacement Workflows
    1. Click 4.1 Active/Hot Replacement Workflows
    2. Click 4.2 Active/Cold Replacement Workflows
    3. Click 4.3 Inactive/Hot Replacement Workflows
    4. Click 4.4 Inactive/Cold Replacement Workflows
    5. Click 4.5 System-Stopped/Hot Replacement Workflows
    6. Click 4.6 System-Stopped/Cold Replacement Workflows
  6. Chapter 5 FRU Addition Workflows
    1. Click 5.1 Active/Hot Addition Workflows
    2. Click 5.2 Active/Cold Addition Workflows
    3. Click 5.3 Inactive/Hot Addition Workflows
    4. Click 5.4 Inactive/Cold Addition Workflows
    5. Click 5.5 System-Stopped/Hot Addition Workflows
    6. Click 5.6 System-Stopped/Cold Addition Workflows
  7. Chapter 6 FRU Removal Workflows
    1. Click 6.1 Active/Hot Removal Workflows
    2. Click 6.2 Active/Cold Removal Workflows
    3. Click 6.3 Inactive/Hot Removal Workflows
    4. Click 6.4 Inactive/Cold Removal Workflows
    5. Click 6.5 System-Stopped/Hot Removal Workflows
    6. Click 6.6 System-Stopped/Cold Removal Workflows
  8. Chapter 7 FRU Maintenance Precautions
    1.  7.1 Precautions for FRU Replacement
    2.  7.2 Precautions for FRU Expansion
    3.  7.3 Precautions for FRU Reduction
  9. Chapter 8 Preparation for Maintenance
    1. Click 8.1 Checking the System Configuration
    2. Click 8.2 Troubleshooting
  10. Chapter 9 Releasing FRUs From the System
    1. Click 9.1 Saving Setting Information
    2. Click 9.2 Checking the Operation Status and Resource Usage Status of Oracle Solaris
    3. Click 9.3 Releasing I/O Resources From a Logical Domain
    4. Click 9.4 Enabling the Removal of Hardware
    5. Click 9.5 Stopping the System
    6. Click 9.6 Releasing FRUs From the System
    7.  9.7 Removing the SPARC M12-2S
    8. Click 9.8 Accessing a FRU
  11. Chapter 10 Setting Up the System
    1. Click 10.1 Preparing Hardware
    2. Click 10.2 Restoring Setting Information
    3.  10.3 Adding the SPARC M12-2S to a Building Block Configuration
    4. Click 10.4 Incorporating a FRU Into the System
    5. Click 10.5 Diagnosing a Replacement FRU
    6. Click 10.6 Incorporating the SPARC M12-2S or an I/O Device Into the PPAR
    7. Click 10.7 Incorporating I/O Resources Into a Logical Domain
    8.  10.8 Powering on a Physical Partition
    9. Click 10.9 Starting the System
  12. Chapter 11 Maintaining the XSCF Unit
    1.  11.1 Maintenance Precautions
    2.  11.2 Location of the XSCFU
    3.  11.3 Before Maintenance on the XSCFU
    4.  11.4 Removing the XSCFU
    5. Click 11.5 Switching an SD Card
    6.  11.6 Installing the XSCFU
    7.  11.7 Checking the XCP Firmware Version
    8.  11.8 Checking the XCP Firmware Version (Building Block Configuration)
  13. Chapter 12 Maintaining PCIe Cards
    1.  12.1 Locations of PCIe Cards
    2.  12.2 Before Maintenance on a PCIe Card
    3. Click 12.3 Removing a PCIe Card
    4. Click 12.4 Installing a PCIe Card
  14. Chapter 13 Maintaining the Power Supply Units
    1.  13.1 Locations of PSUs
    2.  13.2 Before Maintenance on a PSU
    3.  13.3 Removing a PSU
    4.  13.4 Installing a PSU
  15. Chapter 14 Maintaining the Fan Units and Fan Backplane Unit
    1.  14.1 Locations of the FANUs and FANBPU
    2.  14.2 Before Maintenance on a FANU or the FANBPU
    3. Click 14.3 Removing a FANU or the FANBPU
    4. Click 14.4 Installing a FANU or the FANBPU
  16. Chapter 15 Maintaining Internal Storage
    1.  15.1 Locations of HDDs/SSDs
    2.  15.2 Before Maintenance on an HDD/SSD
    3. Click 15.3 Removing an HDD/SSD or Filler Unit
    4. Click 15.4 Installing an HDD/SSD or Filler Unit
  17. Chapter 16 Maintaining the HDD Backplane Unit and Operation Panel
    1.  16.1 Locations of the HDDBPU and OPNL
    2.  16.2 Before Maintenance on the HDDBPU and OPNL
    3. Click 16.3 Removing the HDDBPU or OPNL
    4. Click 16.4 Installing the HDDBPU or OPNL
  18. Chapter 17 Maintaining the CPU Memory Unit and Memory
    1.  17.1 Maintenance Precautions
    2.  17.2 Locations of the CMU and Memory
    3.  17.3 Before Maintenance on the CMU and Memory
    4. Click 17.4 Removing the CMU or Memory
    5. Click 17.5 Installing the CMU and Memory
  19. Chapter 18 Maintaining the Backplane Unit and PSU Backplane Unit
    1.  18.1 Maintenance Precautions
    2.  18.2 Locations of the BPU and PSUBP
    3.  18.3 Before Maintenance on the BPU and PSUBP
    4. Click 18.4 Removing the BPU and PSUBP
    5. Click 18.5 Installing the BPU and PSUBP
  20. Chapter 19 Maintaining the Crossbar Cable
    1.  19.1 Ports for Crossbar Cable Connection
    2.  19.2 Before Maintenance on the Crossbar Cable
    3.  19.3 Removing the Crossbar Cable
    4.  19.4 Installing the Crossbar Cable
  21. Chapter 20 Maintaining the Crossbar Unit
    1.  20.1 Locations of the XBU
    2.  20.2 Before Maintenance on an XBU
    3.  20.3 Removing an XBU
    4.  20.4 Installing an XBU
  22. Chapter 21 Maintaining the XSCF DUAL Control Cable
    1.  21.1 XSCF DUAL Control Port
    2.  21.2 Before Maintenance on the XSCF DUAL Control Cable
    3.  21.3 Removing the XSCF DUAL Control Cable
    4.  21.4 Installing the XSCF DUAL Control Cable
  23. Chapter 22 Maintaining the XSCF BB Control Cable
    1.  22.1 XSCF BB Control Port
    2.  22.2 Before Maintenance on the XSCF BB Control Cable
    3.  22.3 Removing the XSCF BB Control Cable
    4.  22.4 Installing the XSCF BB Control Cable
  24. Appendix A Lists of Cable Connections in a Building Block Configuration
  25. Appendix B External Interface Specifications
    1. Click B.1 Serial Port
    2.  B.2 USB Port
    3.  B.3 SAS Port
    4.  B.4 RESET Switch
  26. Appendix C Removing the Lithium Battery
    1.  C.1 Location of the Lithium Battery
    2.  C.2 Removing the Lithium Battery

8.2.2 Identifying a Fault


8.2.2 Identifying a Fault
This section describes how to identify a fault.
Identify the location of a fault by following the troubleshooting flow in Figure 8-1.
(1) Checking the LED indicators
Check the LEDs on the OPNL, rear panel, and individual units to identify the FRU requiring maintenance. For FRU maintenance, check the status with the LEDs before starting the maintenance.
  1. LEDs of the OPNL
    You can check the system status from the LEDs on the OPNL. For details, see "2.4.1 OPNL LEDs."
  2. Rear panel LEDs
    As with the CHECK LED on the OPNL, you can also check the system status from the CHECK LED on the rear of the SPARC M12-2/M12-2S. For details, see "2.4.2 System Locator."
  3. LEDs of individual FRUs
    From the FRU LEDs, you can locate not only any error occurrence in hardware in the SPARC M12-2/M12-2S but also the hardware that caused the error. For details, see "2.4.3 LEDs of Each Unit."
Note - Some FRUs such as memory do not have mounted LEDs. To check the status of a FRU without a mounted LED, use an XSCF command such as the showhardconf command. For details, see "(3) Checking the FRU status" below.
(2) Checking error messages
If a failure occurs in the system, analyze the failure cause from the failure occurrence time, abnormal event, and other data obtained from XSCF log information and Oracle Solaris messages.
Checking XSCF log information
The following example shows a check of system operation and failure information from XSCF log information. 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.
  1. Checking monitoring messages
XSCF> showlogs monitor
Jan 27 18:42:11 H4U2S115 Event: SCF:System powered on
Jan 27 18:45:41 H4U2S115 Event: SCF:PPAR-ID 0: Reset released
Jan 27 18:45:48 H4U2S115 Event: SCF:POST boot start from PPAR (PPAR ID 0)
Jan 27 18:45:49 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: Banner)
Jan 27 18:45:50 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: CPU Check)
Jan 27 18:45:51 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: CPU Register)
Jan 27 18:45:52 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: STICK Increment)
Jan 27 18:45:53 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: Extended Instruction)
Jan 27 18:45:54 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: MMU)
Jan 27 18:46:07 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: Memory Initialize)
Jan 27 18:46:43 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: MSCAN)
Jan 27 18:46:54 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: Cache)
Jan 27 18:46:59 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: Interrupt Queue)
Jan 27 18:47:00 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: Floating Point Unit)
Jan 27 18:47:10 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: Encryption)
Jan 27 18:47:12 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: Random number)
Jan 27 18:47:13 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: Cacheable Instruction)
Jan 27 18:47:22 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: Softint)
Jan 27 18:47:23 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: CPU Cross Call)
Jan 27 18:47:24 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: CMU-CH)
Jan 27 18:47:26 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: PCI-CH)
Jan 27 18:47:33 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: TOD)
Jan 27 18:47:34 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: MBC Check Before STICK Diag)
Jan 27 18:47:35 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: STICK Stop)
Jan 27 18:47:37 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: STICK Start)
Jan 27 18:47:38 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: CPU Speed Control)
Jan 27 18:47:39 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: SX)
Jan 27 18:47:40 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: RT)
Jan 27 18:47:41 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: RT/SX NC)
Jan 27 18:47:42 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: RT/SX Interrupt)
Jan 27 18:47:45 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: CPU Status Check)
Jan 27 18:47:46 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: System Configuration)
Jan 27 18:47:47 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: System Status Check)
Jan 27 18:47:48 H4U2S115 Event: SCF:Current PPARs' phase (PPARID 0 POST phase: Prepare To Start Hypervisor)
Jan 27 18:47:48 H4U2S115 Event: SCF:POST Diag complete from PPAR (PPAR ID 0)
Jan 27 18:47:54 H4U2S115 Event: SCF:SCF sets the active config to PPAR (PPARID 0 SP-Config:factory-default)
Jan 27 18:48:06 H4U2S115 Event: SCF:HV boot from PPAR (PPAR ID 0)
Jan 27 18:48:13 H4U2S115 Event: SCF:PPARID 0 GID 00000000 state change (OpenBoot initializing)
Jan 27 18:48:28 H4U2S115 Event: SCF:PPARID 0 GID 00000000 state change (OpenBoot Running)
Jan 27 18:48:28 H4U2S115 Event: SCF:PPARID 0 GID 00000000 state change (OpenBoot Primary Boot Loader)
Jan 27 18:48:46 H4U2S115 Event: SCF:PPARID 0 GID 00000000 state change (OpenBoot Running OS Boot)
Jan 27 18:49:32 H4U2S115 Event: SCF:PPARID 0 GID 00000000 state change (Solaris booting)
Jan 27 18:49:32 H4U2S115 Event: SCF:PPARID 0 GID 00000000 state change (Solaris booting)
Jan 27 18:49:32 H4U2S115 Event: SCF:PPARID 0 GID 00000000 state change (Solaris running)
XSCF>
  1. Checking error logs
XSCF> showlogs error
Date: Jan 11 16:33:43 JST 2017
Code: 40000000-014f210000ff0000ff-090101040000000000000000
Status: Warning Occurred: Jan 11 16:33:38.921 JST 2017
FRU: /BB#1/CMUL
Msg: A:mpt_sas9:mpt_sas:RAID status error
Date: Jan 11 18:06:55 JST 2017
Code: 80000000-0056000000ff0000ff-01a100020000000000000000
Status: Alarm Occurred: Jan 11 18:06:52.012 JST 2017
FRU: /BB#0/XSCFU
Msg: XSCF hang-up is detected
Date: Jan 11 20:31:31 JST 2017
Code: 80002000-007c20007811007811-019204050000000000000000
Status: Alarm Occurred: Jan 11 20:31:25.098 JST 2017
FRU: /BB#3/XBU#0/CBL#2L,/BB#3/XBU#0,/BB#0/XBU#0
Msg: XB-XB interface fatal error
XSCF>
Checking messages of the predictive self-repairing tool
Check messages of Oracle Solaris Fault Manager, the predictive self-repairing tool, operating on Oracle Solaris. Oracle Solaris Fault Manager has the following functions:
  1. Receiving telemetry information relating to an error
  2. Troubleshooting
  3. Disabling the FRU where an error occurred
  4. Turning on the LED of the FRU where an error occurred and displaying details in a system console message
Table 8-4 lists typical messages generated at error occurrence. These messages indicate that the fault has already been diagnosed. If corrective actions can be taken, it has already been taken. Also, if the system is in operation, corrective actions continue to be taken.
The messages are displayed on the console and recorded in the /var/adm/messages file.
Table 8-4  Predictive Self-repairing Messages
Displayed Output Description
EVENT-TIME: Thu Apr 19 10:48:39 JST 2012 EVENT-TIME: Diagnosis time stamp
PLATFORM: ORCL,SPARC64-X, CSN: PP115300MX, HOSTNAME: 4S-LGA12-D0 PLATFORM: Description of the server where the error occurred
SOURCE: eft, REV: 1.16 SOURCE: Information about 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: Corrective actions taken (if any) by the system to alleviate any subsequent problems
IMPACT: Automated diagnosis and response for these events will not occur. IMPACT: Description of assumed impact from the fault
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 that the system administrator needs to take
(3) Checking the FRU status
Check the system hardware configuration and status of each FRU. Table 8-5 shows the meaning of each FRU status displayed as a command execution result.
Table 8-5  FRU Status
Display Description
Normal Normal status
Faulted The unit has stopped due to a fault.
Degraded The unit has a fault somewhere but continues to operate.
Deconfigured The unit is degraded as a result of the fault or degradation of another unit.
Maintenance Maintenance work is being performed with the replacefru, addfru, or initbb command.
Checking the hardware configuration and status of each FRU
To check the hardware configuration and FRU status for the entire system, log in to the XSCF shell, and execute the showhardconf command. An asterisk (*) placed at the beginning of an output line indicates a faulty FRU.
XSCF> showhardconf
SPARC M12-2S;
+ Serial:PZ51649002; Operator_Panel_Switch:Service;
+ System_Power:On; System_Phase:Cabinet Power On;
Partition#0 PPAR_Status:Running;
BB#00 Status:Normal; Role:Master; Ver:3015h; Serial:PZ51649002;
+ FRU-Part-Number:CA20369-B17X 005AC/7341758 ;
+ Power_Supply_System: ;
+ Memory_Size:256 GB;
CMUL Status:Normal; Ver:2101h; Serial:PP164804GG ;
+ FRU-Part-Number:CA07855-D301 A5 /7341541 ;
+ Memory_Size:128 GB; Type: C ;
CPU#0 Status:Normal; Ver:4242h; Serial:00070051;
+ Freq:4.250 GHz; Type:0x30;
+ Core:12; Strand:8;
MEM#00A Status:Normal;
+ Code:ce8002M393A2K40BB1-CRC 00-31C04E6E;
+ Type:83; Size:16 GB;
MEM#01A Status:Normal;
+ Code:ce8002M393A2K40BB1-CRC 00-31C04ED1;
+ Type:83; Size:16 GB;
MEM#02A Status:Normal;
+ Code:ce8002M393A2K40BB1-CRC 00-31C0510D;
+ Type:83; Size:16 GB;
MEM#03A Status:Normal;
+ Code:ce8002M393A2K40BB1-CRC 00-31C04F51;
+ Type:83; Size:16 GB;
MEM#04A Status:Normal;
+ Code:ce8002M393A2K40BB1-CRC 00-31C04E6F;
+ Type:83; Size:16 GB;
MEM#05A Status:Normal;
+ Code:ce8002M393A2K40BB1-CRC 00-31C04F50;
+ Type:83; Size:16 GB;
MEM#06A Status:Normal;
+ Code:ce8002M393A2K40BB1-CRC 00-31C04EFB;
+ Type:83; Size:16 GB;
MEM#07A Status:Normal;
+ Code:ce8002M393A2K40BB1-CRC 00-31C051AE;
+ Type:83; Size:16 GB;
CMUU Status:Normal; Ver:2101h; Serial:PP164804GN ;
+ FRU-Part-Number:CA07855-D451 A4 /7341568 ;
+ Memory_Size:128 GB; Type: C ;
CPU#0 Status:Normal; Ver:4242h; Serial:00070043;
+ Freq:4.250 GHz; Type:0x30;
+ Core:12; Strand:8;
MEM#00A Status:Normal;
+ Code:ce8002M393A2K40BB1-CRC 00-31C04EF7;
+ Type:83; Size:16 GB;
MEM#01A Status:Normal;
+ Code:ce8002M393A2K40BB1-CRC 00-31C051AB;
+ Type:83; Size:16 GB;
MEM#02A Status:Normal;
+ Code:ce8002M393A2K40BB1-CRC 00-31C04EFD;
+ Type:83; Size:16 GB;
MEM#03A Status:Normal;
+ Code:ce8002M393A2K40BB1-CRC 00-31C04ED2;
+ Type:83; Size:16 GB;
MEM#04A Status:Normal;
+ Code:ce8002M393A2K40BB1-CRC 00-31C04EF6;
+ Type:83; Size:16 GB;
MEM#05A Status:Normal;
+ Code:ce8002M393A2K40BB1-CRC 00-31C04F57;
+ Type:83; Size:16 GB;
MEM#06A Status:Normal;
+ Code:ce8002M393A2K40BB1-CRC 00-31C04EAC;
+ Type:83; Size:16 GB;
MEM#07A Status:Normal;
+ Code:ce8002M393A2K40BB1-CRC 00-31C04EA8;
+ Type:83; Size:16 GB;
PCI#0 Name_Property:network;
+ Vendor-ID:8086; Device-ID:1521;
+ Subsystem_Vendor-ID:108e; Subsystem-ID:7b18;
+ Model:SUNW,pcie-igb;
PCI#2 Name_Property:network;
+ Vendor-ID:8086; Device-ID:1528;
+ Subsystem_Vendor-ID:108e; Subsystem-ID:7b15;
+ Model:ATO:7070007, PTO:7070005;
PCI#4 Name_Property:network;
+ Vendor-ID:8086; Device-ID:10fb;
+ Subsystem_Vendor-ID:108e; Subsystem-ID:7b11;
+ Model:X1109a-z/1109a-z;
PCI#6 Name_Property:QLGC,qlc;
+ Vendor-ID:1077; Device-ID:2532;
+ Subsystem_Vendor-ID:1077; Subsystem-ID:015d;
+ Model:QLE2562 ;
XBU#0 Status:Normal; Ver:1101h; Serial:PP164601DU ;
+ FRU-Part-Number:CA20369-B18X 004AB/7341570 ;
+ Type: C ;
XBU#1 Status:Normal; Ver:1101h; Serial:PP164601DV ;
+ FRU-Part-Number:CA20369-B18X 004AB/7341570 ;
+ Type: C ;
XSCFU Status:Normal; Ver:0101h; Serial:PP164603JA ;
+ FRU-Part-Number:CA20369-B08X 006AC/7341765 ;
+ Type: A ;
OPNL Status:Normal; Ver:0101h; Serial:PP164702EE ;
+ FRU-Part-Number:CA20365-B35X 006AC/7060922 ;
+ Type: A ;
PSUBP Status:Normal; Ver:1101h; Serial:PP164603HH ;
+ FRU-Part-Number:CA20369-B17X 005AC/7341758 ;
+ Type: C ;
PSU#0 Status:Normal; Ver:303242h; Serial:HWCD1622000551;
+ FRU-Part-Number:CA01022-0850/7334651 ;
+ Power_Status:ON; AC:200 V; Type: C ;
PSU#1 Status:Normal; Ver:303242h; Serial:HWCD1622000586;
+ FRU-Part-Number:CA01022-0850/7334651 ;
+ Power_Status:ON; AC:200 V; Type: C ;
PSU#2 Status:Normal; Ver:303242h; Serial:HWCD1622000524;
+ FRU-Part-Number:CA01022-0850/7334651 ;
+ Power_Status:ON; AC:200 V; Type: C ;
PSU#3 Status:Normal; Ver:303242h; Serial:HWCD1622000496;
+ FRU-Part-Number:CA01022-0850/7334651 ;
+ Power_Status:ON; AC:200 V; Type: C ;
FANU#0 Status:Normal; Type: C ;
FANU#1 Status:Normal; Type: C ;
FANU#2 Status:Normal; Type: C ;
FANU#3 Status:Normal; Type: C ;
FANU#4 Status:Normal; Type: C ;
FANU#5 Status:Normal; Type: C ;
FANU#6 Status:Normal; Type: C ;
FANU#7 Status:Normal; Type: C ;
HDDBP Status:Normal; Type: A ;
XSCF>
Checking for faulty FRUs
To check for faulty FRUs, log in to the XSCF shell, and execute the showstatus command. An asterisk (*) placed at the beginning of an output line indicates a faulty FRU.
XSCF> showstatus
BB#00 Status:Normal;
CMUL Status:Normal;
* MEM#00A Status:Faulted;
Checking the hardware RAID volume status
From the control domain or root domain, execute the sas2ircu command of the SAS2IRCU utility on Oracle Solaris to check for a degraded hardware RAID volume and a faulty HDD/SSD.
root# ./sas2ircu 0 display
LSI Corporation SAS2 IR Configuration Utility.
Version 17.00.00.00 (2013.07.19)
(Omitted)
------------------------------------------------------------------------

IR Volume information (*1)
------------------------------------------------------------------------

(Omitted)
IR volume 2
Volume ID : 286
Volume Name : RAID1-SYS
Status of volume : Degraded (DGD) (*2)
Volume wwid : 0aa6d102f1bf517a
RAID level : RAID1
Size (in MB) : 571250
Physical hard disks :
PHY[0] Enclosure#/Slot# : 2:0
PHY[1] Enclosure#/Slot# : 0:0

------------------------------------------------------------------------

Physical device information (*3)
------------------------------------------------------------------------

Initiator at ID #0

Device is a Hard disk
Enclosure # : 0
Slot # : 0
SAS Address : 0000000-0-0000-0000
State : Failed (FLD) (*4)
Manufacturer : TOSHIBA
Model Number : MBF2600RC
Firmware Revision : 3706
Serial No : EA25PC700855
GUID : N/A
Protocol : SAS
Drive Type : SAS_HDD
(Omitted)
*1 RAID volume information
*2 Degraded operation of the RAID volume
*3 Physical device information
*4 Indicating a fault
Checking the PCI expansion unit status
To check for faulty FRUs in the PCI expansion unit, log in to the XSCF shell and execute the showhardconf and ioxadm commands.
XSCF> showhardconf
(Omitted)
PCI#0 Status:Normal; Name_Property:pci;
+ Vendor-ID:108e; Device-ID:9020;
+ Subsystem_Vendor-ID:0000; Subsystem-ID:0000;
+ Model:;
+ Connection:2003;
PCIBOX#2003; Status:Normal; Ver:1150h; Serial:PZ21332003;
+ FRU-Part-Number:;
IOB Status:Normal; Serial:PP133001CW ;
+ FRU-Part-Number:CA20365-B66X 020AM/7061033 ;

LINKBOARD Status:Normal; Serial:PP140801Z8 ;
+ FRU-Part-Number:CA20365-B60X 009AD/7061035 ;

PCI#11 Name_Property:pci;
+ Vendor-ID:104c; Device-ID:8231;
+ Subsystem_Vendor-ID:0000; Subsystem-ID:0000;
+ Model:;
FANBP Status:Normal; Serial:PP13310038 ;
+ FRU-Part-Number:CA20365-B68X 005AD/7061025 ;

PSU#0; Status:Normal; Serial:FEJD1245001507;
+ FRU-Part-Number:CA01022-0750-D/7060988 ;
* PSU#1; Status:Faulted; Serial:FEJD1245001483; (*1)
+ FRU-Part-Number:CA01022-0750-D/7060988 ;
FAN#0; Status:Normal;
FAN#1; Status:Normal;
FAN#2; Status:Normal;
(Omitted)
*1 Failed
XSCF> ioxadm -v list
Location Type FW Ver Serial Num Part Num State
PCIBOX#2003 PCIBOX - PZ21332003 On
PCIBOX#2003/PSU#0 PSU - FEJD1245001507 CA01022-0750-D/7060988 On
PCIBOX#2003/PSU#1 PSU - FEJD1245001483 CA01022-0750-D/7060988 Off
(*1)
PCIBOX#2003/IOB IOBOARD 1150‍ ‍‍PP133001CW CA20365-B66X 020AM/7061033 On
PCIBOX#2003/LINKBD BOARD - PP140801Z8 CA20365-B60X 009AD/7061035 On
PCIBOX#2003/FANBP FANBP - PP13310038 CA20365-B68X 005AD/7061025 On
BB#00-PCI#00 CARD 1150 PP123300S8 CA20365-B59X 001AA On
*1 Stopped

Top of Page