HP Global Workload Manager 7.0 User Guide

this error happens again, consult gwlmagent man page for steps to return
to compliance.
Workaround
There is no workaround. You can ignore this message since this message is not valid on
non-partitionable machines where iCAP is not supported.
Remove old configuration data from the gWLM database
Changes to workloads are stored in the gWLM database as configuration changes. The gWLM
database will grow over time when workloads are being modified.
NOTE: If workloads are managed by gWLM, historical monitoring data is stored in the database
and using the following commands will delete this data as well.
Workaround
Remove old configuration data from the gWLM database at regular intervals (such as monthly).
The following commands can be used to trim the database based on date or age.
On HP-UX systems, enter the commands from /opt/gwlm/bin/. On Microsoft Windows systems,
enter the commands from the default location at C:\Program Files\HP\Virtual Server
Environment\bin\gwlm\.
• gwlm history --truncate=<CCYY/MM/DD>
For example, to remove data that was stored before January 25, 2012, enter:
gwlm history --truncate=2012/01/25
• gwlm history –-purge=<days>
For example, to remove all data except for the last thirty days, enter:
gwlm history --purge=30
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).
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:
1. In the file /etc/opt/gwlm/conf/gwlmcms.properties (HP-UX) or
install-path\VirtualServerEnvironment\conf\gwlmcms.properties
(Windows), increase the CMS database cache size by increasing the value of the
com.hp.gwlm.cms.cachesize property by 25%. (The cache is more memory efficient if
the size is near a power of 2. If your target cache size is close to a power of 2, round it up
to the next power. For example, if your target cache size is 60,000, round it up to 66,000.)
2. Stop and restart gwlmcmsd using the following commands.
NOTE: Stopping gwlmcmsd disables HP Matrix OE visualization and Capacity Advisor.
54 Global Workload Manager A.7.0.0* Known issues