Sun StorEdge[TM] 351x FC Array: Unable to set scsi-3 persistent reservations

Asset ID:	1-71-1012786.1
Update Date:	2009-01-20
Keywords:

Solution Type Technical Instruction Sure

Solution 1012786.1 : Sun StorEdge[TM] 351x FC Array: Unable to set scsi-3 persistent reservations

Related Items


Sun Storage 3510 FC Array

Related Categories


GCS>Sun Microsystems>Storage - Disk>Modular Disk - 3xxx Arrays

PreviouslyPublishedAs
217562

Description
A Sun StorEdge[TM] 351x FC Array seems to be functioning, but cluster software is unable to set any scsi-3 reservations on the array.

Steps to Follow
The Sun StorEdge 351x FC Array had lds which were removed and recreated. After they were recreated, cluster was unable to reserve the "new" lds.

The array showed the lds as optimal.

Customer attempted to run:

  # /usr/cluster/lib/sc/scsi -c inkeys -d /dev/did/rdsk/d5s2
do_scsi3_inkeys failed
Reservation keys(0):

The error in /var/adm/messages at the time:

 May 17 23:14:16 host       device busy too long
May 17 23:14:16 host Cluster.CCR: [ID 826747 daemon.warning] reservation error(node_join) - do_scsi3_inkeys() error for disk /dev/did/rdsk/d5s2

The reservations needed to be cleared at the array level.

From any host connected to the array, unmount the volumes.

Confirm that you have a host with serial access to the array.

On the host managing the array, run sccli:

   # /usr/sbin/sccli

Choose the correct array if multiple are connected to the host. Run the command to shutdown the controller, it is necessary to sync the cache to the disks so that the LDs remain consistent.

   sccli> shutdown controller

Reset the controller

   sccli> reset controller

From the host with serial port access Watch the boot up until you find message

   ========================================================================
Restoring saved persistent reservations.
Preparing to restore saved persistent reservations. Type 'skip' to skip:
========================================================================

Type skip which will skip the loading of any persistent reservation keys stored on the array, essential scrubbing them from the array.

Allow the array to continue to boot normally.

At this time, retry the cluster command to initiate scsi-3 reservations.

The reset on the array needs only be run once.

If any reservations on any hosts exist prior to this procedure, the host will no longer have access to the lds, and could result in a panic of that host, or an ejection from the cluster.

Product
Sun StorageTek 3510 FC Array
Sun Cluster 3.0

Internal Comments
Similar to:

Issue in Technical Instruction <Document: 1010599.1> . Firmware was at current rev (4.11i).

minnow, scsi-3, persistant, reservations, cluster, se3511, se3510, se351x
Previously Published As
85841

Change History
Date: 2006-06-06
User Name: 97961
Action: Approved
Comment: - Changed title to comply to the standard format
- Applied trademarking
- Made simple sentence/grammatical corrections
- Tidied up formatting
Version: 3
Date: 2006-06-06
User Name: 97961
Action: Accept
Comment:
Version: 0
Date: 2006-06-06
User Name: 124974
Action: Approved
Comment: The document looks good.

Attachments

This solution has no attachment