Document Audience:INTERNAL
Document ID:I1043-2
Title:Sun StorEdge 6120 Arrays and 6320 Systems may reset due to a Controller Board SRAM timing issue.
Copyright Notice:Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved
Update Date:2004-01-15

---------------------------------------------------------
            - Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------  
                        FIELD INFORMATION NOTICE
               (For Authorized Distribution by Sun Services)
FIN #: I1043-2
Synopsis: Sun StorEdge 6120 Arrays and 6320 Systems may reset due to a Controller Board SRAM timing issue.
Create Date: Jan/15/04
SunAlert: No
Top FIN/FCO Report: Yes
Products Reference: StorEdge 6020/6120 Array, StorEdge 6320
Product Category: Storage / Array
Product Affected: 
Systems Affected:
-----------------  
Mkt_ID   Platform   Model   Description                    Serial Number
------   --------   -----   -----------                    -------------
  -       SE6320      -     Sun StorEdge 6320 System          See List 


X-Options Affected:
-------------------
Mkt_ID    Platform   Model     Description                    Serial Number
------    --------   -----     -----------                    -------------
 -        SE6020      ALL       Sun StorEdge 6020 Array          See List
 -        SE6120      ALL	Sun StorEdge 6120 Array          See List
 -        SE6120HA    ALL       Sun StorEdge 6120 Array HA       See List
Parts Affected: 
----------------------
Part Number    Description   	         Model
-----------    -----------   	         -----
540-5559-xx    ASSY,T4,2.5 CONTRLR         -
References: 
BugId:   4930674 

PatchId: 114285-08, 115179-03

URL: http://sdpsweb.central/FIN_FCO/FIN/FINI1043-1_dir/cust_list.sxc 
     http://sdpsweb.central/FIN_FCO/FIN/FINI1043-1_dir/SPE/cust_letter.sxw
     http://edist/edist-cgi/list_tools.cgi?division=Network+Storage
     http://wwws.sun.com/software/download/products/3e9b0da1.html
Issue Description: 
------------------------------------------------------------------------
  | CHANGE HISTORY                                                         |
  | ==============                                                         |                                           
  |                                                                        |
  |  Date Modified: Jan/13/04                                              |
  |                                                                        |  
  |  Updates:  PROBLEM DESCRIPTION, CORRECTIVE ACTION, REFERENCES          |
  |                                                                        |       
  |    PROBLEM DESCRIPTION: Changed solution for SE6320 to SP Image 1.1.2. | 
  |                                                                        |
  |    CORRECTIVE ACTION:  Changed solution for SE6320 to SP Image 1.1.2.  |
  |                        Removed Note.                                   |
  |    REFERENCES: Removed patch 115589-03                                 |
  |                                                                        |
   ------------------------------------------------------------------------  

A specific group of Sun StorEdge 6120 Arrays and 6320 Systems may reset in 
rare circumstances due to a controller interrupt caused by an SRAM timing issue.  
There may be the potential for silent data corruption if this occurs. 

A group of 735 SE6120 Controller Boards with out-of-spec SRAM chips has been 
identified.  As many as 325 may have been shipped to customers.  Of those 
controllers, 1%-2% may be expected to be affected.  The issue has only been 
seen in situations where voltage to an SRAM chip has been set to a lower than 
nominal voltage for test purposes. 

The affected group of StorEdge 6120 Arrays and 6320 Systems may be 
identified by array serial number.  A customer list for these arrays/systems 
is available at this Internal Only URL:

   http://sdpsweb.central/FIN_FCO/FIN/FINI1043-1_dir/cust_list.sxc
	
Systems encountering this issue will experience an unexpected system 
reset and ISP dump.  Installation of 3.0.7 (or higher) firmware, as required
by this FIN, will prevent any potential for data loss should a system 
experience a parity error.  The following type of error message is printed in 
the syslog when the new firmware detects a parity error:

  Oct 13 17:56:19 ISR1[1]: N: u1ctr ISP2300[2] RISC processor paused = 0x8113, 
  HCCR = 0xc30
  Oct 13 17:56:19 ISR1[1]: E: u1ctr ISP2300[2] Qlogic External RISC RAM Parity 
  Error Detected 
  
The timing requirements for the front end Fiber Channel controller and its
associated RISC RAM elements were out of spec as per an updated specification 
from Qlogic.  The speed requirement from Qlogic for interfacing the ISP2310 
to the SRAM changed after the completion of the 6120 controller design.  The 
requirement for RAM speed increased ~10%, from 7.5nSec to 6.8nSec.  This 
change was not communicated to the 6120 design team.  A new vendor was 
qualified and shipped components which violated the 7.5nSec specification 
for the SRAM part.  Together, when tested in a low-voltage environment, 
these two issues combined to create a ~12% fallout in the controllers, 
which was subsequently isolated to this RAM interface. 

SRAM specifications have been updated and a new SRAM is being used on new
SE6120 Controller Boards.  For boards with the old SRAM, a firmware 
modification to add parity protection has been made.  Firmware versions 3.0.7 
and 3.1.1 (patches 114285-08 and 115179-03) address this issue for the SE6120. 
SP Image 1.1.2 and later addresses it for the SE6320.
Implementation: 
---
        | X |   MANDATORY (Fully Proactive)
         ---    
         
  
         ---
        |   |   CONTROLLED PROACTIVE (per Sun Geo Plan) 
         --- 
         
                                
         ---
        |   |   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.

For all affected systems in the customer list referenced above, the following
should be installed:

   SE6120 Array:  114285-08 or later (3.0.7) 
                  OR 
                  115179-03 or later (3.1.1)
                  
   SE6320 System: SP Baseline 1.1.2 or later
  
SE6320 SP Image software may be downloaded as follows:

Internal 
http://edist/edist-cgi/list_tools.cgi?division=Network+Storage

External
http://wwws.sun.com/software/download/products/3e9b0da1.html
     
Please use the following Customer Letter as needed to communicate this 
issue to customers:

   http://sdpsweb.central/FIN_FCO/FIN/FINI1043-1_dir/SPE/cust_letter.sxw
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/index.html

* 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]
--------------------------------------------------------------------------
Statusactive