Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Sun Alert Sure Solution 1000382.1 : Sun StorEdge 3510/3511 Arrays May Fail to Boot Upon Reset/Power Cycle When Connected in a Sun Cluster 3.x Environment With 3+ Nodes
PreviouslyPublishedAs 200504 Product Sun StorageTek 3510 FC Array Sun StorageTek 3511 SATA Array Bug Id <SUNBUG: 6276668> Date of Workaround Release 15-AUG-2005 Date of Resolved Release 02-SEP-2005 Impact Sun StorEdge 3510/3511 arrays may fail to boot upon a reset/power cycle when connected in a Sun Cluster 3.x environment with 3+ nodes. Contributing Factors This issue can occur on the following platforms: SPARC Platform
This issue will only occur in multi host configurations that issue SCSI-3 disk reservations from multiple nodes, including:
and other configurations that share the Sun StorEdge 3500/3511 array among more than two host systems. Symptoms Should the described issue occur, the system will fail to boot upon a system reset or power cycle, and messages similar to the following will be seen on the serial port connection to the array: ======================================================================== Restoring saved persistent reservations. Preparing to restore saved persistent reservations. Type 'skip' to skip: ======================================================================== In this example, the SE3510 tries to restore the persistent reservation but due to this issue, it can not boot and the following error is received: ============================================= Unrecoverable Controller Error Encountered ! Resetting Controller ! Unrecoverable Controller Error Encountered ! Resetting Controller ! =============================================
Workaround There is no workaround. Please see the "Resolution" section below. Resolution This issue is addressed in the following releases:
Modification History Date: 02-SEP-2005 Change History
References<SUNPATCH: 113723-11><SUNPATCH: 113724-05> Previously Published As 101862 Internal Comments Initial investigation to this issue found that there appears to be a limit on the size of the saved persistent reservation file for the 4.11 firmware which when it is exeeded, this issue occurs. We, do not know what that limit is at this time. Also not all configurations are affected. Internal Contributor/submitter [email protected] Internal Eng Business Unit Group NWS (Network Storage) Internal Eng Responsible Engineer [email protected] Internal Services Knowledge Engineer [email protected] Internal Escalation ID 1-9310705 Internal Resolution Patches 113723-11, 113724-05 Internal Sun Alert Kasp Legacy ID 101862 Internal Sun Alert & FAB Admin Info Critical Category: Availability ==> HA-Failure Significant Change Date: 2005-08-15, 2005-09-02 Avoidance: Patch Responsible Manager: [email protected] Original Admin Info: [WF 02-Sep-2005, Jeff Folla: This should have been updated to "Free" in the audience field when it was closed. Corrected the audience field and re-published.] [WF 02-Sep-2005, Jeff Folla: Patches now available. This is now resolved. Sent for re-release.] [WF 15-Aug-2005, Jeff Folla: Sent for release.] [WF 12-Aug-2005, Jeff Folla: Sent for review.] [WF 10-Aug-2005, Jeff Folla: Sent to submitter for review before sending to 24 hr. review.] Product_uuid 58553d0e-11f4-11d7-9b05-ad24fcfd42fa|Sun StorageTek 3510 FC Array 9fdbb196-73a6-11d8-9e3a-080020a9ed93|Sun StorageTek 3511 SATA Array ReferencesSUNPATCH:113723-11SUNPATCH:113724-05 Attachments This solution has no attachment |
||||||||||||
|