HP-UX HB v13.00 Ch-16 - iCAP

HP-UX Handbook – Rev 13.00 Page 15 (of 24)
Chapter 16 Instant Capacity (iCAP)
October 29, 2013
 To view the hardware grouping information, run the command:
# icapmanage -R
 Now the members need to be added by specifying the name for the new member
along with a list of hosts. Specify an OS instance (host) for each nPartition or virtual
partition of the complex (do not specify virtual machine or guest OS instances). A
member of a group must encompass all nPar and vPar OS instances of a complex, and
each OS instance specified as a host must be accessible (ping-able) in order for the
command to succeed. To add members issue the command:
# icapmanage -a -m <member name>:<member hostnames> <groupname>
When you first add new members to a group, you will be prompted for the root
password for each specified host. The password is used only to establish secure
communication and is not saved or stored.
 When adding groups to a Group Manager system, the compatibility for one or more
host systems can be tested in order to determine which groups the system can join.
# icapmanage -T <member hostname> -g <groupname>
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.
You can create multiple GiCAP groups that can be managed by the same Group Manager or by
different Group Manager systems. Systems with no any Instant Capacity components can be part
of a GiCAP group. Deactivating resources on these systems allows them to loan usage rights to
other members in the group.
A server complex can only be a member of a single GiCAP group at a time. In order to
participate in a different group, it must be removed from its group before being added to the
other group.
A larger number of group members can cause an increase in startup time for the Group Manager
and can also affect the performance of icapmodify commands when a transfer of usage rights
occurs. If temporary capacity is being used, then the size of the group may also increase the
amount of communication time needed for tracking of temporary capacity.
Removing a GiCAP Group Member
Before removing a member from a GiCAP group, all the borrowed usage rights must be returned
and all outstanding loans reclaimed.
When a member is removed from a group, some number of sharing rights are released and made
available for future use. The number freed is equal to the number of cores without usage rights
on the removed member.