Document fins/I0742-1
FIN #: I0742-1
SYNOPSIS: Modifying the "st.conf" file might lead to temporary
slowdowns or hangs on systems with Sun StorEdge D1000 or D240 devices
attached
DATE: Nov/20/01
KEYWORDS: Modifying the "st.conf" file might lead to temporary
slowdowns or hangs on systems with Sun StorEdge D1000 or D240 devices
attached
---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by SunService)
SYNOPSIS: Modifying the "st.conf" file might lead to temporary
slowdowns
or hangs on systems with Sun StorEdge D1000 or D240 devices
attached.
Sun Alert: Yes
TOP FIN/FCO REPORT: Yes
PRODUCT_REFERENCE: StorEdge D1000/D240
PRODUCT CATEGORY: Storage / SW Admin
PRODUCTS AFFECTED:
Systems Affected
----------------
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
- ANYSYS - SYSTEM PLATFORM INDEPENDENT -
X-Options Affected
------------------
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
- D1000 ALL StorEdge D1000 -
- D240 ALL StorEdge D240 -
PART NUMBERS AFFECTED:
Part Number Description Model
----------- ----------- -----
- - -
REFERENCES:
BugId 4426535 - st.conf entry causes problems with scsi probe
commands.
ESC: 529829
SunAlert: 26524
PROBLEM DESCRIPTION:
Systems with a modified "/kernel/drv/st.conf" file and a Sun StorEdge
D1000, Netra st D1000, or D240 Array attached might sporadically slow
down or appear hung and become unavailable for about 60 seconds. This
slowdown can happen at system boot time. SCSI errors might appear for
the SCSI Bus containing the D1000/D240 Array.
When the problem occurs, SCSI warnings similar to the following might be
displayed on the console or get logged to the "/var/adm/messages" file:
WARNING: /sbus@55,0/QLGC,isp@1,10000/sd@0,0 (sd0):
SCSI transport failed: reason `reset`: retrying command
This problem can occur in the following releases:
SPARC:
Solaris 2.5.1
Solaris 2.6
Solaris 7
Solaris 8
NOTE: Solaris x86 (Intel platform) is not affected.
Systems will be affected if the following two conditions are met:
For D1000:
----------
. The system has a directly attached StorEdge D1000 / Netra st D1000
Array (no intermediate A3500/A3500FC controller).
. The system has a modified /kernel/drv/st.conf file which contains
entries for SCSI targets 14 or 15 accessing extended LUNs or LUN>7.
For example, systems with directly attached D1000 Arrays will be affected
if they have "st.conf" entries like the following:
name="st" class="scsi"
target=14 lun=8;
and/or
name="st" class="scsi"
target=15 lun=8;
For D240:
---------
. The system has a directly attached StorEdge D240 / Netra st D1000
Array (no intermediate A3500/A3500FC controller).
. The system has a directly attached StorEdge D240.
. The system has a modified /kernel/drv/st.conf file which contains
entries for SCSI targets 2 or 3 accessing extended LUNs or LUN>7.
For example, systems with directly attached D240 Arrays will be affected
if they have "st.conf" entries like the following:
name="st" class="scsi"
target=2 lun=8;
and/or
name="st" class="scsi"
target=3 lun=8;
The specified "lun" number might vary. These lines are, by default,
commented out by a hash ("#") character at the beginning of each line.
The root cause for this issue is that StorEdge D1000 / Netra st D1000
arrays reserve SCSI IDs 14 and 15 for optional environmental
monitoring. These SCSI IDs are assigned to the GEM chips found on the
D1000 controller board. This monitoring is only functional when used
in conjunction with the Sun StorEdge A3500/A3500FC controller. Also,
the D240 reserves SCSI IDs 2 and 3.
At the time of the failure the devices at target 14 and 15 on the D1000,
and the devices in the D240 at target 2 and 3 do not respond to a
SCSI Inquiry. drvconfig asks st_probe to do a scsi_probe and ISP,
which executes the probe, receives nothing back and times out after 60
seconds. When the devices do not respond, the target driver does not
know to abort the SCSI request, leading to the timeout.
IMPLEMENTATION:
---
| | MANDATORY (Fully Pro-Active)
---
---
| | CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
---
---
| X | REACTIVE (As Required)
---
CORRECTIVE ACTION:
The following recommendation is provided as a guideline for authorized
Enterprise Services Field Representatives who may encounter the above
mentioned problem.
To avoid the described issue, leave the lines related to SCSI IDs 14 and
15 relating to extended LUNs ( LUN > 7 ) in the
"/kernel/drv/st.conf" file
commented out, as shown in the
following example:
#name="st" class="scsi"
# target=14 lun=8;
#name="st" class="scsi"
# target=15 lun=8;
For StorEdge D240, SCSI IDs 2 and 3 should not be used on a SCSI bus with
a "Sun StorEdge D240" attached.
NOTE: Using extended LUNs (LUN > 7) on targets 2 and 3 for the D240
devices and targets 14 and 15 for the D1000s. These targets on
the respective devices may be used as long as they do not reference
LUNs above 7.
To avoid the described issue, leave the lines related to SCSI IDs 2 and
3 relating to extended LUNs ( LUN > 7 ) in the
"/kernel/drv/st.conf" file
commented out, as shown in the
following example:
#name="st" class="scsi"
# target=2 lun=8;
#name="st" class="scsi"
# target=3 lun=8;
COMMENTS:
None
============================================================================
Implementation Footnote:
i) In case of MANDATORY FINs, Enterprise Services will attempt to
contact all affected customers to recommend implementation of
the FIN.
ii) For CONTROLLED PROACTIVE FINs, Enterprise Services mission
critical
support teams will recommend implementation of the FIN (to their
respective accounts), at the convenience of the customer.
iii) For REACTIVE FINs, Enterprise Services will implement the FIN as
the
need arises.
----------------------------------------------------------------------------
All released FINs and FCOs can be accessed using your favorite network
browser as follows:
SunWeb Access:
--------------
* Access the top level URL of http://sdpsweb.ebay/FIN_FCO/
* From there, select the appropriate link to query or browse the FIN and
FCO Homepage collections.
SunSolve Online Access:
-----------------------
* Access the SunSolve Online URL at http://sunsolve.Corp/
* From there, select the appropriate link to browse the FIN or FCO
index.
Supporting Documents:
---------------------
* Supporting documents for FIN/FCOs can be found on Edist. Edist can be
accessed internally at the following URL: http://edist.corp/.
* From there, follow the hyperlink path of "Enterprise Services
Documenta-
tion" and click on "FIN & FCO attachments", then choose the
appropriate
folder, FIN or FCO. This will display supporting directories/files
for
FINs or FCOs.
Internet Access:
----------------
* Access the top level URL of https://infoserver.Sun.COM
--------------------------------------------------------------------------
General:
--------
* Send questions or comments to finfco-manager@Sun.COM
---------------------------------------------------------------------------
Copyright (c) 1997-2003 Sun Microsystems, Inc.