HP Instant Capacity Version 10.x Release Notes (5900-2363, September 2012)

Handling errors while re-adding GiCAP member
When re-adding the member to the GM the below steps needs to be executed from both Active
GM and the standby GM. The same steps to be followed when a member, which is earlier part
of the group is removed and is being added again.
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 must 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 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.
Removing the standby group manager when it has a failure
If the standby Group Manager fails and you decide to remove it from being a standby (by executing
the command icapmanage -r -S on the active Group Manager), and 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
database from the previously failed system. Use commands similar to the following on the system
where you want to remove the standby information:
icapmanage -s # verify that this is the *obsolete* standby system
cimprovider -d -m HP_GiCAPProviderModule
rm /etc/opt/iCAP/GiCAP_db
IMPORTANT: You must not run the above sequence of commands on any system that is the active
Group Manager for the group, because it removes the GiCAP database entirely and leaves the
group members in an orphaned state.
icapmanage hangs when specifying illegal standby group manager
When adding a standby Group Manager using the icapmanage -a -S command, you cannot
specify a system to be a standby for itself. The icapmanage command does detect and displays
an error in the case where you specify a hostname exactly equal to the hostname where you invoke
the icapmanage command. However, if you specify an alternate hostname for the OS instance
running the icapmanage command, the command hangs.
8 Instant Capacity support for HP Integrity Superdome 2 with Dynamic Cores release notes