SPARC M6-32
 
SPARC M5-32
 
SPARC M6-32
 

PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: Mx-32
 

In this Document

Symptoms

Changes

Cause

Solution

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: FABs available to Internals and Partners

Applies to:

Symptoms

 Power supplies experiencing this issue will be faulted and not produce any power.  Below is an example consistent with a PSU affected by this issue.

-> show /System/open_problems

Impact

This issue can cause anywhere from 1 to 12 platform PSUs to fail and require replacement.  The platform will become inoperable if more than six power supplies fail, and the system can only be restored to operation once six functioning PSUs are available.

Only the SPARC M5-32 and SPARC M6-32 shipped from manufacturing with these impacted PSUs.  Although the SPARC SuperCluster M6-32 ships with this PSU the firmware fix was already applied prior to any shipments of these systems.  Therefore the only potential for exposure to the SPARC SuperCluster M6-32 was through spares if the firmware was not checked during the PSU replacement.

Changes

Contributing Factors

Transient power loss may cause the power supply to fail.

Cause

A PSU exposed to a power loss where restoration occurs between 100-400ms may exhibit a failure which can only be corrected by replacement.  New firmware addresses this issue and should be loaded on all 12 PSUs.  At the time of publication of this FAB, Service inventory was being purged and reworked with this new firmware via GSAP 6221.B.  However Services will be checking and updating the PSU firmware as required until the above purge is complete.

Solution

Target Completion Date: October 30th, 2014

Workaround

Prior to upgrading the PSU firmware customers experiencing repeated instances of this issue can reduce exposure by improving the quality of the Data Center power.

Resolution

Proactively update PSU firmware on all impacted systems per TSC direction.  To be able to successfully execute this PSU firmware update, ILOM must be at a minimum of 9.1.1.a .

ESG TSC L2 will open SRs and engage the field, who will perform the steps, provided by TSC, to upgrade the firmware on all 12 PSUs per system.

An Oracle Legal approved Customer Ready Document is available and can be found here.

Onsite labor has been estimated at 3.5 hours per system.

Identification of Affected Parts (How To)

There is no physically visible way to tell if a vulnerable part number has had its firmware upgraded or not.  To determine if a platform PSU is at risk for this issue, check the part number and revision

For details on how to check part number and revision, see "SPARC M5-32 and M6-32 Servers: Decoding installed A254 firmware version (Doc ID 1641174.1).  If the PSU has a Board Extra value or fru_rev_level other then 02,  the PSU is affected and the firmware level must be checked.

Hardware Remediation and Material Availability Details

This is a firmware update of the power supplies and therefore hardware remediation is not involved.

Comments

This activity must be performed on-site by a Oracle badged FSE and cannot be performed by the customer.

References

  BugID: 18602165
  Service Alert: 1664921.1
  ECO: E0018839, E0018353
  GSAP: 6221.B
  SR #: 3-791206012

Contacts
  Contributor/Submitter: roy.stiles@oracle.com
  Responsible Engineer: steve.kurihara@oracle.com  
  Responsible Manager: raja.habib@oracle.com
  Business Unit Group: M-Series HW Engineering

This solution has no attachment