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

Chapter 19 377
Logging Location Codes
Control Process Logging Location Codes
which may aid in debugging any hung modules. If the problem occurs
repeatedly or a general protocol bug is suspected, see Appendix A,
“Submitting an SR,” of this manual.
MESSAGE: INTERNAL ERROR; Configuration file error
680 CLAS0002 CAUSE: While reading the home node's path report during initial
NETCP startup, or while starting some network specific protocols for a
LAN, GATEHALF or ROUTER network because a :NETCONTROL
command was issued, NETCP encountered error when trying to
compute the total length of some NMCONFIG file data, prior to getting
a buffer large enough to hold all that data (PARM = 32-bit status
returned by the call to nmconfdatalength).
ACTION: You may have attempted to configure a larger network than is
currently supported by Transport; save a copy of your current
NMCONFIG file, then reduce the size of your configuration and try the
operation again. If your network is small and you therefore do not
suspect size as the cause, there may be some problem with the NMS
subsystem, NMMGR, or NETCP, so see Appendix A, “Submitting an
SR,”of this manual.
MESSAGE: BUFFER MANAGER; Buffer manager error
681 CLAS0002 CAUSE: While reading the home node's path report during initial
NETCP startup, or while starting some network specific protocols for a
LAN, GATEHALF or ROUTER network because a :NETCONTROL
command was issued, NETCP successfully read path report data 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: BUFFER MANAGER; Buffer manager error
682 CLAS0002 CAUSE: While reading X25 configuration data because a :NETCONTROL
command was issued, NETCP successfully read X25 data 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 stopped trying to load additional X25 data; some
required data may not have been loaded, but startup of that network
probably continued. Some or all X25 nodes may not be accessible.