Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1003484.1
Update Date:2017-02-02
Keywords:

Solution Type  Problem Resolution Sure

Solution  1003484.1 :   Sun Storage 3510 FC Array: Getting Command Timeouts for LUNS in a SAN Configuration  


Related Items
  • Sun Storage SAN Foundation Software
  •  
  • Sun Storage 3510 FC Array
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Arrays>SN-DK: SE31xx_33xx_35xx
  •  
  • _Old GCS Categories>Sun Microsystems>Storage - Disk>Modular Disk - 3xxx Arrays
  •  
  • _Old GCS Categories>Sun Microsystems>Storage Software>Sun Storage SAN Software
  •  

PreviouslyPublishedAs
204886


Applies to:

Sun Storage SAN Foundation Software - Version 4.0 and later
Sun Storage 3510 FC Array - Version Not Applicable and later
All Platforms

Symptoms

A specific configuration of a Sun Storage 3510 FC Array might cause attached hosts to experience excessive SCSI timeouts, when a single host is rebooted.

If this occurs, messages similar to the following message appear in the "/var/adm/messages" file of the other hosts when one of the hosts is rebooted:

Apr 27 nsvr-88 /scsi_vhci/ssd@g600c0ff00000000000272a68ad13490a (ssd75): Command Timeout on path /pci@1e,600000/SUNW,qlc@4,1/fp@0,0 (fp3)

Changes

This issue only occurs when the Sun Storage 3510 FC Array is configured in "loop mode" in a storage area network (SAN) configuration with more than one host accessing the same Sun Storage 3510 FC Array.
The configuration affected by this problem is the "High-Performance SAN Configuration" mentioned in older versions of the Sun StorEdge 3000 Family Best Practices Manual

In such a configuration, if you have multiple hosts accessing the logical unit numbers (LUNs) for the Sun Storage FC Array, when one of the hosts is rebooted all the other hosts start getting SCSI timeouts and applications might appear to be hung.

Cause

The problem was first resolved in the controller firmware release v4.11 in <Patch 113723-10> SE3510 411I: StorEdge 3510 array controller firmware upgrade, but it is recommended to install the latest controller firmware release available (v4.23 in <Patch 113723-21> SE3510 423A: StorEdge 3510 array controller firmware upgrade or later).

Solution

To recover from the described issue when it has occurred, either power cycle the whole array or fail/unfail the controller on the Sun Storage 3510 FC Array.

To prevent a re-occurrence of the problem, change from "loop mode" to "fabric point-to-point mode" on the Sun Storage 3510 FC Array:

  1. Telnet to the Sun Storage 3510 FC Array
  2. Select the following from the menu :
    View and Edit Configuration Parameters ----> Host-side SCSI Parameters ----> Fiber Connection Option - Loop only
  3. Change "Fiber Connection Option - Loop only" to "Point to Point only"
  4. Reset and re-map the channels and luns on the array.

An Alert was also released for this problem.
Please see <Document 1001226.1> Sun Storage 3510 FC Array in Loop Mode May Cause Attached Hosts to Experience Excessive SCSI Timeouts Upon a Reboot

See Sun Bug IDs 5038863 and 5061098.
Change History
Date: 2010-07-16
User Name: susan.copeland@oracle.com
Action: Update & Currency

References

<NOTE:1001226.1> - Sun StorEdge 3510 FC Array in Loop Mode May Cause Attached Hosts to Experience Excessive SCSI Timeouts Upon a Reboot

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback