HP Virtual Server Environment Management for Integrity Version 4.0 Release Notes

Workaround You can manage the workloads using compartments based on fss groups
(which have a smaller minimum size) or add resources to the partition or SRD to enable the
pset minimum size requirements to be met.
• Constant Use of TiCAP Global Workload Manager can activate TiCAP if needed to satisfy
SRD policies. To avoid unnecessary consumption of TiCAP, you must have a sufficient
number of CPUs with permanent licenses available. If your SRD is larger than this amount,
TiCAP is consumed to meet the needs of the SRD.
Workaround Deactivate TiCAP resources prior to creating an SRD. Any TiCAP resources
that are active at this time are included in the SRD and, therefore, are consumed whenever
the SRD is deployed.
• Cell-Local Processors and iCAP Environment Using cell-local processors with virtual
partitions inside an nPartition that uses (iCAP) leads to failure of the icod_modify
command.
Workaround Do not assign CPUs using cell specifications. Consider assigning CPUs to
the virtual partitions using a hardware path.
Alternatively, to use cell-local processors, update to vPars A.04.04 on HP-UX 11i v2 (B.11.23)
or to vPars A.05.01 on HP-UX 11i v3 (B.11.31).
• Multiple SRDs in a Complex Allowed to Use TiCAP Global Workload Manager allows
multiple SRDs in a complex to use TiCAP; it should prevent this situation from occurring.
Workaround Do not configure SRDs in this manner.
• 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).
• CMS is Slow to Respond The CMS is slow to respond.
Workaround Time a gwlm list command on the CMS. If it takes more than 10 seconds,
perform the following steps:
Global Workload Manager 41