HP Insight Control - Manual (Page 35)

supported for racks. The conditions that can prevent power history calculation are provided in the
following list. 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: To assign maximum power attributes:
1.
From the System tab of the system, expand the 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, it is not possible to determine the portion that 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, and so on.
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.
Suggestions
Rules take longer to start when invoked or simulated against a large number
of systems
When a Data Center Power Control rule is invoked or simulated against a large number of systems
(hundreds or thousands), it can take several minutes for the Rule Preview page to appear or the
rule simulation to start running. During this delay, the browser will show a progress indicator. If
the browser session that invoked the rule or simulated rule is closed or the user navigated away
from the progress indicator page, the rule or simulated rule will not proceed.
During this rule startup delay period, if any browser session attempts to enter Data Center Power
Control pages, those browser sessions will also show a progress indicator until the preview
processing is complete. This is true even if the original browser session is closed or the user
navigated away from the progress indicator page.
If many user sessions are active on the CMS at the same time, the rule startup delay period can
be proportionally longer.
Suggestions 35