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

PLA-Support>Sun Systems>DISK>Arrays>SN-DK: SE31xx_33xx_35xx
 
_Old GCS Categories>Sun Microsystems>Storage - Disk>Modular Disk - 3xxx Arrays
 

Applies to:

Purpose

This document addresses various problems that may arise for the following arrays:

• Sun Storage 3310 Array
• Sun Storage 3320 Array
• Sun Storage 3510 Array
• Sun Storage 3511 Array

Troubleshooting information is provided to help resolve these issues:

• Fatal Drive Failure
• Lun filtering/mapping misconfiguration on 3510 or 3511
• Unable to access Logical Drive
• Failed or degraded Logical Drive
• Offlined device path
• Logical Drive initialization/rebuild/expansion hangs or fails
• Firmware upgrade/crossload failures

This is a sub-set of <Document 1009557.1> Troubleshooting Fibre Channel Devices from the Solaris Operating System and <Document 1008191.1> Sun StorageTek 33x0 SCSI Array: Troubleshooting SCSI Devices from the Operating System.

Troubleshooting Steps

Please validate that each troubleshooting step below is true for your environment. The steps will provide instructions or a link to a document, for validating the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step.

Step 1: Verify the array can be accessed via telnet or sccli. Refer to <Document 1012660.1> Sun Storage 3000 and T3 Arrays: Troubleshooting Serial and Network Management Port Connections.

Step 2: Verify the correct 3510 or 3511 array is being accessed by comparing the output of sccli> show port with the WWN recorded (luxadm -e dumpmap <device>) in step 2 of <Document 1009556.1> How to verify connectivity on Oracle/Sun Branded Host Bus Adaptors (HBAs).

Example:

For the 3310 and 3320, refer to <Document 1005314.1> Sun Storage 33x0 SCSI Array: How to verify SCSI HBA Connectivity.

Step 3: Verify that the logical drive is healthy.

Example:

If status of the logical drive is FATAL FAIL, refer to the section entitled "Recovering From Fatal Drive Failure" in the Sun StorEdge[TM] 3000 Family Installation, Operation and Service Manual for your product, to be found in Oracle Disk Storage Systems Documentation.

Step 4: If Logical Drive state is DEGRADED or FAILED_DRV, verify that there are no hardware failures on the array by referring to <Document 1011431.1> Troubleshooting Sun Storage 3000 Array Series Hardware.

Step 5: Verify array configuration parameters are correct. See the appendix entitled "Parameter Summary Tables for Default Settings" in the Sun StorEdge 3000 Family RAID Firmware User's Guide, to be found in Oracle Disk Storage Systems Documentation.

Step 6: Additionally, See <Document 1009716.1> Sun Storage 3000 Arrays: Steps to Verify Configuration Parameter Settings.

Step 7: Verify channels settings are correct. Refer to the section entitled "Channel Settings" for your array in the Sun StorEdge 3000 Family RAID Firmware User's Guide, to be found in Oracle Disk Storage Systems Documentation.

Step 8: For the 3510 and 3511, if using lun filtering/mapping, verify filtering/mapping is set correctly by referring to <Document 1009196.1> Sun StorEdge 3510: How to Map Partitions to Multiple Hosts in a SAN Using Host Filters.

Step 9: If the device is still not able to be seen by the OS, verify that all the correct patches and packages are loaded by referring to <Document 1001781.1> Sun StorEdge[TM] A5x00, T3, 6120,33xx,351xFC,A3500FC Arrays: Disk Firmware/Patch Matrix Summary.

Step 10: At this point, if you have validated that each troubleshooting step above is true for your environment and problems with the configuration persist, further troubleshooting is required. Gather output from the latest Sun Explorer and call Oracle Support. Include configuration topology. If the array is attached to a switch, please run Explorer with the following option:

References

This solution has no attachment