HP Superdome 2 Partitioning Administrator Guide HP-UX 11i v3 (766170-001, May 2014)

[Containing nPartition Details]
nPartition number: 1
nPartition name: nPar0001
Current boot mode: vpars
Next boot mode: vpars
or
MyComplex> vparmodify —N {npar_id} —p {vpar_id} —m
socket:{socket_is}:cpu::{count}
NOTE: The system deletes any core from that socket irrespective of the method in which the
core from that socket is added to the vPar (by count, by socket specified count, or by path).
• By individual core hardware path: This method is similar to addition. You can specify cores
that you want to delete, only if you do not specify the boot processor. The format for deletion
of cores is —d cpu:{enclosure}/{blade}/{socket}/{core}.
NOTE: After the deletion is complete you can reassign the resources (either cores or RTUs
or both). If the system is busy, it might take few minutes after the command exits to the prompt
(which occurs without waiting for completion). If the system uses Temporary Instant Capacity
(TiCAP), the TiCAP consumption is reduced by the number of cores deactivated.
Moving cores between partitions (vPars)
If you want to move cores between partitions, you must delete the cores from the source partition
and then add the cores to the target partition. There are no single step tools to move cores. The
cores may be deleted using any of the methods discussed above, and then added to the target
partition using any of the methods discussed above (count-based, socket-based or by path).
Modifying the number of active cores in nPartition without vPars (iCAP only)
nPartitions are specified in a granularity of blades, on a complex with iCAP components it is
common to have some of the cores on the blades inactive. The following three methods can be
used to increase the size of an nPartition when it is necessary:
1. Release cores in another nPartition (if using GiCAP, the other nPartition may be on any machine
in the GiCAP group), to freeze RTUs, then use the frozen RTUs to activate cores in the target
partition.
2. Authorize or pre-authorize the use of TiCAP with the icapmodify command.
3. Purchased additional RTUs.
Activating or deactivating cores in a running nPartition
You must use icapmodify to modify the number of active cores in a running partition because
nPartitions work at a granularity of the entire blade. When you use icapmodify, it does not change
the blades which are in the nPartition, nor does it change the blades that are activated for the
boot. To add cores successfully to an nPartition, icapmodify requires both available RTUs and
sufficient number of inactive cores on active blades within the partition. The command format is:
MyComplex> icapmodify —p {npar_id} —[ads] {count}
Moving Right to use between nPars
You can move the RTUs across nPartitions. In this process, you must use the icapmodify command
to deactivate cores in an nPartition (causing the RTUs to be freed up), and then activating free
cores (iCAP cores) in another nPartition using the freed up RTUs. icapmodify is the only supported
method of performing online operations on nPartitions.
Managing: Modifying Virtual Partitions online 117