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

FIN #: I0902-1

Create Date: Nov/27/02

SunAlert: No

Top FIN/FCO Report: Yes

Products Reference: Sun StorEdge 3310 SCSI Array

Product Category: Storage / SW Admin

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
------   --------   -----    -----------                   -------------
  -        3310      ALL     Sun StorEdge 3310 SCSI Array        -

Parts Affected: 

Part Number      Description                       Model
-----------      -----------                       -----
F370-5403-01     Controller LVD 512 Minnow           -

References: 

Manual: 816-7321-12: Sun StorEdge 3310 SCSI Array Controller Replacement 
                     Guide.
        816-7290-11: Sun StorEdge 3310 SCSI Array Installation; Operation; 
                     and Service Manual.

Issue Description: 

A specific group of RAID Controller Module FRU's for the Sun StorEdge
3310 SCSI Array were shipped to the Field with the "Controller Unique
ID" set to a non-zero value.  This could cause incorrect device
identifiers and an incorrect MAC Address to be presented to the host
system when these FRUs are installed into an array.  This can result in
software applications not being able to access the array due to changed
device names.

This issue only affects forty-eight (48) RAID Controller Module FRUs
shipped between 6-Sep-2002 and 24-Sep-2002 with the following serial
numbers:

   3705403000009 3705403000022 3705403000038 3705403000045 3705403000047 
   3705403000059 3705403000081 3705403000082 3705403000084 3705403000085 
   3705403000086 3705403000087 3705403000091 3705403000092 3705403000093 
   3705403000095 3705403000096 3705403000098 3705403000101 3705403000102 
   3705403000103 3705403000107 3705403000110 3705403000114 3705403000154 
   3705403000214 3705403000220 3705403000221 3705403000258 3705403000260 
   3705403000262 3705403000270 3705403000274 3705403000276 3705403000278 
   3705403000283 3705403000286 3705403000288 3705403000289 3705403000295 
   3705403000297 3705403000299 3705403000301 3705403000308 3705403000310 
   3705403000313 3705403000314 3705403000317

It is believed that few, if any, of these FRUs have been installed into
customer systems.  There is no way to determine if a Controller is
affected other than by reading the serial number.

This problem manifests itself primarily in a Sun Cluster environment.
It will only occur during Controller replacement if the array is
powered down, or in a single Controller environment, and the Controller
has a serial number in the affected serial number range listed above.
This is not an issue in a dual Controller environment if the array
stays powered on and a single Controller is replaced.

When this issue occurs, the array will be seen by the host, however,
device identifiers presented to Sun Cluster may have changed, and
therefore device names will have changed.   Since most software
applications rely on using device names that do not change,
applications could hang.

This issue occurs due to a process problem at Sun Manufacturing.  This
has been corrected and all Controller Modules are now shipping with
"Controller Unique ID" set to "0".  With a Controller ID set to zero,
the controller at powerup will read the serial number from the midplane
which is programmed to a unique value during manufacturing.  This value
is used to create the Ethernet MAC Address and device identifiers.

For Controller Modules listed above, the Controller ID must set to "0"
at the time of Controller replacement.  See details provided below.

Field spares inventories were not purged and reworked to address this 
issue.

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
Sun Services Field Representatives who may encounter the above
mentioned problem.

Follow the RAID Controller Module replacement procedure shown in the
Sun StorEdge 3310 SCSI Array Controller Replacement Guide (816-7321-12)
which is shown below.  Pay special attention to the section which
describes setting the "Controller Unique Identifier".  This procedure
is also documented in the Sun StorEdge 3310 SCSI Array Installation,
Operation, and Service Manual (816-7290-11) section "Replacing a
Controller Module".


Controller Replacement Procedure
--------------------------------

The Controller Module is hot-swappable and can be replaced with the array 
powered on.  The replacement procedures for the RAID controller follows.

CAUTION: If you power off the array and replace a Controller, the replacement 
         Controller could become the primary Controller and overwrite any 
         configuration settings previously set.  Before replacing a RAID 
         Controller, save the configuration settings to NVRAM.  If power is 
         removed before you replace a RAID Controller, the settings can be 
         restored from NVRAM.

If you must power off the array before or during Controller
replacement, stop all I/O before you power off and verify that the
cache status returns to a CLEAN state in the top right bar of the
firmware application window.

To Save Configuration Settings to NVRAM:

   1. From the firmware application main menu, choose system functions.

   2. Use the arrow keys to scroll down, and select Controller Maintenance.

   3. Select save NVRAM to disks and press Enter.  Choose Yes to confirm.
      A prompt will inform you that NVRAM information has been successfully 
      saved.

To Remove a Controller Module:

   1. Keep the array powered on.

   2. Turn the thumbscrews on the left and right sides of the Controller  
      Module counterclockwise until the thumbscrews are disengaged from 
      the chassis.

   3. Hold the thumbscrews, and pull out the Controller Module.

To Insert a Controller Module:

   1. Keep the array powered on.  Gently slide the Controller Module into 
      the unit until it clicks and is seated in the backplane.

CAUTION: Be sure that the Controller Module is properly inserted into the 
         guide rails.

   2. Turn the thumbscrews on the left and right side of the Controller 
      Module clockwise until finger-tight, to secure the Module and to make 
      the Modules front-panel flush with the chassis. The new Controller will 
      automatically become the secondary Controller.

If the Array Was Powered Off During Replacement or a Single Controller 
Configuration Had a Replacement:

If the array was powered off during the Controller replacement or if you 
replaced a Controller in a single-Controller configuration, perform the 
following important steps:

   1. Restore configuration settings from NVRAM if the new Controller replaced 
      an old Controller:
   
	a. On the firmware main menu, select system functions, select 
	   Controller Maintenance, and press Enter.
	b. Select Restore NVRAM from disks and press Enter. Press Yes to 
	   confirm.
	   
   2. Set the parameter called the "Controller Unique Identifier" to the 
      correct value:
   
	a. Select view and edit configuration parameters, then select 
           Controller Parameters, and press Enter.
	b. On the Controller Parameters menu, select Controller Unique 
	   Identifier  and press Enter.  Type in the value "0"
	   (to automatically read the chassis serial number from the 
           midplane) or type the hex value for the original serial number 
           of the chassis (used when the chassis has been replaced).

The Controller Unique Identifier is used to create Ethernet Addresses
and World Wide Names. The value "0" is immediately replaced with the
hex value of the chassis serial number.  A non-zero value should only
be specified if the chassis has been replaced but the original chassis
serial number must be retained; this feature is especially important in
a Sun Cluster environment to maintain the same disk device names in a
cluster.

   3. To implement the revised configuration settings from step 1 or 2, 
      select System Functions, select Reset Controller, and press Return.

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.Corp/

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

Internet Access:
----------------
* Access the top level URL of https://infoserver.Sun.COM
--------------------------------------------------------------------------
General:
--------
* Send questions or comments to finfco-manager@Sun.COM
--------------------------------------------------------------------------