HP Superdome 2 Partitioning Administrator Guide (5900-2064, November 2011)

Non-socket-specific:
User assigned [Count]: 0
System assigned [Count]: 3
Socket-specific [Count]: Socket-ID/Count
<none>
[IO Details]
[Root Port] [Slot]
10/1/0/2/0 10/1/1
[Memory Details]
ILM Total (MB): 8192
ILM Granularity (MB): 512
SLM (Socket-ID MB):
SLM Granularity (MB): 1024
[OL* Details]
Sequence ID: 2
Operation: CPU Deletion
Status: PASS
[Containing nPartition Details]
nPartition number: 1
nPartition name: nPar0001
Current boot mode: vpars
Next boot mode: vpars
or
MyComplex> icapmodify —p {npar_id:vpar_id} —d {count}
You can also use the following command to specify the number of cores you want for the vPar:
MyComplex> vparmodify —N {npar_id} —p {vpar_id} —m cpu::{count}
MyComplex> icapmodify —p {npar_id:cpar_id} —s {count}
or you can use the following command from the OS prompt:
# vparmodify —p {vpar_id} —d cpu::{count}
# icapmodify —d {count}
# vparmodify —p {vpar_id} —m cpu::{count}
# icapmodify —s {count}
If LORA mode is enabled in HP-UX, the system selects the appropriate cores to delete using
LORA algorithms.
NOTE: During online deletion, the operating system can delete any core irrespective of the
method in which it is added to the vPar. But when the vPar is DOWN, the cores must be
deleted in the method in which it is added.
If you reduce the number of cores in use, the command failure due to running out of Right of
Use will not occur. On a complex with iCAP components, it is necessary to delete and release
RTUs before addition, regardless of how many physical cores are idle.
• By specifying socket along with count: This method is similar to socket based core addition
which is done by vparmodify command. The number of cores available in the vPar must
be enough to allow the removal of cores specified on the socket in addition to retaining a
boot processor. The command fails if the boot processor is on the selected socket and the
Managing: Modifying Virtual Partitions online 111