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

Chapter 19 361
Logging Location Codes
Control Process Logging Location Codes
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 an SR,” of this manual.
MESSAGE: BUFFER MANAGER; Buffer manager error
626 CLAS0002 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 an SR,” of this manual.
MESSAGE: INTERNAL ERROR; Internal resource error
627 CLAS0002 CAUSE: While stopping an NI because a network was being shut down,
NETCP encountered an error trying to delete a mapping table it had
previously created for the NI (PARM = 32-bit status returned by the
call to map_create_table).
ACTION: This error in itself was not fatal, and shutdown continued.
However, depending on the error, the amount of system memory used
by the table and its secondary tables be inaccessible until the next
system restart. If the problem occurs repeatedly, see Appendix A,
“Submitting an SR,”A of this manual.
MESSAGE: Bad status
628 CLAS0002 CAUSE: While attempting to stop one of the devices on an existing NI,
NETCP disconnected the device at the MAP level, then encountered an
error trying to send a device stop message to the NI (PARM = 32-bit
status returned by the call to send_msg).
ACTION: This error in itself was not fatal, and shutdown may continue.
However, 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: PACKET DISCARD; Late reply
629 CLAS0002 CAUSE: During processing of a Path Verify operation on behalf of some
other Transport module because of a possible problem or change in
state of a certain network, NETCP sent Path Verify request messages
to all the general protocols, but failed to receive a reply from one of