3. Verify that all volumes are mounted using the vol stat command.

Volumes must be mounted to supply data access.  The example below shows that volume v1 is inaccessible.

storage-t3b:/:<1>vol stat
v1: unmounted
 u1d05: mounted
 u1d06: mounted
 u1d07: mounted
 u1d08: mounted
 Standby: u1d09: mounted
v3: mounted     
 u2d05: mounted
 u2d06: mounted
 u2d07: mounted
 u2d08: mounted
 Standby: u2d09: mounted

• If the vol mount succeeds, and this is a T3, proceed to Step 8.
• If the vol mount succeeds, and this is a T3+, running 2.x firmware, proceed to Step 5.
• If the vol mount succeeds, and this is a T3+ running 3.x firmware or a 6120, proceed to Step 6.
• If the vol mount fails, continue to Step 4.

 4.  Verify whether drives have failed within the same volume.

The vol mount command will list the drives that make up the volume.  Use the fru stat command to check the state and status of the drives.  The drives, if optimal, will be listed as ready enabled.

• If there are one or more drives in a state/status other than ready enabled, reference <Document: 1009745.1>  Troubleshooting Sun StorEdge[TM] T3, T3+, and 6120 Disk Faults.

• If all the drives in the volume are optimal, proceed to Step 8.

storage-t3b:/:<1>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

• If enable_volslice is on, continue to Step 6.
• Otherwise, go to Step 8.

• If there are no volume slices, then you will need to create them.  Data access will not be available without using the vol slices, as indicated by your array model and firmware revision.

• If there are vol slices, continue to Step 7.

storage-t3b:/:<27>lun perm list
lun    slice   WWN       GroupName      GroupPerm      WWNPerm  EffectivePerm                            
-----------------------------------------------------------------------------------
0       0       default     --              --              none   none
1       1       default     --              --              none   none
1       1 210000e08b09b58c ralph          none               rw     rw

Make sure that the WWN for the slice in the output matches the Port WWN from your 
HBA.  The EffectivePerm field should be rw, for this HBA. 

• If either the WWN or Effective Perm is not set correctly, use the lun perm command to set it correctly.

Reference Sun StorEdge[TM] 6020 and 6120 Arrays System Manual
Reference Sun StorEdge[TM] T3+ Administrator's Manual, Firmware 2.1 Controller Firmware

• If the permissions are correct, then proceed to Step 8.

Note:  Changes to the lun permissions may require action at the server level.

8.  Verify the host port status on the array.

Use the port list command to show the status of the Fibre Channel(FC) port on each RAID controller.


storage-t3b:/:<1>port list
port   targetid   addr_type   status   host   wwn
u1p1      1        hard       online   sun    50020f230000c21e
u2p1      2        hard       online   sun    50020f23000035df

• If the status is offline, there is a connection problem between the array port and the HBA or FC Switch.
• Otherwise, continue to Step 9.

9.  Contact Oracle for support

Please collect a Solaris explorer and contact Oracle support.  It is recommended that you collect the
data from the host that cannot access the array, by running:

/opt/SUNWexplo/explorer -w default,t3extended

This will collect both the connectivity data from the host side, as well as the array data collection.




 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+, lun masking, failed components, vol stat, Audited


 Previously Published As


 86682


 Change History


 Publishing Information


 Date: 2007-11-13


 User Name: 7058


 Action: Approved


 Comment: Internal link referenced in external section.  Fixed.


 Version: 6