HP Global Workload Manager 7.3 and 7.3 Update 1 User Guide

Missing or unexpected historical data (system clocks differ)
You might have no historical data available for graphing, even though you are certain an SRD
was deployed for the time period in question.
A related issue occurs when you select a time period where you expect high system activity, but
the graph shows limited activity. Similarly, you might expect very little activity for a time period,
but the graph shows lots of activity.
Workaround
Check that the system clocks on the CMS and on all the systems in the SRD are synchronized. If
the clocks differ significantly, gWLM might not be able to match the data from the managed nodes
with the time period you are trying to graph.
Sample missing at start or end of gwlmreport output
A report from gwlmreport is based on a report period that starts at midnight the day the report
begins and ends at midnight the day the report ends. Any samples that overlap midnight at the
start or end of the report period are excluded from the report.
Workaround
There is no workaround, but you should be aware of this behavior.
Workload with fixed policy gets more resources than requested
In an SRD with nested partitions, assigning fixed policies where the sum of the fixed values is less
than the minimum of the parent compartment can result in workloads getting more resources than
specified in the fixed policies.
Workaround
Set up the fixed policies so that the number of CPUs requested is greater than or equal to the
minimum number of CPUs required by the parent compartment.
Only one SRD is allowed to be deployed
You might see a message similar to the following:
Error trying to deploy SRD, mysystem.vpar.000 to mysystem2.mydomain.com.
SRD, mysystem2.fss.000 is already deployed. Only one SRD is allowed to
be deployed.
Workaround
Undeploy the SRD using the --force option with the gwlm undeploy command, and restart
gwlmagent on the managed node.
SRD deployment times out and displays a blank screen
If you attempt to deploy an SRD, but:
• gWLM times out and displays a blank screen
• There are events from each managed node similar to the following event:
gWLM Agent MySystem.MyDomain.com
Information Unable to manage the following hosts:
Associated Exception Unable to manage the following hosts: MySystem.MyDomain.com: The gWLM agent
process on the host is not running -- start the agent and retry.
You need to configure gWLM to work with hosts on multiple LANs.
Workaround
See “Using gWLM with Hosts on Multiple LANs” (page 47) for information on configuring gWLM
to work with hosts on multiple LANs.
Documentation or minor issues 65