|
|
|
|
Once a session has been established, NDMA handles any commands sent down from the host. NDMA operates unattended until it is terminated.
If the program is running in the foreground, it writes messages to the screen to provide information about its processing. These can be progress messages to indicate which operations are being performed, or error messages indicating conditions such as failure to access a file or insufficient disk space. These messages are listed in Progress Messages.
Information about NDMA processing is also recorded as follows:
NDMA writes an entry to the command log file for each command that it attempts to execute. The entry includes information about the file name, if any, processed by the command, and on whether the command was successful. For more information, see Command Log.
If an error occurs, NDMA writes a message to the SNAP-IX error log file. For more information, see Diagnostics.
This section lists the progress messages that NDMA writes to the screen during normal operation.
MESSAGE 1: Initialization successful. NDMA has successfully completed its internal initialization, and is
now waiting for a session to be established. MESSAGE 2: Initialization failed-check error log for cause. NDMA has failed to establish communications with the local node during
initialization, and is terminating. Check the error log file to determine
the reason for the failure. MESSAGE 4: Communications with the host have been established. A valid BIND has been received from the host, establishing a session
between NDMA and the host. MESSAGE 5: Communications with the host have ended normally. An UNBIND has been received from the host, ending the current session
normally. NDMA waits for a new session to be established. MESSAGE 6: Communications with the host have ended unexpectedly. The current session has ended abnormally owing to a line outage or other
error. NDMA logs the command it is processing as unsuccessful, and waits for
a new session to be established. Check the error log file to determine the
reason for the failure. MESSAGE 7: Communications link has failed. The node has reported a failure of the communications link to the host.
Check the error log file to determine the reason for the failure. MESSAGE 8: Communications link is not usable. The communications link to the host may be broken, or otherwise is not
usable. NDMA waits for the node to acknowledge successful sending of a message
on the link. Check the error log file to determine the reason for the failure.
MESSAGE 9: Error in accessing local disk. NDMA has failed to read or write to a file. Check the error log file
to determine more details of the failed file access operation; check the access
permissions on the file or directory. MESSAGE 10: The requested disk is full. NDMA cannot write to a file because the disk is full. Clear some disk
space by removing unnecessary files. MESSAGE 14: Communications have been restarted after an error. NDMA has closed and reopened its communications with the node in order
to clear an error condition. It is now ready to resume communications with
the host. MESSAGE 15: Communications could not be restarted after an error. NDMA attempted to close and reopen its communications with the node,
in order to clear an error condition, but could not reestablish communications.
NDMA will terminate. MESSAGE 16: Communications fault-communications will be restarted.
NDMA has detected an error condition in its communications with the
local node. It will close and reopen its communications with the node in order
to clear this condition. This message should be followed by either Message
14 or Message 15, indicating whether communications were successfully re-established.
MESSAGE 20: NDMA has ended normally. The user has terminated NDMA normally, by pressing F3.
MESSAGE 21: NDMA has been instructed to stop regardless of current status.
The user terminated NDMA abnormally, either by pressing Ctrl
+ C (or the keys the user has defined for interrupting operations),
or by using the Solaris kill command. MESSAGE 22: Please check communications lines and settings, then restart
NDMA. NDMA ended because it could not restart its communications with the
node. MESSAGE 23: Please check NDMA configuration, then restart. NDMA cannot initialize because of a configuration problem. Check that SNAP-IX
is configured correctly for NDMA (for more information, see Configuring NDMA).
If an error occurs while NDMA is communicating with the host, NDMA takes appropriate measures to try to recover, as well as logging the error in the log file. The error recovery action depends on the error.
For most errors, this consists of informing the host of the error with a negative response or a negative status response. The host takes the appropriate action to recover, such as retrying the command.
If NDMA detects an error condition from which it cannot recover, for example if it loses contact with the local node and cannot reestablish contact, it logs a message providing information about the error and then terminates.
For more information about messages logged by NDMA, see Diagnostics.
|
|
|
 |
|