Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1011431.1
Update Date:2011-05-16
Keywords:

Solution Type  Technical Instruction Sure

Solution  1011431.1 :   Troubleshooting Sun StorEdge[TM] 33x0/351x Hardware  


Related Items
  • Sun Storage 3510 FC Array
  •  
  • Sun Storage 3310 Array
  •  
  • Sun Storage 3511 SATA Array
  •  
  • Sun Storage 3320 SCSI Array
  •  
Related Categories
  • GCS>Sun Microsystems>Storage - Disk>Modular Disk - 3xxx Arrays
  •  

PreviouslyPublishedAs
215672


Applies to:

Sun Storage 3310 Array
Sun Storage 3320 SCSI Array
Sun Storage 3510 FC Array
Sun Storage 3511 SATA Array
All Platforms

Goal

Troubleshooting Sun StorEdge[TM] 33x0/351x Hardware

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community - Storage Disk 3000 Series RAID Arrays

Solution

Symptoms

  • show fru shows failed components
  • Controller/IOM, disk, power, battery, cable, jbod failures
  • Errors in eventlog
  • Audible alarms and/or amber LED's
  • Drive Missing,Used or Bad
  • Performance issue
  • Environmental(temperature or voltage) issues
  • Offlined device paths
  • Redundant path failure on 351x
  • Logical Drive initialization/rebuild/expansion hangs or fails
  • Firmware upgrade/crossload failures
  • Controller amber or hung
  • Cache issues

Troubleshooting Steps

NOTE
This is a sub-set of <Document: 1005313.1> :Troubleshooting Sun StorEdge[TM] 33x0/351x Configurations. For troubleshooting a 3120 JBOD, refer to <Document: 1002790.1> :Troubleshooting Sun StorEdge [TM] 3120/33x0/351x JBOD Failures.

Step 1. Verify that all hardware components are 'OK' for Fru Status by using the sccli> sh fru command.

Example:
sccli> sh fru
7 FRUs found in chassis SN#000F26 at ch 2 id 12

Name: FC_CHASSIS_BKPLN
Description: SE3510 FC Chassis/backplane
Part Number: 370-5535
Serial Number: 000Fxx
Revision: 01
Initial Hardware Dash Level: 01
FRU Shortname: 370-5535-01
Manufacturing Date: Wed Jan 29 22:23:50 2003
Manufacturing Location: Milpitas,CA,USA
Manufacturer JEDEC ID: 0x0301
FRU Location: FC MIDPLANE SLOT
Chassis Serial Number: 000Fxx
FRU Status: OK

Name: FC_RAID_IOM
Description: SE3510 I/O w/SES + RAID Cont 1GB
Part Number: 370-5537
Serial Number: 0006xx
Revision: 04
Initial Hardware Dash Level: 04
FRU Shortname: 370-5537-04
Manufacturing Date: Wed Sep 17 05:36:35 2003
Manufacturing Location: Milpitas California, USA
Manufacturer JEDEC ID: 0x0301
FRU Location: UPPER FC RAID IOM SLOT
Chassis Serial Number: 000Fxx
FRU Status: OK

Name: BATTERY_BOARD
Description: SE3510 Hot Swap Battery Module
Part Number: 370-5545
Serial Number: 0005xx
Revision: 01
Initial Hardware Dash Level: 01
FRU Shortname: 370-5545-01
Manufacturing Date: Thu Feb 6 02:47:21 2003
Manufacturing Location: Milpitas,CA,USA
Manufacturer JEDEC ID: 0x0301
FRU Location: UPPER BATTERY BOARD SLOT
Chassis Serial Number: 000Fxx
FRU Status: Expired

Name: AC_POWER_SUPPLY
Description: Minnow AC PWR SUPPLY/FAN Mod
Part Number: 370-5398
Serial Number: 0065xx
Revision: 01
Initial Hardware Dash Level: 01
FRU Shortname: MN2-PUM-AC-02
Manufacturing Date: Thu Dec 12 17:44:07 2002
Manufacturing Location: Irvine California, USA
Manufacturer JEDEC ID: 0x048F
FRU Location: RIGHT AC PSU SLOT #1 (RIGHT)
Chassis Serial Number: 000Fxx
FRU Status: OK

Name: AC_POWER_SUPPLY
Description: Minnow AC PWR SUPPLY/FAN Mod
Part Number: 370-5398
Serial Number: 0065xx
Revision: 01
Initial Hardware Dash Level: 01
FRU Shortname: MN2-PUM-AC-02
Manufacturing Date: Thu Dec 12 17:38:51 2002
Manufacturing Location: Irvine California, USA
Manufacturer JEDEC ID: 0x048F
FRU Location: AC PSU SLOT #0 (LEFT)
Chassis Serial Number: 000Fxx
FRU Status: OK

Name: FC_RAID_IOM
Description: SE3510 I/O w/SES + RAID Cont 1GB
Part Number: 370-5537
Serial Number: 0031xx
Revision: 04
Initial Hardware Dash Level: 04
FRU Shortname: 370-5537-04
Manufacturing Date: Thu Sep 11 14:27:35 2003
Manufacturing Location: Milpitas California, USA
Manufacturer JEDEC ID: 0x0301
FRU Location: LOWER FC RAID IOM SLOT
Chassis Serial Number: 000Fxx
FRU Status: OK

Name: BATTERY_BOARD
Description: SE3510 Hot Swap Battery Module
Part Number: 370-5545
Serial Number: 0038xx
Revision: 01
Initial Hardware Dash Level: 01
FRU Shortname: 370-5545-01
Manufacturing Date: Thu May 29 06:05:53 2003
Manufacturing Location: Milpitas,CA,USA
Manufacturer JEDEC ID: 0x0301
FRU Location: LOWER BATTERY BOARD SLOT
Chassis Serial Number: 000Fxx
FRU Status: Expired

Step 2.  Physically verify that all hardware components are present  by comparing results of output from step 1 above to a visual inspection.

Step 3.  Check eventlog to confirm there are no FRU failures with the 'show event' command(for 3.x firmware) or  show persistent (for 4.x firmware or later).

Example:
sccli> sh event
Thu Feb 8 16:38:05 2007
[Primary] Notification
Controller Initialization Completed

Thu Feb 8 16:38:05 2007
[Secondary] Notification
Controller Initialization Completed

Tue Mar 6 21:11:23 2007
[Secondary] Notification
Controller BBU is Charging !

Wed Mar 7 00:21:13 2007
[Secondary] Notification
NOTICE: Controller BBU Fully Charged !

Wed Mar 7 11:43:55 2007
[Primary] Notification
Controller BBU is Charging !

Wed Mar 7 15:27:52 2007
[Primary] Notification
NOTICE: Controller BBU Fully Charged !

Wed Mar 7 15:27:54 2007
[Primary] Notification
Controller BBU is Charging !

Wed Mar 7 15:27:58 2007
[Primary] Notification
NOTICE: Controller BBU Fully Charged !

Wed Mar 7 15:28:00 2007
[Primary] Notification
Controller BBU is Charging !

Wed Mar 7 15:28:01 2007
[Primary] Notification
NOTICE: Controller BBU Fully Charged !

Sun Apr 8 01:38:47 2007
[Secondary] Notification
Controller BBU is Charging !

Sun Apr 8 04:47:57 2007
[Secondary] Notification
NOTICE: Controller BBU Fully Charged !

Sun Apr 8 04:47:59 2007
[Secondary] Notification
Controller BBU is Charging !

Sun Apr 8 04:48:00 2007
[Secondary] Notification
NOTICE: Controller BBU Fully Charged !

Mon Apr 9 10:29:57 2007
[Primary] Notification
Controller BBU is Charging !

Mon Apr 9 14:12:52 2007
[Primary] Notification
NOTICE: Controller BBU Fully Charged !

If eventlog and sh fru do not indicate a hardware problem, refer back to step 6 in <Document: 1005313.1> :Troubleshooting StorEdge[TM] 33x0/351x Configuration.

Step 4. Based on the sh fru and/or eventlog information, refer to the appropriate document depending on the failed, absent or missing component.

  • Controller/IOM problems refer to <Document: 1002641.1> :Troubleshooting StorEdge [TM] 33x0/351x Controller Failures
  • Disk Failures refer to <Document: 1008190.1> :Troubleshooting Sun StorEdge [TM] 33x0/351x Disk Failures
  • 351x Loop problems refer to <Document: 1006856.1> :Troubleshooting Sun StorEdge [TM] 351x redundant loop failures
  • Battery problems refer to <Document: 1008188.1> :Troubleshooting Sun StorEdge [TM] 33x0/351x Battery Problems
  • Power supply problems refer to <Document: 1012984.1> :Troubleshooting Sun StorEdge [TM] 33x0/351x Power Supply Problems
  • JBOD problems refer to <Document: 1002790.1> :Troubleshooting Sun StorEdge [TM] 33x0/3120/351x JBODs

Step 5. Verify cabling.

  • For 351x refer to <Document: 1008193.1> :Troubleshooting Sun StorEdge [TM] 351x Cabling
  • For 33x0 refer to <Document: 1006857.1> :Troubleshooting Sun StorEdge [TM] 33x0/3120 Cabling

Step 6. For any audible alarm, refer to The Sun StorEdge 3000 Family Installation, Operation, and Service Manual, Appendix C. For amber LED's, refer to Checking LEDs Chapter 6.

Step 7. If hardware fault persists gather the latest explorer information and escalate appropriately.

Step 8. If no problems found during this procedure please refer back to <Document: 1005313.1> :Troubleshooting Sun StorEdge[TM] 33x0/351x Configurations.



Internal Comments

This document contains normalized content and is managed by the the Domain Lead(s) of
the respective domains. To notify content owners of a knowledge gap contained in this
document, and/or prior to updating this document, please contact the domain engineers
that are managing this document via the “Document Feedback” alias(es) listed below:

storage-os-disk-low-domain@sun.com

The Knowledge Work Queue for this article is KNO-STO-VOLUME_DISK
JBOD, fru, fru status, eventlog, battery, power supply, cable, LED, loop, troubleshooting,
3510, 3511, 3310, 3320, JBOD, audited

Previously Published As
89034

Change History
Date: 2007-12-11
User Name: 29589
Action: Approved


Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback