![]() | Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type FAB (standard) Sure Solution 1404618.1 : FCO A0320-1: Proactive: 3.3v DC-DC Converter failures on some Sun SPARC Enterprise M5000 systems.
In this Document
Oracle Confidential (PARTNER). Do not distribute to customers
Applies to:Sun SPARC Enterprise M5000 Server - Version: Not Applicable to Not Applicable - Release: N/A to N/AInformation in this document applies to any platform. __________ Affected Parts: 300-2363 - 3.3V DC-DC Converter, DDC_B SymptomsThe 3.3V DC to DC Converters (part number 300-2363) used on I/O Units (part number 541-2240) and shipped in the Sun SPARC Enterprise M5000 may fail under high PCI load conditions, resulting in system availability issues. Impact This will cause the I/O Units (IOUs) to fail and system to become unusable. ChangesContributing Factors There is no evidence that the M4000 is impacted by this issue. CauseNewly qualified 3.3v DC-DC Converters (p/n 300-2363) may experience a signal integrity issue under heavy PCI load condition. These new converters were not tested at full load in Manufacturing. This omission was recognized soon after converter introduction and a StopShip/Purge was initiated on November 14, 2011 at which time M5000 systems again began shipping with the previous converters (p/n 300-2010).Further root cause to determine why some units fail under heavy load is currently underway with the supplier. Until then the 300-2363 has be dis-qualified for use in the M5000. SolutionTarget Completion Date: 31-Jul-2012 Workaround Using the attached customer list proactively replace all affected 3.3v DC-DC Converters (p/n 300-2363) with part number 300-2010 until the above Target Completion Date. Each impacted M5000 system will contain 2 affected converters. A Customer Ready document and Cover Sheet are available as attachments to this knowledge article. ...to be used to proactively contact customers with affected systems. This customer list has two tabs; The first tab is customer information taken from contract and SR data and should be used first to locate affected systems. The second tab is customer information from shipment data and should be used if affected systems are not located using the first tab. To help identify the affected part a picture is attached to this knowledge article. Hardware Remediation and Material Availability Details: For information about FAB documents, its release processes, implementation strategies and billing information, click here. ReferencesFAB > Hardware Remediation > MandatoryAttachments This solution has no attachment |
||||||||||||
|