Sun Microsystems Sun Enterprise 10000 Dynamic Reconfiguration User Manual page 92

TABLE A-8
Error Message
DR Error:
drain_board_resources:
invalid board state
DR Error: Remaining system
memory (memory_size mb) below
minimum threshold
(minimum_memory_size mb) . .
. .Not enough space
DR Error: Some devices not
re-attached. Examine the
host syslog for details . .
. errno_description
DR Error: sysconf failed
(_SC_NPROCESSORS_ONLN) . .
. errno_description
76 Sun Enterprise 10000 Dynamic Reconfiguration User Guide • February 2000
Detach-Related Failure Error Messages (Continued)
Probable Cause
Communication protocol has been
breached over the eligibility of a
board. To the SSP, the board is part of
the domain, so the SSP attempts to
drain the resources. However, to the
DR driver and daemon, the board is
not part of the domain.
The domain must have enough
memory to accomodate the memory of
the board that is being detached. The
detach operation failed because the
domain does not have enough
memory to detach the board.
Devices could not be reattached to the
operating environment during an
Abort Detach operation. Errors were
encountered while the DR daemon
tried to communicate with the device
drivers for one or more devices on the
board.
The sysconf(3c) system call failed to
return the total number of online CPUs
in the domain. Thus, the DR daemon
cannot determine if the domain would
be left with any online CPUs after the
board is detached.
Suggested Action
Examine the state of the board
by using the
dr_cmd_board_states(?)
command, and determine the
cause of the problem. Retry the
Drain and/or Complete-
Detach operations to
determine if the error is
recoverable. Stop and start the
DR daemon and driver.
Attach as many boards as
necessary so that the memory
in the domain will hold the
memory on the board being
detached.
Examine the system logs to
determine which devices were
not reattached. If possible, fix
the problem then issue the
complete_attach(1M)
command again to fully
configure the board. If this
action fails, the failure may be
caused by an unsupported
device for which a state cannot
be resolved until the domain is
rebooted.
See the sysconf(3c) man page
for more details about this
error. Use those details and the
errno_description to diagnose
and solve the error. Retry the
DR operation after you have
solved the error. If no fix is
apparent, stop and restart the
DR daemon, then retry the DR
operation.