Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1006725.1
Update Date:2009-04-27
Keywords:

Solution Type  Technical Instruction Sure

Solution  1006725.1 :   Verify LUN Masking Settings  


Related Items
  • Sun Storage T3 Array
  •  
  • Sun Storage T3+ Array
  •  
Related Categories
  • GCS>Sun Microsystems>Storage - Disk>Modular Disk - Other
  •  

PreviouslyPublishedAs
209368


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.

Symptoms:

- Lun permissions

- Can't see devices



Steps to Follow
Verify LUN Masking Settings

NOTE:  This technical instruction is a sub-set of <Document: 1012673.1> : "Troubleshooting Sun StorEdge[TM] T3 Configuration." The steps below will help verify and resolve LUN masking problems.

Troubleshooting:

1.  Verify that enable_volslice is  "on" with "sys list"command.

     Example:

     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

2.  If enable_volslice is "on", then verify the slices are set correctly with the "lun perm list" command.  The WWN for the slice in "lun perm list" matches the Port ID WWN from the HBA (luxadm -e dump_map) and the Effective Perm in "lun perm list" is 'rw'.

     Example:

     # luxadm -e dump_map
devices/pci@1f ,0/pci@1/SUNW,qlc@3/fp@0,0:devctl Pos AL_PA ID Hard_Addr Port WWN Node WWN Type 0 1 7d 0 210000e08b09b58c 200000e08b09b58c 0x1f (Unknown Type,Host Bus Adapter) 1 e4 2 e4 50020f23000035df 50020f20000035df 0x0 (Disk device)

     NOTE:  The HBA for the specified device path will be indicated by the Type (Unknown Type, Host Bus Adapter).

     storage-t3b:/:<27>lun perm list
     lun     slice   WWN                     Group Name      Group Perm      WWN PermEffective Perm
     -----------------------------------------------------------------------------------------------------
     0       0       default                 --              --              none   none
     1       1       default                 --              --              none   none
     1       1       
210000e08b09b58c
        ralph           none            rw     
rw

     -----------------------------------------------------------------------------------------------------

3.  If either WWN or Effective Perm is not set correctly, then use "lun perm" command to map it to the correct HBA and/or give the correct permissions.

     Example:

     # lun map lun 0 rw wwn 210000e08b09b58c

4.  Verify the devices are configured on the host with the " cfgadm -lao show_FCP_dev" command.

      Example:

     # cfgadm -lao show_FCP_dev
Ap_Id                          Type         Receptacle   Occupant     Condition
c1                             fc-private   connected    configured   unknown

c1::50020f23000035df,0         disk         connected    configured   unknown

     c1::50020f23000035df,1         disk         connected    configured   unknown
c2                             fc           connected    unconfigured unknown

5.  If Occupant is "unconfigured", then run "cfgadm -c configure <c#::#>" and verify the state has changed to  configured. 

      Example:

     # cfgadm -c configure c1::50020f23000035df,0

5.  On the host, run  devfsadm  to build the device paths.

      Example:

     # devfsadm

6.  If the devices are not seen by the OS then return to step 9 in <Document: 1012673.1> : "Troubleshooting Sun StorEdge[TM[ T3 Configuration."



Product
Sun StorageTek T3+ Array
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:

storage-os-disk-mid-domain@sun.com


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+, normalized, lun, slice, masking, audited
Previously Published As
86565

Change History
Date: 2007-09-17
User Name: 88109
Action: Update Canceled
Comment: *** Restored Published Content *** document was too T3 specific. Need to draft a new doc.
Version: 0
Date: 2007-09-17
User Name: 88109
Action: Update Started
Comment: Updating for 6920 normalization
Version: 0

Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback