---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------  
                            FIELD INFORMATION NOTICE
                  (For Authorized Distribution by SunService)

FIN #: I0747-1

Create Date: Dec/10/01

Keywords: 

In a multi-host environment, systems attached to Sun StorEdge 99x0 Arrays using Logical Unit Size Expansion (LUSE) may lose access to LUN 0:0

SunAlert: No

Top FIN/FCO Report: Yes

Products Reference: Sun StorEdge 99x0

Product Category: Storage / Service

Product Affected: 

Systems Affected
----------------
Mkt_ID   Platform   Model   Description                   Serial Number
------   --------   -----   -----------                   -------------
  -      ANYSYS       -     System Platform Independent         -


X-Options Affected
------------------
Mkt_ID   Platform   Model   Description        Serial Number
------   --------   -----   -----------        -------------

  -      SE9910      ALL    Sun StorEdge 9910        -
  -      SE9960      ALL    Sun StorEdge 9960        -

Parts Affected: 

Part Number   Description   Model
-----------   -----------   -----

    -             -           -

References: 

DOC: HDS 9900 Alert #47: 9900 LUSE Denies LUN Access

URL: http://se9900.emea/information/9910manual.html
     http://se9900.emea/information/9960manual.html
     http://edist.central.sun.com/edist-cgi/list_docs.cgi?division=Network+Storage

Issue Description: 

This FIN provides to the Field a description of and a recommended fix 
for Hitachi Data Systems Alert #47 (9900 LUSE Denies LUN Access).  

In a multi-host environment connected to a Sun StorEdge 99x0, when one
host issues a "SCSI Reserve" command to a LUN which is part of a LUSE,
LUN 0:0 is also reserved, unexpectedly.  This causes I/O from any other
host to LUN 0:0 to fail with a status of "Reservation Conflict."  This
problem is due to a Sun StorEdge 99x0 microcode bug.

Any user running a multi-host environment with host software that
issues "SCSI Reserve" commands to a Sun StorEdge 99x0 running LUSE, can
lose access to LUN 0:0 due to a SCSI reservation conflict.  Some
examples of host configurations that could encounter this problem
include:

  . Windows NT/2000 hosts running Microsoft Cluster Server.

  . AIX hosts.

  . Solaris hosts running SunCluster 2.2 (or later) or hosts running 
    shared disk configurations under Solstice Disk Suite.

NOTE: This FIN does not imply support for any of the above mentioned
      configurations, but rather are merely provided as examples.

In order for this problem to occur, the following additional conditions 
must exist:

  A. At least one LUSE defined on a port configured in an environment 
     as described above.

  B. Use of LUN 0:0 (CU:LDEV=0:0) from any hosts attached to the same 
     port as described in A. above.

  C. Use of Sun StorEdge 99x0 systems running microcode versions prior 
     to 01-15-39-00/05.
     
To identify the version of the microcode in an array, please perform
the following:

   On the Service Processor (SVP), open the "Maintenance" window and
   select "Version." This will indicate which version of microcode is in
   use.  There is no command line equivalent.

To determine if the Control Unit (CU) is using LUSE, please do the following:

   From either the SVP, or the Remote Console use the LUN Manager Tab, one
   can see SCSI Mappings and easily recognize a LUSE volume. First,
   non-LUSE volumes will have an emulation of "*1" e.g., "(OPEN-9*1)++".
   However, LUSE volumes will have an emulation of "*n" where n > 1. "n" is
   the number of LDEVs used by the LUSE. 
     
This problem has been fixed by Hitachi with microcode version 01-15-39-00/05.
StorEdge 99x0 Arrays shipped after November 1, 2001 will have this new
microcode installed.

Implementation: 

---
        |   |   MANDATORY (Fully Proactive)
         ---    
         
  
         ---
        | X |   CONTROLLED PROACTIVE (per Sun Geo Plan) 
         --- 
         
                                
         ---
        |   |   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.

Enterprise Services Field Representatives should notify their affected
Sun StorEdge 99x0 customers about the problem and arrange for a time to
upgrade the microcode in StorEdge 99x0 Arrays.  If a customer's
configuration is at risk for this problem, upgrade the Sun StorEdge
99x0 microcode to version 01-15-39-00/05 (Rev. 1.1 - 11/01/01) or later
using the instructions provided in the field service manual and the
upgrade kit.  Please use the following online documentation:

   http://se9900.emea/information/9910manual.html
   http://se9900.emea/information/9960manual.html

Or, download the StorEdge 9900 Array Maintenance Manual from edist:

   http://edist.central.sun.com/edist-cgi/list_docs.cgi?division=Network+Storage

Upgrade kits are available by sending an email request to [email protected].
There is no charge to Sun personnel for this upgrade kit.  The following 
information is required when sending a microcode upgrade kit request:

   . Date required by
   . Requesters name
   . Requesters e-mail address (if different than the one used)
   . Requesters phone number (a number where he can be contacted if problems
     occur in shipping the microcode)
   . Address (where the micro code shipment is to be sent)
       o Recipients name
       o Company
       o Suite
       o Street Address
       o City, State, Zip, Country
   . Type of delivery (second day delivery, AM, PM)

The standard 9900 field microcode update set contains the following material:

   ---------------------------------------------------------------------
  | Component	  |  Program Name		      | Remarks         |
  |===============+===================================+=================|
  | PK-99MC001-01 |  9900 Micro code DKCMAIN CD-ROM   |	CD ROM          |
  | PK-99MC002-01 |  9900 RMCMAIN CD-ROM	      |	CD-ROM          |
  | PK-99MC003-01 |  9960 Configuration Diskette      |	Floppy Diskette |
  | PK-99MC004-01 |  9910 Configuration Diskette      | Floppy Diskette |
  | PK-99MC005-01 |  9900 Micro code Bill of material | Document        |
   ---------------------------------------------------------------------

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 [email protected]
--------------------------------------------------------------------------