Practices for maintaining compliance with iCAP on Superdome 2

16
Definitions of terms used in this document
Environment
A complex, if GiCAP has not been purchased or all of the complexes in a GiCAP group.
Core without Usage Rights
HP Integrity Superdome 2 servers contain blades that are available with both sockets fully populated.
An iCAP blade contains two inactive quad-core processors or eight inactive cores. Such cores
purchased under the iCAP program are initially defined to be Cores without Usage Rights. We also
call these iCAP cores. However, it’s important to keep in mind that the iCAP software and program do
not at any time care about the identity or location of cores within a partition, only the total counts. In
the future we anticipate that only the total count within the complex will be used.
Core with Permanent Usage Rights
A processor RTU on HP Integrity Superdome 2 servers permanently activates a total of four iCAP cores
(all or one at a time). Once a customer purchases an 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. For example, an active HP Integrity Superdome 2
blade comes with eight cores with Permanent Usage Rights.
Active core
A core that is capable of running an application. 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 icapstatuscommand.
Inactive core
Any core that is not an active core.
Intended active cores
The number of cores that the iCAP software would activate at partition boot time. It is adjusted by the
use of the icapmodifycommand with the “-a,” “-d,” and “-s” options. The number of intended active
cores for any booted partition is displayed in the output of the icapstatuscommand.