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

488 Chapter21
Logging Location Codes
Control Process Logging Location Codes
ACTION: None. This is an informative message only. IPU will use
information in the message to update its tables.
171 CLAS0002 MESSAGE: BUFFER MANAGER; Buffer manager error
CAUSE: While attempting to collect current address configuration data
from NMCONFIG because an X25 network was either starting or being
updated, NETCP was unable to obtain a logical buffer from its own pool
to hold all the X25 information (PARM = 32-bit status returned by the
call to bmgr_get_buffer).
ACTION: Check the configuration file using NMMGR, to see that the
amount of X25 configuration data seems to be within limits. Also verify
your system has any and all software patches that may be needed to
use the amount of X25 configuration data you are specifying, especially
if you configuration contains more than 1024 X.25 paths. If the problem
still cannot be isolated, the NMCONFIG file may be corrupt, or there
may be a bug in NETCP or the NMS subsystem; see Appendix A ,
“Submitting a CR,” of this manual.
222 CLAS0002 MESSAGE: PACKET DISCARD; Allowable max exceeded
CAUSE: While configuring a GATEHALF or a ROUTER network
mapping entry, NETCP was unable to find free space in a global array
to hold another new phone number (PARM = maximum phone numbers
per system, in hex).
ACTION: Even after attempting to eliminate duplicate phone numbers,
no free cells were available for an additional number; all entries appear
to be in use. If phone numbers have been changed via :NETCONTROL
UPDATE, stop and restart the network, stop any started ROUTER or
GATEHALF networks that are not needed, or decrease the number of
unique phone numbers configured in the
NETXPORT.NI.niname.MAPPING.entryname paths of your NMCONFIG
file. Depending on the version of Transport you are running, the
maximum number of unique phone numbers is either 1024 or 4096 for
the whole system, and the per-NI limit is either 256 or 1024
respectively.
232 CLAS0002 MESSAGE: BUFFER MANAGER; Buffer manager error
CAUSE: While attempting to build a DCN start message for IPU
because of a network start, a :NETCONTROL ADDLINK command, or an
X25 auto restart, NETCP was unable to obtain a buffer from its own
pool to hold alias list information (PARM = 32-bit status returned by
the call to bmgr_get_buffer).
ACTION: Though no DCN message was sent, network startup probably
continued to completion, but connections over the affected network may
not work. Probably all the NETCP buffers have somehow been used up,
though it should have allowed for enough to support starting any
supported network configuration. Stop Transport and use NMMGR to
validate the NMCONFIG file and check for obvious file corruption, then