Maintaining iCAP Compliance on HP Integrity & HP 9000 Mid-range & Superdome Servers

6
Intended Active count OR use “icapmodify” (“parmodify”, etc.) to increase Intended Active
count if that is possible.
• Best practices related to nPars on an iCAP system:
– It is recommended that all nPars that are created are ignited and booted with HP-UX.
Otherwise as described in the “Overview” section components in that partition will be
counted against the number of usage rights and could prevent activations on other
partitions. The inactive nPar can be removed to free consumed usage rights or the partition
can be booted and the “icapmodify” command can be used to change the number of
intended active cores for that partition
– While creating a new nPar in an iCAP system, ensure that there are enough usage rights
on the system to cover all cores in the new nPar. If possible free up enough cores in the
system to free up sufficient usage rights. If this is not possible, HP support should be
contacted to have code words created to temporarily give the system enough usage rights
to create the nPar.
• For more details on this refer to the iCAP User's Guide available
at http://docs.hp.com/en/B9073-90183/B9073-90183.pdf.
Note: From iCAP version 8.02 or later a negative TiCAP balance is no longer cleared when applying
an RTU codeword.
GiCAP
The same principles apply to a GiCAP group but the calculations are done at the group level rather
than at the complex level.
Definitions of Terms Used in this Document
• Cores without Usage Rights
Cores purchased under the iCAP program are initially defined to be Cores without Usage
Rights. We also call these iCAP cores. (It’s important to keep in mind however that the iCAP
software and program do not at any time care about the identity or location of cores, only the
total counts.)
• Core with Permanent Usage Rights
Once a customer purchases a Right to Use (RTU) and applies it to a core the core is then
defined to be a Core with Permanent Usage Rights. Any other core that is purchased and not
an iCAP core is also a Core with Permanent Usage Rights.
• Active Core
Typically a core that is running an operating system but also includes cores that the iCAP
program counts as being active as described in the Overview section.
• Inactive Core
Any core that is not an Active Core.
• The Intended Active number
The number of cores that the Instant Capacity software attempts to activate at system boot
time. It is adjusted by the use of the icapmodify command with the -a, -d and -s options.
The number of Intended Active cores for each partition is displayed in the output of the
icapstatus command.