HP Virtual Server Environment Management for Integrity Version 4.0 Release Notes

Using the HP SIM interface: Select the menus Configure → Configure VSE Agents
→ Start gWLM Agent
• 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 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 while the CMS sees it 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).
• 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.
• Missing Historical Data (gWLM CMS Daemon/Service Restarted) You may have blank
sections of a historic report for a workload, or you may 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 of gWLM historic data in HP SIM, 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
1. Log out of HP SIM
2. Log in to HP SIM again
3. Generate the historic report again
• Real-Time Data is Currently Loading You might see the following message when trying to
view real-time reports:
Real-time data is currently loading, please wait... You might also
verify that the remote node is running and SRDs have been deployed.
Workaround Normally, this condition is only temporary. If it persists, check that the
gwlmagent daemon is running on the remote nodes. If it is running, stop and restart it. If
the condition still persists, undeploy and redeploy the SRD.
• Data Missing in Real-time Monitoring Global Workload Manager might not display
monitoring updates for an SRD on the command line or through the graphical interface in
HP SIM. This can be caused by attempts to reform an SRD timing out, leaving the SRD in a
46 Known Issues