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

Chapter 21 499
Logging Location Codes
Control Process Logging Location Codes
driver, through the DCLDM (PARM = 32-bit adjusted status returned
by the call to xp_connect_the_driver: add decimal 256 to get the
actual status).
ACTION: This event may follow a previous asynchronous link error,
which may indicate the original problem. Another possibility is that the
DCLDM or LAPB driver are hung. Also check the validity of the phone
number in the configuration. If the situation continues, additional
information may be gained by enabling logging classes 10 and 12 for
link subsystem 28 (LAPB), and class 0 for subsystem 4 (DCLDM). If
this still does not reveal the problem, see Appendix A , “Submitting a
CR,” of this manual.
322 CLAS0003 MESSAGE: INTERNAL ERROR; Dial
CAUSE: While processing a legal dial request message, NETCP found
that the link was already closed, due to system timing conditions
(PARM = adjusted LAPB status).
ACTION: This is an informative error message only. Attempt to dial out
again if necessary.
401 CLAS0003 MESSAGE: 2 IP adr for 1 adr key
CAUSE: While collecting configuration data for startup of an X25
network, NETCP found two IP addresses mapping to the same X25
address key (PARM = 0).
ACTION: This error in itself was not fatal, and collection of the X25 data
continued. The logging does not tell which address was involved. You
may wish to run NMMGR and inspect the X25 configuration data for
mistakes.
404 CLAS0002 MESSAGE: BUFFER MANAGER; Buffer manager error
CAUSE: An attempt to create a frozen inbound buffer pool for a
particular NI device failed (PARM = 32-bit status returned by the call
to bmgr_create_pool). Always followed by another error indicating
whether LAPB (see error 407) or non-LAPB (see error 619) pool
creation was being attempted.
ACTION: The NI did not start. Check the packet size configured in the
NMCONFIG file. For LAPB links, pool creation parameters are
obtained from this file, but other link types have a more complex
process for determining packet size. Depending on the error, it is
possible too much frozen memory is being used by the system, but this
can change with time. Use GLANCEXL or a similar utility to check
memory usage by the system. If these are not the causes and the
problem persists even if retried after a suitable waiting period, see
Appendix A , “Submitting a CR,” of this manual.
406 CLAS0003 MESSAGE: INTERNAL ERROR; NM Entry
CAUSE: While creating a frozen inbound buffer pool for a particular NI