Users Guide

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.
Power policy not updated after the changes
Scenario:
When the time span of an active policy is changed, the policy is not disabled on the device.
Resolution:
Resolve the issue using one of the following methods:
● Manually disable the policy on the device.
● Disable the policy in Power Manager, change the time span, and then enable the policy.
Events not generated for alert thresholds
Scenario:
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
● Upper Critical to Lower Critical
Resolution:
Provide realistic warning and critical values so that there are no immediate alert generating temperature changes.
Error when removing a device from a group using REST API
Scenario:
When you try to remove a device that is part of multiple groups using the REST API, then an error message is displayed.
Resolution:
To remove a device that is part of multiple groups, remove the device from the group in OpenManage Enterprise. The changes
are automatically reflected in Power Manager.
Multiple alerts for group membership changes in Audit Logs
Scenario:
Multiple entries on group membership changes in Audit Logs.
Resolution:
When there are updates to the static group membership through OpenManage Enterprise, there are multiple entries of this
update in the Audit Logs and Alert Log.
Ignore action not working for groups-related alerts
Scenario:
56
Troubleshooting