Sun Fire[TM] Server System Board (SB) Voltage Errors.
(Doc ID 1019667.1)
Last updated on JULY 31, 2020
Applies to:Sun Fire 3800 Server - Version Not Applicable to Not Applicable [Release N/A]
Sun Fire E2900 Server - Version All Versions to All Versions [Release All Releases]
Sun Fire 6800 Server - Version Not Applicable to Not Applicable [Release N/A]
Sun Fire E6900 Server - Version Not Applicable to Not Applicable [Release N/A]
Sun Netra 1280 Server - Version Not Applicable to Not Applicable [Release N/A]
This document describes how to identify and resolve System Board (SB) errors related to voltage. The servers included are as follows:
- Serengeti - Sun Fire[TM] 3800, 4800, 4810, 6800, E4900, E6900
- Lw8 - Sun Fire[TM] v1280, E2900 and Netra[TM] 1280, 1290
This document does not address I/O Board (IB) voltage errors. See Document 1017844.1 if you have similar errors associated to an IB.
Look for these "Key Indicators" of a voltage issue in error messaging in the System Controller's (SC) log files (showlogs) or console:
When a server encounters an SB voltage error and the domain is not yet booted or in operation the domain it is part of will either fail POST tests, domain or board poweron, a Keyswitch operation, or fail to boot properly. If the domain is already in operation it will crash when a SB encounters a voltage issue.
If the domain crashes, showlogs data might indicate all sorts of Parity Error events as having taken place, such as an Address Parity Error, Parity Bidi Event, L2CheckError Event, or more. The most important thing to note is that when a domain crashes in addition to one of the key following errors, the root cause is likely to be a voltage issue which caused the Parity Error event - not the other way around. See the Additional Information section of this article for an example.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!