HP Instant Capacity Version 10.x Release Notes (5900-2062, December 2011)

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)
Resolving errors during addition of Standby GM
While adding Standby GM there is a possibility of certificate exchange failure
nl
for the Superdome 2 members. This can be resolved by re-adding the member to the GM.
Handling errors while re-adding GiCAP member
Follow these steps if you get an error while re-adding a member to the GM from both Active GM
and standby GM:
1. Execute the cimtrust -l command to view the list of certificates available in the GM (AGM
and SGM).
2. Look for the certificate which contains the Common Name mentioned in the OA certificate on
the member. You can obtain OA certificate information on the member, by executing Show
OA certificate on the OA CLI.
3. Execute the cimtrust -r i <Issuer> -S <Subject> command to remove the certificate.
Issuer and subject information should be taken from cimtrust -l output.
Negative Cores without Usage rights value in icapmanage -s output
If icapmanage -s reports a negative cores without usage rights value after a seize operation is
performed on one of the members, execute icapmanage -s on the GM again after sometime.
Inconsistent values reported by icapmanage during rapid updating
If the command icapmanage -s is executed while the group is being rapidly updated (for
example, during gWLM load balancing), the number of loans and borrows assigned to each
member may not add up in a consistent manner. This is because the status reporting checks with
each member in turn, and if resources are simultaneously being reassigned between group members,
the reporting may reflect an intermediate state. If this occurs, reissue the status command when the
group is in a quiescent state.
Invalid contact address corrupts the GiCAP database
If a GiCAP member sets the contact email address value of spaces (using the command
icapmodify -c " "), the GiCAP database gets corrupted. If this happens, the GiCAP group
must be re-created.
Removing the standby group manager when it has a failure
If the standby Group Manager has a failure and you decide to remove it as a standby (by executing
the command icapmanage -r -S on the active Group Manager), then if the failed system
subsequently is booted, it still considers that it is a standby Group Manager. This occurs even
though the rest of the group does not consider it to be a standby Manager. If you want to re-establish
it as the standby, run the command icapmanage -a -S on the active Group Manager. However,
if you have already established another standby Group Manager (for example), or just want to
remove the leftover standby information, you need to stop the cimprovider and remove the GiCAP
8 Instant Capacity support for HP Integrity Superdome 2 with Dynamic Cores release notes