HP Instant Capacity Release Notes for Version 9.x

Known Problems
Codependency between vPars and iCAP (HP-UX)
If you are installing iCAP on an HP-UX 11i v1 vPars system, and want to update to vPars version
A.03.05, or configure mixed 11i v1 vPars A.03.05, and 11i v2 vPars A.04.05 or 11i v3 vPars A.05.03,
you must install iCAP version 8.03 or later on each 11i v1 virtual partition. This also installs the
required versions of WBEM and nParProvider and necessary patches. Installing iCAP version
8.03 or later onto an 11i v1 system running versions of vPars prior to A.03.05 exhibits an
incompatibility error message which can be ignored, and you can proceed with updating the
vPars software. After the vPars installation (which includes halting every vPar and rebooting
the nPar to the new vpmon), you must go to each 11i v1 vPar and run the swconfig -v B9073BA
command to complete the iCAP installation.
Occasional failure message (HP-UX)
On a busy system, you might occasionally get the message, “Failure writing Instant Capacity
data to Dynamic Profile”. This indicates that the Instant Capacity software needs to update the
volatile data, which is synchronized by the MP. If multiple readers and writers are accessing the
data at the same time, a natural race condition can result in a failure to update the data. If that
happens, retry the Instant Capacity operation you initiated.
icapmodify and parmodify timeout (HP-UX)
Commands that try to activate resources in a GiCAP group, such as icapmodify and parmodify,
might fail because of a timeout error. If you receive a timeout error similar to the following, and
resources are available, retry the command:
Internal Error: Exception caught for modify.Timed out waiting for a
response.[Error received whenconnecting to or getting information from
theInstant Capacity (iCAP) provider]
Interaction between iCAP and gWLM (HP-UX)
gWLM version 2.5 fails to migrate CPUs if it is used with iCAP version 8.00 (or later) and there
is a zero or negative TiCAP balance. This problem does not exist in later versions of gWLM.
Low-level WBEM errors (HP-UX)
Occasionally, on a busy system, especially one with many partitions, you might see errors such
as the following:
icapd: Caught exception: ERROR: The following low-level WBEM error occurred:
CIM_ERR_FAILED:A general error occurred that is not covered by a more specific error code:
"@4:Software error.[Error on ioctl.] Connection timed out"
or:
icapd: ERROR: The following low-level error occurred:
ERROR: The following low-level WBEM error occurred: connection timed out
or:
ERROR: The following low-level WBEM error occurred: Empty HTTP response message.
or:
ERROR: The following low-level WBEM error occurred: Locking or unlocking the target failed.
These errors result from contention for system resources from the various partitions in the
complex. If you see these messages, retry the Instant Capacity operation.
26 Major Changes, New Features, and Requirements of Instant Capacity Version 9.x