System Quiescence Operation - Sun Microsystems Sun Enterprise 10000 Dynamic Reconfiguration User Manual

a DR operation, check the domain. The daemon must be configured in the
/etc/inetd.conf file of the domain. The following line (which appears on a single
line) must be present in the file:
300326/4 tli rpc/tcp wait root \
/platform/SUNW,Ultra-Enterprise-10000/lib/dr_daemon/ dr_daemon
If the DR daemon is configured in /etc/inetd.conf, kill the dr_daemon(1M) if it
is currently running. In addition, send a HUP signal to the inetd(1M) daemon to
cause it to re-read the inetd.conf(4) configuration file:
# kill dr_daemon_pid
# kill -HUP inetd_pid
In the first command, dr_daemon_pid is the process ID of the DR daemon. In the
second command, inetd_pid is the process ID of the inetd(1M)daemon. You can
check /var/adm/messages for possible error messages from inetd(1M)if it is
having trouble starting the dr_daemon(1M). The DR daemon executable file should
exist in the /platform/SUNW,Ultra-Enterprise-10000/lib directory.
At this point, try the DR operation again, starting from the beginning.

System Quiescence Operation

During a DR Detach operation on a system board with nonpageable OBP or kernel
memory, the operating environment is briefly quiesced; that is, all operating
environment and device activity on the domain centerplane must cease during the
critical phase of the operation. The quiescence only affects the target domain; other
domains in the system are not affected.
Before it can quiesce, the operating environment must temporarily suspend all
processes, processors, and device activities. If the operating environment cannot
quiesce, it displays its reasons, which may include the following:
Real-time processes are running in the domain.
A device that cannot be quiesced by the operating environment (that is, a
suspend-unsafe device) is open.
The conditions that cause processes not to suspend are generally temporary in
nature. You can retry the operation until the quiescence succeeds.
Chapter 11