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

364 Chapter19
Logging Location Codes
Control Process Logging Location Codes
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 an SR,” of this manual.
MESSAGE: INTERNAL ERROR; Internal resource error
635 CLAS0002 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 an SR,” of this manual.
MESSAGE: Bad status
636 CLAS0002 CAUSE: While attempting to send a debug message to one of the
Transport protocol modules in response to a :NETCONTROL DIAG
command, NETCP encountered an error on the send (PARM = 32-bit
status returned by the call to send_msg).
ACTION: This error was not fatal, and NETCP continued running.
However, the desired module did not receive its debug message, and
will not respond as expected. If the problem persists, see Appendix A,
“Submitting an SR,” of this manual.
MESSAGE: Bad status
637 CLAS0002 CAUSE: While processing a :NETCONTROL DELLINK command, and
trying to send a DCN stop message to the IPU module of Transport
because at least one network link was active, NETCP encountered an
error on the send (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 the operation 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
638 CLAS0002 CAUSE: While attempting to start all the general protocols because a
:NETCONTROL START command was starting a new instance of
Transport, NETCP successfully started some modules, then