Release Notes

New in this release
Power Manager can now support devices up to 6000.
Disabled incompatible version of Power Manager after upgrading OpenManage Enterprise.
Flexibility to download the Power Manager files and install the plugin or extension at a convenient time.
Sort and filter information for all the features in Power Manager.
Support for configuring the power cap value in Watts or percentage at a group level.
Dedicated landing page for Power Manager
Improvements in widgets for better user experience
Support for creating and maintain temperature-triggered policies to prevent damage to managed devices due to overheating
caused by failure of cooling infrastructure by applying Emergency Power Reduction (EPR) on the devices.
Added support to view temperature-triggered policy details in existing in-built reports.
View the top 10 devices and groups violating power and temperature thresholds.
Support for Dell EMC VxRail systems.
Support for PowerEdge servers with AMD processors with iDRAC version 4.10.10.10 onwards.
Support for iDRAC Datacenter license.
Known issues
Issue 1
Description:
When you are trying to apply EPR on a device, the EPR operation may fail and there is an entry in the Audit Logs.
Resolution:
Ensure that all the following conditions are met:
There is at least one device in the group that is eligible for applying EPR.
Throttle option is applicable for the following devices:
If the device is a server, then iDRAC Enterprise license is applied.
If the device is PowerEdge M1000e or PowerEdge MX7000 chassis.
Shutdown option is applicable only for servers.
Issue 2
Description:
After rebooting OpenManage Enterprise appliance, if you try to perform any plugin lifecycle-related actions for Power Manager,
the job is initiated in the back-end but you still see the Console and Plugins or Console and Extensions page. And, the following
message is displayed after some time: This page isn't working
Resolution:
Wait for some time, and view the status. The plugin lifecycle-related action is completed successfully.
Issue 3
Description:
For an MX7000 chassis, the power cap value is displayed as same as the upper bound value. When you manually change the
power cap percentage, the value is not updated and even if you change the value, the percentage is not updated.
Resolution:
Provide the power cap value, and save the policy. The policy imposes the specified power cap value on the selected devices or
groups.
Issue 4
Description:
Events are not generated for the following combination of temperature threshold violations:
Lower Warning to Upper Warning
Lower Critical to Upper Critical
Upper Warning to Lower Warning
2