HP Instant Capacity (iCAP) manual Member system from which they were, Seized, Expiration

	the member system from which they were
	seized.
Core usage rights	This field displays the number of expiring core

seized from npar <n>: usage rights that were seized from a specific

	partition of the member. This field is displayed
	only when the -voption is specified, and it is
	repeated for each partition where usage rights
	were seized for disaster recovery, if none of the
	member partitions could be contacted.
Expiration:	This field displays the expiration date for core
	usage rights that were seized with icapmanage
	-xoperations from the preceding named
	partition, or from the complex in the case of
	unassigned usage rights. The expiration date
	for a rights seizure operation effectively
	terminates the period during which the core
	usage rights are available to other group
	members for purposes of disaster recovery.
	This field is displayed only when the -voption
	is specified and only for systems where usage
	rights were seized for disaster recovery, if none
	of the member partitions could be contacted.

Guidelines for Interpretation of Usage Rights Counts

In general, the Instant Capacity software is designed to enforce the concept that a certain number of resources must remain inactive in order to stay in compliance with the iCAP contract. For that reason, many of the display fields for icapstatus and also for icapmanage are negative counts of usage rights, such as Cores without usage rights and Cells without usage rights.

At the same time, the GiCAP software is intended to allow the transfer of usage rights among members of the group. So, seizure of usage rights, borrows and loans of usage rights are described as positive counts of usage rights, such as Number of core usage rights seized and Borrowed core rights. The Group Manager also sometimes holds usage rights during transient states, so all the Group Manager resources are described as positive counts of core usage rights.

To properly interpret the icapmanage display of usage rights, it is sometimes necessary to total the usage rights using both positive and negative (subtractive) values. For example, if the group contains two members, each having 3 cores without usage rights, then the total for the group is 6 cores without usage rights. If a rights are seized from one member, for example taking 2 core usage rights away, then those 2 core usage rights are held by the Group Manager before the 4 are used by another member of the group. During that transitional period, the total for the group remains 6 cores without usage rights, but the member total for the unreachable member is adjusted to be 5 cores without usage rights (2 were taken away from the unreachable member) and 3 cores without usage rights (for the other member). At the same time, the Group Manager holds 2 usage rights. The total for cores without usage rights is calculated as 6=5+3-2.

In this example, “counts of cores without usage rights” are also adjusted as a result of rights seizure operations in order to maintain the contractually required balance of cores without usage rights. Similar adjustments are made every time a resource (cores, cells, memory) is borrowed from or loaned to other members of the group. These adjustments are automatically reflected in the icapstatus output on the member systems; in the case of unreachable members and rights seizure, you might see the adjustment first in the display from the icapmanage output.

171