Dell PowerEdge VRTX Chassis Management Controller Version 1.0 for Dell PowerEd - Page 151

Viewing Power Budget Status Using RACADM, Redundancy Status and Overall Power Health

Get Dell PowerEdge VRTX PDF manuals and user guides View all Dell PowerEdge VRTX manuals
Add to My Manuals
Save this manual to your list of manuals

Page 151 highlights

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 PowerEdge VRTX 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 AC Redundancy and the redundancy status indicates that the system is operating with redundancy, the overall power health is typically OK. However, if the conditions for operating with AC 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. NOTE: CMC does not perform a pre-check of these conditions when you change the redundancy policy to or from AC redundancy. So, configuring the redundancy policy may immediately result in redundancy lost or a regained condition. Power Management After PSU Failure When an insufficient-power event occurs, such as a PSU failure, CMC reduces power supply to the servers . After reducing the power, CMC reevaluates the power needs of the chassis. If power requirements are still not met, CMC turns off the lower priority servers. However, this is done on the basis of power redundancy policy that you set on your CMC. A redundant server can tolerate the loss of power without impacting the performance of the 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. Power Management After Removing PSU CMC may begin conserving power when you remove a PSU or a PSU AC cord. 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 again evaluates the power requirements when the second PSU is removed to determine the firmware response. If power requirements are still not met, CMC may turn off the low-priority servers. Limits • CMC does not support automated power-down of a low-priority server to allow turning-on of a higher priority server; however, you can perform user-initiated turn-offs. • Changes to the PSU redundancy policy are limited by the number of PSUs in the chassis. You can select any of the two PSU redundancy configuration settings listed in Default Redundancy Configuration. New Server Engagement Policy If a new server that is turned on exceeds the power available for the chassis, CMC may decrease the power to the lowpriority servers. This could happen if the administrator has configured a power limit for the chassis that is below what would be required for full power allocation to the servers, or if insufficient power is available in case higher power requirements by all servers in the chassis. If enough power cannot be freed by reducing the allocated power of the lowpriority servers, the new server is not allowed to turn on. 151

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
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 PowerEdge VRTX 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 AC Redundancy and the redundancy status indicates that the system is operating with redundancy, the
overall power health is typically
OK
. However, if the conditions for operating with AC 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.
NOTE:
CMC does not perform a pre-check of these conditions when you change the redundancy policy to or from
AC redundancy. So, configuring the redundancy policy may immediately result in redundancy lost or a regained
condition.
Power Management After PSU Failure
When an insufficient-power event occurs, such as a PSU failure, CMC reduces power supply to the servers . After
reducing the power, CMC reevaluates the power needs of the chassis. If power requirements are still not met, CMC
turns off the lower priority servers. However, this is done on the basis of power redundancy policy that you set on your
CMC. A redundant server can tolerate the loss of power without impacting the performance of the 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
.
Power Management After Removing PSU
CMC may begin conserving power when you remove a PSU or a PSU AC cord. 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 again evaluates the power requirements when the second PSU is removed to determine the firmware
response. If power requirements are still not met, CMC may turn off the low-priority servers.
Limits
•
CMC does not support
automated
power-down of a low-priority server to allow turning-on of a higher priority
server; however, you can perform user-initiated turn-offs.
•
Changes to the PSU redundancy policy are limited by the number of PSUs in the chassis. You can select any of
the two PSU redundancy configuration settings listed in
Default Redundancy Configuration
.
New Server Engagement Policy
If a new server that is turned on exceeds the power available for the chassis, CMC may decrease the power to the low-
priority servers. This could happen if the administrator has configured a power limit for the chassis that is below what
would be required for full power allocation to the servers, or if insufficient power is available in case higher power
requirements by all servers in the chassis. If enough power cannot be freed by reducing the allocated power of the low-
priority servers, the new server is not allowed to turn on.
151