Fujitsu Siemens Computers SPARC Enterprise M8000 - Manual (Page 37)

Chapter 2 What You Must Know Before Using DR 2-5
A CPU to be deleted must meet the following conditions:
■ No running process is bound to the CPU to be deleted. If a running process is
bound to the target CPU, you must unbind or stop the process.
■ The CPU to be deleted does not belong to any processor set. If the target
processor belongs to a processor set, you must delete the CPU from the processor
set by using the psrset(1M) command.
■ If the resource pools facility is in use by the domain, the CPU cannot be deleted
unless the minimum processor set sizes can otherwise be maintained. Use the
Solaris commands pooladm(1M) and poolcfg(1M) to check these parameters
and, if necessary, adjust the sizes of the domain's resource pools.
Note – These conditions also apply to movement of a system board.
If any of the above conditions are not met, the DR operation is stopped and a
message is displayed. However, if you specify the deleteboard(8) command with
the -f (force) option, these protections are ignored and DR continues the deletion
process.
Note – Exercise care when using the force option, as doing so introduces risk of
domain failure.
To avoid this problem and automate the operations for CPUs, the Solaris OS
provides the Reconfiguration and Coordination Manager (RCM) script function. For
details of RCM, see
Section 3.4, “RCM Script” on page 3-27 .
2.1.1.2 Memory
The DR functions classify system boards by memory usage into two types:
■ Kernel memory board
■ User memory board
(1) Kernel Memory Board
A kernel memory board is a system board on which kernel memory (memory
internally used by the Solaris OS and containing an OpenBoot PROM program) is
loaded. Kernel memory cannot be removed from the system. But the location of
kernel memory can be controlled, and kernel memory can be copied from one board
to another.