HP Instant Capacity Version 10.x Release Notes (5900-1580, March 2011)
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.
GiCAP Known Problems (HP-UX)
Network-related problems when re-adding members to groups
Some users upgrading to iCAP Version 9 have encountered messages like the following, when
re-adding existing members to a GiCAP group:
icapmanage -a -g Group1 -m xyzmember:abc.hp.com,def.hp.com,ghi.hp.com
icapmanage command failed.
Attempt to re-add xyzmember to Group1 failed due to a match in the list of OSAddresses.
This error means that one or more of the hosts listed in the icapmanage -a -g -m command
may not resolve to the same name as it previously did when the member was first added to the
group. Specifically, in the reported cases it meant that the name lookup for one of the hosts had
changed from a fully qualified host name (abc.hp.com) to being a simple host name (abc).
GiCAP does not match abc with abc.hp.com and therefore, reports this as a mismatch.
If this error occurs, you should execute the nslookup command for each specified host of the
member complex and make sure that each host name is qualified in exactly the same way that
icapmanage -s reports that particular host name for the member. Typically, this problem can
occur if the /etc/hosts file is being used for network name lookups, and the file was changed
to return simple host names when it previously returned fully qualified host names. In this case, the
problem can be fixed by editing the /etc/hosts file.
Partial complex failure with rights seizure
The V9.0 User's Guide and manpages do not properly describe the following condition that can
occur when rights are seized from a server where at least one other nPartition of the complex is
still running.
Rights seized in this situation do not expire.
However, if the system is not rebooted within 12 to 24 hours of the rights seizure, the Instant
Capacity software in the still-running partition(s) takes note that the iCAP daemon has not been
running in the failed partition for a significant period of time. The software assumes that the failed
partition might be booted to an operating system that is unaware of iCAP will use all cores on the
partition. This is referred to as the assumed active state and can result in temporary capacity
charges or compliance exceptions. To avoid this, cells can be made inactive by removing them
20 Major Changes, New Features, and Requirements of Instant Capacity Version 10.x