HP Global Workload Manager 7.3 and 7.3 Update 1 User Guide

result in a high enough number of events that the performance of the System Insight Manager 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 System Insight Manager C.05.01.00.01.xx on the CMS. This version
of System Insight Manager 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 System Insight
Manager.
For more information about any of these workarounds, see the System Insight Manager
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.
Only workloads with managed siblings can be added to SRDs with nested partitions
Using the gWLM command-line interface, you cannot add a workload to an SRD that has nested
partitions unless a sibling of that workload is already managed in that SRD.
Workaround
This is not an issue when you use the gWLM interface in System Insight Manager. Simply follow
the instructions in Step 1 of the Manage Systems and Workloads wizard (reached by selecting
Create→Shared Resource Domain), and select the set of hosts to include in a single SRD.
Configurations with Psets nested in virtual partitions rejected with vPars versions
earlier than vPars A.03.05
gWLM does not support nesting psets in virtual partitions when the vPars version is earlier than
vPars A.03.05. However, it has not always rejected such configurations. gWLM 4.0 and later
does reject these configurations though. So, configurations you used with gWLM 2.x or gWLM
3.x can be rejected when you begin using gWLM 4.0 (and later) agents. Given such a
Limitations 59