HP Instant Capacity User's Guide for Versions 8.x

Glossary
activated core A core that has been turned on by the Instant Capacity software or during installation. Cores
are activated with the icapmodify command (or the vparmodify command in an HP-UX
virtual partition) while HP-UX or OpenVMS is running.
active cell A cell that is available for use by the software running on the nPartition. This implies that the
cell’s processors and memory (and I/O, if the cell is attached to an I/O chassis) are all available
for use by the operating system. An active cell has the following characteristics:
• It is present and populated.
• It is powered on.
• It is assigned to an nPartition.
• It is released from boot-is-blocked.
active nPartition An nPartition is active if at least one of the cells in the nPartition is active.
add-on system A system that has been converted to an Instant Capacity system. This process is performed by
an HP service representative.
BCH Boot console handler. The system firmware user interface that allows boot-related configuration
changes and operations on PA-RISC systems. For example, BCH provides a way to specify boot
options and the choice of boot devices. The EFI Boot Manager provides a similar function for
Itanium-based systems.
BIB Boot-is-blocked. The state of a cell that is powered on but is not allowed to boot.
bound core For vPars versions before A.04, a core that can process interrupts for a virtual partition. Bound
cores cannot be migrated from one virtual partition to another if either of the partitions is
running. Every virtual partition must have at least one bound core.
cell A circuit board that contains cores and memory, controlled by a cell controller chip. A cell board
is the basic building block of an nPartition in a complex.
codeword The mechanism used with Instant Capacity software B.06.x and later to adjust available usage
rights for system components (RTU codewords), apply an amount of temporary capacity to a
system (TiCAP codewords), and to apply Sharing Rights to a GiCAP system to enable the
creation of one or more groups (GiCAP codewords). Codewords are purchased from HP and
retrieved from the Utility Pricing Solutions web portal.
configured
processor
A processor that has been configured at the boot console handler (BCH) and whose cores are
now available for activation.
core The actual data processing engine within a processor. A single processor might have multiple
cores, and a core might support multiple execution threads.
deactivated core A core that either has not yet been activated or that has been turned off by the Instant Capacity
software and returned to the pool of inactive cores. These cores are available for activation.
Note that new HP-UX or OpenVMS processes are not assigned to a deactivated core and all
processes running on the deactivated core are migrated to other cores (with the exception that
interrupt handlers may not be migrated from deactivated cores).
deconfigured
processor
A processor that has not yet been configured at the boot console handler (BCH). The Instant
Capacity software cannot activate a processor core that is deconfigured.
failover The operation that takes place when a primary service (network, storage, or CPU) fails, and
the application continues operation on a secondary unit.
guest The virtual machine running the guest OS and guest applications.
guest OS A guest operating system is the operating system that is running on a virtual machine.
hard partition A physical partition of an HP server, comprising a group of cells (containing processors and
memory), and I/O chassis. Each hard partition operates independently of other hard partitions,
and can run a single instance of HP-UX or some other operating system. A hard partition can
be further divided into virtual partitions. Hard partitions are also referred to as “nPartitions”.
Hyper-Threading The logical CPU feature that allows multiple execution threads (logical CPUs) within a single
core.
207