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

• A partition with iCAP has a configuration change (that is, a core is activated or deactivated).
• A codeword is applied.
• Usage rights are seized from a GiCAP system.
You can view all events in the iCAP log files in the /var/adm/icap.log or /var/adm/
icap.log.old file on HP-UX systems, and in the sys$manager:icap.log file on OpenVMS
systems. GiCAP events can be viewed on the Group Manager system in /var/adm/GiCAP.log
(see “GiCAP” (page 138)).
How can I obtain codewords for newly purchased usage rights if the Utility Pricing Solutions portal
is down?
If the Utility Pricing Solutions portal is down, contact the HP Response Center. The Response Center
can create an emergency codeword via the iCAP codeword backup tool.
What licensing is required for the iCAP software?
For iCAP version 10.x, to activate additional components (cores, cell boards, or memory), you
must acquire additional usage rights individually. For details, see “Usage rights requirement”
(page 24)s. To create a GiCAP group, you must purchase sharing rights. For more information
about sharing rights, see “GiCAP sharing rights” (page 70).
The resulting configuration of my iCAP system does not agree with what I ordered from HP. How
did this configuration change occur?
The iCAP software can control the granularity of processor activation or deactivation to the
single-core level. The iCAP ordering and manufacturing rules often do not allow such fine granularity.
The iCAP ordering rules dictate the quantity of cores with and without usage rights in the cell
boards. Because the iCAP software distributes the core usage rights (for a given partition) in a
manner that optimizes loads across all cells, the resultant configuration might be different than the
original order. However, the number of cores with and without usage rights matches what was
ordered.
For example, suppose you order an rx8620 server with 2 cell boards, in which the first cell board
contains 4 active cores with usage rights, and the second cell board contains 2 active cores with
usage rights and 2 inactive cores without usage rights, for a total of 6 active and 2 inactive cores.
At run time, the iCAP software balances the distribution of active cores across the cell boards so
that each cell has 3 active cores with usage rights and 1 inactive core without usage rights.
How does iCAP interact and coexist with partitions running software other than HP-UX?
iCAP is supported only on HP-UX and OpenVMS for Integrity systems. If other partitions of an iCAP
system are running another operating system, all the system components in the non-HP-UX and
OpenVMS partitions appear to the iCAP software as active components (with usage rights). When
verifying the correct number of inactive components without usage rights, only the HP-UX and
OpenVMS partitions are examined.
What email is sent by the iCAP software?
The following table lists the email messages sent to the system from the iCAP software. On OpenVMS
systems, the iCAP software agent is ICAP_SERVER rather than icapd.
Table 11 Email sent by the iCAP software
Email MessageTriggered By
Information about the configuration change is sent to the system contact,
if specified, and if change notification is set to “on”.
icapmodify (if a configuration change
occurs)
A temporary capacity expiration notification is sent to the system
contact, if specified, and root.
icapd (daily, when the projected TiCAP
balance expiration is less than the warning
period: by default, when less than 15 days)
136 Frequently asked questions