LPMC and resulting CPU States

CPU Conditions as the Result of a LPMC Error in a vPar Environment 2
Monarch CPU, the LPMC Monitor will make a call to mark-for-deconfiguration. The LPMC Monitor will not
attempt to deallocate this Monarch CPU. Upon vPar OS reboot, the Bound Monarch CPU will reappear in
the vPar as an active CPU (however it is still marked for deconfiguration). Upon vPar Monitor reboot (i.e.
reboot of the hard partition), PDC will deconfigure the Bound Monarch CPU and the vPar Monitor will no
longer see it.
A Bound NON-Monarch CPU behaves the same EXCEPT that it CAN be deallocated. It is marked for
deconfiguration and also deallocated. However upon vPar OS reboot, again, this Bound NON-Monarch
CPU is put back in use and will reappear in the vPar and will be an active CPU (however it is still marked
for deconfiguration). Upon vPar Monitor reboot (i.e. reboot of the hard partition), PDC will deconfigure the
Bound NON-Monarch CPU and the vPar Monitor will no longer see it.
Floating CPUs behave a bit differently. If the LPMC error threshold has been exceeded, the LPMC
Monitor will make a call to deallocate and a call to mark-for-deconfiguration the Floating CPU. It is then
deallocated and marked for deconfiguration. Upon vPar reboot, this Floating CPU is NOT put back in use
and will NOT reappear in the vPar and it is still marked for deconfiguration. Upon vPar Monitor reboot (i.e.
reboot of the hard partition), PDC will deconfigure the Floating CPU and the vPar monitor will no longer
see it.
Assigning CPUs to vPars
In a NON-vPars environment, a marked Monarch CPU will be deconfigured during a reboot. The PDC will
assign another CPU to be the Monarch and the system will boot.
In a vPars environment, CPUs can be specified by min/max numbers or by hardware paths. If a CPU is
specified via min/max specification, and the CPU is no longer available to the vPars Monitor
(deconfigured), the vPars Monitor will attempt to meet the min (Bound) CPU count, even if it needs to
remove CPUs from the pool of available Floating CPUs. The vPar Monitor will do this until it has no more
Floating CPUs.
If a CPU is specified via hardware path, and the CPU is no longer available to the vPars Monitor
(deconfigured), the vPars Monitor will again attempt to replace the CPU with one of the available Floating
CPUs. The vPar Monitor makes several passes to meet the CPU requirements and whether the CPUs
are specified by min/max or hardware path, the vPar Monitor will allocate CPUs.
At this time there is no advantage to specifying CPUs by hardware path.
Summary
• Bound Monarch CPUs are marked-for-deconfiguration but not deallocated or taken out of the
system (deconfigured) until the vPar Monitor (i.e. system/nPar) is rebooted. These CPUs will
reappear as active CPUs if ONLY the vPars OS is rebooted, and not the vPar Monitor.
• Bound NON-Monarch CPUs are marked-for-deconfiguation AND deallocated but not deconfigured
from a vPar until the vPar Monitor is rebooted. These CPUs will reappear as active CPUs if
ONLY the vPars OS is rebooted, and not the vPar Monitor.
• Floating CPUs are marked-for-deconfiguration AND deallocated. These CPUs will NOT be
reassigned to a vPar when the vPars OS is rebooted. And a system/nPar reboot or vPar Montitor
reboot will deconfigure the Floating CPU and the vPar monitor will no longer see it.