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-1001279.1
Update Date:2011-02-25
Keywords:

Solution Type  Sun Alert Sure

Solution  1001279.1 :   Two-Node Cluster Directly Connected to a StorEdge 6920 System May Experience a SCSI Reservation Panic  


Related Items
  • Sun Storage 6920 System
  •  
Related Categories
  • GCS>Sun Microsystems>Sun Alert>Criteria Category>Availability
  •  
  • GCS>Sun Microsystems>Sun Alert>Release Phase>Resolved
  •  

PreviouslyPublishedAs
201739


Product
Sun StorageTek 6920 System

Bug Id
<SUNBUG: 6230109>

Date of Workaround Release
03-MAY-2005

Date of Resolved Release
29-NOV-2005

Impact

When both nodes of a two-node cluster are directly connected to a Sun StorEdge (SSE) 6920, the SSE 6920 may not handle the release of SCSI-2 (FC-AL) disk reservations properly. The SSE 6920 may become inaccessible, and one of the two cluster nodes may return a "SCSI reservation panic" on bootup.


Contributing Factors

This issue can occur in the following release:

  • Sun StorEdge 6920 with System Processor (SP) version 2.0.5 and earlier (with Sun Cluster 3.x for Solaris 8 and 9)

Note: This issue can only occur when both nodes of a two-node cluster are directly connected to the SSE 6920.

To verify the Storage Service Processor Image revision:

  1. Log in into the Storage Automated Diagnostic Environment web console. (This can be done with the guest login/password).
  2. Click on the Storage Automated Diagnostic Environment link that is under the "Storage" category.
  3. Click on the "Monitor" tab, then click on the "Device" tab (under the Monitor tab).
  4. In the "Monitored Devices" list that comes up, find in the "Type" category an entry titled "Summary" that has for its Device entry 6920-spx (where x equals the sp number for this site; typically 0).
  5. Click on that 6920-spx link.
  6. In the window that comes up, insure that the "Page:" window has "Summary Report" selected, or if not, select "Summary Report" and click the "Go" button next to it.
  7. In the upper left hand window of the window that comes up there will be a "Name:" field with the 6920 spx information in it. Immediately below that is a "Revision:" field that will contain the current System Service Processor version.

The system processor version can be determined from "/etc/release" with the following command (run on the SP):

    [sp0]# cat /etc/release
    Solaris 9 s9_58shwpl3 SPARC
    ...
    Sun StorEdge(tm) 6920
    Version: 2.0.2

Symptoms

Cluster node host will experience a SCSI reservation panic on bootup.


Workaround

To work around this issue, use fibre channel switches between the cluster nodes and the SE6920 and have all the SAN connections operate in fabric mode (which can be confirmed with a simple status check at the fibre channel switches). To perform this workaround, do the following:

  1. Make sure all SCSI reservations on the storage have been removed.
  2. Shut down the cluster using "scshutdown -g0 -y" [WARNING: Avoid shutting down the cluster one node at a time. This will cause SCSI reservations to be placed on the disks again]
  3. Boot both cluster nodes in non-cluster mode using "boot -x".
  4. Run "format" on both nodes to confirm that no SCSI reservations are on the LUNs.
  5. Obtain at least 2 fibre channel switches for the connections from the cluster nodes to the SE6920.
  6. Establish the new connections between the cluster nodes and the SE6920 such that all connections use fabric mode, and not arbitrated loop mode, and so that there are no direct connections from the cluster nodes to the SE6920.
  7. Re-map the LUNs in the SE6920 and the fibre channel switches, as necessary, to this new hardware configuration.
  8. Use cfgadm and devfsadm, as necessary, and confirm the storage is accessible from both cluster nodes. [Note: It should be possible to make these changes without altering the paths to the storage. This should also leave all cluster global device entries unchanged as well.]
  9. IMPORTANT... Reboot the DSP in the SE6920.
  10. Reboot both cluster nodes into cluster mode and test that each has access to the storage.
  11. Test that the workaround has been completed properly by shutting down the cluster one node at a time, until the cluster is completely down, and then rebooting both cluster nodes into cluster mode again [Note: The SCSI reservations should be released and the nodes should be able to form a cluster again at the end of this step.]

Complete details of this process can be found in "Sun Cluster 3.x With Sun StorEdge 6920 System Manual for Solaris OS" at http://docs.sun.com/app/docs?q=817-6747-11.


Resolution

This issue is addressed in the following release:

  • Sun StorEdge 6920 with System Processor (SP) version 3.0.0.25 and later

Information for upgrade procedures for the 6920 can be found in the following document: http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-5229-14.pdf

 



Modification History
Date: 29-NOV-2005

29-Nov-2005:

  • Updated Contributing Factors and Resolution sections, re-release as Resolved


Previously Published As
101678
Internal Comments


The version 2.0.6 was dropped as there was a lack of customer's awaiting this release. Therefore bug 2123693, will not be fixed, since there are no more 2.x releases on the books. The fix was implemented in the 3.0.0.16 build, and is in either of the current releases of the 6920(3.0.0.25 or 3.0.0.30).



The bug for this fix is actually 6230109.


Internal Contributor/submitter
don.curren@sun.com

Internal Eng Business Unit Group
NWS (Network Storage)

Internal Eng Responsible Engineer
don.curren@sun.com

Internal Services Knowledge Engineer
david.mariotto@sun.com

Internal Escalation ID
1-6965641

Internal Sun Alert Kasp Legacy ID
101678, 57770 (Sun Alert)

Internal Sun Alert & FAB Admin Info
Critical Category: Availability ==> Pervasive
Significant Change Date: 2005-05-03, 2005-11-29
Avoidance: Upgrade, Workaround
Responsible Manager: david.treen@sun.com
Original Admin Info: [WF 29-Nov-2005, Dave M: upgrade, resolved, re-release]
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:

The following field(s) have been migrated with dummy values and need adjustment:
Original Product: Sun StorEdge 6920
Migrated Product: SunTea v3.55 (Dummy)

Original KMS Creator attributes below:

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

Sun Alert ID: 57770
Synopsis: Two-Node Cluster Directly Connected to a StorEdge 6920 System May Experience a SCSI Reservation Panic
Category: Availability
Product: Sun StorEdge 6920
BugIDs: 2123693
Avoidance: Workaround
State: Committed
Date Released: 03-May-2005
Date Closed:
Date Modified:
Escalation IDs: 1-6965641
Pending Patches:
Resolution Patches:
FIN:
FCO:
Date Submitted: 15-Apr-2005
Submitter: don.curren@sun.com
Responsible Engineer: don.curren@sun.com
Responsible Manager: david.treen@sun.com
CTE group: NWS
Responsible Writer: david.mariotto@sun.com
Distribution: Contract SunSolve

Workflow History:

WF State: Issued, 03-May-2005, David Mariotto
WF Note: sending for release

WF State: Draft, 03-May-2005, David Mariotto
WF Note: sending for release

WF State: Draft, 03-May-2005, David Mariotto
WF Note: no further comments; OK by Roberta, send for release this afternoon.

WF State: Draft, 02-May-2005, David Mariotto
WF Note: no further information from submitters;
sending for review 1:00pm



WF State: Draft, 28-Apr-2005, David Mariotto
WF Note: approved by BU, waiting on additional information
from submitters; received 1/2, need output for Symptoms



WF State: Draft, 27-Apr-2005, David Mariotto
WF Note: waiting on additional information/corrections from submitters


WF State: Draft, 26-Apr-2005, David Mariotto
WF Note: Bill replied 2pm - still waiting on more comments for
final approval.

WF State: Draft, 26-Apr-2005, David Mariotto
WF Note: requested approval status from Roberta's people (she
is on vacation)

WF State: Draft, 22-Apr-2005, David Mariotto
WF Note: Have not heard anything back yet for approval from
team members Bill Stearn and Mark Keener

WF State: Draft, 22-Apr-2005, David Mariotto
WF Note: Roberta is going on vacation next week, she assigned
approval to team members Bill Stearn and Mark Keener


WF State: Draft, 20-Apr-2005, David Mariotto
WF Note: waiting on BU approval (Roberta)

WF State: Draft, 18-Apr-2005, David Mariotto
WF Note: Article created.

Exported from KMS Creator Sat May 21 09:17:52 2005 GMT, olaf.reineke@sun.com
Internal SA-FAB Eng Submission
Two-Node Cluster Directly Connected to a StorEdge 6920 System May Experience a SCSI Reservation Panic

Product_uuid
67794720-356d-11d7-8ef2-ce2ac2bc9136|Sun StorageTek 6920 System

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