Processors
The boot processor is responsible for servicing the tick-timer interrupts and for
maintaining the netcon BBSRAM buffer. Before detaching a board on which the boot
processor resides, the dr_daemon(1M) must assign the boot processor role to
another active (online) processor.
Finishing the Complete Detach Operation
After all board usage is terminated, you can perform the Complete Detach
operation. If a device is still in use at this time, the detach operation fails and the
device in use is reported. After you resolve the problem, you can perform the
Complete Detach operation again.
If the board that you want to detach contains nonpageable memory, the Complete
Detach operation may also fail due to quiescence problems, which are described in
"System Quiescence Operation" on page 11. After you resolve the quiescent
problem, you can again execute the complete detach operation.
If you decide that you do not want to proceed with the detach operation at this time,
you can abort the detach. The memory on a board is returned to normal usage and
detached board devices are reattached. If the system configuration was modified to
remove board usage (that is, file systems were unmounted and networks were
unplumbed), you must undo these modifications and return the devices to normal
operation.
After the board is successfully detached from the operating environment, it is
isolated from the centerplane. In addition, the board list is automatically updated in
the SSP domain_config(4) file.
You can now attach the board to another domain, power it off, and remove it by way
of hot-swapping, leaving it in the system unattached, or reattaching it at a later time.
30
Sun Enterprise 10000 Dynamic Reconfiguration User Guide • February 2000
Need help?
Do you have a question about the Sun Enterprise 10000 Dynamic and is the answer not in the manual?