HP Matrix Operating Environment Software - Manual (Page 64)

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.
Workaround
Perform the following steps:.
1.
Log out of System Insight Manager
2. Log in to System Insight Manager (again)
3. Generate the historic report (again)
Negative current size for NONVM
If the CPUs on a VM Host are oversubscribed when you deploy an SRD on that host, gWLM shows
current size for NONVM as a negative value.
Workaround
Two options are available:
•
Adjust the entitlements of those virtual machines that are on so that the CPUs are not
oversubscribed.
•
Stop one or more virtual machines until those still on do not oversubscribe the CPUs.
Unmanaging a VM or vPar that is ON leaves SRD undeployed
When unmanaging a started VM or vPar on VSP, the SRD can be undeployed, even though the
following message is displayed:
The virtual machine VM_name on host hostname is on but does not have
an associated gWLM policy. Please turn the virtual machine off, or apply
a gWLM policy to provide the necessary resources.
64 Global Workload Manager A.7.1.0* known issues