HP Global Workload Manager 7.0 User Guide

cannot be calculated when there are not enough resources on the system to manage the set of
monitored workloads in pset compartments.
Workaround
You can manage the workloads using compartments based on fss groups (which have a smaller
minimum size), or add resources to the partition or SRD, to fulfill the pset minimum size requirements.
Unable to remove workload from nested partitions SRD
When attempting to remove the last (default) fss group from an SRD with nested partitions, you
might encounter a message that includes the following text:
Unable to remove workload workload_name: Attempting to remove a
compartment with an unachievably low Fixed policy size. Increase the
Fixed policy resource amount and try again.
Workaround
Undeploy the SRD and delete it. Then, create a new SRD without the fss group that you were trying
to remove.
Discovery does not show current information for stopped virtual machines
Global Workload Manager discovery does not always report current information for stopped
virtual machines. Specifically, when a virtual machine is stopped and the number of vCPUs is
changed, gWLM discovery does not show the changed number of vCPUs. Instead, it shows the
number of vCPUs from the virtual machine's most recent start.
Workaround
Start the virtual machines before performing discovery.
Configuration of agent and CMS not synchronized
Occasionally, a gWLM agent and the gWLM CMS disagree on whether an SRD is actually
deployed. This can occur when you use Ctrl-C to interrupt a gwlm deploy or gwlm undeploy
command. It can also occur if there are errors saving a gWLM configuration; the configuration is
deployed and then saved to the gWLM configuration repository. If the deploy occurs but the save
fails, the gWLM agent sees the SRD as deployed; however, the CMS sees the SRD as undeployed.
Workaround
Use the --force option with gwlm deploy or gwlm undeploy to synchronize the agent and
the CMS.
For example, run the following command to force both the agent and the CMS to consider the SRD
as deployed, substituting the name of your SRD for SRD
# gwlm deploy --srd=SRD --force
For more information about the gwlm command, see gwlm(1M). The agents should be restarted
to clear their configuration. The following steps should be performed on all agents:
# gwlmagent --stop
# rm /etc/opt/gwlm/deployed.config
# rm /var/opt/gwlm/RPmap (If it exists.)
# gwlmagent
Missing historical data (gWLM CMS daemon/service restarted)
You might have blank sections of a historic report for a workload, or you might see the following
error message when displaying historic data for a workload:
There is no gWLM historical data for the workload MyWorkload.wkld. The
workload has never been managed by gWLM, or the historical data has
been removed.
Because of caching gWLM historic data in System Insight Manager, if the gWLM CMS
daemon/service is restarted after initially viewing historic data, the interface incorrectly reports
that there is no data available to view or fails to load portions of the data.
58 Global Workload Manager A.7.0.0* Known issues