Asset ID: |
1-75-1010052.1 |
Update Date: | 2012-07-17 |
Keywords: | |
Solution Type
Troubleshooting Sure
Solution
1010052.1
:
Troubleshooting temperature warnings on an individual component within a Sun Fire [TM] Serengeti or LightWeight8 system
Related Items |
- Sun Fire 4810 Server
- Sun Fire 3800 Server
- Sun Netra 1290 Server
- Sun Fire E6900 Server
- Sun Fire 6800 Server
- Sun Fire 4800 Server
- Sun Fire E2900 Server
- Sun Fire V1280 Server
- Sun Fire E4900 Server
- Sun Netra 1280 Server
|
Related Categories |
- PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: Exx00
- .Old GCS Categories>Sun Microsystems>Servers>Entry-Level Servers
- .Old GCS Categories>Sun Microsystems>Servers>Midrange Servers
- .Old GCS Categories>Sun Microsystems>Servers>Midrange V and Netra Servers
|
PreviouslyPublishedAs
213801
Applies to:
Sun Netra 1280 Server - Version Not Applicable and later
Sun Netra 1290 Server - Version Not Applicable and later
Sun Fire V1280 Server - Version Not Applicable and later
Sun Fire 3800 Server - Version Not Applicable and later
Sun Fire 4800 Server - Version Not Applicable and later
All Platforms
Purpose
This document addresses temperature warnings or errors on an individual component (board, repeater, etc) in 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 or errors related to temperature exist in the configuration on a single implicated device.
Note: If you have multiple devices in the same chassis reporting temperature warnings, see Document
1013119.1: Troubleshooting temperatur warnings on multiple components within a Sun Fire [TM] Serengeti or LightWeight8 system
Troubleshooting Steps
Symptoms:
- A System Board, I/O Board, Repeater, or System Controller reports unusually high or low temperature warnings or messages.
- Fan Tray(s) may be marked Failed in showenvironment output from the System Controller.
- A domain may be unable to be powered on and booted or it could be completely unaffected by the issues.
- The System Controller should be accessible (able to login).
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 systems lights are on, fans are spinning, and SC is responsive or you are able to login to the SC or domain.
- See Document 1010053.1: Troubleshooting Complete system Power Outages on Sun Fire [TM] Serengeti or LightWeight8 Systemsif the system has no power.
2. Verify that all Fan Trays are active and ok (not marked FAILED in showenvironment).
- Confirm the status as shown in Document 1011930.1: Sun Fire[TM] (3800-6800) System Controller Application (ScApp) How To's.
- If there is a failed Fan Tray then please follow the instructions detailed in Document 1008393.1: Troubleshooting Cooling Fan Failures on Sun Fire [TM] Serengeti or LightWeight8 Systems starting after Step 3 of that document.
3. Verify that a single System Board, I/O Board, Repeater, or System Controller's temperature is high as shown in showenvironment output.
- Confirm the status as shown in Document 1011930.1: Sun Fire[TM] (3800-6800) System Controller Application (ScApp) How To's.
4. Verify the errors persist if the component is replaced.
- Reference the appropriate System Service Manual for complete instructions on FRU replacement and procedures:
5. Confirm the errors persist on the same component when the other SC is main.
- If the errors cease utilizing the new SC, then the former SC is suspect.
- SC failover reference: Document 1003245.1: Sun Fire[TM] 3800-6900: System Controller failover functionality
6. Collect the following data and collaborate with the next level of support .
- Oracle Explorer Data Collector - Product Information Center (Doc ID 1312847.1)
- Sun Fire[TM] 3800, 4800, 4810, 6800, E4900, and E6900 servers: How to run scextended Oracle Explorer Data Collector (Doc ID 1011830.1)
- Sun Fire[TM] V1280, E2900, Netra[TM] 1280 And 1290 Servers: Gathering 1280extended Information Using Sun[TM] Explorer Software (Doc ID 1009102.1)
- 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
Product
Netra 1280 Server
Sun Netra 1290 Server
Sun Fire V1280 Server
Sun Fire E6900 Server
Sun Fire E4900 Server
Sun Fire E2900 Server
Sun Fire 6800 Server
Sun Fire 4810 Server
Sun Fire 4800 Server
Sun Fire 3800 Server
Internal Section
At this point, if the customer has validated that each troubleshooting step above is true for their environment, and the issue still exists, collaborate with the next level of technical support.
References
<NOTE:1003245.1> - Sun Fire[TM] 3800-6900: System Controller failover functionality
<NOTE:1008393.1> - Sun Fire [TM] SF3800/SF4800/SF4810/SF6800 - E4900/E6900 - V1280/E2900 - Netra 1280/1290 : Troubleshooting Cooling Fan Failures
<NOTE:1010053.1> - Sun Fire [TM] SF3800/SF4800/SF4810/SF6800 - E4900/E6900 - V1280/E2900 - Netra 1280/1290 : Troubleshooting complete system power outages
<NOTE:1011930.1> - Sun Fire[TM] 3800, 4800, 4810, 6800, E4900, and E6900 System Controller Application (ScApp) How To's.
<NOTE:1013119.1> - Sun Fire [TM] SF3800/SF4800/SF4810/SF6800 - E4900/E6900 - V1280/E2900 - Netra 1280/1290 : Troubleshooting temperature warnings on multiple components
@<NOTE:1018748.1> - How to Run Oracle Explorer and Forward the Data to an Oracle Service Engineer
Attachments
This solution has no attachment