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

Chapter 21 523
Logging Location Codes
Control Process Logging Location Codes
661 CLAS0002 MESSAGE: Bad status
CAUSE: After successfully starting a LAN 802.3 or Ethernet link and all
its network specific protocols because a :NETCONTROL command was
issued, NETCP encountered an error trying to send a broadcast
information message to the UDP protocol module (PARM = 32-bit
status returned by the call to send_msg).
ACTION: This error in itself was not fatal, and network startup
continued. After this failure, most of Transport, with the exception of
UDP, will probably run correctly. However, certain actions, such as Path
Verifies, can indirectly result in more sends to UDP, which may cause
more errors. When convenient, try stopping Transport using
:NETCONTROL STOP, then restart it and bring up the LAN link again. If
the same problem persists, see Appendix A , “Submitting a CR,” of this
manual.
664 CLAS0002 MESSAGE: INTERNAL ERROR; Internal resource error
CAUSE: While starting Transport’s first active X25 NI because a
:NETCONTROL command was issued, NETCP encountered an error
trying to start the X25 Flow Control Manager (PARM = 32-bit status
returned by the call to netfc_config). NETCP keeps track of the
number of X25 networks started, and only makes this call then starting
the first one. The Flow Control Manager dynamically allocates the flow
control buffer pools for X25.
ACTION: This error in itself was not fatal, and network startup
continued. However, X25 may not operate correctly. If X25 connections
are not working, stop then restart the network. If the problem persists,
see Appendix A , “Submitting a CR,” of this manual.
665 CLAS0002 MESSAGE: Bad status
CAUSE: After successfully starting a TOKEN link and all its network
specific protocols because a :NETCONTROL command was issued, NETCP
encountered an error trying to send a broadcast information message to
the UDP protocol module (PARM = 32-bit status returned by the call to
send_msg).
ACTION: This error in itself was not fatal, and NETCP startup
continued. After this failure, most of Transport, with the exception of
UDP, will probably run correctly. However, certain actions, such as Path
Verifies, can indirectly result in more sends to UDP, which may cause
more errors. When convenient, try stopping Transport using
:NETCONTROL STOP, then restart it and bring up the TOKEN link
again. If the same problem persists, see Appendix A , “Submitting a
CR,” of this manual.
666 CLAS0002 MESSAGE: Bad status
CAUSE: While processing a :NETCONTROL STATUS command, NETCP
encountered an error trying to send a reply message back to the NETUI
module (PARM = 32-bit status returned by the call to send_msg).