HP Instant Capacity Version 10.x User Guide (5900-1581, March 2011)

Temporary Instant Capacity Expiration and Compliance Enforcement
IMPORTANT: If you leave cores without usage rights activated beyond the purchased temporary
capacity duration, the software automatically deactivates one or more cores on the next reboot of
any partition in the complex.
After the temporary capacity is depleted and you continue to have more active cores than usage
rights across the complex, a notice similar to the following appears at the bottom of the
icapstatus output:
WARNING: Temporary capacity has expired and this complex is out
of compliance with the Instant Capacity contract because there
are 2 more active cores than there are core usage rights.
Deactivation of cores may occur during partition reboot to
bring the complex into compliance. In order to avoid the
deactivation of cores upon reboot, you need to take corrective
action immediately. Either deactivate 2 core(s), apply
additional temporary capacity codewords, or purchase and apply
Right to Use codewords for 2 core(s).
As stated in the warning, if cores without usage rights continue to be used, then on the next reboot
of any partition in the complex, the software automatically deactivates one or more cores in order
to bring the system into a closer state of compliance. The Instant Capacity software deactivates as
many cores as is necessary to either stop consumption of temporary capacity or to bring the partition
to the minimum number of required active cores. You must purchase either additional temporary
capacity or the appropriate number of usage rights (RTU codewords) to be in full compliance.
For examples of the error messages that are sent as a result of compliance enforcement, see
“Temporary Instant Capacity Exceptions” (page 61).
Auditing of temporary capacity is done at the complex (OpenVMS node) level on Instant Capacity
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 OpenVMS node (or to the entire GiCAP group, if applicable).
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 57).
Example 13 shows an error message for attempting to activate an inactive core without usage
rights and without a sufficient balance of temporary capacity:
Example 13 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
Temporary Instant Capacity Expiration and Compliance Enforcement 61