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

Chapter 19 363
Logging Location Codes
Control Process Logging Location Codes
problem with the path, and may continue to try to use it. In addition,
PING commands from NETTOOL may report errors against the
affected network. If the problem persists, see Appendix A, “Submitting
an SR,”A of this manual.
MESSAGE: Bad status
632 CLAS0002 CAUSE: While processing a :NETCONTROL STOP command or a system
shutdown, NETCP encountered an error trying to send a DCN stop
message to the IPU module of Transport (PARM = 32-bit status
returned by the call to send_msg). A DCN stop message is required for
a Directly Connected Network such as X25.
ACTION: This error in itself was not fatal, and shutdown may continue.
However, some versions of Transport may hang if this problem occurs
or if the IPU module initially failed to start (see error 654), 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 an SR,” of this manual.
MESSAGE: Bad status
633 CLAS0002 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 an SR,” of this
manual.
MESSAGE: Bad status
634 CLAS0002 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