![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Predictive Self-Healing Sure Solution 1676591.1 : Power source recommendations for Oracle T5xx0, T3-x, T4-x, T5-x, T7-x, S7-x, M7-x, T8-x, & M8-x servers
Applies to:SPARC T3-1 - Version All Versions and laterSPARC T3-2 - Version All Versions and later SPARC T7-4 - Version All Versions and later SPARC SuperCluster T4-4 Full Rack - Version All Versions and later SPARC S7-2L - Version All Versions and later Information in this document applies to any platform. PurposeThis documents the source of power that Oracle recommends for it's T5xx0, T3-x, T4-x, T5-x, T7-x, & S7-x, M7-x, T8-x, & M8-x servers. Scope
DetailsThe power specifications for Oracle T5xx0 & newer servers are stated in the Released Installation Guide for each server, such as the SPARC T4-1's E22988-08. The "Electrical and Power Specifications" section will state the input voltage, current, & power specifications. DC powered systems typically accept voltages as low as 48V DC & typically recommend a positive ground (eg -48V DC). AC powered systems could either allow 100V AC to 120V AC or 200V AC to 240V AC. For example, the T3-2 minimally requires 200V AC. Line voltage drop must be taken into account for power distribution with in racks for the system furthest from the source due to distribution losses.
The higher the PSU's load, the quicker it will drop out when power is lost.
Power Redundancy:
Uninterruptible Power Supplies (UPS): UPSs have two commonly used operating modes. One method is Standby USP mode where the UPS can switch to battery output mode if the input source falls out of threshold. This mode could have problems when the UPS switches back to the AC source shortly after AC power is restored. Some brands of UPSs may not properly handle several power interruptions over a short time period which could results in a power interruption to the server. A more reliable method is to use Double Conversion On-Line UPS where the UPS output is always derived from a power inverter which is typically supplied by the AC input unless an AC problem occurs. The other modes are not commonly used, so usage should only be done at the UPS vendor's recommendation. A second UPS on the redundant power source helps to avoid outages at sites with problematic power sources since it's unlikely that the timing of the UPS output interruptions on both sources will overlap for 10ms. Oracle recommends a pure sine wave UPS using the double conversion mode which provides the greatest reliability. Please note that Schneider has a great document on the advantages of different operating modes. You can point customers to this document by:
SPARC T3-x through T8-x / M7-x through M8-x Server PSU generations & input voltage sensors:
A249: Used in the T5x20, T5140, T5240, T3-1 & T4-1 systems. The only PSU input sensor is VINOK which is periodically sampled at roughly a 5 second rate & is not latched. VINOK indicates if the input voltage falls outside the upper or lower critical threshold even if the PSU remains operational. Unfortunately, a sensor event is not typically detected if a PSU's power source has a temporary brown-out unless caught by a 5 second sample. If a fault is detected, it is latched until cleared by the ILOM or by the PSU being power cycled. If all PSUs lose power at once, then there is no indication that the system rebooted due to power loss & a POK fault is typically generated for the event. When A249 PSUs power the system & a host reboot occurs, one should first determine if the also ILOM went offline & rebooted once power was restored. An ILOM outage will always result in an ILOM reboot once power is restored. On the other hand, a similar scenario can occur if the ILOM becomes inoperable due to a firmware problem which also affects the host & a power cycle is used to restore operation. One should check for VINOK events on multiple PSUs with in the last 3 months which increases the likelihood that a reboot could be due to power loss. A238/A246: Used in the T5440. Same comments as the A249. A239: Used in the T3-2, T3-4, T4-2, T4-4, & T5-2. These PSUs have 2 latched sensors:
If all PSUs lose power at once, then there is no indication that the system rebooted due to power loss. When A239 PSUs power the system & a host reboot occurs, one should first determine if the also ILOM went offline & rebooted once power was restored. An ILOM outage will always result in an ILOM reboot once power is restored. On the other hand, a similar scenario can occur if the ILOM becomes inoperable due to a firmware problem which also affects the host & a power cycle is used to restore operation. One should check for V_IN_ERR events on multiple PSUs with in the last 3 months which increases the likelihood that a reboot could be due to power loss. T4-2 & T4-4 systems with firmware 8.2.2.b or newer may not show most V_IN_ERR events due to event filtering added to that firmware. Please see T4-2 issue 10: I2C bus filtering due to FCO: 1570318.1. A258: Used in the T7-1. Firmware supplies PSU register info on some PSU faults via ereports. A power cycle clears these registers, though. A261: Used in the T5-4, T5-8, T7-4, M7-8, & M7-16. Same comments as the A239 unless firmware 9.5.1.b is installed which allows PSU register data to be displayed in some PSU fault related ereports. This data remains intact after power cycles & is cleared via system clear. The M7 PSU's firmware can be obtained: here. A263: Used in the T7-2 & T8-2. Firmware supplies PSU register info on some PSU faults via ereports. This data remains intact after power cycles & is cleared via system clear. A265 (Bell) & A265D (Delta): Used in the T8-4 & M8-8. Similar to A261 but different size & input faults retained over power cycles. A266: Used in the T8-1. Similar to A256 & A258 but double the output power, input faults retained over power cycles, & additional functionality added.
FMA Faults related to input power: SPT-8000-MJ (fault.chassis.power.fail) - Power Supply general failure
FMA Alerts related to input power:
Attachments This solution has no attachment |
||||||||||||
|