HP Insight Control Power Management 6.3 User Guide

When DCPC Shutdown rule is invoked on a managed node, the system does
not shut down.
When DCPC Shutdown rule is invoked on a managed node running on Windows Server 2003 SP2 (x64)
operating system, the task is successful. But, the system does not shut down and the following message
appears:
System shutdown initiated successfully
'shutdown' is not recognized as an internal or external command, operable
program or batch file.
Solution: Perform the following to resolve the problem:
1. Install the hot fix, KB942589, for Windows Server 2003 x64 SP2 from the Microsoft website http://
support.microsoft.com/kb/942589/.
2. Invoke the Shutdown rule from DCPC.
Power history calculation
For the non-monitored power distributors and power consumers, it is possible for power management
sometimes to determine their power history from other sources. Power history calculation is supported for
racks as well. The conditions that can prevent power history calculation are listed below. For some of the
conditions, suggested actions are provided to resolve the conditions.
• Some power consumers do not have user-defined maximum power attributes.
Solution: For the user-defined maximum power attributes, perform the following:
1. From the System tab of the system, expand Power Management section and click Configure.
2. Enter the maximum possible power consumption value in the Maximum Possible Power
Consumption (Watts) field and click OK. The maximum power value will be used to represent
the power history of the system.
• Some power consumers do not have monitored power sources.
Solution: Where possible, attach monitored power distributors.
• The rack is empty.
Solution: Populate the rack.
• The power distributor does not feed any monitored power consumers.
• The power delivery hierarchy does not lend itself to a departmentalization of the available power
history. For example, when you assume that there are two unmonitored outlets connected to a monitored
enclosure, then it will not be possible to determine the portion each outlet provides to the enclosure. In
such situations, power history calculation is not possible.
Solution: Where possible, use power distribution devices with outlet monitoring.
• Power history is available to calculate history from other sources, but the data does not overlap in time.
It is possible that the date and time on the various systems and devices are not synchronized, or there
are gaps in the history data. It is possible that one or more of the systems and devices is unable to yield
power history data for some intervals of time due to various reasons: network problems, licensing issues,
maintenance down time, etc.
Solution: Check the status of these systems and devices.
Power history construction takes an all or none approach. If there is missing data, power history is not
calculated for the interval in time.
32 Troubleshooting