HP Superdome 2 Partitioning Administrator Guide (5900-1801, August 2011)

configuration to use the available healthy CPU-cores. The following are some of the cases where
the partition controller may not allow the when parspec change policy is disabled:
• There is a deconfigured or deactivated CPU, which has been reserved for the partition as part
of the total (cpu::num) request and partition controller does not have any free CPUs with which
to replace it. To correct this, you can delete CPUs from other partitions or from this partition.
• There is a deconfigured or deactivated CPU that has been bound to the partition by resource
path (cpu:hw_path). Partition Controller does not try to replace a CPU-core assigned to a vPar
by resource path. To correct this, you can remove the CPU specified by resource path using
vparmodify -d cpu:resourcepath to allow the deconfigured or deactivated CPU to be
decommissioned. Add a different CPU to vPar using vparmodify if needed.
• There is a deconfigured CPU which has been reserved for the partition as part of a SLP request
(socket id:cpu::num) and there are no free SLPs in that socket. To correct this, you can make
available CPUs from that socket by deleting the CPUs that are part of this socket from other
partitions or delete the CPUs from the socket in this partition.
If the parspec change policy is enabled (default), then the partition is booted with existing resources
and the parspec is modified to delete the deconfigured resource. Please note that you will need
to manually add back the resource using the vparmodify command when the resource is healthy
and available for use.
Examples
• A CPU, 1/1/0/0, is added by path to a vPar with total 4 CPUs.
• The CPU is deconfigured because of an error on the next boot of the vPar.
• If parspec change policy is enabled, the vPar will boot without 1/1/0/0 and with the remaining
3 CPUs that are part of the partition, and the parspec will be modified to delete 1/1/0/0.
• The CPU might be acquitted by the health subsystem at a later point or the blade containing
the CPU might be replaced. So, the CPU is now available, but is not automatically added
back to the vPar. The vPar will continue to boot with 3 CPUs, until the user does a vparmodify
and adds the same CPU or another CPU.
88 Planning Your System for Virtual Partitions