HP Instant Capacity Version 10.x Release Notes (5900-1580, March 2011)

Other Changes
Fixed a problem where an icapmodify -d or an icapmodify -s operation would erroneously
issue an exit code of success even if the operation was only partially satisfied. With this release,
a partially satisfied request will correctly exit with an error code.
Error messages from nPar Provider have been standardized and now include an “NPAR” prefix.
ssh can now be configured with a banner. In previous releases, this would produce errors when
managing a GiCAP group (icapmanage error).
Changes in Version 8.1 (OpenVMS)
Implementation of Global Instant Capacity (GiCAP)
GiCAP is fully functional in iCAP version 8.1 on OpenVMS systems. The Group Manager must be
an HP-UX system running Instant Capacity software version 8.01.01 or later.
Known Problems
TiCAP warning period does not default to 15 days
After installing iCAP version 10.01 on HP Integrity Superdome 2, the temporary capacity expiration
warning period is set to 0 days instead of the default 15 days (this can be confirmed by running
the icapstatus command).
This problem can be solved by running the icapmodify -w number_of_days command to
set the warning period to the required value. If this command is not executed, the temporary
capacity expiration warning mails will not be sent to the contact address specified.
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]
Known Problems 19