HP Instant Capacity (iCAP) Temporary Instant Capacity Exceptions, Temporary Capacity Enforcement

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 79).

Example 5-5shows an error message for attempting to activate an inactive core without usage rights and without a sufficient balance of temporary capacity:

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 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 by doing one of the following:

•Deactivate Instant Capacity 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 Instant Capacity contract if a negative balance of temporary capacity occurs.

The Instant Capacity 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 137).

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 “Temporary Instant Capacity Expiration and Compliance Enforcement” (page 86). 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.

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 reboot to bring the system into a state closer to compliance (by deactivating one or more cores). Example 5-6shows the message that is sent when enforcement results in a partially compliant state but temporary capacity continues to be depleted. Example 5-7shows the message that is sent when the enforcement is able to deactivate enough cores so that temporary capacity is no longer used.

Temporary Instant Capacity Exceptions 87