HP Instant Capacity User's Guide for Versions 8.x

component on a third member system needs to be activated, the usage rights made available by
the deactivated component may be taken by the system using temporary capacity. In this case
it may be necessary to use the “-t” option to icapmodify to activate the component on the
third member system using temporary capacity.
Status Reporting
Usage rights and temporary capacity can sometimes be temporarily assigned to the Group
Manager, which can result in difficulty interpreting some of the data from icapstatus. The
total temporary capacity reported for the group by icapmanage -s may not equal the sum of
temporary capacity reported by each member system. This is because the Group Manager will
prefetch an amount of temporary capacity in anticipation of needing it for a future operation, so
the temporary capacity may not be immediately assigned to a member system. Also, individual
counts of cores/cells/memory without usage rights for each member of the group may not add
up to the total counts of cores/cells/memory without usage rights for the group. In all cases, totals
reported (by icapmanage -s) for group temporary capacity and usage rights are the important
values representing available resources for the group. With Instant Capacity version 8.02 and
later, use the verbose (-v) option of the icapmanage -s command to see resources held by the
Group Manager.
The icapstatus command reports usage rights borrowed by or loaned by the system from or
to other members of the group. Borrowed rights are rights currently resident on the member
that originated elsewhere. Loaned rights originated on the system but are currently resident
somewhere else in the group. They may be either in use or unassigned on another group member,
or they may be unassigned on the group manager itself. The icapmanage -s command displays
the status of the entire group, while icapstatus is an isolated view of a single member.
Also note that unassigned usage rights are free to be moved to other member systems, even if a
particular activation request fails. For example, consider a group where there are no free usage
rights. If member m1 releases 2 core usage rights by deactivating 2 cores, and member m2 tries
to activate 3 cores, the activation request will fail (not enough usage rights), after the Group
Manager has already migrated 2 core usage rights from m1 to m2. The borrow/loan values for
m1 and m2 will show that the loan has occurred, even though the activation on m2 has failed to
activate any cores. A subsequent activation of 2 cores on m2 should be successful, and will occur
more quickly because the 2 core usage rights are already assigned to m2, or the rights may be
moved elsewhere in the group if requested.
108 Global Instant Capacity