HP Instant Capacity user's guide for Version 10.x (March 2011)

9 Troubleshooting
This chapter covers the following topics:
• “Handling Compliance Exceptions” (page 107)
• “Troubleshooting the Instant Capacity Software” (page 109)
• “Diagnosing Email Configuration” (page 111)
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) Sharing rights are insufficient.
• (GiCAP) Hardware is added that is incompatible with the group.
NOTE: Your system might be out of compliance because it has 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
determines that all components in partitions that have B9073AA installed are active. For details of
correcting this noncompliant state, see “Upgrading to Instant Capacity version B.06.x or later
(HP-UX)” (page 160).
The Instant Capacity software sends an exception report (via email) if one of these 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. For more details about enforcement,
see “Temporary Instant Capacity Expiration and Compliance Enforcement” (page 67) and virtual
partition “Boot Time Compliance” (page 54).
Example 20 shows an email exception report for having more cores active than expected.
Handling Compliance Exceptions 107