HP Instant Capacity User's Guide for Version 9.x

To avoid this problem, usage rights must be restored
(using the -z option) before failback.
-z <host>
Restore previously seized core usage rights to the nPartition
containing the specified host. Core usage rights must be
available in the GiCAP group or the command fails.
This option can be useful particularly when core usage
rights have been seized from systems running vPars,
because the restoration of core usage rights may be
necessary in order to be able to reboot the vPar, depending
on the vPars database definition and the allocation of usage
rights among the vPars. If this is a potential problem, the
restoration command must be performed before rebooting
any vPar within an nPar from which rights were seized.
-C <codeword>
GiCAP codeword application. This option allows the user
to apply a GiCAP codeword to a Group Manager system.
(This option cannot be used to apply an iCAP codeword
such as an RTU or TiCAP codeword.) For GiCAP sharing
rights codewords, first purchase the GiCAP codeword
from HP. The number of rights purchased must equal or
exceed the number of cores without usage rights for all
planned members for all groups managed by the Group
Manager. Next, retrieve the codeword from the HP Utility
Pricing Solutions portal and apply it to the Group Manager
system. Unlike iCAP codewords, GiCAP codewords are
generated for a specified partition on a Group Manager
system, and can only be applied to that partition. Like iCAP
codewords, GiCAP codewords are also generated in a
sequence and must be applied in the order they are
generated for the Group Manager partition. However,
GiCAP codewords are sequenced independently from any
iCAP codewords for the same complex, and can be applied
independently from any such iCAP codewords.
Application of the GiCAP codeword allows members to
be added to one or more GiCAP groups.
-Q
Make a standby GiCAP Group Manager the active Group
Manager for all group members. The new active Group
Manager attempts to contact all group members, informing
them that this system is the active Group Manager. The
new Group Manager also attempts to contact the previous
Group Manager to make it the standby Group Manager.
If the new Group Manager cannot contact a group member,
that group member will continue to be managed by its
current manager. This may result in the member not being
able to loan or borrow usage rights or it may result in a
split group. The current system becomes the active Group
Manager regardless of whether these attempted contacts
succeed or fail.
When attempting to contact all group members, the new
active Group Manager may find that it must establish SSL
communication with a member host. If so, it will prompt
for that host's root password so that it can exchange SSL
keys with the host (unless the -n option is also specified).
HP recommends that SSL communication between the
157