HP Virtual Server Environment Management for Integrity Version 4.0 Release Notes

— 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.
• Incorrectly Configured Host Name or IP Address You may see the following message in a
log file (gwlmagent.log.0 or gwlmcmsd.log.0):
Unable to determine the network address and/or hostname
of the current host. This indicates a mis-configured network and/or a host
name resolution issue for this host. For troubleshooting information, see the
VSE Management Software Release Notes and search for this message.
The most common cause for this error is a problem in the host name configuration file in
/etc/hosts (or equivalent on Windows) or incorrect settings of the /etc/nsswitch.conf
file (HP-UX only).
Background information gWLM is not a simple client/server application. It involves:
— Multiple managed-node “servers” (the set of gWLM agents in an SRD are all peer servers
that cooperatively manage the SRD)
— The CMS management server handling configuration and monitoring
Under normal operation, all of these components need complete connectivity. At a minimum,
gWLM requires that each host have a primary IP address/host name that is reachable from
every other interacting gWLM component--the CMS and all gWLM agents in a single SRD.
(gWLM agents in multiple SRDs need not have connectivity within undeployed SRDs.)
By default, gWLM uses the primary IP address/host name for a given host. However, you
can set up a management LAN, as discussed in the HP Global Workload Manager User's Guide,
to use other IP addresses/host names.
Workaround Correct the configuration of the host so that:
— The primary fully qualified domain name can be properly resolved (by DNS or by
configuration files)
— The IP address and primary fully qualified domain name are consistent for the host—and
do not resolve to a local-host address (for example, 127.0.0.1)
The procedure below explores one way to check the host's configuration.
1. Run the vseassist tool to perform initial network configuration checks.
2. To validate proper configuration on HP-UX, try the following steps:
a. Get the current host name using the hostname command:
[mysystem#1] > hostname
mysystem
b. Get the IP address configured for the host using nslookup:
[mysystem#2] > nslookup mysystem
Trying DNS
Name: mysystem.mydomain.com
Address: 15.11.100.17
c. Verify that /etc/hosts has the same name configured for the address. Note that
the first name should be the fully qualified domain name, and any aliases are listed
afterward.
44 Known Issues