| Asset ID: |
1-75-1018272.1 |
| Update Date: | 2010-07-01 |
| Keywords: | |
Solution Type
Troubleshooting Sure
Solution
1018272.1
:
Troubleshooting Sun StorageTek[TM] T3, T3+ and 6120 Arrays
| Related Items |
- Sun Storage T3+ Array
- Sun Storage T3 Array
- Sun Storage 6120 Array
|
| Related Categories |
- GCS>Sun Microsystems>Storage - Disk>Modular Disk - Other
- GCS>Sun Microsystems>Storage - Disk>Modular Disk - 6xxx Arrays
|
PreviouslyPublishedAs
229673
Applies to:
Sun Storage T3+ Array
Sun Storage T3 Array
Sun Storage 6120 Array - Version: Not Applicable to Not Applicable [Release: NA to NA]
All Platforms
Purpose
This document is intended to provide a
basic overview on how to determine general array component health. If
there are problems with a component identified, you will be directed to
another document specific to the component in question.
Symptoms: -
Fru stat shows failed components
-
controller, disk, power, loop card failures
-
errors in syslog
Please validate that each troubleshooting step below is true for your
environment. Each step will provide instructions via 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.
Last Review Date
June 14, 2010
Instructions for the Reader
A Troubleshooting Guide is provided to assist
in debugging a specific issue. When possible, diagnostic tools are included in the document
to assist in troubleshooting.
Troubleshooting Details
1.
Verify that you can log into your array.
Use any telnet client to log into your array as the root user.
If you cannot connect or log into
your array, reference <Document 1012660.1> Troubleshooting Sun StorEdge[TM] T3, T3+ and 6120
Access Problem.
If you are successful at logging into your array, continue to
Step 2.
2. Verify that all hardware is ready for STATUS
and enabled for STATE by using the fru stat command.
Example:
storage-t3b:/:<8>fru stat
CTLR STATUS STATE ROLE PARTNER TEMP
------ ------- ---------- ---------- ------- ----
u1ctr ready enabled master u2ctr 31
u2ctr ready enabled alt master u1ctr 30
DISK STATUS STATE ROLE PORT1 PORT2 TEMP VOLUME
------ ------- ---------- ---------- --------- --------- ---- ------
u1d01 ready enabled data disk ready ready 34 v2
u1d02 ready enabled data disk ready ready 38 v2
u1d03 ready enabled data disk ready ready 36 v2
u1d04 ready enabled data disk ready ready 37 v2
u1d05 ready enabled data disk ready ready 39 v1
u1d06 ready enabled data disk ready ready 41 v1
u1d07 ready enabled data disk ready ready 36 v1
u1d08 ready enabled data disk ready ready 38 v1
u1d09 ready enabled standby ready ready 29 v1
u2d01 ready enabled data disk ready ready 39 v4
u2d02 ready enabled data disk ready ready 40 v4
u2d03 ready enabled data disk ready ready 37 v4
u2d04 ready enabled data disk ready ready 39 v4
u2d05 ready enabled data disk ready ready 32 v3
u2d06 ready enabled data disk ready ready 37 v3
u2d07 ready enabled data disk ready ready 39 v3
u2d08 ready enabled data disk ready ready 41 v3
u2d09 ready enabled standby ready ready 31 v3
LOOP STATUS STATE MODE CABLE1 LB CABLE2 LB TEMP
------ ------- ---------- ------- --------- -- --------- -- ----
u1l1 ready enabled master - - installed 11 27
u1l2 ready enabled slave - - installed 10 33
u2l1 ready enabled master installed 11 - - 28
u2l2 ready enabled slave installed 10 - - 32
POWER STATUS STATE SOURCE OUTPUT BATTERY TEMP FAN1 FAN2
------ ------- --------- ------ ------ ------- ------ ------ ------
u1pcu1 ready enabled line normal normal normal normal normal
u1pcu2 ready enabled line normal normal normal normal normal
u2pcu1 ready enabled line normal normal normal normal normal
u2pcu2 ready enabled line normal normal normal normal normal
NOTE: There are four areas in the fru stat output: CLTR, DISK, LOOP, and POWER.
Based on the output, refer to the appropriate article, depending on
the part or section in question.
- For Controller (CLTR Section) problems refer to <Document 1005177.1> T3 controller failures.
- For Disk (DISK Section) problems, refer to <Document 100974.1> Troubleshooting Sun StorEdge[TM] T3, T3+ and 6120 Disk Failures.
- For Loop Card (LOOP Section) problems, refer to <Document 1018190.1> T3 loop card failures.
- For Power Cooling Unit (POWER Section) problems, refer to <Document 1123923.1> Troubleshooting Sun StorEdge[TM] T3, T3+ and 6120 Power Cooling Unit Faults.
- If none of the sections shows a fault, continue to Step 3.
3. Check the array syslog to confirm whether there are any
hardware based messages that may indicate a system fault.
The syslog may be viewed by using more syslog, if logged
into the array. We suggest reviewing the system log over the
past 6-8 weeks.
Check for warning or error messages over the last 4 weeks. These
are easily identified by the : W: or : E: in the log.
For example:
Jan 09 18:27:09 array00 ISR1[1]: W: u1ctr ISP2300[2]
Received LOOP DOWN async event.
Messages may correlate to a seen or an, as yet, undiscovered array
issue.
If there are :W: or
:E: messages in the log, continue to Step 4.
Otherwise, you have verified that the system is healthy.
For more information on messages, reference:
<Document 1001873.1> Sun StorEdge[TM] T3 Array: Understanding Sense Key Errors (Disk Failures); Clearing Disk Errors Using Vol Verify; Performing a Single-Drive Read Operation.
<Document 1007340.1> Sun StorEdge[TM] T3 Syslog Abbrevations and Useful references.
4. Collect a Solaris explorer and open a call with Oracle.
# /opt/SUNWexplo/explorer -w !default,t3extended
Attachments
This solution has no attachment
