HP Insight Global Workload Manager 6.0 Software: User Guide

Host name aliases are not supported
Host name aliases are not supported by gWLM. Only canonical DNS host names (fully qualified
domain names) are supported.
Workaround Use only canonical DNS names when configuring gWLM through either HP SIM
or an XML file used with the gwlm command.
Making a configuration change to a large SRD is slow
Changes made to the configuration of a large SRD that is deployed might take a long time (several
minutes) to take effect.
Workaround There is no workaround. The amount of time needed to complete a change
depends on the time it takes to communicate with all the compartments in the SRD.
Events for gWLM CPU migration can affect HP SIM CMS performance
The HP products System Fault Management (SFM) and Event Monitoring Service (EMS hardware
monitors in particular) generate events, or indications, when CPUs are migrated. Depending on
workload characteristics, gWLM can migrate CPUs rapidly. Over time, this frequent migration
can result in a high enough number of events that the performance of the HP SIM CMS is adversely
affected.
Workaround The following options are available as workarounds:
Option 1 For systems managed by gWLM that are running HP-UX 11i v3, install the patches
PHCO_36126 and PHSS_36078. (These patches are included in the September 2007
Operating Environment Update Release.) A fix to EMS hardware monitors is
available with the September 2007 Operating Environment Update Release. Even
with these patches and fixes, there is still one event generated for each change in
CPU count.
For systems managed by gWLM that are running HP-UX 11i v2, upgrade to the
June 2007 Operating Environment Update Release.
Option 2 Upgrade to HP SIM C.05.01.00.01.xx on the CMS. This version of HP SIM does not,
by default, subscribe to these events and will not have a performance degradation.
Option 3 If you want to subscribe to events, set up automatic event purging in HP SIM.
For more information about any of these workarounds, see the HP SIM documentation (available
from http://www.hp.com/go/hpsim).
Deleting workloads takes a long time
Once a request to delete a workload is issued, it can take a long time (several minutes) to complete
the deletion.
Workaround Remove old historical monitoring and configuration data from the gWLM database
by entering the following command:
# gwlm history --truncate --truncate=<CCYY/MM/DD>
If you prefer not to trim the database, you can delete multiple workloads simultaneously using
the gwlm delete command.
For more information, see gwlm(1M).
Integrity VM prevents discovery of psets and fss groups
When the gWLM agent is installed on a system that has Integrity VM installed, discovery
operations report only Integrity VM compartments even if psets and fss groups are present.
Workaround To discover psets or fss groups on the system, you must remove Integrity VM.
Limitations 59