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

Chapter 21 511
Logging Location Codes
Control Process Logging Location Codes
establish connections with it may fail. Restart the network. If this
problem persists, see Appendix A , “Submitting a CR,” of this manual.
624 CLAS0002 MESSAGE: Bad status
CAUSE: While attempting to send a device stop message to the DIAL
module because protocols on an existing ROUTER network are being
shut down, 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.
625 CLAS0002 MESSAGE: BUFFER MANAGER; Buffer manager error
CAUSE: While deconfiguring an NI for a network that was being shut
down and which also had IP Store and Forward enabled, after first
deleting that Store and Forward buffer pool ID from the NS Registry,
NETCP encountered an error trying to delete the buffer pool itself
(PARM = 32-bit status returned by the call to bmgr_delete_pool).
ACTION: This error was not fatal, and network shutdown continued.
However, the amount of system memory used by the pool may be
inaccessible until the next system restart. Probably some buffers for the
pool were lost, or are still outstanding in link drivers or in Transport
modules which had previously encountered errors. If the problem
occurs repeatedly, see Appendix A , “Submitting a CR,” of this manual.
626 CLAS0002 MESSAGE: BUFFER MANAGER; Buffer manager error
CAUSE: While deconfiguring an NI for a network that was being shut
down, after first deleting the outbound buffer pool ID from the NS
Registry, NETCP encountered an error trying to delete the buffer pool
itself (PARM = 32-bit status returned by the call to
bmgr_delete_pool).
ACTION: This error was not fatal, and network shutdown continued.
However, the amount of system memory used by the pool may be
inaccessible until the next system restart. Probably some buffers for the
pool were lost, or are still outstanding in link drivers or in Transport
modules which had previously encountered errors. If the problem
occurs repeatedly, see Appendix A , “Submitting a CR,” of this manual.