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

• Boot-is-blocked.
• The cell is assigned to an nPartition.
See also active cell.
inactive 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. Inactive cores are available for activation.
New HP-UX or OpenVMS processes are not assigned to an inactive core, and all processes
running on the inactive core are migrated to other cores (with the exception that interrupt handlers
might not be migrated from inactive cores).
inactive nPartition An nPartition in which all of its cells are inactive.
See also active nPartition.
Instant Access
Capacity
Also called IAC. The amount of temporary capacity included with the purchase of an Instant
Capacity component.
Instant Capacity Also called iCAP. The HP Utility Pricing Solutions product that allows you to purchase and install
additional processing power through the use of a two-step purchase model. Initially, you purchase
system components (cores, cell boards, memory) at a fraction of the regular price because the
usage rights are not included. These Instant Capacity components are inactive but are installed
and ready for use. When extra capacity is needed, you pay the remainder of the regular price
for the usage rights to activate the components. If the regular price for the component is reduced
by the time the usage rights are purchased, the remainder price is proportionally reduced,
providing additional savings.
Earlier versions of iCAP were referred to as Instant Capacity on Demand, or iCOD.
Instant Capacity
component
Also called a component without usage rights. A core, cell board, or memory that is physically
installed in an Instant Capacity system but is not authorized for use. Before it can be used, an
RTU must be purchased and a codeword must be applied to the system.
Instant Capacity
core
Also called a core without usage rights. A core that is physically installed in an Instant Capacity
system but that does not have usage rights and is not activated. After obtaining usage rights,
Instant Capacity cores can be turned on by the Instant Capacity software or during installation.
Cores with usage rights are activated with the icapmodify command (or the vparmodify
command in a virtual partition) while HP-UX or OpenVMS is running.
Integrity Virtual
Machines
See Integrity VM.
Integrity VM A soft partitioning virtualization product that allows you to install and run multiple systems (virtual
machines) on the same physical host system (Integrity server or nPartition). The Integrity server or
nPartition acts as a VM Host for the virtual machines (also referred to as guests). The virtual
machines share a single set of physical hardware resources, yet each virtual machine is a complete
environment in itself and runs its own instance of an operating system (referred to as a guest OS).
See also virtual machine, VM Host.
intended active The number of cores a user requests to be active for a partition by the Instant Capacity software
at the next reconcile operation. A reconcile operation is normally a reboot, although other actions
can trigger a reconcile operation, such as moving cores between virtual partitions. You adjust
the number of intended active cores by using the icapmodify -a, -d, and -s options. Other
commands, such as parmodify and parcreate, can also affect this value. The number of
intended active cores for each partition is displayed using the icapstatus command.
See also actual active.
load balancing The distribution of processing activity across two or more servers to avoid overloading any one
server. Load balancing is performed on Instant Capacity systems by activating or deactivating
resources on partitions and spreading the load across the system (or across members of a GiCAP
group) so that no partition or member of a group is overloaded.
local nPartition When an nPartition command is being executed, the nPartition that is running the command.
migrating
processing cores
The process of activating and deactivating cores across partitions or across members in a GiCAP
group for load balancing.
220 Glossary