__________________________________________________________________

***  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 CHANGE ORDER
            (For Authorized Distribution by Enterprise Services)
            

FCO #: A0231-2

Status: inactive

Date: Nov/17/2004

SunAlert: No

Top FIN/FCO Report: No

Products Reference: Fujitsu MAN3367FC and MAN3735FC

Product Category: Storage / Disk

Product Affected: 

Systems Affected:

Mkt_ID   Platform   Model   Description        
------   --------   -----   ----------- 
-        Anysys     -       System Platform Independent   


X-Options Affected:

Mkt_ID      Platform    Model    Description       
------      --------    -----    -----------	
-           -           -        Sun StorEdge 39x0 
-           -           -        Sun StorEdge 69x0        
-           -           -        Sun StorEdge T3                   
-           -           -        Sun StorEdge T3+

Parts Affected: 

Part Number   Description              
-----------   -----------              
540-4519-01   Fujitsu 73GB FCAL Drive   
540-4367-01   Fujitsu 36GB FCAL Drive  


Type    Vendor    Model      SerialNumber(Min)   SerialNumber(Max)  
----    ------    -------    -----------------   ----------------- 
Disk	Fujitsu	  MAN3735FC  01Vxxxxx            04Vxxxxx
			     16Vxxxxx            52Vxxxxx
			     
Disk	Fujitsu	  MAN3367FC  01Vxxxxx            04Vxxxxx
			     16Vxxxxx            52Vxxxxx

References: 

BugID: 4913211     
   ESC:   547906, 548788
   DPCO:  416                      
   PatchID: 116515-02 or later

Issue Description: 

-----------------------------------------------------------------------
| Change History                                                        |
| --------------                                                        |
| Nov/16/2004   Rolled FCO ID to A0231-2.  Changed PatchID 116515-01 to | 
|               116515-02 in References, Issue Description, and Special | 
|               Considerations.  Added note regarding screening script  |
|               support for FW 3.1.4 to Issue Description.              |    
 ----------------------------------------------------------------------- 


Sun StorEdge T3A/T3+ and Sun StorEdge 69x0/39x0 controllers may experience
assertion errors due to 0bx47 SCSI Parity Errors reported by Fujitsu 36GB
and 73GB drives which results in loss of drive availability.

The actual affected drive is passing bad frames to the drives further down 
the loop causing them to report 0bx47 SCSI Parity Errors, although there is
nothing wrong with the drive reporting the error.

The following error messages will be seen in the /var/adm/messages file:

   Sep 16 05:10:15 ISR1[1]: W: u1d7 SCSI Disk Error Occurred (path = 0x1)
   Sep 16 05:10:15 ISR1[1]: W: Sense Key = 0xb, Asc = 0x47, Ascq = 0x0
   Sep 16 05:10:15 ISR1[1]: W: Sense Data Description = SCSI Parity Error

Note:  Before replacing any drives, perform the procedures identified in the
Special Consideration and Corrective Action sections of this FCO.

Root cause has determined that when a drive fails, the defective drive has a
marginal condition in the disk drive's oscillator signal confirmation circuit
that causes the port bypass signals to be enabled and then disabled
intermittently.

When the port bypass is enabled, the loop frames passing through the defective
drives are cut off and the loop frames go to the loop bypass circuit,
effectively breaking up the loop data frames.  This results in this particular
drive passing intermittent broken frames to downstream drives.

Due to the broken frames being intermittently passed around the FC loop,the
controller cannot access the system area of subsequent downstream drives,
and therefore gives up and asserts.

If the disk is intermittently passing broken frames, the controller cannot
successfully complete I/O transactions with any of the disk drives in the FCAL
Loop because the defective drive in the loop breaks up the data frames in that
loop.

Corrective action was made available by the vendor using the screening script
included in patch 116515-02 (or above).  Note: In version -02 of this patch, 
the screening script was modified to work with controller firmware 3.1.4 
and later.

Corrective action was made available in Sun Services via DPCO# 416 as of
November 10, 2003.

Implementation: 

---
|   |   MANDATORY (Fully Pro-Active)
 ---

 ---
|   |   CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
 ---

 ---
| X |   UPON FAILURE
 ---

Replacement Time Estimate: 

4.0 hours

Special Considerations: 

Do _not_ proactively install patch (116515-02) and attempt to screen disks.
Please wait until the specific errors of "0bx47 SCSI Parity Error" have been
reported.  The reason is because of how the patch works.

The screening script first checks the disk Vendor, Model and affected
workweeks.  If the disks fall within this criteria, it then runs in the
background for approximately 1 week testing for a "loss of sync" condition.
Unfortunately the last drive in the loop cannot be measured and it will be
identified as a drive to be replaced, even though it may be a good disk.  Do
not attempt to move disks around for testing.

Therefore, if your customer has experienced "0bx47 SCSI Parity Errors",
install the patch below and proceed to screen the disks.  Hopefully this can
be done before the issue becomes so severe that assertion errors by the
controller results.  When this happens one or all disks become inaccessible.

Follow these instructions:

   o Load patch 116515-02 (or above)

To run the script copy the tar file to a directory, for example;

    # cp Screen.tar.112504 /export
    # cd /export
    # tar xvf Screen.tar.112504

The tar file opens up to files and sub-directories, including a README file.
Refer to the README file for further instructions regarding the screening
script.

    # ./get_linkstatus #

The above command will run the script.  To abort, type ^C any time.

This screening script specifically identifies the affected drives that test
positive for a "loss of sync" condition and recommends their removal.  You do
not need to run the "frulist" command.

If the screen identifies any defective drives, they should be replaced.

The serial number range below shows the affected workweeks and is provided
below for informational purposes only.  (Use the patch to determine drives to
be replaced)


   Part Number        SerialNumber(Min)    SerialNumber(Max)
   -----------        -----------------    -----------------
   540-4367-01        01Vxxxxx             04Vxxxxx
                      16Vxxxxx             52Vxxxxx

   540-4519-01        01Vxxxxx             04Vxxxxx
                      16Vxxxxx             52Vxxxxx

Corrective Action: 

If defective drives are identified using the instructions above in SPECIAL
CONSIDERATIONS, please follow normal maintenance procedures for drive
replacement.

   - replace 540-4367-01 or 540-4519-01 with non-affected disks
   
Replacement drives have been screened and will be labeled with a DPCO 416
sticker if appropriate.

Comments: 

The replacement of the drive should be done during a scheduled maintenance
window without affecting the customer.

The Fujitsu MAP3735FC 73.4GB Allegro 8 (Sun p/n 540-5694) is not affected by
this issue.

________________________________________________________________________

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

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

    o Enter FCO ID number in the REFERENCE ID field.
      For example; A0222-1.

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

Implementation Notes
--------------------

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

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

For "Upon Failure" FCOs, Sun Services and partners will implement
the necessary corrective actions as the need arises.

The CIC process must be used for proactive hardware replacement
requests when an FCO is classified as "Upon Failure".


Billing Information
-------------------

Warranty: Sun will provide parts at no charge under Warranty
          Service.  On-Site Labor Rates are based on specified
          Warranty deliverables for the affected product.

Contract: Sun will provide parts at no charge.  On-Site Labor Rates
          are based on the type of service contract.

Non Contract: Sun will provide parts at no charge.  Installation by
              Sun is available based on the On-Site Labor Rates
              defined in the Price List.

________________________________________________________________________

All FCO 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 FCO, go to:

        http://pronto.central/fco.html

To access the Service Partner Exchange, use:

        https://spe.sun.com

________________________________________________________________________