------------------------------------------------------------
            - Sun Proprietary/Confidential: Internal Use Only -
------------------------------------------------------------------------

  ***  Sun Confidential:  Internal Use and Authorized VARs Only  ***
________________________________________________________________________

  This message including any attachments is confidential information
  of Sun Microsystems, Inc.  Disclosure, copying or distribution is
  prohibited without permission of Sun.  If you are not the intended
  recipient, please reply to the sender and then delete this message.
________________________________________________________________________
  
                        FIELD INFORMATION NOTICE
               (For Authorized Distribution by Sun Service)

FIN #: I1150-1

Create Date: Dec/17/04

SunAlert: No

Top FIN/FCO Report: No

Products Reference: Sun StorEdge 3310, SE3510, SE3511 Arrays

Product Category: Storage / Diag-Doc-Service

Product Affected: 

Systems Affected:
-----------------  
Mkt_ID      Platform    Model     Description                     Serial Number
------      --------    -----     -----------                     -------------
  -          Anysys      ALL      System Platform Independent           -


X-Options Affected:
-------------------
Mkt_ID      Platform     Model     Description                    Serial Number
------      --------     -----     -----------                    ------------- 
  -          SE3310       ALL      Sun StorEdge 3310 Array              -
  -          SE3510       ALL      Sun StorEdge 3510 Array              -
  -          SE3511       ALL      Sun StorEdge 3511 Array              -

Parts Affected: 

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

References: 

N/A

Issue Description: 

Each of the storage arrays SE3310, SE3510, SE3511 can have up to two
RAID controllers.  While a dual controller array provides better
availability, the performance for write operations is less than the
write performance with single controller.  The difference is
specifically significant for sequential write operations; the
performance with dual controller can be as low as one third of a single
controller array. The reason is as follows:

The controller cache manager handles all communication and cache
coherency between redundant controllers.  The sequential write
performance increases the overall thread time mainly due to:

   . processor access to data cache utilizing processor cycles and
     bandwidth.
   . peer controller must acknowledge the receipt of the user data.

Sequential write benchmark is the worst case; increased processor
access to data cache results in a heavy reduction of overall throughput
versus a single controller configuration.

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.

This issue is not going to be fixed in the current architecture.  Next
generation of products with new architecture will not have this write
performance issue.  There will be no workaround provided, and this FIN
will be updated once the next generation products with new architecture
is available.

If you have issues, concerns or questions regarding on the Corrective
Action, please contact Bagher Vahdatinia, or Raj Chellani of Network
Storage Engineering Group.

Comments: 

None.

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

NOTE: FIN Tracking Instructions for Radiance/SPWeb:
--------------------------------------------------

If a Radiance case involves the application of a FIN to solve a customer
issue, please complete the following steps in Radiance/SPWeb prior to
closing the case:
 
    o Select "Field Information Notice" in the REFERENCE TYPE field.

    o Enter FIN ID number in the REFERENCE ID field.
      For example; I1111-1.

If possible, include additional details in the REFERENCE SUMMARY field
(ie. implementation complete, customer declined, etc.)
--------------------------------------------------------------------------


Implementation Notes:
--------------------

In case of "Mandatory" FINs, Sun Services will attempt to contact
all known customers to recommend proactive implementation.

For "Controlled Proactive" FINs, Sun Services mission critical
support teams will initiate proactive implementation efforts for
their respective accounts as required.

For "Reactive" FINs, Sun Services and partners will implement
the necessary corrective actions as the need arises.


Billing Information:
-------------------

Warranty: On-Site Labor Rates are based on specified Warranty deliverables
          for the affected product.

Contract: On-Site Labor Rates are based on the type of service contract.

Non Contract: On-Site implementation by Sun is available based on On-Site
              Labor Rates defined in the Price List.

--------------------------------------------------------------------------

All FIN documents are accessible via Internal SunSolve.  Type "sunsolve"
in a browser and follow the prompts to Search Collections.

For questions on this document, please email:

        [email protected]

The FIN and FCO homepage is available at:

        http://sdpsweb.central/FIN_FCO/index.html

For more information on how to submit a FIN, go to:

        http://pronto.central/fin.html

To access the Service Partner Exchange, use:

        https://spe.sun.com
--------------------------------------------------------------------------