In data center operations and other cases, you may have hosts
on multiple LANs or separated by firewalls. These hosts may be addressable
on a public network or an internal network. However, they cannot communicate
with each other because of the separation by the LANs or firewalls. Figure 5-2 shows a possible
scenario.
On the public network, the hosts can be accessed through their
hostnames: vparA, vparB, vparC, and vparD. However, they cannot access
each other through those names.
Although gWLM may be able to discover the hosts and you can
even configure an SRD including the hosts, when you attempt to deploy
the SRD, gWLM will eventually time out and display a blank screen.
No error message is displayed. However, there will be events from
each managed node similar to the following event:
gWLM Agent MySystem.MyDomain.com
Information Unable to manage the following hosts:
Associated Exception Unable to manage the following hosts: MySystem.MyDomain.com: The gWLM agent process on the host is not running -- start the agent and retry.
|
If the environment allows, open ports on the firewalls between
the CMS and managed nodes as documented in the VSE Management
Software Version 4.1 Installation and Update Guide for HP-UX section “Compatibility with HP-UX Bastille and Other Network
Firewalls.” If opening firewall ports on the primary LAN is
not an option, use a secondary LAN to manage the hosts.
 |
| |
|
 | NOTE: Each gWLM agent must be able to communicate with the CMS and
with all the other agents in the SRD. |
|
| |
|
A CMS can only manage hosts on the same LAN as the CMS itself.
Thus, if you set up a separate LAN (sometimes referred to as a management
LAN or a backup LAN) that includes the CMS and all the hosts to be
managed, you can manage these hosts in a single SRD.
Figure 5-2 shows
a management LAN in which the hosts are known as mgmtA, mgmtB, mgmtC,
and mgmtD. With this management LAN, gWLM can manage the hosts in
a single SRD. Complete the following procedure to set up gWLM to manage
such hosts in an SRD:
For each host in the management LAN that you want to manage
in an SRD:
Edit the /etc/opt/gwlm/conf/gwlmagent.properties file to include the following property:
com.hp.gwlm.security.virtualLocalHostName=hostnameOnLAN
For example, with the host mgmtA, its property would be:
com.hp.gwlm.security.virtualLocalHostName=mgmtA
Restart gwlmagent on the host:
# /opt/gwlm/bin/gwlmagent
--restart
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:
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
may have been selected at installation.)
Restart HP SIM and gwlmcmsd.
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.
Discover (or re-discover) the hosts using the gWLM Manage
Systems and Workloads wizard.
Printable version
