Troubleshooting Power Supply Warnings or Failures on Sun Fire [TM] Serengeti or LightWeight8 systems

Asset ID:	1-75-1007049.1
Update Date:	2011-03-18
Keywords:

Solution Type Troubleshooting Sure

Solution 1007049.1 : Troubleshooting Power Supply Warnings or Failures on Sun Fire [TM] Serengeti or LightWeight8 systems

Applies to:

Sun Netra 1290 Server
Sun Netra 1280 Server
Sun Fire V1280 Server
Sun Fire 3800 Server
Sun Fire 4800 Server
All Platforms

Purpose

Description
This document addresses power, voltage, or Power Supply Unit warnings or failures on Sun Fire [TM] 3800, 4800, 4810, E4900, 6800, E6900 and Sun Fire [TM] v1280, E2900, and Netra [TM] 1280, 1290 systems.

This document covers situations where the system is powered on, but warnings, errors, or suspected failed Power Supplies exist in the current configuration.

If your system will not power on, see <Document 1010053.1> Troubleshooting Complete system Power Outages on Sun Fire [TM] Serengeti or LightWeight8 Systems.
If you have a component that will not power on, see <Document 1013120.1> Troubleshooting "can't power on" component errors on Sun Fire [TM] Serengeti or LightWeight8 systems.

Symptoms:

The issue may be described as a "power supply failure".
There may be no lights or LEDs lit on individual Power Supply Unit(s).
There may be an amber LED ("wrench" or warning LED) lit on Power Supply Unit(s).
There may be power warnings, voltage warnings, or i2c messages associated with a Power Supply Unit.
The System Controller should be reachable and users should be able to login to it (domains likely unaffected as well).

Last Review Date

March 18, 2011

Instructions for the Reader

A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting Details

Steps to Follow
Please validate that each troubleshooting step below is true for your environment. The steps will provide instructions or a link to a document, for validating the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step.

1. Verify external power is present for the system.

Confirm that the system LEDs are lit, fans are spinning, and the SC is responsive or you are able to login to the SC or domain.
If your system will not power on, see <Document 1010053.1> Troubleshooting Complete system Power Outages on Sun Fire [TM] Serengeti or LightWeight8 Systems.

2. Verify a PSU or multiple PSUs are marked FAILED in showenvironment output.

Confirm the status as shown in <Document 1011930.1> Sun Fire (3800-6800) System Controller Application (ScApp) How To's

3. Verify that all the PSU breakers are on.

This verification includes RTU/RTS breakers (and confirms that no Warning/Amber LEDs exist on the RTU/RTS) if the system is rackmounted.
Reference the appropriate System Service Manual (the Power section) for diagrams and instructions relating to where the breakers are located:

If any breaker is off, have the site administrator or electrician confirm the status of the power to the configuration.
DO NOT TURN THE BREAKER BACK ON WITHOUT HAVING THE POWER FEED VERIFIED FIRST.

4. Confirm the same component errors when the other SC is main (if dual SC configuration)

If the errors cease utilizing the new SC, then the former SC is suspect.
System Controller failover reference is <Document 1003245.1> Sun Fire 3800-6900: System Controller failover functionality

NOTE: A Sun "badged" engineer or Certified Partner engineer should perform most service actions that relate to System or I/O Board re-seats or replacements (upcoming steps).

At this point if you are a customer and have reached this stage in the troubleshooting process, please open a Service Ticket with Sun Support Services or engage your local field office to obtain assistance with resolving this issue. Make sure to mention this knowledge article so we can continue with the following steps to resolve this issue.

5. Verify PSU reseat does not resolve if recently serviced or installed.

When dispatching this replacement to the onsite service technician, instruct the engineer to verify that the RTU/RTS (if rackmounted) shows no warning lights prior to replacing the PSU.
Reference the appropriate System Service Manual for complete instructions on FRU handling and insertion procedures (See links in step 3 above).

6. Verify the PSU still fails after replacing power supply.

Reference the appropriate System Service Manual for complete instructions on FRU handling and insertion procedures (See links in step 3 above).

7. Verify the power cord is not defective.

Each PSU has it's own power cord, so switch the power cord with another functional PSU's cord to see if the issue follows the cord or stays with the suspect PSU.

8. Verify that the PSU works in another slot and "formerly good" PSU fails in "suspect" slot.

Essentially, we're confirming if the failure follows the PSU or stays with the slot.

9. Verify still fails after replacing power backplane/centerplane.

Reference the appropriate System Service Manual for complete instructions on FRU handling and insertion procedures (See links in step 3 above).

10. Collect the following data and collaborate with the next level of support.

It is preferred that Explorer with the appropriate scextended or 1280extended option as detailed in <Document 1018748.1> How to run Sun data and send to Sun engineer
If Explorer data can not be collected for whatever reason see <Document 1003529.1> Procedure to manually collect Sun Fire[TM] Midrange System Controller level failure data

At this point, if you have validated that each troubleshooting step above is true for your environment, and the issue still exists, collaborate with the next level of technical support.

Previously Published As 91425

Attachments

This solution has no attachment