Document Audience: | INTERNAL |
Document ID: | A0220-1 |
Title: | A total of 13 Sun Fire 6800 power distribution centerplanes with date code "08-03" may experience a thermal event. |
Copyright Notice: | Copyright © 2007 Sun Microsystems, Inc. All Rights Reserved |
Update Date: | Thu Aug 19 00:00:00 MDT 2004 |
__________________________________________________________________
*** 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 #: A0220-1
Status: inactive
Synopsis: A total of 13 Sun Fire 6800 power distribution centerplanes with date code "08-03" may experience a thermal event.Date: Aug/19/2004
SunAlert: No
Top FIN/FCO Report: Yes
Products Reference: Sun Fire 6800
Product Category: Server / System Component
Product Affected:
Systems Affected:
Mkt_ID Platform Model Description
------ -------- ----- -----------
- S24 - Sun Fire 6800
X-Options Affected:
Mkt_ID Platform Model Description
------ -------- ----- -----------
N/A
Parts Affected:
Part Number Description
----------- -----------
501-5005-04 Power Distribution Centerplane
(SCSI Devices)
Type Vendor Model SerialNumber(Min) SerialNumber(Max) Firmware
---- ------ ------- ----------------- ----------------- --------
N/A
References:
WWStopShip: P001-20148.A2
Manual: http://sunsolve.central/data/805/805-7363/pdf/
Issue Description:
A total of 13 power distribution centerplanes (501-5005-04) may experience
a thermal event. These 13 affected centerplanes were only shipped in the
Sun Fire 6800 servers. The potential for a thermal event increases over
time.
Only centerplanes with a date code of "08-03" are affected.
A total of 46 Sun Fire 6800 systems were shipped during the suspect
time frame, and need to be inspected for the affected centerplanes.
Provided following documentation is provided below;
. Customer List
. Inspection Instructions
. Customer Letter
An internal only link to the customer list identifying the affected systems
can be viewed via the below "Internal Only" URL;
http://sdpsweb.central/FIN_FCO/FCO/FCO_A0220-1_Dir/Customer_List.sxc
To assist the field in a visual Date Code Inspection (with pictures) use
the following URL ;
http://sdpsweb.central/FIN_FCO/FCO/FCO_A0220-1_Dir/SPE/Inspection_Instructions.sxw
To assist the field in a communication of this issue to customers, a Customer
Letter is provided via the below URL;
http://sdpsweb.central/FIN_FCO/FCO/FCO_A0220-1_Dir/SPE/Customer_Letter.sxw
Symptoms
--------
This issue has not caused a thermal event to date, however, there is the
potential for smoke and carbonization of the centerplane.
Another possible symptom would be errors showing the Fan Tray can not be
sensed by an SSC as shown below:
SSC console messages:
Sep 22 15:40:21 ssc0 Platform.SC: FT3: Could not get i2cSwitch
Command output :
ssc1:SC>showboards
Slot Pwr Component Type State Status Domain
---- --- -------------- ----- ------ ------
SSC0 On System Controller Spare - -
SSC1 On System Controller Main Passed -
ID0 On Sun Fire 6800 Centerplane - OK -
FT0 On Fan Tray High Speed OK -
FT1 On Fan Tray High Speed OK -
FT2 On Fan Tray High Speed OK -
FT3 ? Unknown board - - -
...
The above example shows "FT3" as an "Unknown board" which should
show "Fan Tray".
ssc1:SC>poweron FT3
java.lang.IllegalArgumentException: Fan Tray #3 not in HW tree
at sun.serengeti.api.GetFanSpeed.invoke(Unknown Source)
at sun.serengeti.api.GlobalApi.getFanSpeed(Unknown Source)
at sun.serengeti.cli.CliPower.powerAttempt(Unknown Source)
at sun.serengeti.cli.CliPower.powerHpu(Unknown Source)
at sun.serengeti.cli.CliPower.powerList(Unknown Source)
at sun.serengeti.cli.CliPower.invoke(Unknown Source)
at sun.serengeti.cli.CmdProxy.invoke(Unknown Source)
at sun.serengeti.cli.SpShell.parse(Unknown Source)
at sun.serengeti.cli.SpShell.run(Unknown Source)
WARNING!
A fatal error occurred while executing the last command.
Rebooting the system controller is recommended.
In the above example ">poweron FT3" results in a "fatal error".
Root cause analysis determined that Manufacturing process defects at
the supplier led to cracked line traces developing over time.
Corrective action was provided by manufacturing via StopShip Notice
P001-20148.A2. There was no change to the dash level of the part
and no DPCO label, as the affected centerplanes are being scrapped
at the Repair Vendor.
Implementation:
---
| X | MANDATORY (Fully Pro-Active)
---
---
| | CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
---
---
| | UPON FAILURE
---
Replacement Time Estimate:
1.5 hours
Special Considerations:
Only after inspecting the centerplane and determining it to be affected
should it be replaced.
Due deligence should be pursued by inspecting all 46 systems listed in
the customer list to find all 13 affected centerplanes.
Corrective Action:
Using the above Customer List and Inspection Instructions, proactively
replace:
- "08-03" date coded 501-5005-04 with 501-5005-04 (or above) outside
of the affected date code
The inspection process will need to be performed until all "08-03" date coded
501-5005-04 centerplanes are recovered. The system should not need to
be shutdown during the visual inspection.
Identification of the date code "08-03" centerplanes can be challenging.
Please use the included Inspection Instructions document as a guide to
implement this corrective action.
For actual centerplane removal instructions use the documentation provided at:
http://sunsolve.central/data/805/805-7363/pdf/
Centerplane removal does require a system shutdown.
Defective Material Tags should be marked with;
"FCO A0220-1 - Return to Vendor to Scrap"
Comments:
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, Sun Services will attempt to contact
all known customers to recommend the part upgrade.
ii) For controlled proactive swap FCOs, Sun Services mission critical
support teams will initiate proactive swap efforts for their respective
accounts, as required.
iii) For Replace upon Failure FCOs, Sun Services partners will implement
the necessary corrective actions as and when they are required.
--------------------------------------------------------------------------
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 [email protected]
---------------------------------------------------------------------------