HP Instant Capacity Version 10.x User Guide (762794-001, March 2014)

icapstatus output). When this state occurs, you need to take corrective action immediately by
doing one of the following:
Deactivate iCAP cores that are using temporary capacity.
Apply additional temporary capacity codewords.
Acquire additional core usage rights and apply the RTU codeword.
Temporary capacity negative balance
A complex is out of compliance with the iCAP contract if a negative balance of temporary capacity
occurs.
The iCAP software sends 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 117).
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 58). 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.
NOTE: You must purchase additional temporary capacity to change the temporary capacity
balance positive.
Temporary capacity enforcement
When the temporary capacity balance is depleted and you continue to have more active cores
than core usage rights across the complex, an enforcement action occurs at partition power-on
(boot) timing to bring the system into a state closer to compliance (by deactivating one or more
cores). Example 14 shows the message that is sent when enforcement results in a partially compliant
state but temporary capacity continues to be depleted. Example 15 shows the message that is sent
when the enforcement is able to deactivate enough cores so that temporary capacity is no longer
used.
TiCAP exceptions 59