HP Global Workload Manager 7.3 and 7.3 Update 1 User Guide

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.
Incorrectly configured host name or IP address
You might 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
HP Matrix Operating Environment 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. To use other IP addresses/host names, see “Using gWLM with Hosts on
Multiple LANs” (page 47).
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:
Incorrectly configured host name or IP address 49