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-77-1000407.1
Update Date:2011-03-01
Keywords:

Solution Type  Sun Alert Sure

Solution  1000407.1 :   Improper LUN Permission on Sun StorEdge T3+, Sun StorEdge 6120 or 6320 Array With Firmware 3.1.2 May Cause Performance Degradation  


Related Items
  • Sun Storage 6320 System
  •  
  • Sun Storage T3 Array
  •  
  • Sun Storage T3+ Array
  •  
  • Sun Storage 6120 Array
  •  
Related Categories
  • GCS>Sun Microsystems>Sun Alert>Criteria Category>Availability
  •  
  • GCS>Sun Microsystems>Sun Alert>Release Phase>Resolved
  •  

PreviouslyPublishedAs
200535


Product
Sun StorageTek T3 Array
Sun StorageTek T3+ Array
Sun StorageTek 6120 Array
Sun StorageTek 6320 System

Bug Id
<SUNBUG: 4972795>

Date of Resolved Release
05-AUG-2004

Impact

Sun StorEdge T3+, Sun StorEdge 6120 or 6320 Arrays with firmware 3.1.2 or earlier may experience performance degradation if the LUN permission of volume slices are modified or the HBA port World-Wide-Number (wwn) is improperly changed.


Contributing Factors

This issue can occur on the following platforms:

SPARC Platform

  • Sun StorEdge 6120 and 6320 Array with firmware 3.1.2 or earlier and without firmware 3.1.3 (as delivered with patch 115179-06)
  • Sun StorEdge T3+ Array with firmware 3.1.2 or earlier and without firmware 3.1.3 (as delivered with patch 115180-04)

Symptoms

Should the described issue occur, the storage array may experience noticeable performance degradation.


Workaround

There is no workaround for this issue. Please see the "Resolution" section below.


Resolution

This issue is addressed on the following platforms:

SPARC Platform

  • Sun StorEdge 6120 and 6320 Array with firmware 3.1.3 (as delivered with patch 115179-06) or later
  • Sun StorEdge T3+ Array with firmware 3.1.3 (as delivered with patch 115180-04) or later


Modification History

References

<SUNPATCH: 115179-06>
<SUNPATCH: 115180-04>

Previously Published As
101541
Internal Comments



From Engineering:



The following steps will cause "lmk_data.lmk_filter.accessibility[elun]" internal flag to be set to "ACC_PARTIAL_DEF_YES" for the slice (i.e. for the slice whose permission is being modified). This flag will not change back to ACC_ALL even if the configuration is changed back to the initial setting. In the following example, if we assign a read/write permission to lun 0 for host PWWN 210000e08b08ab10, then changed the permission to "none" or "read only" (which causes the "ACC_PARTIAL_DEF_YES" flag to be set), then changed it back to "read/write", the flag is not set back to ACC_ALL:


    <hostname>:/:<1> lun perm lun 0 rw wwn 210000e08b08ab10
<hostname>:/:<2> lun perm list
<hostname>:/:<3> lun perm 0 <ro|none> wwn 210000e08b08ab10
<hostname>:/:<4> lun perm lun 0 rw wwn 210000e08b08ab10
<hostname>:/:<5> lun perm list


The above condition by itself does not cause the performance degradation, as long as the HBA's PWWN does not change. If a different HBA is connected to the array and the PWWN of the new HBA is not shown in the output of "lun wwn list" then the performance degradation will be observed. To fix this condition, execute the following:


    <hostname>:/:<1> lun perm all_lun rw all_wwn
<hostname>:/:<2> wwn rm all


The above will insure the flag is properly set and any possible stale WWNs cleared. Obviously, you need to set the permissions again after executing the above commands.



Notes: Should the described issue occur, the storage array may experience noticeable performance degradation, possibly on the order of 30% slower (depending on the environment). The output after the last step (step <5>) is the same as the output of step 1 when the accessibility flag was set to ACC_ALL. This condition by itself does not cause the performance degradation as long as the HBA's PWWN does not change. If a different HBA is connected to the array after step <4>, and the PWWN of the new HBA is not shown in the output of 'lun wwn list', or the PWWN is removed (thru the 'lun wwn rm <all|wwn #>' command), then the performance is impacted. This condition can occur if the array's slice permission is modified (using the above steps) during testing/integration before shipping the box to a customer. The customer will then configure the lun permission using, for example, the "lun perm lun # <rw|ro|none> <wwn #>" command without knowing the existing state of the lun permission.



The last step and the first step are not the same. But the net effect from the 1st step to the last setp would be eqivalent. i.e. all the host HBAs can access any of the luns in the system.



The issue here is that since the global flag of this LUN remains the same as "ACC_PARTIAL_DEF_YES" after the last step which can cause unnecessary delay for each coming I/O command to go through the port login code path. This process results in performance impact.



The ACC_PARTIAL_DEF_YES is an internal flag that's not visible to the user, and there are no commands that allow the user to examine the register containing the state of Access Definition setting.





Internal Contributor/submitter
saaid.magidi@sun.com

Internal Eng Business Unit Group
NWS (Network Storage)

Internal Eng Responsible Engineer
Chung-De.Li@Sun.COM

Internal Services Knowledge Engineer
david.mariotto@sun.com

Internal Resolution Patches
115179-06, 115180-04

Internal Sun Alert Kasp Legacy ID
101541, 57610 (Sun Alert)

Internal Sun Alert & FAB Admin Info
Critical Category: Availability ==> Pervasive
Significant Change Date: 2004-08-05
Avoidance: Patch
Responsible Manager: Seetharaman.Padmanabhan@Sun.COM
Original Admin Info: This document has been imported from KMS Creator and may need adjustment before re-publishing.

This imported document has been reviewed/adjusted by:
Review Name:
Review Date:

Original KMS Creator attributes below:

--- PLEASE DO NOT MAKE ANY CHANGES BELOW THIS LINE! ---

Sun Alert ID: 57610
Synopsis: Improper LUN Permission on Sun StorEdge T3+, Sun StorEdge 6120 or 6320 Array With Firmware 3.1.2 May Cause Performance Degradation
Category: Availability
Product: Sun StorEdge T3+, Sun StorEdge 6120 and 6320 Array
BugIDs: 4972795
Avoidance: Patch
State: Resolved
Date Released: 05-Aug-2004
Date Closed: 05-Aug-2004
Date Modified:
Escalation IDs:
Pending Patches:
Resolution Patches: 115179-06, 115180-04
FIN:
FCO:
Date Submitted: 23-Jul-2004
Submitter: saaid.magidi@sun.com
Responsible Engineer: Chung-De.Li@Sun.COM
Responsible Manager: Seetharaman.Padmanabhan@Sun.COM
CTE group: CPRE NWS US
Responsible Writer: david.mariotto@sun.com
Distribution: Public SunSolve

Workflow History:

WF State: Issued, 05-Aug-2004, David Mariotto
WF Note: OKd for release (OK by all)

WF State: Draft, 05-Aug-2004, David Mariotto
WF Note: Final rewrite from Steve Chessin completed - both RE
and submitter notified of changes - sending for
release today.

WF State: Draft, 04-Aug-2004, David Mariotto
WF Note: considerable changes are needed per Steve Chessin
sent to both RE and Submitter for rework

WF State: Draft, 03-Aug-2004, David Mariotto
WF Note: final comments from submitter OK - sending for review,
4:30 pm.

WF State: Draft, 03-Aug-2004, David Mariotto
WF Note: sent copy to Roger (chung-de-li) for final approval
before sending to sunalert_review

WF State: Draft, 02-Aug-2004, David Mariotto
WF Note: sent copy to Bug owner Michael Hosrom for changes,
comments, approval (noon)

WF State: Draft, 02-Aug-2004, David Mariotto
WF Note: per Steve Chessin - needs more work

WF State: Draft, 29-Jul-2004, David Mariotto
WF Note: sent email to Roger (Chung-De.Li@Sun.COM)
requesting clarification where Saaid left off...(this draft
had already been approved and is not a part of the new
process.

WF State: Draft, 26-Jul-2004, David Mariotto
WF Note: waiting on clarification from submitter

WF State: Draft, 26-Jul-2004, David Mariotto
WF Note: Article created.

Exported from KMS Creator Sat May 21 09:12:04 2005 GMT, olaf.reineke@sun.com
Internal SA-FAB Eng Submission
Improper LUN Permission on Sun StorEdge T3+, Sun StorEdge 6120 or 6320 Array With Firmware 3.1.2 May Cause Performance Degradation

Product_uuid
2a6d7d50-0a18-11d6-8e0b-f0bd33b24928|Sun StorageTek T3 Array
2a714b10-0a18-11d6-86e2-d56b387d4fbf|Sun StorageTek T3+ Array
2cd2e7d2-2980-11d7-9c3f-c506fe37b7ef|Sun StorageTek 6120 Array
4de60cc2-a08e-4610-b8bf-6a1881cb59c6|Sun StorageTek 6320 System

References

SUNPATCH:115179-06
SUNPATCH:115180-04

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