HP-UX Virtual Partitions Administrator's Guide (includes A.05.02)

CPU, Memory, and I/O Resources (A.04.xx)
CPU: Using iCAP (Instant Capacity on Demand) with vPars (vPars A.04.xx and iCAP B.07)
Chapter 7
267
CPU: Using iCAP (Instant Capacity on Demand) with vPars
(vPars A.04.xx and iCAP B.07)
iCAP CPUs are unlicensed CPUs. The unlicensed CPUs may be shown as available CPUs in the vparstatus
-A output. To use iCAP CPUs, you must first purchase them; then, you can activate and assign them to a
virtual partition.
For detailed information on using iCAP in vPars environment, including using earlier versions of iCAP
(formerly known as iCOD) with earlier versions of vPars, see the corresponding HP Instant Capacity User’s
Guide.
Purchasing Licenses for iCAP CPUs
To purchase licenses for any iCAP components, including iCAP CPUs, you must follow the normal iCAP
process as shown in the HP Instant Capacity User’s Guide. If you attempt to assign an iCAP CPU before
purchasing the license, you will get an iCAP authorization error.
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” on page 268).
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 /* assigns 3 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.