Release Notes

Known Issues
Issue 1: On the Power Analysis page, the available power of a group is not displayed correctly when the rack’s peak power exceeds
its allocated power.
Description: When the peak power consumption in the rack exceeds the power capacity, the available power capacity becomes a
negative value. While calculating the available power capacity on the parent group it should be reduced in the total available power
capacity. But in current OMPC code, the available power capacity is counted as 0.
Resolution: When the peak power exceeds power capacity, OMPC will sent out critical event to remind the user about the abnormal
case. The user has to increase the available power of the rack by editing the rack properties.
Issue 2: Power/temperature history data of last one hour time period is not updated.
Description: In all 30 minutes time zones (UST +30min, +1.30, +2.30, +3.30, and so on), the last one hour data cannot be updated.
You have to wait till the second half of each hour to get the data. For example, you may have to wait till +3.00 to get the updated
information, as it is not possible at +2.30 time period.
Resolution: If you are in the 30 minute time zone, it is recommended to wait till the second half of an hour to query the last one hour
data.
Limitations
Issue 1: The power graph is blank while viewing the power (or temperature) history.
Description: When viewing the power history (or temperature) of a selected group in the 15 minute/1H window, the graph is blank.
Possible cause: OpenManage Power Center has just been installed and has not collected enough data to provide a power history
graph.
Resolution or workaround: It is recommended to wait as OpenManage Power Center collects appropriate data to present the graph.
Issue 2: Getting Average inlet temperature events on an empty group. There is no device in the group, why is the event generated?
Description: The event is generated because you set the Min Warning threshold or Min critical Threshold values, but there are no
devices present in the group. The temperature is reported as 0 in an empty group, and hence the event is generated.
Resolution or workaround: This is not a recommended practice. You should only set the temperature or power threshold on groups
that contains devices.
Issue 3: Getting event Power returns to normal, but the server is in the lost connection state.
Description: I got an alert that the average power usage exceeds the set threshold, and then I got an alert that Power returns to
normal, but when checking the server, I nd that the server is in the lost connection state. What do I do now?
The reason you had a “Power returns to normal” message is because OpenManage Power Center cannot communicate with the
server to collect power data on the power usage threshold due to the “lost connection” issue.
Resolution or workaround: The message is misleading; however, when getting the lost connection alert, Dell recommends that you
analyze and re-establish the connection with OpenManage Power Center rst. Once the server is connected, OpenManage Power
Center collects the required power data and then reports the status or sends the appropriate event alert.
Issue 4: Though I have edited and saved the IPMI key, the next time I open the saved IPMI prole, the key is once again displayed as
0000.
Description: The key might have changed, and the you may have updated the value . However, while the display should read the
value as xxxx… as the key is encrypted, the encrypted key is instead displayed as 0000….. There is no dierence between the display
0000…. and xxxx….
Resolution or workaround: N/A
Issue 5: OMPC does not provide a warning when I delete my own LDAP account..
Description: I logged into OpenManage Power Center with my LDAP account, and then deleted the LDAP account in the user
management settings screen, but OpenManage Power Center did not provide a warning that was deleting the account I was using
to log in.
To be xed in the subsequent release which will have a warning message to ensure that you aware that you are deleting the current-
user account.
4