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

Handling Compliance Exceptions
A complex can get out of compliance with the Instant Capacity contract if any of the following
occurs:
• More cells are active than expected (not enough inactive cells)
• More memory is active than expected (not enough inactive memory)
• More cores are active than expected (not enough inactive cores)
• There is a negative temporary capacity balance
• (GiCAP) Not enough sharing rights
• (GiCAP) Hardware added which is incompatible with the group
NOTE: Your system may be out of compliance due to having different Instant Capacity software
products installed. For example, if a partition has the old product B9073AA installed (Instant
Capacity versions B.03.x through B.05.x) and another partition in the same system has the new
product B9073BA installed (Instant Capacity version B.06.00 or greater), the B9073BA software
assumes that all components in partitions that have B9073AA installed are active. See “Upgrading
to Instant Capacity versions B.06.x or later (HP-UX)” (page 171) for details of correcting this
non-compliant state.
The Instant Capacity software sends an exception report (via e-mail) if one of the above exception
conditions occurs. Exception information is also written to the system log file. In some cases,
compliance is enforced by deactivating cores at boot time. See also “Temporary Instant Capacity
Expiration and Compliance Enforcement” (page 82) and virtual partition “Boot Time Compliance”
(page 181) for more details about enforcement.
Following is an example of the e-mail exception report for having more cores active than expected:
122 Troubleshooting