Changing the interval on the command line, Using gwlm with hyper-threading, Using gwlm with hosts on multiple lans – HP Matrix Operating Environment Software User Manual

Page 40

Advertising
background image

Create

→Shared Resource Domain

When editing an SRD

From the System Insight Manager menu bar, select:

Tools

→HP Matrix OE visualization...

Then, click the Shared Resource Domain tab. From the HP Matrix OE visualization menu bar,
select:

Modify

→Shared Resource Domain

Changing the interval on the command line

Use the gwlm command and a text editor to change the interval on the command line:
1.

Use gwlm export to get a copy of the SRD’s XML definition from the gWLM configuration
repository.

2.

Edit the “interval” attribute, which is in seconds.

NOTE:

If you are managing virtual machines, set the interval attribute value to a multiple of

the vm_fssagt interval, which defaults to 10 seconds. If you need a gWLM interval attribute
value of fewer than 10 seconds, set the interval for the VM agents (using vm_fssagt -i)
to the same value.

3.

Use gwlm import --clobber to place the updated definition in the gWLM configuration
repository.

If an SRD of the same name is already deployed, the import operation puts the new interval
into effect. Otherwise, the interval is used the next time you deploy the SRD you just defined
and imported.

Using gWLM with Hyper-Threading

Hyper-Threading, available starting with HP-UX 11i v3 (B.11.31), enables you to use multiple
execution threads per core. (Cores were formerly known as CPUs.) Each execution thread is a
logical CPU.

Utilization is based on the usage of a core—not a logical CPU. For example, assume a four-core
system has Hyper-Threading enabled so that it has eight logical CPUs. If the system has four
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.

40

Additional configuration and administration tasks

Advertising