HP Instant Capacity Version 10.x User Guide (5900-2170, January 2012)

Standby GiCAP Group Manager
The active GiCAP Group Manager can designate a standby Group Manager. This standby Group
Manager can take control of GiCAP group management from the active Group Manager using
the command icapmanage -Q. This allows GiCAP group operations to continue if the GiCAP
Group Manager is unable to function.
Note that the requirements and recommendations defined for the Group Manager also apply to
the standby Group Manager; it is a Group Manager with standby status. The Group Manager in
charge of the group has active status. If the standby Group Manager takes control, the intention
is that its status becomes active and the former Group Manager's status becomes standby. For
more information, see “Group manager failover considerations”.
GiCAP group members
Every operating system on a GiCAP group member must be running Instant Capacity version 9.0
or later. Every GiCAP group member must be hardware-compatible with other GiCAP group
members, as determined by the GiCAP grouping rules.
GiCAP grouping rules
After you have determined which system will host the active Group Manager, you must acquire
grouping rules from the portal and install the encrypted file on the active Group Manager system
using the icapmanage -i command. Under some circumstances (for example, when adding
new hardware not covered by the grouping rules currently in use), you might need to acquire
newer grouping rules from the portal.
GiCAP sharing rights
To create a GiCAP group with members, you must purchase GiCAP sharing rights, acquire the
GiCAP codeword from the HP Utility Pricing Solutions portal (http://www.hp.com/go/icap/portal),
and then apply the associated codeword to the active Group Manager system. You must purchase
as many GiCAP sharing rights as the total number of cores without usage rights being applied
across all the potential group members. Members can be added to a GiCAP group if sufficient
sharing rights are available, and if the grouping rules indicate hardware compatibility.
Unlike other iCAP codewords, GiCAP codewords must be generated for and applied to a specific
partition, if the active Group Manager is on a partitionable system. Therefore, to retrieve the
codeword, you must specify the purchase order number, the system serial number, and the partition
information, if any. Use the icapmanage -s command on the active Group Manager system to
get the applicable serial number and nPar ID, or vPar code.
GiCAP codewords also have a sequence value and must be applied in the order in which they
are generated for the Group Manager system. However, GiCAP codewords are sequenced
independently from any other types of iCAP codewords that might be generated for the same
system, and can therefore be applied independently from iCAP codewords.
GiCAP Group creation
After the sharing rights codeword and the grouping rules are applied to the active Group Manager,
a GiCAP group can be created by issuing the icapmanage command using the -a, -g and -m
options. Members are added by issuing the icapmanage command using the -a option, the -g
option to select the group name, and the -m option to specify a name for the new member along
with a list of hosts running on the system. The list of hosts must include at least one host per nPartition
or virtual partition on the system.
Note that a single partition of a complex cannot join a GiCAP group. All partitions of a complex
must be specified when creating a group member. All partitions on a group member must be
running HP-UX or OpenVMS. Each member that joins the group decreases the available GiCAP
sharing rights by the number of cores without usage rights contributed by that member complex.
185