Memory - Fujitsu SPARC Enterprise M4000 Features Manual

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
Oracle 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 -f (force) option, as doing so introduces risk of
domain failure.
To avoid this problem and automate the operations for CPUs, the Oracle Solaris OS
provides the Reconfiguration and Coordination Manager (RCM) script function. For
details of RCM, see
For information about mixed configurations of SPARC64 VII+, SPARC64 VII, and
SPARC64 VI processors, see
SPARC64 VI Processors and CPU Operational Modes" on page
2.1.1.2

Memory

The DR functions classify system boards by memory usage into two types:
Kernel memory board
■
User memory board
■
Section 3.4, "RCM Script" on page
Section 2.5.9, "SPARC64 VII+, SPARC64 VII, and
Chapter 2
3-27.
2-30.
What You Must Know Before Using DR 2-5