NS3000/iX Error Messages Reference Manual (36923-90043)

514 Chapter21
Logging Location Codes
Control Process Logging Location Codes
633 CLAS0002 MESSAGE: Bad status
CAUSE: While attempting to send a device stop message to notify the
DIAL module that an existing ROUTER network was being shut down,
because of a :NETCONTROL DELLINK command or a previous
asynchronous link error, NETCP encountered an error on the send
(PARM = 32-bit status returned by the call to send_msg).
ACTION: The error in itself was not fatal, and shutdown of this network
probably continued, ending with deletion of this instance of the DIAL
module. However, DIAL was not notified the device has stopped, which
may have caused more errors if it happened to run again before it was
deleted. In addition, some versions of Transport may hang if this
problem occurs, requiring a system restart to recover. On a non critical
terminal, attempt a :NETCONTROL STATUS command; if results are
reported, then try restarting the network. If the network restarts but
the problem returns, see Appendix A , “Submitting a CR,” of this
manual.
634 CLAS0002 MESSAGE: Bad status
CAUSE: While processing an asynchronous event message from the
DCLDM indicating that its LAPB PSI link either experienced a
problem related to autodial, or else that an autodial succeeded, NETCP
encountered an error trying to send a reply message back to DIAL
telling the type of event that occurred (PARM = 32-bit status returned
by the call to send_msg).
ACTION: DIAL did not receive the reply message, and will be unaware
of the results of the autodial operation. It may take up to 30 minutes for
DIAL to time out and reset itself, and during this delay, new autodial
connections cannot be established, and sessions which attempt it may
hang. To clear this condition, first try a :NETCONTROL
DELLINK=linkname; NET=niname command against the affected link,
followed by a :NETCONTROL ADDLINK=linkname; NET=niname. If this
does not help, a system restart will probably be required to clear the
hang. If the problem occurs again, take a dump when the error is
reported and before any attempts to recover, and see Appendix A ,
“Submitting a CR,” of this manual.
635 CLAS0002 MESSAGE: INTERNAL ERROR; Internal resource error
CAUSE: NETCP received an asynchronous exception event message
from a link driver, but no device having the SDI link ID in that message
was found in NETCP’s device tables (PARM = 32-bit SDI device ID from
the message).
ACTION: Either the driver or NETCP are confused. Though NETCP
may continue working, the affected network will most likely hang,
possibly requiring a system restart to recover. See Appendix A ,
“Submitting a CR,” of this manual.