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

FIN #: I1076-1

Create Date: Mar/22/04

SunAlert: No

Top FIN/FCO Report: No

Products Reference: Sun StorEdge A1000/A3x00 Arrays

Product Category: Storage / Diag-Doc-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
------             --------   -----   -----------                 -------------
  -                A1000       ALL     A1000 Storage Array              -
  -                A3000       ALL     A3000 Storage Array              -
  -                A3500       ALL     A3500 Storage Array              -
  -                A3500FC     ALL     A3500FC Storage Array            -
X6530A                -         -      Sun RSM Array 63GB 15X4GB        -
X6531A                -         -      Sun RSM Array 147GB 7X4GB        -
X6532A                -         -      A3000 15*4.2GB/7200 FWSCSI       -
X6533A                -         -      RSM2000 35*4.2GB/7200 FWSCSI     -
X6534A                -         -      A3000 15*9.1GB/7200 FWSCSI       -
X6535A                -         -      A3000 35*9.1GB/7200 FWSCSI       -
SG-XARY1*             -         -      STOREDGE A1000/RACK              -
SG-XARY3*             -         -      STOREDGE A3500/RACK              -
UG/CU-A3500FC*        -         -      ASSY TOP OPT 1X5X9 MAX 9GB 10K   -
UG-A3K-A3500FC        -         -      ASSY UPGRADE A3500FC/TABASCO     -
UG-A3500-A3500FC      -         -      ASSY UPGRADE A3500FC/DILBERT     -
X6538A                -         -      X-OPT A3500FC CONTROLLER         -
6538A                 -         -      FCTY CONTROLLER A3500FC          -
X2611A                -         -      OPT INT I/O BD FOR EXX00         -
X2612A                -         -      OPT INT I/O BD EXX00 W/FC-AL     -
X2622A                -         -      OPT INT GRAPHICS I/O BD EXX00    -

Parts Affected: 

----------------------
Part Number     Description   	                      Model
-----------     -----------   	                      -----
540-4520-01     DRV ASSY 36GB 1-in SCSI SPUD&PLAT       -
540-5455-01     DRV ASSY 73GB 1-in SCSI4 SPUD$PLAT      -

(SCSI Devices)
Type    Vendor    Model      SerialNumber(Min)   SerialNumber(Max)   Firmware
----    ------    -------    -----------------   -----------------   --------
Disk	Hitachi	  DK32EJ36N	    -			-	      PQ08
Disk	Hitachi	  DK32EJ72N	    -			-	      PQ08

References: 

BugId:   4960420 - Newly Installed Hitachi Drives Disappear from dstDevs.

ESC:     549186 - A3500FC has dead luns: Need to know how to recover the 
                  luns.

PatchId: 116369-01: for 36GB SCSI Hitachi drive model DK32EJ36N
         116370-01: for 72GB SCSI Hitachi drives mode DK32EJ72N

Issue Description: 

Replacement Hitachi disk drives with PQ08 firmware in A1000/A3x00
arrays may disappear after "sysReboot" and "dstDevs" commands are
issued.  This only occurs for certain drive ID's.  It may occur
approximately 1% of the time in A3x00 arrays.

This issue affects Hitachi DK32EJ36N (36GB) and DK32EJ72N (72GB) drives
having firmware version PQ08.

If a Hitachi drive is freshly inserted into the [1,0] location, and if
it is missing after "sysReboot", the drive will not be listed as shown
in the following example with the RM6 "drivutil -i" command:

   NOTE: Drive [1,0] does not appear in the list.

   # ./drivutil -i c1t4d1

   Drive Information for monty36

 
 -------------------------------------------------------------------------
|Location |Capacity |Status  |Vendor  |Product         |Firmware |Serial  |
|         |  (MB)   |        |        |ID              |Version  |Number  |
|=========+=========+========+========+================+=========+========|
|[2,0]    |34732    |Optimal |FUJITSU |MAN3367M SUN36G |1502     |00X01696|
|[3,0]    |34732    |Optimal |FUJITSU |MAN3367M SUN36G |1502     |00X01646|
|[4,0]    |34732    |Optimal |FUJITSU |MAN3367M SUN36G |1502     |00X01507|
|[5,0]    |34732    |Optimal |FUJITSU |MAN3367M SUN36G |1502     |00X00921|
 -------------------------------------------------------------------------
..
..

   drivutil succeeded!
   #

Likewise, the drive will not be shown in the RM6 GUI.

NOTE: Drive [1,0] does not appear in the list.

For example,

RM6 GUI -> Configuration -> Module profile -> drives

 --------------------------------------------------------------------------- 
|Location|Capacity|Status  |Vendor  |Product ID      |Firmware|Serial  |Date|
|        |  (MB)  |        |        |                |Version |Number  |Code|
|========+========+========+========+================+========+========+====|
|[2,0]   |34732MB |Optimal |FUJITSU |MAN3367M SUN36G |1502    |00X01696|0129|
|[3,0]   |34732MB |Optimal |FUJITSU |MAN3367M SUN36G |1502    |00X01646|0129|
|[4,0]   |34732MB |Optimal |FUJITSU |MAN3367M SUN36G |1502    |00X01507|0129|
|[5,0]   |34732MB |Optimal |FUJITSU |MAN3367M SUN36G |1502    |00X00921|0129|
 ---------------------------------------------------------------------------
..
..

For troubleshooting, or to see error messages, the FE must establish a
serial connection to the A3x00 to initiate debug mode and enable 
dstEnablePrintDriveSense as follows:

   ld 4952683.

After resetting/rebooting the A3xx controller(s)  OR after reseating
the drive followed by a reboot of A3xx controller(s),  Hitachi drives
may timeout to a "START/STOP UNIT" command sent by the A3x00
controller(s) which will result in the controller disabling the drive.
Once a timeout has occured the drive may not be recognized by the
system.  Engineering analysis has confirmed the START/STOP UNIT command
for the replaced drive may timeout due to a drive Id arbitration
issue.

The problem has been fixed with a new release of drive Firmware.
Hitachi drives with Firmware level PQ08 should be upgraded to Firmware
level PQ0B.

The firmware has been modified such that the "START/STOP UNIT" command
for the replaced drive delays arbitration until all lower drive Id
arbitrations are complete.

Implementation: 

---
        |   |   MANDATORY (Fully Proactive)
         ---    
         
  
         ---
        |   |   CONTROLLED PROACTIVE (per Sun Geo Plan) 
         --- 
         
                                
         ---
        | X |   REACTIVE (As Required)
         ---

Corrective Action: 

The following recommendation is provided as a guideline for authorized
Sun Services Field Representatives who may encounter the above
mentioned issue.

If the system does not recognize a newly installed Hitachi drive after
performing a "sysReboot" command:

1. If you lose a drive after a "sysReboot", reseat the drive. This should
   result in the system recognizing the drive.  If yes go to step 2. If not,
   continue as follows:

  If the Hitachi drive is not recognized by the system, even after
  reseating the drive:

 . remove the Hitachi drive from the system.
 . install the Hitachi drive into a JBOD (StorEdge MultiPack,
   D1000 or D2).
 . upgrade the firmware to PQ0B by following the patch instructions.

2. If you have Hitachi drives with PQ08 code, update to PQ0B:

   Run "drvutil -i" and look at the firmware level and model designator.

    . If it is Hitachi drive DK32EKJ72N or DK32EJ36N, upgrade
      the firmware with one of the following patches.

       . Patch 116369-01 for 36GB SCSI Hitachi model # DK32EJ36N
       . Patch 116370-01 for 72GB SCSI Hitachi model # DK32EJ72N

    . Before installing the FW:

       . ensure all I/O's to the A3xxx is stopped.
       . follow the README's for the identified patches to install
         the drive firmware to the A3xxx systems.

Comments: 

None.

============================================================================

Implementation Footnote: 

i)   In case of MANDATORY FINs, Sun Services will attempt to contact   
     all affected customers to recommend implementation of the FIN. 
   
ii)  For CONTROLLED PROACTIVE FINs, Sun 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, Sun 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.central/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.central/

* From there, select the appropriate link to browse the FIN or FCO index.

Internet Access:
----------------
* Access the top level URL of https://spe.sun.com
--------------------------------------------------------------------------
General:
--------
* Send questions or comments to [email protected]
--------------------------------------------------------------------------