Cost-Effective High-Availability Solutions with HP Instant Capacity on HP-UX

Figure 6 shows a GiCAP group with two members and an active Group Manager named ap1. There
is no standby Group Manager. It has 24 inactive cores without usage rights across the group (8 on
Server 1 and 16 on Server 2). Twenty-four sharing rights are purchased for this group. Also, note that
there are two cell boards without usage rights. Usage rights for cell boards and memory can be
shared in a group, but the number of iCAP cell boards with memory does not affect the number of
sharing rights required for the group. (The number of sharing rights needed is based on the total
number of cores without usage rights across all servers in the group.)
Figure 6: Global Instant Capacity group
Note that migration of resources in this situation is exactly analogous to the previously described
capability where iCAP resources are migrated from one partition to another. The migration is
achieved through a deactivation/activation sequence. With GiCAP, the migration scope is extended
from the partition to the group. For example, by deactivating cores and cells in the Test partition on
Server1, usage rights are freed and available to any other partition of any member in the group for
potential activation of cores and cells. Once the group is created, the normal iCAP commands for
activation and deactivation are used to migrate usage rights from one group member to another.
13