Troubleshooting Sun Storage 3000 Array Series Hardware

Asset ID:	1-71-1011431.1
Update Date:	2017-03-20
Keywords:

Solution Type Technical Instruction Sure

Solution 1011431.1 : Troubleshooting Sun Storage 3000 Array Series Hardware

Applies to:

Sun Storage 3310 Array - Version Not Applicable and later
Sun Storage 3510 FC Array - Version Not Applicable and later
Sun Storage 3511 SATA Array - Version Not Applicable and later
Sun Storage 3320 SCSI Array - Version Not Applicable and later
All Platforms

Goal

This document provides troubleshooting information for the following arrays:

Sun Storage 3310
Sun Storage 3320
Sun Storage 3510
Sun Storage 3511

Solution

Symptoms

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

Troubleshooting Steps

This is a sub-set of <Document 1005313.1> Sun Storage 3000 Arrays: Troubleshooting Configuration Problems.
For troubleshooting a 3120 JBOD, refer to <Document 1002790.1> Sun Storage 3000 Arrays: Troubleshooting 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 the results of output from step 1 above to a visual inspection.

Step 3. Check the array eventlog to confirm there are no FRU failures with the sccli '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 the eventlog and sh fru do not indicate a hardware problem, refer back to step 6 in <Document 1005313.1> Sun Storage 3000 Arrays: Troubleshooting Configuration Problems.

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> Sun Storage 3000 Arrays: Troubleshooting Controller Problems
Disk Failures refer to <Document 1008190.1> Sun Storage 3000 Arrays: Troubleshooting Disk Failures
351x Loop problems refer to <Document 1006856.1> Sun Storage 3510 and 3511 Arrays: Troubleshooting Redundant Loop Failures
Battery problems refer to <Document 1008188.1> Sun Storage 3000 Arrays: Troubleshooting Battery Problems
Power supply problems refer to <Document 1012984.1> Sun Storage 3000 Arrays: Troubleshooting Power Supply Problems
JBOD problems refer to <Document 1002790.1> Sun Storage 3000 Arrays: Troubleshooting JBOD Failures

Step 5. Verify cabling.

For 351x refer to <Document 1008193.1> Sun Storage 3510 and 3511 Arrays: Troubleshooting the Cabling
For 33x0 refer to <Document 1006857.1> Verifying and Troubleshooting Sun Storage 3120, 3310 and 3320 Cabling

Step 6. For any audible alarms, 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 a hardware fault persists, gather the latest explorer information and engage Oracle support for assistance.

Step 8. If no problems are found during this procedure, please refer back to <Document 1005313.1> Sun Storage 3000 Arrays: Troubleshooting Configuration Problems.

Do you still have questions? You can use My Oracle Support Communities. Communities put you in touch with industry professionals like yourself. They are monitored by Oracle support engineers, so you can expect reliable and correct answers. Ask questions and see what others are asking about in the Disk Storage 2000, 3000, 6000 RAID Arrays & JBODs Community.

Internal Comments

Previously Published As
89034

References

<NOTE:1002641.1> - Sun Storage 3000 Arrays: Troubleshooting Controller Problems
<NOTE:1006856.1> - Sun Storage 3510 and 3511 Arrays: Troubleshooting Redundant Loop Failures
<NOTE:1008190.1> - Sun Storage 3000 Arrays: Troubleshooting Disk Failures
<NOTE:1005313.1> - Sun Storage 3000 Arrays: Troubleshooting Configuration Problems
<NOTE:1002790.1> - Sun Storage 3000 Arrays: Troubleshooting JBOD Failures
<NOTE:1008188.1> - Sun Storage 3000 Arrays: Troubleshooting Battery Problems
<NOTE:1008193.1> - Sun Storage 3510 and 3511 Arrays: Troubleshooting the Cabling
<NOTE:1012984.1> - Sun Storage 3000 Arrays: Troubleshooting Power Supply Problems

Attachments

This solution has no attachment