HP Instant Capacity (iCAP) manual Information displayed for the local virtual partition

	group. This value must be 0 in order to remove the member
	from the GiCAP group.
Borrowed/Loaned memory usage	This field identifies the count of memory usage rights that
rights:	were either borrowed from or loaned to the GiCAP group.
	This value must be 0 in order to remove the member from
	the GiCAP group.

The output of icapstatus reflects the results of any GiCAP group operations: the borrowing or loaning of component usage rights or the transfer of temporary capacity. The output does not take into account any component usage rights or temporary capacity that is available on other GiCAP group members. Thus, icapstatus on group member A may report that there are no additional cores that may be activated with current usage rights even though there is an inactive core on group member A and an available core usage right on group member B. Use the icapmanage command on the Group Manager system to get more complete information about available group resources.

When a group member is using temporary capacity and core usage rights are made available on another group member through the use of icapmodify -d <n>, there may be a delay between the time the core usage rights are made available and the time the core usage rights move to the group member using temporary capacity. This also means that there may be a delay before the final result is reflected in the output of icapstatus for each group member involved in the transfer of the core usage rights.

Information displayed for the local virtual partition

The following status is displayed when icapstatus is run on a virtual partition. Note that some of the displayed information pertains specifically and only to the local virtual partition (such as the “number of active assigned cores” or “number of inactive assigned cores”). However, because usage rights and temporary capacity are always calculated globally across the entire complex, other local values involving these items (such as the “can be assigned” or “could be assigned” values) are the result of calculations using count values across all the partitions.

Total number of assigned cores:

This field displays the total number of cores assigned to the local virtual partition.

Number of active assigned cores:	This field displays the number of assigned cores in the
	local virtual partition that are currently active.
Number of inactive assigned cores:	This field displays the number of assigned cores in the
	local virtual partition that are currently inactive.

Additional cores that can be assigned with current usage rights:

Number of cores that could be assigned with additional usage rights:

Number of cores that can be assigned with temporary capacity:

This field displays the number of unassigned cores in the hard partition that are not currently assigned to any virtual partition and can be instantly assigned, because enough usage rights are available.

This field displays the number of cores that are available for assignment to the virtual partition if additional usage rights are purchased, or additional usage rights were borrowed from a GiCAP group.

This field displays the number of additional cores (beyond the number allowed by purchased usage rights or currently borrowed GiCAP usage rights) that can be assigned to the virtual partition and activated using temporary capacity currently available on the complex. When assigning and activating a core using temporary capacity, icapmodify assumes the core is active for at least 30 minutes. Thus, if a complex has a small temporary capacity balance, it may not be possible to activate all the inactive cores in a partition using temporary capacity. Also, temporary

184