User's Manual

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)
Missing workload application criteria after gWLM and HPSIM service restart
If workloads are defined with application criteria, the criteria definition goes missing after gWLM
and HPSIM restart.
Workaround
To restore the workload's application criteria definition:
1. Click Workload under Workloads tab.
2. Select by application option.
3. Select the application that is defined with the workload.
4. Click Add to definition.
5. Click OK.
After you click OK, the following error occurs:
The workload named <workload_name> already exists in the Application
Discovery server.
6. Click Cancel and ignore the error message.
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.
Documentation or minor issues 69