SSP Error Messages

NGNGDR Error: abort_attach_board: invalid board number

The RPC is attempting to perform a DR operation on a board number that is not in the range of valid numbers. The DR applications carefully filter the user input to catch out-of-range board numbers before they send the RPC. Therefore, this error indicates a breakdown on the SSP or in the network connection to the SSP. Or, it indicates an incompatibility between the SSP applications and the DR daemon. 

Check the SSP network connection and/or the SSP and DR applications to ensure that they are operating properly. 

NGNGDR Error: abort_detach_board: invalid board number

The RPC is attempting to perform a DR operation on a board number that is not in the range of valid numbers. The DR applications carefully filter the user input to catch out-of-range board numbers before they send the RPC. Therefore, this error indicates a breakdown on the SSP or in the network connection to the SSP. Or, it indicates an incompatibility between the SSP applications and the DR daemon. 

Check the SSP network connection and/or the SSP and DR applications to ensure that they are operating properly. 

NGNGDR Error: attach_finished: invalid board number

The RPC is attempting to perform a DR operation on a board number that is not in the range of valid numbers. The DR applications carefully filter the user input to catch out-of-range board numbers before they send the RPC. Therefore, this error indicates a breakdown on the SSP or in the network connection to the SSP. Or, it indicates an incompatibility between the SSP applications and the DR daemon. 

Check the SSP network connection and/or the SSP and DR applications to ensure that they are operating properly. 

NGDR Error: complete_attach_board: invalid board number

The RPC is attempting to perform a DR operation on a board number that is not in the range of valid numbers. The DR applications carefully filter the user input to catch out-of-range board numbers before they send the RPC. Therefore, this error indicates a breakdown on the SSP or in the network connection to the SSP. Or, it indicates an incompatibility between the SSP applications and the DR daemon. 

Check the SSP network connection and/or the SSP and DR applications to ensure that they are operating properly. 

NGDR Error: cpu0_move_finished: invalid board number

The RPC is attempting to perform a DR operation on a board number that is not in the range of valid numbers. The DR applications carefully filter the user input to catch out-of-range board numbers before they send the RPC. Therefore, this error indicates a breakdown on the SSP or in the network connection to the SSP. Or, it indicates an incompatibility between the SSP applications and the DR daemon. 

Check the SSP network connection and/or the SSP and DR applications to ensure that they are operating properly. 

NGDR Error: detach_board: invalid board number

The RPC is attempting to perform a DR operation on a board number that is not in the range of valid numbers. The DR applications carefully filter the user input to catch out-of-range board numbers before they send the RPC. Therefore, this error indicates a breakdown on the SSP or in the network connection to the SSP. Or, it indicates an incompatibility between the SSP applications and the DR daemon. 

Check the SSP network connection and/or the SSP and DR applications to ensure that they are operating properly. 

NGDR Error: detach_finished: invalid board number

The RPC is attempting to perform a DR operation on a board number that is not in the range of valid numbers. The DR applications carefully filter the user input to catch out-of-range board numbers before they send the RPC. Therefore, this error indicates a breakdown on the SSP or in the network connection to the SSP. Or, it indicates an incompatibility between the SSP applications and the DR daemon. 

Check the SSP network connection and/or the SSP and DR applications to ensure that they are operating properly. 

NGDR Error: detachable_board: invalid board number

The RPC is attempting to perform a DR operation on a board number that is not in the range of valid numbers. The DR applications carefully filter the user input to catch out-of-range board numbers before they send the RPC. Therefore, this error indicates a breakdown on the SSP or in the network connection to the SSP. Or, it indicates an incompatibility between the SSP applications and the DR daemon. 

Check the SSP network connection and/or the SSP and DR applications to ensure that they are operating properly. 

NGDR Error: drain_board_resources: invalid board number

The RPC is attempting to perform a DR operation on a board number that is not in the range of valid numbers. The DR applications carefully filter the user input to catch out-of-range board numbers before they send the RPC. Therefore, this error indicates a breakdown on the SSP or in the network connection to the SSP. Or, it indicates an incompatibility between the SSP applications and the DR daemon. 

Check the SSP network connection and/or the SSP and DR applications to ensure that they are operating properly. 

NGDR Error: get_board_config: invalid board number

The RPC is attempting to perform a DR operation on a board number that is not in the range of valid numbers. The DR applications carefully filter the user input or catch out-of-range board numbers before they send the RPC. Therefore, this error indicates a breakdown on the SSP or in the network connection to the SSP. Or, it indicates an incompatibility between the SSP applications and the DR daemon. 

Check the SSP network connection and/or the SSP and DR applications to ensure that they are operating properly. 

NGDR Error: get_board_state: invalid board number

The RPC is attempting to perform a DR operation on a board number that is not in the range of valid numbers. The DR applications carefully filter the user input to catch out-of-range board numbers before they send the RPC. Therefore, this error indicates a breakdown on the SSP or in the network connection to the SSP. Or, it indicates an incompatibility between the SSP applications and the DR daemon. 

Check the SSP network connection and/or the SSP and DR applications to ensure that they are operating properly. 

NGDR Error: get_cpu_info: invalid board number

The RPC is attempting to perform a DR operation on a board number that is not in the range of valid numbers. The DR applications carefully filter the user input to catch out-of-range board numbers before they send the RPC. Therefore, this error indicates a breakdown on the SSP or in the network connection to the SSP. Or, it indicates an incompatibility between the SSP applications and the DR daemon. 

Check the SSP network connection and/or the SSP and DR applications to ensure that they are operating properly. 

NGDR Error: get_obp_board_config: invalid board number

The RPC is attempting to perform a DR operation on a board number that is not in the range of valid numbers. The DR applications carefully filter the user input to catch out-of-range board numbers before they send the RPC. Therefore, this error indicates a breakdown on the SSP or in the network connection to the SSP. Or, it indicates an incompatibility between the SSP applications and the DR daemon. 

Check the SSP network connection and/or the SSP and DR applications to ensure that they are operating properly. 

NGDR Error: initiate_attach_board: invalid board number

The RPC is attempting to perform a DR operation on a board number that is not in the range of valid numbers. The DR applications carefully filter the user input to catch out-of-range board numbers before they send the RPC. Therefore, this error indicates a breakdown on the SSP or in the network connection to the SSP. Or, it indicates an incompatibility between the SSP applications and the DR daemon. 

Check the SSP network connection and/or the SSP and DR applications to ensure that they are operating properly. 

NGDR Error: initiate_attach_board: invalid cpu number

The RPC is attempting to perform a initiate an attach of a board that contains a CPU that is not on the board. The DR applications carefully filter the user input or catch invalid CPU numbers before they send the RPC. Therefore, this error indicates a breakdown on the SSP or in the network connection to the SSP. Or, it indicates an incompatibility between the SSP applications and the DR daemon. 

Check the SSP network connection and/or the SSP and DR applications to ensure that they are operating properly. 

NGDR Error: Unauthorized RPC call . . . Not owner

The DR daemon received an RPC that failed authentication. 

Check the system log for more information about this error. Also, make sure that the version numbers match for the SSP and the DR daemon and that the SSP user and network services are properly configured. 

NGDR Error: abort_attach_board: invalid board state

The attach operation could not be aborted because the board is not in the init_attach state, awaiting to be configured into the domain. 

Wait for the board to enter the init_attach state. Only then can the attach operation be aborted. 

NGDR Error: attach_finished: invalid board state

Communication protocol has been breached over the state of the attach operation. The DR driver and daemon disagree with the SSP that the board was waiting for the confirmation of the attach operation from the SSP. 

Exit and restart the current DR application, then retry the operation. If this error persists, stop and restart the DR daemon. You may need to reboot the domain to recover from this error. 

NGDR Error: Cannot abort attach. Board ineligible for further DR operations.

The board entered the FATAL state after the abort command was issued, causing the abort operation to fail and the board to be lost from the system. 

Reboot the domain. 

dr_attach: failure executing A3000 hot_add script . . . error message

The Sun(TM) StoreEdge(TM) A3000 hot_add script is executed directly after a DR attach operation. If the script exists, but it cannot be executed, the error message explains why.

If you are not using, nor plan to use, A3000 devices, you can rename the script so that it will not be found. 

initiate_attach_board: already init_attached

You attempted to initiate the attach of a board that was already initiated. 

Go to the complete attach window and continue the attach process. 

NGDR Error: complete_attach_board: invalid board state

You tried to initiate an attach operation on a board that is not eligible--the board is not in the init_attach state awaiting attachment to the domain. 

Wait for the board to enter the init_attach state. Only then can the attach operation be aborted. 

NGDR Error: initiate_attach_board: invalid board state

You tried to initiate an attach operation on a board that is not eligible--the board is not in the PRESENT state awaiting attachment to the domain. 

Wait for the board to enter the init_attach state. Only then can the attach operation be aborted. 

NGDR Error: Some devices not attached. Examine the host syslog for details . . . errno_description

Some of the devices were not configured into the domain. 

Look at the system logs for more details about what devices were not configured into the domain and why they were not configured. Some devices on the board may not be supported by the operating environment or by the DR feature. You should blacklist unsupported devices. 

NGDR Error: Cannot detach board board_number. It has interface_name interfaces configured.

The board is not eligible to be detached because it has one or more network interfaces attached to it that are critical to the operation of the domain. The network interfaces can be any mix of primary, SSP, AP, or PBF interfaces. 

Use the ifconfig(1M) command to determine the role of the interface(s). If the configured interface is the primary network or the SSP, manually switch the interface to the alternate interface if one exists. For an interface other than the primary and the SSP, unplumbing it may enable the detach operation to succeed. Otherwise, the domain must be shut down, and the interfaces must be moved to another board.

NGDR Error: cpu0_move_finished: invalid board state

Communication protocol has been breached over the eligibility of a CPU. To the SSP, the CPU has been moved off of the board. To the DR driver, the move operation is an invalid operation for that board. 

None 

ifconfig down failed.

The ifconfig(1M) command failed to bring down the network interfaces. The ifconfig(1M) command unplumbs and brings down the network interfaces before the board is detached. One of the network interfaces on the board could be busy, so manual intervention may be needed.

Log in to the domain, and, if possible, bring down the network interfaces on the board manually by using the ifconfig(1M) command with the down option. The manual execution of the command may yield more detailed information about the failure.

ifconfig unplumb failed.

The ifconfig(1M) command failed to unplumb the network interfaces. The ifconfig(1M) command unplumbs and brings down the network interfaces before the board is detached. One of the network interfaces on the board could be busy, so manual intervention may be needed.

Log in to the domain, and, if possible, unplumb the network interfaces manually by using the ifconfig(1M) command with the unplumb option. The manual execution of the command may yield more detailed information about the failure.

Warning: Error return from /opt/SUNWconn/bin/nf_snmd_kill (return_value)

The command failed. Certain daemons keep network interfaces open continuously. Those daemons must be stopped before the devices they control can be detached. 

Analyze the return_value to determine why the kill(1) command failed, and try to correct the problem. If necessary, use the ps(1) command to obtain the PID number for the daemons, and use the kill(1) command to stop the daemons manually.

Warning: Error return from /opt/SUNWconn/bin/pf_snmd_kill (return_value)

The kill(1) command failed. The daemons that are used to control certain network devices must be stopped before the devices can be detached because the daemons keep the interfaces open continually.

Analyze the return_value to determine why the kill command failed, and try to correct the problem. If necessary, use the ps(1) command to obtain the PID number for the daemons, and use the kill(1) command to stop the daemons manually.

NGDR Error: abort_detach: board already drained

The CANCEL ioctl() failed while the DR daemon was trying to abort the detach operation. The failure caused the board to be reported as being in the UNREFERENCED state, indicating that the memory has already been drained.

The board must be completely detached before you can recover from this error. Retry the DR operation after the board has been successfully detached. 

NGDR Error: abort_detach_board: invalid board state

Communication protocol has been breached over the eligibility of a board. To the SSP, the board is part of the domain and has been, or is being, drained of its resources. The SSP, therefore, issues the abort command to stop the detach operation. However, to the DR driver and daemon, the board is not part of the domain. 

Exit and restart the DR application. 

NGDR Error: board configuration query failed.

The DR daemon failed to ascertain the eligibility of the configuration of the board. 

Stop and start the DR daemon and/or the DR driver. If this error persists, use the modinfo(1M), modload(1M), and modunload(1M) commands to work with the driver after you have stopped the DR daemon. Also, check the size of the DR daemon with the ps(1) command. If it is not between 300- and 400 Kbytes, report this error, providing as much information from the system logs as possible.

NGDR Error: Cannot abort detach. Board detached from OS (detach completed).

This message indicates that the detach operation has completed. It follows the message that is displayed for the NGDR Error: abort_detach: board already drained error message.

See the NGDR Error: abort_detach: board already drained message.

NGDR Error: couldn't query cpu configuration

The complete_detach operation has failed because the DR daemon could not ascertain the CPU configuration just prior to the beginning of the complete_detach operation. After a board is detached, the DR daemon uses the information about the CPU configuration to update the utmp and wtmp entries for each CPU on the board. Although the complete_attach operation does not depend on the updates, if the mechanisms through which the CPU configuration is queried are broken, serious problems exist, so a completion of the detach operation should not proceed.

Stop and start the DR daemon and/or the DR driver. Also, check the size of the DR daemon with the ps(1) command. If it is not between 300- and 400-Kbytes, report this error, providing as much information from the system logs as possible.

NGDR Error: detach_board: invalid board state

Communication protocol has been breached over the eligibility of a board. To the SSP, the board is part of the domain, and its resources have been drained, causing the SSP to attempt to complete the detach operation. However, to the DR driver and daemon, the board is not part of the domain. 

Examine the state of the board by using the showdevices(1m) 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.

NGDR Error: detach_board: invalid board state

The proper sequence of board states has not been followed, meaning that the board went into the error state or that an earlier failure in the drain-detach sequence of events was not properly reported. 

Examine the state of the board by using the showdevices(1m) 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.

NGDR Error: detach_finished: invalid board state

Communication protocol has been breached over the eligibility of a board. To the SSP, the board has been detached. However, to the DR driver and daemon, the board has not been detached from the domain. 

Examine the state of the board by using the showdevices(1m) 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.

NGDR Error: detachable_board: invalid board state

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. 

Examine the state of the board by using the showdevices(1m) 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.

NGDR Error: detaching board would leave no online CPUs

The detach operation failed because no CPUs would be left online after the board is detached. 

Bring more CPUs online on other boards in the domain, or add more boards with online CPUs to the domain, so that the domain will have enough online CPUs after the board is detached. 

NGDR Error: drain_board_resources: invalid board state

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. 

Examine the state of the board by using the showdevices(1m) 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.

NGDR Error: Remaining system memory (memory_size mb) below minimum threshold (minimum_memory_size mb) . . . .Not enough space

The domain must have enough memory to accommodate 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. 

Attach as many boards as necessary so that the memory in the domain will hold the memory on the board being detached. 

NGDR Error: Some devices not re-attached. Examine the host syslog for details . . . errno_description

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. 

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.

NGDR Error: sysconf failed (_SC_NPROCESSORS_ONLN) . . . errno_description

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.

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.

NGDR Error: Complete pending DR operation prior to running autoconfig . . . Invalid argument

The autoconfig(1M) command failed because a DR operation was still pending (that is, the board was not fully detached or attached before you issued the autoconfig(1M) command to reconfigure the operating environment).

Use the showdevices(1M) command to determine the state of the board. Decide to abort or complete the pending operation before you try to use the autoconfig(1M) command to reconfigure the operating environment.

NGDR Error: Could not get /tmp/AdDrEm.lck lock . . . errno_description

The DR daemon failed to get the lock it needs so that it can reconfigure the operating environment. 

Check the additional errno_description and/or error number that is sent with the error message to determine why the lock could not be acquired.

NGDR Error: Could not unlock /tmp/AdDrEm.lck lock . . . errno_description

The DR daemon could not release the lock. 

Check the additional errno_description and/or error number that is sent with the error message to determine why the lock was not released.

NGDR Error: devlinks cmd failed. . . error descriptions

The devlinks(1M) command failed to reconfigure the operating environment.

Check the additional error descriptions and/or error number that is sent with the error message to determine why the command failed. Manually run the command on the domain.

NGDR Error: disks cmd failed . . . error descriptions

The disks(1M) command failed to reconfigure the operating environment.

Check the additional error descriptions and/or error number that is sent with the error message to determine why the command failed. Manually run the command on the domain.

NGDR Error: drvconfig cmd failed. . . error description

The drvconfig(1M) command failed to reconfigure the operating environment.

Check the additional error description and/or error number that is sent with the error message to determine why the command failed. Manually run the command on the domain.

NGDR Error: ports cmd failed . . . error description

The ports(1M) command failed to reconfigure the operating environment.

Check the additional error description and/or error number that is sent with the error message to determine why the command failed. Manually run the command on the domain.

NGDR Error: sync cmd failed . . . error description

The sync(1M) command failed to reconfigure the operating environment.

Check the additional error description and/or error number that is sent with the error message to determine why the command failed. Manually run the command on the domain.

NGDR Error: tapes cmd failed . . . error descriptions

The tapes(1M) command failed to reconfigure the operating environment.

Check the additional error description and/or error number that is sent with the error message to determine why the command failed. Manually run the command on the domain.