Document Audience:INTERNAL
Document ID:I1120-1
Title:Some Vixel Short Wave GBICs 370-2303 has been identified as Long Wave when installed in A5x00 storage array.
Copyright Notice:Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved
Update Date:2004-08-02

------------------------------------------------------------
            - Sun Proprietary/Confidential: Internal Use Only -
------------------------------------------------------------------------  
                        FIELD INFORMATION NOTICE
               (For Authorized Distribution by Sun Services)
FIN #: I1120-1
Synopsis: Some Vixel Short Wave GBICs 370-2303 has been identified as Long Wave when installed in A5x00 storage array.
Create Date: Aug/02/04
SunAlert: No
Top FIN/FCO Report: No
Products Reference: Vixel Short Wave GBICs on A5x00 StorEdge 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
------       --------     -----    -----------            -------------
   -          A5000        ALL     StorEdge A5000               -
   -          A5100	   ALL     StorEdge A5100               -
   -          A5200	   ALL     StorEdge A5200               -
Parts Affected: 
----------------------
Part Number                Description   	                  Model
-----------                -----------                            -----
370-2303-03                Fibre Channel FC AL SW GBIC              -
References: 
N/A
Issue Description: 
A small batch of Vixel Short Wave GBICs, Sun P/N 370-2303-03, that have
the serial ID feature are identifed as long wave when used in the A5x00
StorEdge Arrays.  When these GBICs are installed in A5x00 chassis and
running firmware version 1.09, they are identified on the Front Panel
Module (FPM) as long wave.

These GBICs still function as short wave and they pass data normally
when tested as short wave.  This has significantly increased the number
of DOAs retuned from the field, and the NFT rate has reached 98-100%.
This is an issue with the A5x00 firmware mis-interpreting the serial
number information returned by the GBIC.  Since the A5x00 product has
been EOL'ed, it will not be possible to fix this issue in the
firmware.

The root cause of this issue is related to the A5x00 firmware
misinterpreting the serial ID information returned by this small batch
of Short Wave GBICs. When a GBIC is initially installed in the A5xx
storage array, the A5xx firmware senses it's presence and requests for
it's serial number.  If the returned serial number does not match an
expected serial number for a Short Wave GBIC, then the firmware
classifies it as Long Wave and incorrectly displays such status on the
FPM.
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.

Long Wave and Short Wave GBICs can be visually identified by the color
of it's SC connector (The SC connector is where the external Fibre
Channel cable is plugged into the GBIC).  If the color of the SC
connector is black, then the GBIC is a Short Wave type.  If on the
other hand the SC connector is blue, then the GBIC is a Long Wave
type.  Therefore, the recommended action is to visually inspect the SC
connector when an incorrect status is displayed for a Short Wave GBIC
on the FPM.  If it is black, then you can ignore the FPM status and
continue using the GBICs as long as it's functioning properly.
Comments: 
DOA = Dead On Arrival
NTF = No Trouble Found

============================================================================
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:
 
SunSolve Internal 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


FIN/FCO Homepage 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.

To submit either a FIN or FCO refer to the following URLs for templates
and instructions;

*  For FCO: http://pronto.central/fco.html
*  For FIN: http://pronto.central/fin.html
--------------------------------------------------------------------------
General:
--------
* Send questions or comments to finfco-manager@Sun.COM
--------------------------------------------------------------------------
Statusactive