HP Global Workload Manager 7.0 User Guide

2. The CMS must also be in the management LAN. If the primary hostname for the CMS is not
the name it uses in the management LAN:
a. Edit the gwlmagent.properties file on the CMS to include the property:
com.hp.gwlm.security.virtualLocalHostName=hostnameOnLAN
On HP-UX, the gwlmagent.properties file is in /etc/opt/gwlm/conf/. On
Windows, it is in C:\Program Files\HP\Virtual Server Environment\conf\.
(The given Windows path is the default; however, a different path might have been
selected at installation.)
b. Restart System Insight Manager and gwlmcmsd.
3. On each host in the SRD (CMS and managed nodes), ping every other host in the SRD—using
the hostname you intend to have gWLM discover (its hostnameOnLAN)—to verify
communication is possible.
4. Discover (or re-discover) the hosts using the gWLM Manage Systems and Workloads wizard.
Creating “Golden Images”
If you create golden images of a system’s applications and operating system to store in an IgniteUX
server for distribution to other systems, here are tips for creating images that include gWLM.
When creating an image of a managed node:
• Ensure the gWLM agent is set to start automatically.
In the file /etc/rc.config.d/gwlmCtl, set the variable GWLM_AGENT_START equal to
1.
• Ensure no deployed SRD includes the node. (If the file /etc/opt/gwlm/deployed.config
exists, an SRD is deployed on the node. Temporarily undeploy the SRD or unmanage the
node.)
If a node based on a virtual partition is part of a deployed SRD and you make a golden image
of the virtual partition, once you push that golden image out, the gWLM agent on the new
system will still consider itself part of the SRD. The agent will then try to rendezvous with that
SRD’s other managed nodes. You can reset the agent by deleting the deployed.config
file (mentioned previously), then stopping and restarting gwlmagent.
Multiple network interface cards
As a client/server application, gWLM is more sensitive than other types of applications to the
network configuration of your host. It supports management only within a single network domain.
For example, if your CMS host has multiple network interface cards that are connected to multiple
distinct networks, gWLM requires that the fully qualified host name resolve to the IP address that
is reachable by the gWLM agents to be managed.
This issue is most often a concern when a host is connected to both of the following items:
• A corporate LAN/WAN via one network interface card and IP address
• A second, private internal network and private IP address for communicating with a certain
other set of hosts (such as cluster members)
Global Workload Manager attempts to detect and report network configuration issues that can
cause undesirable behavior, but in some cases this detection occurs in a context that can be
reported only into a log file.
Workaround
If you encounter some unexpected behavior (such as a gWLM agent that fails to update or report
the status of its workloads), inspect the /var/opt/gwlm/glwmagent.log.0 file on the host for
errors.
42 Additional configuration and administration tasks