Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Sun Alert Sure Solution 1000214.1 : Sun StorEdge 3510 FC Array May Lose In-band Connectivity After Generating Parity Regeneration on the Secondary Controller
PreviouslyPublishedAs 200287 Product Sun StorageTek 3510 FC Array Bug Id <SUNBUG: 4916011> Date of Workaround Release 04-FEB-2004 Date of Resolved Release 23-MAR-2004 Impact On a Sun StorEdge 3510 FC Array, running parity regeneration on a logical drive from the GUI may never finish the parity regeneration process on the secondary controller. As a result all the disks in the logical drive may not be available. Contributing Factors This issue can occur in the following releases: SPARC Platform
Note: This issue only occurs if the logical drive (ld0) is mapped to the primary controller, and the other logical drives are mapped to the secondary controller. Symptoms When a parity check is scheduled from the GUI to run to several logical drives in one array, the array will run these parity checks sequentially starting with "ld0" and continuing upward. The parity check running on the secondary controller never completes and the last logical drive to run will show disk lights blinking green indicating activity when there should not be any activity occuring (no I/O to the logical drive). Workaround To work around the described issue, arrange the ordering of the logical drives such that the last logical drive is assigned to the primary controller if possible. Resolution This issue is addressed in the following releases:
Modification History Date: 23-MAR-2004
References<SUNPATCH: 113723-07>Previously Published As 101442 Internal Comments
Internal Contributor/submitter [email protected] Internal Eng Business Unit Group NWS (Network Storage) Internal Services Knowledge Engineer [email protected] Internal Escalation ID 548972 Internal Resolution Patches 113723-07 Internal Sun Alert Kasp Legacy ID 101442, 57494 (Sun Alert) Internal Sun Alert & FAB Admin Info Critical Category: Availability ==> Pervasive Significant Change Date: 2004-02-04, 2004-03-23 Avoidance: Patch, Workaround Responsible Manager: [email protected] 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: 57494 Synopsis: Sun StorEdge 3510 FC Array May Lose In-band Connectivity After Generating Parity Regeneration on the Secondary Controller Category: Availability Product: Sun StorEdge 3510 FC Array BugIDs: 4916011 Avoidance: Workaround, Patch State: Resolved Date Released: 04-Feb-2004, 23-Mar-2004 Date Closed: 23-Mar-2004 Date Modified: 23-Mar-2004 Escalation IDs: 548972 Pending Patches: Resolution Patches: 113723-07 FIN: FCO: Date Submitted: 29-Jan-2004 Submitter: [email protected] Responsible Engineer: Responsible Manager: [email protected] CTE group: CPRE AMER NWS US Responsible Writer: [email protected] Distribution: Public SunSolve Workflow History: WF State: Issued, 23-Mar-2004, Jeff Folla WF Note: Updated sun alert with available patch. Status is now resolved. Sent for re-release. WF State: Issued, 04-Feb-2004, Jeff Folla WF Note: Signoff approved by Younan. Sending for release. WF State: Draft, 03-Feb-2004, Jeff Folla WF Note: sent email requesting signoff WF State: Draft, 03-Feb-2004, Jeff Folla WF Note: Sent for review on 2/2/04 WF State: Draft, 02-Feb-2004, Jeff Folla WF Note: Article created. Exported from KMS Creator Sat May 21 09:08:03 2005 GMT, [email protected] Internal SA-FAB Eng Submission Sun StorEdge 3510 FC Array May Lose In-band Connectivity After Generating Parity Regeneration on the Secondary Controller Product_uuid 58553d0e-11f4-11d7-9b05-ad24fcfd42fa|Sun StorageTek 3510 FC Array ReferencesSUNPATCH:113723-07Attachments This solution has no attachment |
||||||||||||
|