| Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback |
| Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | ||
|
|
||
 |
||||||||||||
Solution Type Problem Resolution Sure Solution 1003639.1 : Sun StorEdge[TM] 6320/SE6120 sscs and array LUN permissions mismatch
PreviouslyPublishedAs 205140 Symptoms On certain occasions when sscs is used to manage the array (such as the case of a SE6320), we can get LUN permissions mismatch between sscs and the array. Below is an example. LUN masking in array01 does not match with SSCS GUI/CLI. # sscs list -a array01 volume Volume: t0pool1v0 Volume: t0pool1v1 Volume: t1pool1v0 Volume: t1pool1v1 # sscs list -a array01 volgroup Volume Group: vg1 Volume Group: vg2 # sscs list -a array01 volgroup vg1 Volume Group: vg1 Initiator Group: ig1 Permissions: Read/Write Volume: t0pool1v0 Volume: t1pool1v0 # sscs list -a array01 volgroup vg2 Volume Group: vg2 Initiator Group: ig2 Permissions: Read/Write Volume: t0pool1v1 Volume: t1pool1v1 # sscs list -a array01 initgroup Initiator Group: ig1 Initiator Group: ig2 # sscs list -a array01 initgroup ig1 Initiator Group: ig1 Initiator: 210000E08B091D39 Initiator: 210000E08B093EF6 # sscs list -a array01 initgroup ig2 Initiator Group: ig2 Initiator: 210000E08B0911F6 Initiator: 210000E08B09AF37 If we telnet to the array we can see that the permissions does not match: array01:/:<1>lun perm list lun slice WWN Group Name Group Perm WWN Perm Effective Perm -------------------------------------------------------------------------------------------------------- 0 0 default -- -- rw rw 1 1 default -- -- rw rw 2 2 default -- -- rw rw 3 3 default -- -- rw rw -------------------------------------------------------------------------------------------------------- The above indicates all hosts will have permission to the luns and hence no permissions (LUN masking) is active. Resolution This is because the array defaults are not set up correctly, and it is a simple step of setting these defaults that will fix the issue. Note this can be done at any time, the permissions are actually there except they are being overridden by the defaults. Each LUN in a T3/T4 array has three permission settings:
The three types of permission are added up where the largest permission set prevails. So if any of the three has read/write (rw) permission then that is the overriding one and is the one that takes effect. The "Effective Perm" column below is what is important (i.e. the end result). Hence if default permissions is set to rw then there is no point in setting Group or WWN as all hosts will have rw access despite what WWN and Group has. So lets look at an example. Below is the same array above. Note how the permissions are by default open to all hosts. array01:/:<1>lun perm list lun slice WWN Group Name Group Perm WWN Perm Effective Perm -------------------------------------------------------------------------------------------------------- 0 0 default -- -- rw rw 1 1 default -- -- rw rw 2 2 default -- -- rw rw 3 3 default -- -- rw rw -------------------------------------------------------------------------------------------------------- So let us set the default to have none. array01:/:<2>lun default all_lun none Note that once that is done, the permissions for Group and WWN now appear array01:/:<3>lun perm list lun slice WWN Group Name Group Perm WWN Perm Effective Perm -------------------------------------------------------------------------------------------------------- 0 0 default -- -- none none 0 0 210000e08b091d39 ig1 rw rw rw 0 0 210000e08b093ef6 ig1 rw rw rw 0 0 210000e08b0911f6 ig2 none rw rw 0 0 210000e08b09af37 ig2 none rw rw 1 1 default -- -- none none 1 1 210000e08b091d39 ig1 none rw rw 1 1 210000e08b093ef6 ig1 none rw rw 1 1 210000e08b0911f6 ig2 rw rw rw 1 1 210000e08b09af37 ig2 rw rw rw 2 2 default -- -- none none 2 2 210000e08b091d39 ig1 rw rw rw 2 2 210000e08b093ef6 ig1 rw rw rw 2 2 210000e08b0911f6 ig2 none rw rw 2 2 210000e08b09af37 ig2 none rw rw 3 3 default -- -- none none 3 3 210000e08b091d39 ig1 none rw rw 3 3 210000e08b093ef6 ig1 none rw rw 3 3 210000e08b0911f6 ig2 rw rw rw 3 3 210000e08b09af37 ig2 rw rw rw -------------------------------------------------------------------------------------------------------- Now notice that permissions above still doesn't match our sscs outputs. This is because the WWN permissions is set to rw, while sscs deals only with Group permissions. Hence we need to set those to none as well. array01:/:<6>lun perm all_lun none all_wwn array01:/:<7>lun perm list lun slice WWN Group Name Group Perm WWN Perm Effective Perm -------------------------------------------------------------------------------------------------------- 0 0 default -- -- none none 0 0 210000e08b091d39 ig1 rw rw rw 0 0 210000e08b093ef6 ig1 rw rw rw 1 1 default -- -- none none 1 1 210000e08b0911f6 ig2 rw rw rw 1 1 210000e08b09af37 ig2 rw rw rw 2 2 default -- -- none none 2 2 210000e08b091d39 ig1 rw rw rw 2 2 210000e08b093ef6 ig1 rw rw rw 3 3 default -- -- none none 3 3 210000e08b0911f6 ig2 rw rw rw 3 3 210000e08b09af37 ig2 rw rw rw -------------------------------------------------------------------------------------------------------- As you can see from above the permissions now match the sscs output. In general this has been seen in the field when the array is newly added to the SE6320 or is a new SE6120 that had the default setting as above. Product Sun StorageTek 6320 System Sun StorageTek 6120 Array Sun StorageTek 6020 Array Internal Comments For Internal Use Only This Document was inspired by the following Escalation ID: 1-7588929 sscs, se6x20, se6320, se6020, se6120, t4, 6020, 6120, 6320, lun permission, volgroup, initgroup Previously Published As 80768 Change History Date: 2005-03-31 User Name: 25440 Action: Approved Comment: Publishing. Version: 3 Date: 2005-03-31 Product_uuid 4de60cc2-a08e-4610-b8bf-6a1881cb59c6|Sun StorageTek 6320 System 2cd2e7d2-2980-11d7-9c3f-c506fe37b7ef|Sun StorageTek 6120 Array 5475c17c-c204-11d7-9de1-080020a9ed93|Sun StorageTek 6020 Array Attachments This solution has no attachment |
||||||||||||
|
||||||||||||