Diagnosing performance problems on Sun StorEdge[TM] T3 array

Asset ID:	1-75-1002464.1
Update Date:	2009-04-20
Keywords:

Solution Type Troubleshooting Sure

Solution 1002464.1 : Diagnosing performance problems on Sun StorEdge[TM] T3 array

Related Items


Sun Storage T3 Array

Related Categories


GCS>Sun Microsystems>Storage - Disk>Modular Disk - Other

PreviouslyPublishedAs
203437

Description
In order to provide you the most accurate fix, please validate that each statement under the symptoms below is true for your environment. These symptoms will hyperlink you into a relevant content that will 1) tell you how to validate the listed symptom and 2) how to fix the symptom if it is true for your environment. The listed symptoms are ordered in the most appropriate sequence to isolate the issue and be certain about the related fix. Please do not skip a step.

Purpose: This document will confirm that the setting on the Sun StorEdge[TM] T3 are correct and that there are no hardware failures on the T3 that could be causing a T3 performance problem.

Symptoms:

- poor performance

- slow

Steps to Follow
Diagnosing performance problems on Sun StorEdge[TM] T3 array

1. Identify which T3 device(s) is slow.

NOTE: If using volume management software (ie. VxVM or LVM), verify that the virtual volume is optimal.

2. Verify cache is 'writebehind.' Log into T3 and run the command "vol mode."

Example:

     storage-t3b:/etc:<28>vol mode
volume         mounted 
cache
        mirror
v1             yes     
writebehind
  on
v3             yes     
writebehind
  on

3. If cache is 'writethrough', verify that cache is set to either 'auto' or 'writebehind' in "sys list" command.

Example:

     storage-t3b:/:<6>sys list
controller         : 2.0
blocksize          : 64k
cache              : auto
mirror             : auto
mp_support         : rw
naca               : off
rd_ahead           : off
recon_rate         : med
sys memsize        : 128 Mbytes
cache memsize      : 1024 Mbytes
enable_volslice    : on
fc_topology        : auto
fc_speed           : 1Gb
disk_scrubber      : on
ondg               : befit

4. If it is not set to 'auto' or 'writebehind', set it to 'auto' with "sys cache auto" command.

Example:

     storage-t3b:/:<7>sys cache auto

5. Verify cache is 'writebehind' with the "vol mode" command.

6. If the cache is still 'writethrough', then there may be a hardware problem. Refer to <Document: 1018272.1> : "Troubleshooting Sun StorEdge[TM] T3 Hardware" to troubleshoot possible T3 hardware problems.

7. If the cache is 'writebehind' and any hardware problems have been resolved, then the performance problem is most likely not a T3 array problem and further investigation is needed.

Product
Sun StorageTek T3+ Array Controller FW 2.1
Sun StorageTek T3 Array

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:

[email protected]

The Knowledge Work Queue for this article is KNO-STO-MIDRANGE_DISK

Place Sun Internal-Use Only content here. This content will be
published to internal SunSolve[SM] only.

t3, t3+, performance, cache, writebehind, writethrough, Audited
Previously Published As
86542

Change History
Date: 2007-11-13
User Name: 7058
Action: Approved
Comment: Link to 86681 was pointing to internal sunsolve2 server. Fixed.
Version: 7
Version: 0
Date: 2006-08-18
User Name: 7058
Action: Approved
Comment: Format reworked. Cross-references redone.
Spell ck OK. Trademarking done.
OK to publish.
Version: 3
Date: 2006-08-18
User Name: 78962
Action: Approved
Comment: normalized doc...
Version: 0
Date: 2006-08-07
User Name: 88218
Action: Approved
Comment: t3 norm group
Version: 0

Attachments

This solution has no attachment