HP Instant Capacity Version 10.x User Guide (762794-001, March 2014)

Example 27 Error message for temporary capacity complete enforcement
To: [e-mail]
Subject: Instant Capacity enforcement notice
This message is being sent to inform you that, due to expiration of
temporary capacity, 1 core(s) were deactivated on your Instant Capacity
complex (containing the partition par1) to bring the complex into compliance
with the Instant Capacity contract.
Prior to deactivation, the number of active cores exceeded the number
of available usage rights by 1. 1 core(s) without usage rights were
found to be active in the complex. This state was likely the result of
having activated Instant Capacity core(s) using temporary capacity (TiCAP)
and then allowing the temporary capacity balance to expire prior to
deactivation of the core(s).
As a result, the intended active value was reduced by 1 and 1 core(s)
were deactivated. To activate these 1 core(s) again, you can perform
one of the following actions:
1. Purchase additional temporary capacity, apply the TiCAP codeword(s)
to the complex, and use temporary capacity to activate the core(s).
2. Deactivate cores in other partitions. This frees up core usage
rights which can be used to activate cores on this partition.
There are currently 3 active core(s) and 3 core usage rights. This complex
is now compliant with the Instant Capacity contract.
You can view the current temporary capacity compliance of your system by
using the icapstatus command.
See the Instant Capacity user's guide at /usr/share/doc/icapUserGuide.pdf
for more information.
Activity Logging
/etc/.iCOD_data, /var/adm/icap.log and /var/adm/icap.log.old are no longer
available.
You need to check OA syslog with the OA command "show syslog OA" about the iCAP and TiCAP
execution log.
GiCAP
This section provides guidelines to set up GiCAP groups containing HP Integrity Superdome 2
systems. For more information on the GiCAP feature, see “GiCAP” (page 67).
Requirements for managing HP Integrity Superdome 2
Software requirements on Group Manager
The Group Manager managing HP Integrity Superdome 2 systems must be running the iCAP
Software version 10.04.01 or later. The Group Manager must have the grouping rules version
2.18 or later installed. For more information on grouping rules, see “GiCAP grouping rules”
(page 70)
Group Manager must be running HP-UX 11.31 for managing the SD2 systems.
To use GiCAP, WBEM version A.02.09.10 or later must be installed on the Group Manager.
When HP Integrity Superdome 2 systems are using the complex firmware bundle 3.6.46 or later,
WBEM version A.02.09.14 or later must be installed on the Group Manager. The CIM Server
configuration property sslClientVerificationMode must be set to a value of “optional” and
enableHttpsConnection must be set to “true” on all GiCAP Group Managers. Otherwise, the CIM
Server must be restarted. For more information, see cimconfig(1M).
HP Integrity Superdome 2 with dynamic cores 111