Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2008.0626 -- [Appliance][Solaris]
Collecting Support Data On Certain Arrays May Cause One or
Both Array Controllers to Reboot
18 June 2008
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: Sun StorageTek Flexline 240 Array
Sun StorageTek Flexline 280 Array
Sun StorageTek Flexline 380 Array
Sun StorageTek 6130 Array
Sun StorageTek 6140 Array
Sun StorageTek 6540 Array
Publisher: Sun Microsystems
Operating System: Network Appliance
Impact: Denial of Service
Access: Existing Account
Original Bulletin:
http://sunsolve.sun.com/search/printfriendly.do?assetkey=1-66-231741-1
- --------------------------BEGIN INCLUDED TEXT--------------------
Solution Type: Sun Alert
Solution 231741 : Collecting Support Data On Certain Arrays May
Cause One or Both Array Controllers to Reboot
Bug ID: 6620880
Product
Sun StorageTek Flexline 240 Array
Sun StorageTek Flexline 280 Array
Sun StorageTek Flexline 380 Array
Sun StorageTek 6130 Array
Sun StorageTek 6140 Array
Sun StorageTek 6540 Array
Date of Workaround Release: 15-Feb-2008
Date of Resolved Release: 16-Jun-2008
SA Document Body
Collecting Support Data On Certain Arrays May Cause One or Both Array
Controllers to Reboot
1. Impact
For Sun StorageTek 6130, 6140, 6540 and Flexline 240, 280, and 380
arrays, collecting support data may cause one or both array
controllers to reboot. Results can range from device path failovers to
loss of access due to both primary and secondary paths to a device
being inaccessible.
2. Contributing Factors
This issue can occur on the following platforms and in the following
releases:
* Sun StorEdge 6130 arrays with array firmware 06.19.25.10 (or
later)
* Sun StorageTek 6140, 6540 arrays with array firmware 06.16.81.10
(or later)
* Sun StorageTek Flexline 240, 280, 380 arrays with array firmware
06.19.25.00 (or later)
* Sun StorageTek SANtricity Storage Manager 06.16 (or later)
* Sun StorageTek Common Array Manager 6.0
Notes:
This issue can only occur during array support data collection using
SANtricity or Common Array Manager (CAM). Specifically the "Capture
State" function of the collection which generates the
stateCaptureData.dmp file.
The following specific circumstances lead to this bug:
1) The Host Port/HBA must be or have been seen in the SAN by one or
both controllers. This can be verified if it is listed in the WWPN
drop down in CAM, or as an un-aliased Host Port in SANtricity. This
means that "fake" WWPNs that are aliased on the array, or proactively
created before the SAN is zoned WILL NOT cause this issue.
2) The Host Port/Initiator must have an existing alias. This means
that not only had the HBA been seen by the array, but at some point
the user had created an alias for it to assign to a specific host for
Volume-to-LUN mapping on the array.
3) Since having been aliased, as in step 2, the Host Port/Initiator
must have either:
A) been removed from (unliased) and placed in the "Free" list
(available as a drop down in CAM)
or
B) had the alias name changed
4) After conditions 1-3 are met, the execution of collecting the "All
Support Data" or specifically the "State Capture" (SANtricity Only)
will cause the controllers to panic.
3. Symptoms
At a minimum, users will see device path fail-overs. At worst, they
will see a loss of access due to both primary and secondary paths to a
device being inaccessible.
This issue can only occur during array support data collection. Host
message events showing SCSI or Fibre Channel messages indicating loss
of access to one or both array controllers are the most common symptom
associated with this issue. SANtricity or CAM may throw an error
during collection, similar to the following (CAM error shown):
ionShow 99 fails!
devmgr.v0916api13.sam.jal.ManagementOperationFailedException:
ManagementOperationFailedExceptionError 1007 - Could not communicate
with the controller in slot A to complete this request.
The controller(s) will boot due to a defined inititiator or host port
not being seen by the array at the time the data collection command is
run.
4. Workaround
This issue can be avoided by not collecting support data when you know
that:
A) An Initiator/Host Port alias for a connected HBA has been changed
B) An Initiator/Host Port alias has been deleted from the array. This
is normal if you replace/remove an HBA as part of reallocation or
hardware replacement.
If either of the above, consider performing a controller reset to
avoid an unplanned outage.
Otherwise, individual collections of "Alarms", "Array Profiles", and
"Major Event Logs" are possible within each of the management
utilities.
The following CLI commands can be run to obtain support data for CAM:
service -d <array_name> -c print -t arrayprofile > arrayProfileSummary.txt
service -d <array_name> -c print -t mel > majorEventLog.txt
service -d <array_name> -c read -q region=0xEE > NVSRAMdata.txt
service -d <array_name> -c print -t rls > readLinkStatus.csv
sscs list -a <array_name> alarms > alarms.txt
The following SMcli or script editor commands can be run under
SANtricity:
save controller [a] NVSRAM file="A-NVSRAMdata.txt"
save controller [b] NVSRAM file="B-NVSRAMdata.txt"
save allDrives logFile="driveDiagnosticData.bin"
save storageArray configuration file="storageArrayConfiguration.txt" allConfig
save storageArray allEvents file="majorEventLog.txt
save storageArray performanceStats file="persistentReservations.txt"
save storageArray RLSCounts file="readLinkStatus.csv"
show storageArray profile
5. Resolution
This issue is addressed in the following releases:
* Sun StorEdge 6130, 6140, 6540 arrays with array firmware
06.60.11.10 or later
* Sun StorageTek Flexline 380 array with array firmware 06.60.11.10
or later
* Sun StorageTek Flexline 240, 280 arrays with array firmware
06.60.11.20 or later
* Sun StorageTek SANtricity Storage Manager 10.10 or later
* Sun StorageTek Common Array Manager 6.1.0 or later
The above firmware releases are available with CAM 6.1.0 at:
http://www.sun.com/download/index.jsp
View by Category -> Systems Administration -> Storage Management
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.
Copyright 2000-2008 Sun Microsystems, Inc., 4150 Network Circle, Santa
Clara, CA 95054 U.S.A. All rights reserved
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
http://www.auscert.org.au/render.html?cid=1980
If you believe that your computer system has been compromised or attacked in
any way, we encourage you to let us know by completing the secure National IT
Incident Reporting Form at:
http://www.auscert.org.au/render.html?it=3192
===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072
Internet Email: auscert@auscert.org.au
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967
iQCVAwUBSFiCsyh9+71yA2DNAQIYQAQAkw59wA8whRWVyeG/yYzakq9bpNl6tNyw
PcXy7PxJtgwhuIa0KVlfTEvb2G6fP2JtHW9lCADM+n8EiX8/XsHWAGkmgkpWrTHO
vzVK8x9u9NQl4RTDgEkcaK6aS8Z0EIz0YrciM0o4UHUfZgr/zcBEOK0kobIaxwPm
gVBUXlbykQs=
=4axj
-----END PGP SIGNATURE-----