HP UX 11i Workload Management (gWLM/WLM) Software manual Using gWLM with hosts on multiple LANs

processes, each consuming an entire logical CPU, the reported utilization depends on where those processes are. If the processes are on only two cores, the utilization is 50% (2/4). With the processes distributed across all four cores though, each process can consume an entire core, resulting in a utilization of 100%.

When fss groups are being used, gWLM disables Hyper-Threading for the default pset, where fss groups are created, to optimize workload performance.

When an SRD is undeployed, gwlmagent restores the lcpu_attr tunable to the value it had when the system booted. This value can be different from the value in effect before deployment if kctune was used without a reboot.

Using gWLM with hosts on multiple LANs

In data center operations and other cases, you may have hosts on multiple LANs or separated by firewalls. These hosts might 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 3 shows a possible scenario.

Figure 3 Using gWLM with hosts separated by firewalls

vparA

mgmtA

vparB

mgmtB

vparC

mgmtC

Firewall

Public network

Hostname

vparD on public network

CMS

mgmtD	Hostname on
	management LAN

Management LAN

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 might 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 HP Matrix Operating Environment Software Version 4.1 Installation and Update Guide for HP-UXsection “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.

Using gWLM with hosts on multiple LANs 47