Users Guide

Viewing Power Budget Status Using RACADM
Open a serial/Telnet/SSH text console to CMC, log in, and type:
racadm getpbinfo
For more information about getpbinfo, including output details, see the getpbinfo command section in the Chassis Management
Controller for Dell PowerEdge M1000e RACADM Command Line Reference Guide.
Redundancy Status and Overall Power Health
The redundancy status is a factor in determining the overall power health. When the power redundancy policy is set, for example, to Grid
Redundancy and the redundancy status indicates that the system is operating with redundancy, the overall power health is typically OK. If
the PSU installed on a chassis fails owing to some reason, the overall power health status of the chassis is displayed as Non-Critical.
However, if the conditions for operating with grid redundancy cannot be met, the redundancy status is No, and the overall power health is
Critical. This is because the system is not able to operate in accordance with the configured redundancy policy.
The active CMC polls the health status from the standby CMC to determine if the chassis is redundant. When you disconnect the
network cable, a chassis failover is triggered after 30 seconds. And, the standby CMC is active. The network disruption causes the
originally active CMC to boot after about three minutes and becomes a standby CMC. The health monitoring task on the standby CMC
resumes after five minutes. Health changes, if any, on the standby are processed only after the standby is stable. The active CMC must
wait for eight-and-a-half minutes to determine if redundancy exists. Ensure that the redundancy state is healthy before initiating any
failover owing to the health changes.
NOTE: CMC does not perform a pre-check of these conditions when you change the redundancy policy to or from grid
redundancy. So, configuring the redundancy policy may immediately result in redundancy lost or a regained condition.
Related concepts
PSU Failure With Degraded or No Redundancy Policy
PSU Removals With Degraded or No Redundancy Policy
New Server Engagement Policy
Power Supply and Redundancy Policy Changes in System Event Log
PSU Failure With Degraded or No Redundancy Policy
CMC decreases power to servers when an insufficient power event occurs, such as a PSU failure. After decreasing power on servers,
CMC re-evaluates the power needs of the chassis. If power requirements are still not met, CMC turns off lower priority servers.
Power for higher priority servers is restored incrementally while power needs remain within the power budget. To set the redundancy
policy, see Configuring Power Budget and Redundancy.
NOTE:
When a chassis exceeds the power budget, the CMC displays the message, Unable to turn on Module-x
because of insufficient power.
PSU Removals With Degraded or No Redundancy Policy
CMC may begin conserving power when you remove a PSU or a PSU AC cable. CMC decreases power to the lower priority servers until
power allocation is supported by the remaining PSUs in the chassis. If you remove more than one PSU, CMC evaluates power needs again
when the second PSU is removed to determine the firmware response. If power requirements are still not met, CMC may turn off the
lower priority servers.
Limits
• CMC does not support automated power-down of a lower priority server to allow power up of a higher priority server; however, you
can perform user-initiated power-downs.
• Changes to the PSU redundancy policy are limited by the number of PSUs in the chassis. You can select any of the three PSU
redundancy configuration settings listed in Default Redundancy Configuration.
200
Managing and Monitoring Power