Users Guide

Table Of Contents
Resolution: Add devices to the group and assign power before viewing the graph.
Scenario 3
Possible Cause: The Power Capacity of the group is not available.
Resolution: Congure the power capacity of the group or add rack (for which the power capacity is mandatory) in a group, so that the
power capacity of the group can be calculated from the power capacity of the racks in that particular group.
Scenario 4
Possible Cause: The monitored peak power of the group is higher than the power capacity of the group.
Resolution: Congure the power capacity of the group or the racks in the group.
I am not able to manage the servers discovered by
OMPC through the Redsh protocol. Events are also
not logged. How do I troubleshoot and resolve the
issue?
In OMPC 4.0, you may not be able to use certain features when you discover the servers through Redsh protocol with the lockdown
feature of iDRAC enabled. The below matrix lists the restrictions:
Table 16.
Protocol Monitoring (Devices) Managing ( Device, task, and reports) Set iDRAC location Event subscription
IPMI Supported Supported Supported Supported
Redsh Not Supported Not Supported Not Supported Not Supported
To resolve the issue or overcome the restrictions, turn o the lockdown feature in the iDRAC interface or discover the servers using IPMI.
I discovered a server through the Redsh protocol.
When I tried to manage the server, the events are not
logged in the event list. What do I do now?
By default, the Redsh events are not logged into the event list due to security restrictions. You may choose to receive the events by
following the steps provided here.
Open service.xml le from [OMPC installation folder]/external/apache-tomcat/conf location.
Change the value of clientAuth value to false.
Restart OMPC services to start receiving the Redsh events.
Troubleshooting
129