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

Chapter 19 379
Logging Location Codes
Control Process Logging Location Codes
encountered an error trying to read other data entries to match up to
the first one (PARM = 32-bit status returned by the call to
bmgr_read_buffer).
ACTION: The current matching operation stopped, then more merging
of X25 mappings may have continued, possibly causing more errors,
then the bad configuration data was passed to the X25 protocol module.
The X25 network will probably not operate correctly now. Because
NETCP already wrote to the buffer, it should have also been able to
read from it; since it already read once, this indicates a probable bug in
NETCP. 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
686 CLAS0002 CAUSE: After successfully opening the NSDIR network directory file,
while preparing to read X25 network directory information from the
file, NETCP was unable to obtain a buffer from its own buffer pool large
enough to hold the maximum possible number of X25 mapping entries
(PARM = 32-bit status returned by the call to bmgr_get_buffer). The
size of the buffer NETCP tried to obtain was based on the size of the
mapping table, a value which was obtained from a hidden field in the
NI record of the NMCONFIG file.
ACTION: No network directory data was read, and NETCP attempted
to recover and close the opened file. Some versions of transport may
then attempt to build X25 mappings, even though no buffer was
obtained, and send a restart message to X25. After the error, network
startup may continue to completion, but the resulting network will
probably not operate correctly. Verify you have all the required patches,
especially a coherent set of patches required to support 2048 X25 SVC
paths under NMMGR and NS Transport. Also verify that the number of
X25 paths configured in the NMCONFIG file is within the supported
limits. If the problem still cannot be found, see Appendix A,
“Submitting an SR,” of this manual.
MESSAGE: INTERNAL ERROR; Internal resource error
688 CLAS0002 CAUSE: While starting or updating a ROUTER network, because a
:NETCONTROL command was issued, NETCP successfully started a
LAPB link device, then encountered an error trying to read information
from the NMCONFIG file about the number of mappings in that NI,
prior to actually loading the mappings (PARM = 32-bit status returned
by the call to nmconf3soninfo).
ACTION: No mapping entries were read, and though network startup
probably continued to completion without a command error, you will
not be able to connect to any remote nodes configured in the mapping
entries. Verify you have a coherent set of patches installed, especially
between Transport and NMMGR, and especially if your NMCONFIG
file contains a large number of ROUTER mappings. Try stopping and
restarting the network. If the problem persists, you may have a