| 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 Sun Alert Sure Solution 1019249.1 : One or More Incorrect Storage Domain Licenses May be Enabled on Sun StorageTek 25xx Arrays
PreviouslyPublishedAs 237684 Bug Id <SUNBUG: 6685210> Product Sun StorageTek 2510 Array Sun StorageTek 2530 Array Sun StorageTek 2540 Array Date of Workaround Release 12-May-2008 Date of Resolved Release 14-Jan-2009 One or More Incorrect Storage Domain Licenses May be Enabled on Sun StorageTek 25xx Arrays 1. Impact One or more incorrect Storage Domain licenses may be enabled on Sun StorageTek 25xx arrays, which may cause inability to modify or create volumes/hotspares/virtual disks, CAM alarms of non-compliance, array health reported as "degraded", or invalid license features to be enabled. 2. Contributing Factors This issue can occur on the following platforms:
3. Symptoms The following symptoms may occur:
Alarm ID : alarm2 Alarm ID : alarm3 Example of invalid Storage Domain (64 and 16 both enabled) in the Support Data file "storageArrayProfile.txt": Feature summary and status Example of valid information in the Support Data file "storageArrayProfile.txt" (for one 2540 array with an expansion tray): Storage array pseudo worldwide name (ID): 600A0B80002F9DBA00000000481620F8 4. Workaround To work around the described issues: For CAM: 1. Login to the Sun StorageTek Common Array Manager (CAM) software: Under: -> Array Administration ->
Licensing
2. Disable the incorrect license feature: For sscs: 1. Login to the array with the sscs cli: # sscs login -h localhost -u root2. View the licenses: sscs list -a <arrayname> licenseExample: bash-3.00# sscs list -a rw_2540_1 license3. Remove the incorrect license value that shows up in the above 'sscs list' command. # sscs -a <arrayname> remove license <incorrect value>Example: # sscs -a array01 remove license StorageDomain4. Verify the license value has been removed. Only the default value should be enabled: #sscs list -a <arrayname> license5. Resolution Please see the Workaround section above to resolve this issue. If neither of the above procedures correct this issue, contact your Sun Support representative (This issue has since been corrected in the manufacturing process). This Sun Alert notification is being provided to you on an "AS IS" basis. This Sun Alert notification may contain information provided by third parties. The issues described in this Sun Alert notification may or may not impact your system(s). Sun makes no representations, warranties, or guarantees as to the information contained herein. ANY AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT YOU ACKNOWLEDGE THAT SUN SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE OUT OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN. This Sun Alert notification contains Sun proprietary and confidential information. It is being provided to you pursuant to the provisions of your agreement to purchase services from Sun, or, if you do not have such an agreement, the Sun.com Terms of Use. This Sun Alert notification may only be used for the purposes contemplated by these agreements.
Modification History 14-Jan-2009: Updated Resolution section, republish Resolved Internal Comments Please send technical questions to the following email: [email protected] and CC the following persons: Internal Contributor/Submitter Internal Eng Responsible Engineer Internal Services Knowledge Engineer If the above procedures do not resolve the issue, a safeSysWipe command will need to be issued on each controller in the debug shell to clear the security and Feature Enabler ID. NOTE: After executing the 'safeSysWipe' command on both controllers, reboot both controllers. safeSysWipe: *** WARNING: wipes the security region which contains Enabler ID numbers. After running this command any premium features will show up as "Out Of Compliance" and will require new keys. Example of incorrect licenses before safeSysWipe: Storage array pseudo worldwide name (ID): 600A0B8000388F020000000047A923D0 Feature enable identifier: 30363039392000000000000047a923be Storage Domain - 2 Enabled true Compliant true WithinLimits true Storage Domain - MAX Enabled true Compliant true WithinLimits false Drive Tray Addition Enabled true Compliant true WithinLimits true Correct Licenses after safeSysWipe: Storage array identifier (SAID): 600A0B8000388F020000000047A923D0 Feature enable identifier: 30363039392000000000000047f2f0dc Feature summary and status Storage Domain - 2 Enabled true Compliant true WithinLimits true Drive Tray Addition Enabled true Compliant true WithinLimits true Internal Contributor/submitter [email protected] Internal Eng Responsible Engineer [email protected] Internal Services Knowledge Engineer [email protected] Internal Eng Business Unit Group NWS (Network Storage) Internal Escalation ID 70190566, 38053086, 65881221, 65891994, 70162996, 65875405, 11209254 Internal Sun Alert & FAB Admin Info 09-May-2008, david m: draft created, send for review 12-May-2008, david m: review completed, send for release 14-Jan-2008, david m: no further activity will be taken, no new escalations, Workaround is the Resolution Attachments This solution has no attachment |
||||||||||||
|
||||||||||||