Asset ID: |
1-75-1010053.1 |
Update Date: | 2011-03-18 |
Keywords: | |
Solution Type
Troubleshooting Sure
Solution
1010053.1
:
Troubleshooting complete system power outages on Sun Fire [TM] Serengeti or LightWeight8 Systems
Related Items |
- Sun Fire E6900 Server
- Sun Fire 3800 Server
- Sun Fire 6800 Server
- Sun Netra 1280 Server
- Sun Fire E4900 Server
- Sun Fire 4800 Server
- Sun Fire V1280 Server
- Sun Fire E2900 Server
- Sun Netra 1290 Server
- Sun Fire 4810 Server
|
Related Categories |
- GCS>Sun Microsystems>Servers>Midrange V and Netra Servers
- GCS>Sun Microsystems>Servers>Entry-Level Servers
- GCS>Sun Microsystems>Servers>Midrange Servers
|
PreviouslyPublishedAs
213802
Applies to:
Sun Netra 1280 Server
Sun Netra 1290 Server
Sun Fire V1280 Server
Sun Fire 3800 Server
Sun Fire 4800 Server
All Platforms
Purpose
DescriptionThis document addresses power outages affecting
Sun Fire [TM] 3800, 4800, 4810, E4900, 6800, E6900 (Serengeti) and Sun
Fire [TM] v1280, E2900, and Netra [TM] 1280, 1290 (LightWeight8)
systems.
This document covers situations where the system is
unable to be powered on, believed to be down (dead), or is simply
unreachable and the suspect cause is related to power problems either
within the system, rack, or environment.- If your system is powered on and you are seeing errors or
warnings associated to a Power Supply Unit, see Document: 1007049.1 Troubleshooting Power Supply Warnings or Failures 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 system may be described as
completely down, dead, or unresponsive to ping, telnet, or similar.
- There may be no lights or LEDs lit
on the system.
- The fans may not be spinning on
the platform.
- The System Controller may or may
not be reachable. Domains are likely to be down, unreachable,
unable to ping, logged into, etc.
- Multiple systems in the same rack
or environment could be effected or this could be a single system
event.
Assumption:
This document assumes that AC power source (for Sun Fire[TM]
systems) is 200-240 VAC, 47-63 Hz, 32 A(per power cord) and DC
power source (for Netra systems) is -48VDC / -60VDC. See the
Sun
System Handbook (SSH) for each system's specific environmental
requirements.
Last Review Date
August 11, 2010
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 FollowPlease 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 the system in question is
completely powered down.
- The domains will be completely unaccessible and the System
Controller should also be unaccessible to pings, telnet, serial
connection, or SSH connections.
- There should be no lights on
the system or fans spinning.
2. Verify this is the only
system suffering a power outage.
- If other systems are suffering power outages, the issue is external to this system and needs to be troubleshot by the site electrician or data center management team.
- If the issue affects only a single rack within the entire data center configuration troubleshoot the rack's power distribution components and the power being provided to this rack configuration.
3. Verify the RTS, RTU, and AC
Input Modules have their power cables securely
attached.
- Reference the appropriate System Service Manual (Power section) for pictures of each of these devices:
- Reference Document: 1011893.1 Sun Fire [TM] 3800-6800 AC/DC Power Distribution for a diagram of how the parts connect to each other.
- See the Assumption listed in the beginning of this document for power source requirements.
4. Confirm that the RTS/RTU, AC Input Module, and the power source (environment) breakers are ON for the system in question.
- Same references should be used from Step 3 to verify the breaker status with the addition of confirming that the site's electrician or data center manager has confirmed this system's power source is in working order.
- Future steps may require hardware replacement - If so, Oracle Support Services may need to be engaged to proceed. Try to validate what checks you can on your own and engage support if/when it is determined that hardware must be replaced.
5. Verify the RTS/RTU LEDs are lit, and there is no wrench light (fault light) lit.- If the lights on the RTS/RTU are not lit or the fault light is lit, and external power is confirmed fine (previous steps), the RTS/RTU is suspect.
6. Verify the AC Input Modules are lit, and there is no wrench light (fault light) lit.- If the lights on the AC Input Module are not lit or the fault light is lit, the AC Input Module is suspect.
7. Verify all PSUs are lit , and there is no wrench light (fault light) lit on a PSU.- If the lights on a PSU is not lit or a fault light is lit on one unit, the PSU is suspect.
- If the lights on multiple PSUs are not lit or a fault light is lit on multiple units the Power Centerplane is suspect.
8. Verify the system is still unable to be powered on after replacing any of the suspect components identified above.- Discuss the next steps with Oracle Support Services, who should already be engaged to replace components in the system (if they are suspect).
- They may need to collaborate with the next level of technical support to coordinate the next steps involved in resolving this issue.
Attachments
This solution has no attachment