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

Asset ID:	1-75-1005313.1
Update Date:	2011-05-16
Keywords:

Solution Type Troubleshooting Sure

Solution 1005313.1 : Troubleshooting Sun StorEdge[TM] 33x0/351x Configurations

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
207422

Description

Symptoms:

-Fatal Drive Failure

-Lun filtering/mapping mis-configuration on 351x

-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

Purpose/Scope:

NOTE: This is a sub-set of Troubleshooting <Document: 1009557.1> Troubleshooting Fibre Channel Devices from the OS and <Document: 1008191.1> Troubleshooting SCSI Devices from the OS. The steps below will help determine if there is a 33x0/351x issue.

Steps to Follow

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

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.

NOTE: All Troubleshooting to verify the Array Status can be done via sccli, telnet GUI or serial connection.

Step 1 - Verify the array can be accessed via telnet or sccli
Refer to <Document: 1012660.1> Can't Connect to Sun StorEdge[TM] array via Ethernet.

Step 2 - Verify the correct 351x is being accessed by comparing the output of "show port " with the WWN recorded (luxadm -e dumpmap <device>) in step 2 of <Document: 1009556.1> How to verify HBA Connectivity.
Example:

sccli> sh port
Ch  Id   WWPN
-------------------------
 0  40   216000C0FF800F26
 1  42   226000C0FFA00F26
 4  44   256000C0FFC00F26
 5  46   266000C0FFE00F26

For the 33x0, 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:

sccli> sh log
LD    LD-ID        Size  Assigned  Type   Disks Spare  Failed Status
------------------------------------------------------------------------
ld0   4CBFBA6F 235.68GB  Primary   RAID0  7     0      0      Good
Write-Policy Default          StripeSize 128KB

If status of the logical drive is DEAD or FATAL FAIL, refer to section 9.5 of Sun StorEdge[TM] 3000 Family Installation, Operation, and Service Manual

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 StorEdge[TM] 33x0/351x Hardware"

Step 5 - Verify array configuration parameters are correct. See Appendix B , Parameter Summary Tables for Default Settings in Sun StorEdge 3000 Family RAID Firmware User's Guide.

Step 6 - Additionally, See <Document: 1009716.1> Sun StorEdge [TM] 33x0/351x Configuration Parameter Settings

Step 7 - Verify channels settings are correct. For the 33x0, refer to Chapter 4 Channel Settings for SCSI, for 351x refer to Chapter 5 Channel Settings for Fibre in the Firmware User's Guide

Step 8 - For 351x, if using lun filtering/mapping, verify filtering/mapping is set correctly by referring to <Document: 1009196.1> How to Map multiple partitions on 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,351FC,A3500FC arrays: Disk Firmware/Patch Matrix Summary

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

# explorer -v -w default,sanextended -w default,se3kextended

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:

Domain Lead: [email protected]
Feedback Alias: [email protected]

3310, 3510, 3320, drive, lun filter, crossload, path, normalized
Previously Published As
89031

Change History
Date: 2007-08-23
User Name: 7058
Action: Approved
Comment: Fixed links.
Version: 4
Date: 2007-08-23
User Name: 7058
Action: Update Started
Comment: links are pointing to internal sunsolve server.
Comment: Only one hinging document is still awaiting publish.
I'm going ahead with publication of this one.

Notes for Normalizaton:
Subset of: 89050
Subset Root path:
89031-->89050
References: 43212, 89038, 79546, 89051, 89034, 86488*, 86520, 86541
Project: Minnow Normalization

Attachments

This solution has no attachment