HP Instant Capacity Version 10.x User Guide HP-UX 11i v1, HP-UX 11i v2, and HP-UX 11i v3 (5900-3361, December 2013)

9 Troubleshooting
This chapter covers the following topics:
• “Handling compliance exceptions” (page 116)
• “Troubleshooting the iCAP software” (page 119)
• “Diagnosing email configuration” (page 121)
• “Resolving errors during addition of standby GM” (page 121)
• “Handling errors while re-adding GiCAP member” (page 121)
• “Negative cores without usage rights value in icapmanage -s output” (page 122)
• “Behavior on occurrence of INIT (TOC) in nPartition” (page 122)
Handling compliance exceptions
A complex can get out of compliance with the iCAP 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 iCAP software products
installed. For example, if a partition has the old product B9073AA installed (iCAP versions B.03.x
through B.05.x) and another partition in the same system has the new product B9073BA installed
(iCAP 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 199).
The iCAP 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 “TiCAP expiration
and compliance enforcement” (page 57) and virtual partition “Boot time compliance” (page 45).
Example 27 shows an email exception report for having more cores active than expected.
116 Troubleshooting