Document Audience:INTERNAL
Document ID:A0109-1
Title:SBus Timeout errors occur during back to back writes using FDDI/S 5.0 board on Ultra systems.
Copyright Notice:Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved
Update Date:Tue Sep 30 00:00:00 MDT 1997

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

 
FCO #: A0109-1
Status: inactive
Synopsis: SBus Timeout errors occur during back to back writes using FDDI/S 5.0 board on Ultra systems.
Date: Sep/30/97
Keywords: 

SBus Timeout errors occur during back to back writes using FDDI/S 5.0 board on Ultra systems

Product Category: Network
Product Affected: 
Mkt_ID   Platform   Model   Description          Serial Number
------   --------   -----   -----------          -------------
A11      Ultra 1    ALL     Ultra Enterprise 1           -
A12      Ultra 1    ALL     Ultra Enterprise 1E          -
A14      Ultra 2    ALL     Ultra Enterprise 2           -

X1025A      -        -      SAS FDDI/S 5.0        510001 - 512702
X1026A      -        -      DAS FDDI/S 5.0        510001 - 512702
Parts Affected: 
Part Number                 Description
-----------                 -----------
370-2339-01 (596-1963-01)   SAS FDDI 5.0 with version 1.0 PLD, noted on label
370-2340-01 (596-1964-01)   DAS FDDI 5.0 with version 1.0 PLD, noted on label
References: 
Esc # : 509135, 508989
BugID # : 4024138 & 4038343
DPCO # : 120
Issue Description: 
SBus Timeout errors occur during back to back writes using FDDI/S 5.0 board
on Ultra systems.  The errors arise due to a marginal timing problem.  Typical
error messages are as follows...

   unix: NFS write error on host LTU1: Stale NFS file handle.
   unix: (file handle: 304484f 4d450000 0 0 b4ed b0198 21228000 0) 

   unix: WARNING: SBus0 Primary Error Timeout: AFSR 0x40000020 00000000
                  AFAR 0x000001ff 0000804c Id 31

Another failure symptom that may be experienced is that the SAS board hangs 
under heavy load.

All FDDI 5.0 SBus cards the version 1.0 PLD chip are affected. Positive 
identification can be achieved by viewing the label on the PLD at 
location U16 on the SBus adapter.  If the Label shows "650-0336-01 Rev. 1.0" 
the board is affected.  If the label shows "650-0336-02 Rev. 1.1" the board 
is not affected by this problem. It is expected that the FDDI/S 5.0 boards 
in the following range of serial numbers are suspect;  

   510001-512702

This problem was corrected in October 1996 in Sun Manufacturing when the 
vendor implemented the use of version 1.1 PLD chip in place of the 
version 1.0 PLD chip.
Implementation: 
---
  	|   |  	MANDATORY (Fully Pro-Active)
	 ---    

         ---
  	| X | 	CONTROLLED PRO-ACTIVE (per Sun Geo Plan) 
	 ---   
			
         ---
  	|   | 	UPON FAILURE
	 ---
Replacement Time Estimate: 
Special Considerations: 
30 minutes
Corrective Action: 
Replace upon failure with the following as applicable:

 	370-2339-01	SAS FDDI 5.0	with version 1.1 PLD chip at U16,
					or with "DPCO_120" label

 	370-2340-01	DAS FDDI 5.0	with version 1.1 PLD chip at U16,
					or with "DPCO_120" label
OR
 
 	370-3142-01	SAS FDDI/S 5.0 w/2-piece backpanel
 	370-3143-01	DAS FDDI/S 5.0 w/2-piece backpanel
Billing Type: 
Warranty: Sun will provide parts at no charge under Warranty 
           Service. On-Site Labor Rates are based on how the
           system was initially installed.

 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.

--------------------------------------------------------------------------
Implementation Footnote: 
________________________

i)   In case of Mandatory FCOs, SunService will attempt to contact all known
     customers to recommend the part upgrade.

ii)  For controlled proactive swap FCOs, SunService mission critical support
     teams will initiate proactive swap efforts for their respective accounts,
     as required.

iii) For Replace upon Failure FCOs, SunService partners will implement the
     necessary corrective actions as and when they are required.

SunWeb Access: 
______________

All released FINs and FCOs can be accessed internally on the SunWeb using your 
favorite network browser as follows:

* Access the top level URL of http://cte.corp/FIN_FCO/

* From there, select the appropriate link to query or browse the FIN and
  FCO Homepage collections.

Supporting documents for FIN/FCOs can be found on Edist.  Edist can be 
accessed internally at the following URL: http://edist.corp/.
 
* From there, follow the hyperlink path of "SunService Documentation" and 
  click on "FIN & FCO attachments", then choose the appropriate folder, FIN or 
  FCO.  This will display supporting directories/files for FINs or FCOs.

--------------------------------------------------------------------------
General:
________

Send questions or comments to [email protected]

---------------------------------------------------------------------------
Statusinactive