vparresources.5 (2010 09)

v
vparresources(5) vparresources(5)
needed to move any current work to another CPU. The OS cannot allow the boot processor to cease exe-
cution, so these states are disallowed for that CPU.
The monitor may not boot a vPar whose configuration includes a CPU in either the
Failed or MarkDC
state. Nor will it silently modify a vPar’s configuration to reduce CPU count by the number of defective
CPUs. Therefore, the ability to boot depends on how the ailing CPU has been configured:
• If the defective CPU was assigned by the monitor, whether as a CLP or as a non-CLP, and a replace-
ment processor is available, the monitor will assign it in place of the defective CPU and boot the vPar.
• If a replacement processor is not available, the vPar configuration is not changed and the monitor does
not allow the vPar to boot. You must use the
vparmodify command to delete a CPU from the vPar’s
configuration. Or, you can make a replacement CPU available by deleting one from another vPar.
• If you assigned the CPU specifically by hardware path, it remains assigned to that vPar even when the
vPar is shutdown. The monitor will not allow that vPar to boot until the user has deleted the CPU by
specific hardware path,
-d cpu:
path. Since the vPar is Down, this operation does not change the
total CPU count of the vPar. At that point, the ability to boot depends on the availability of a replace-
ment processor, as before.
Once the defective CPU has been removed from its vPars environment, it no longer appears in the
monitor’s list of Available CPUs.
CPUs and Instant Capacity (iCAP)
The iCAP product manages a hardware complex (all nPartitions in a server) that has one or more unli-
censed components. It prevents the use of those unlicensed components. Such a complex is said to be
compliant. Compliance is determined at the complex level and enforced at the nPartition level. Systems
in which all components are licensed are fully compliant. iCAP does not restrict their use in any way.
In a vPars environment, iCAP restricts CPU assignments to a vPar such that the total number of CPUs
assigned to all virtual partitions in an nPartition must not exceed that displayed by the
icod_stat com-
mand as the Intended Active number for the nPartition. iCAP enforces this restriction when you try to
add processors, either to an existing vPar or when creating a new vPar.
The Intended Active number cannot be changed as the result of a vPars command. You must use the
icod_modify command to change this value. Refer to the icod_modify (1M) manpage and to the iCAP
document referenced at the end of this section.
The vPars product interacts with iCAP as follows to maintain compliance:
• In a running vPars environment, any number of processors may exist in the pool of unassigned (Avail-
able) CPUs in the vPar monitor. A
vparstatus -A will display them. But a
vparcreate or
vparmodify command that would cause the total CPU configuration of all virtual partitions,
whether Up or Down, to exceed the Intended Active number will not be authorized by iCAP and will
result in a command error.
• Whenever you attempt to add CPUs when creating or modifying a vPar in an alternate database (one
not loaded into the monitor, or when the monitor is not running), iCAP tests the CPU configuration of
that database against the Intended Active number in the hard partition in which you run the com-
mand. An excessive CPU configuration is allowed here, but is reported as a warning.
• If you try to load such a database into the monitor when it is booted, iCAP reboots any initially
launched virtual partitions and notifies the monitor. The monitor will then not allow any virtual par-
titions to launch. You must reboot in nPar (non-vPar) mode, adjust either the Intended Active number
or the database configuration as an alternate database, then reboot the monitor.
A detailed discussion of iCAP is beyond the scope of this manpage. Refer to "Using Instant Capacity to
Manage Processing Capacity" chapter in the Instant Capacity User’s Guide available at
http://www.hp.com/go/hpux-core-docs
, and to the icod (5) manpage for more information.
Memory
CLM and ILM
There are two major types of memory designation, Cell Local Memory, (CLM), and InterLeaved Memory,
(ILM). With CLM, entire contiguous memory address ranges are found on a single cell. ILM is an
address range of memory whose adjacent addresses reside on one or more cells in the underlying hard
partition (nPartition). Both have their advantages. In this topic, we confine ourselves to the mechanics of
managing each memory type.
HP-UX 11i Version 3: September 2010 − 5 − Hewlett-Packard Company 5