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

368 Chapter19
Logging Location Codes
Control Process Logging Location Codes
from the NMCONFIG file, then encountered an error trying to write
that data into a buffer it obtained a short time earlier (PARM = 32-bit
status returned by the call to bmgr_write_buffer).
ACTION: NETCP was unable to write all the required data, and
attempted to recover and free the buffer. The network operation that
was being performed will not work correctly. Because the buffer given to
NETCP by the buffer manager should have been large enough to
contain all data that was to be written, there may be a problem in
either NETCP, the buffer manager, the NMS subsystem, or NMMGR, or
the NMCONFIG file may be corrupt. Stop the network and retry the
operation. If the problem persists, see Appendix A, “Submitting an SR,”
of this manual.
MESSAGE: Bad status
649 CLAS0002 CAUSE: After successfully building a buffer containing needed
configuration data for an X25 network that was being started, NETCP
encountered an error trying to send the buffer to the X25 protocol
module (PARM = 32-bit status returned by the call to send_msg).
ACTION: X25 did not receive its configuration data, though the rest of
network startup continued. The X25 network will not operate correctly
in this condition. In addition, the buffer may have been lost, which may
result in error 613 when the network is stopped. Try stopping and
restarting the network. If the problem persists, see Appendix A,
“Submitting an SR,” of this manual.
MESSAGE: INTERNAL ERROR; Module Deconfig Failed
650 CLAS0002 CAUSE: During the final phases of shutdown because of a
:NETCONTROL STOP command or a system shutdown, NETCP
encountered and error while attempting to stop the ICMP Server
module it previously started (PARM = 32-bit status returned by the call
to icmp_server_module_deconfig)
ACTION: This error in itself was not fatal, and shutdown continued.
However, any system resources owned by the ICMP Server may be lost
until after the next system restart. If this problem occurs repeatedly,
see Appendix A, “Submitting an SR,” of this manual.
MESSAGE: INTERNAL ERROR; Internal resource error
651 CLAS0002 CAUSE: While attempting to start all the general protocols because a
:NETCONTROL command was starting a new instance of Transport,
NETCP encountered an error trying to start the TCP protocol module
(PARM = 32-bit status returned by the call to tcp_module_config).
Always preceded by another error from another entity (having a
different Entity number, such as 151–160), logging the reason for the
original failure.
ACTION: None of the general protocols were started, so Transport will
not work. Older versions of Transport will improperly continue the
startup after this error, and may also hang when stopped. Record the