HP-UX Virtual Partitions Administrator's Guide (includes A.04.06 and A.05.04)

Activating and Deactivating CPUs
When you are in standalone (PA-RISC) or nPars (Integrity) mode, you can activate CPUs using
the icod_modify -a command. Then, while you are in the vPars environment or vPars mode,
you can use vparmodify -a as long as you do not go above the number of Intended Active
CPUs (see “Intended Active Boundary” (page 238)).
When you are in the vPars environment or vPars mode, you can activate a CPU using
icod_modify -a. However, this automatically activates and assigns the CPU to the local
partition (the virtual partition from which the icod_modify -a was invoked). For example,
after you have purchased 3 licenses, you can activate and assign the 3 CPUs to the local virtual
partition using iCAP commands:
winona1# icod_modify -a 3
1
1
Assign three CPUs to winona1.
At this point, the 3 CPUs have already been added; you do not need to run vparmodify -a
cpu::3. If you do run vparmodify -a cpu::3, this will add 3 more CPUs to the virtual
partition (in addition to the 3 CPUs that were added with the icod_modify command).
Note that if you deactivate CPUs while in the vPars environment or in vPars mode using
icod_modify -d, this will un-assign those CPUS from the local virtual partition.
Assigning and Unassigning CPUs
While in the vPars environment, as long as the number of CPUs assigned to your virtual partitions
is less than or equal to the number of Intended Active CPUs, you can use vparmodify to add
CPUs to your virtual partitions. As long as the number of CPUs assigned to your virtual partitions
does not go below your specified vPars minimums (cpu:::[min]), you can delete CPUs from
your virtual partitions, regardless of the number of Intended Active.
Note that as stated above, while in the vPars environment or vPars mode, using icod_modify
-a assigns as well as activates those CPUs to the local virtual partition.
Intended Active Boundary
Using the iCAP software, the Intended Active number represents the number of licensed CPUs
that could be activated within an nPartition. To view the current Intended Active number, you
can use the iCAP command icod_stat. To change the Intended Active number, you can use
the iCAP command icod_modify.
While in the vPars environment (PA) or vPars mode (Integrity), the total number of CPUs assigned
to the virtual partitions cannot exceed Intended Active. This is true regardless of whether the
virtual partitions are up or down. If you encounter this situation, you may need to increase
Intended Active using icod_modify -a to activate and assign CPUs to your nPartition.
While in standalone (PA) or nPars (Integrity) mode, when the total number of CPUs assigned
to the virtual partitions exceeds the current Intended Active number for the nPartition, iCAP
allows this in the vPars database but displays a warning that the virtual partitions in the vPars
database will not boot. If you attempt to boot the vPars Monitor using this vPars database without
increasing Intended Active using the iCAP commands, the iCAP software will disallow this and
shut down any virtual partitions attempting to boot. You must reboot to standalone (PA) or
nPars mode (Integrity), fix the situation so that the total number of assigned CPUs is less than
or equal to the Intended Active number, and then reboot the vPars Monitor.
When assigning to an alternate and inactive vPars database, vPars and iCAP will allow the
assignments, but as in the above situation, if you attempt to boot this vPars database without
increasing the Intended Active number using the iCAP commands, the iCAP software will not
allow this and will shut down any virtual partitions attempting to boot. You must reboot to
standalone (PA-RISC) or nPars mode (Integrity), fix the situation so that the total number of
238 CPU, Memory, and I/O Resources (A.04.xx)