HP Instant Capacity Version 10.x User Guide (5900-2063, December 2011)

Temporary capacity is audited at the complex level on iCAP systems that support partitioning and
are not part of a GiCAP group. Although temporary capacity might have been purchased for use
by a specific partition, it is available to all partitions in the complex (or to the entire GiCAP group,
if applicable).
TiCAP exceptions
Error for activation with insufficient TiCAP
You cannot activate an iCAP core with temporary capacity unless there is a sufficient balance of
temporary capacity available. For information on how to increase the temporary capacity balance,
see “Acquiring and configuring TiCAP” (page 104).
The following example shows an error message for attempting to activate an inactive core without
usage rights and without a sufficient balance of temporary capacity:
Example 21 Error message for activation with insufficient TiCAP (HP-UX)
> icapmodify -t -a 2
iCAP authorization denied for partition 2.
Error: Insufficient usage rights or temporary capacity for 2 additional
cores.
TiCAP negative balance
A complex is out of compliance with the iCAP contract if a negative balance of temporary capacity
occurs.
The iCAP software sends you an exception report (via email) if there is a negative balance of
temporary capacity. Exception information is also written to the syslog file. For details of the
exception report for a negative temporary capacity balance, see “Handling compliance exceptions”
(page 113).
If you continue to have more active cores than core usage rights across the complex, a negative
capacity balance results in a compliance enforcement action, as described in “TiCAP expiration
and compliance enforcement” (page 106). If there is a negative temporary capacity balance but
the number of cores with usage rights is greater than or equal to the number of active cores, then
the complex remains in an exception state, but without (additional) enforcement action.
TiCAP enforcement
When the temporary capacity balance is depleted and the number of active cores are more than
the core usage rights across the complex, an enforcement action occurs at partition reboot. This
is to bring the system into a state closer to compliance (by deactivating one or more cores).
Example 22 shows the message that is sent when enforcement results in a partially compliant state,
but temporary capacity continues to be depleted. Example 23 shows the message that is sent when
the enforcement is able to deactivate enough cores so that temporary capacity is no longer used.
NOTE: To receive mail notifications, the Alertmail feature must be enabled and configured
correctly on the Onboard Administrator associated with the HP Integrity Superdome 2 system.
HP Integrity Superdome 2 with Dynamic Cores 107