Users Guide

Table Of Contents
Why do I encounter a network exception while adding
a chassis to a group?
Possible Cause: The chassis platform response could be slow. The web server may timeout before the chassis responds to OpenManage
Power Center, resulting in the network exception.
Resolution: The chassis is added to the group at the back-end, but the GUI times out before the chassis responds to OpenManager Power
Center.
In the compare report, why is the average power value
of a device dierent when the service is stopped for a
few hours?
Possible Cause: There may be an inconsistency in the logic for All Devices and Managed Groups.
Resolution: You can select the device from the Managed Groups where the power value calculation is more accurate.
Why is the “policy return to normal” event not
displayed when the only device in the Chassis
Management Controller (CMC) is deleted?
Possible Cause: When the last blade in the chassis is deleted, the power value returns to “1” as there is no device in the chassis. The
comparison between the power value and the policy capping fails and the “policy return to normal” event is not triggered.
Resolution: You can add a blade to the chassis if the power value does not exceed the power capping value. The “policy return to normal”
event is triggered. You can delete the events manually.
After discovering the devices, incorrect device
information is displayed? Why is this happening?
Possible Cause: It may be due to the IPMI privilege level limit set to operator/user level in iDRAC.
Resolution: Ensure that in the iDRAC page, the channel privilege level limit in the IPMI settings section is set to Administrator.
I am not able to view the power headroom graph on
the home screen. How do I troubleshoot?
Scenario 1
Possible Cause: The Estimated Max Power for some unsupported devices is not available.
Resolution: Congure the Estimated Max Power and then view the graph.
Scenario 2
Possible Cause: The peak power of a group is not available.
128
Troubleshooting