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

Temporary Instant Capacity Exceptions
Error for Activation with Insufficient Temporary Capacity
You cannot activate an Instant Capacity core with temporary capacity unless there is a sufficient
balance of temporary capacity available. For details on how to increase the temporary capacity
balance, see “Acquiring and Configuring Temporary Instant Capacity” (page 77).
Here is an example of the error message for attempting to activate an inactive core without usage
rights and without a sufficient temporary capacity balance:
Example 5-5 Error Message for Activation with Insufficient Temporary Capacity (HP-UX)
> /usr/sbin/icapmodify -t -a 1
ERROR: Operation not approved because there is not enough temporary capacity
to satisfy the request. Activations require at least 30 minutes
worth of temporary capacity per core consuming temporary capacity.
Temporary Capacity Balance Needing Action
If the temporary capacity balance reaches 30 minutes or less, the icapstatus command’s output
displays “less than 30 minutes” in the Exception status field (at the beginning of the
icapstatus output). When this state occurs, you need to take corrective action immediately
and do one of the following:
• Deactivate Instant Capacity cores that are utilizing 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 Instant Capacity contract if a negative balance of
temporary capacity occurs.
The Instant Capacity software sends an exception report (via e-mail) if there is a negative balance
of temporary capacity. Exception information is also written to the syslog file. See “Handling
Compliance Exceptions” (page 122) for details of the exception report for a negative temporary
capacity balance.
If you continue to have more active cores than core usage rights across the complex, a negative
capacity balance will result in a compliance enforcement action, as described in “Temporary
Instant Capacity Expiration and Compliance Enforcement” (page 82). 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.
Purchase of sufficient additional temporary capacity will clear out a negative balance.
Temporary Capacity Enforcement
When the temporary capacity balance has been depleted and you continue to have more active
cores than core usage rights across the complex, an enforcement action occurs on a partition
reboot to bring the system into a state closer to compliance (by deactivating one or more cores).
Example 5-6 is an example of the message that is sent when the enforcement results in a partially
compliant state, but temporary capacity continues to be depleted. Example 5-7 is an example of
the message that is sent when the enforcement is able to deactivate enough cores so that temporary
capacity is no longer being used.
Temporary Instant Capacity Exceptions 83