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

350 Chapter19
Logging Location Codes
Control Process Logging Location Codes
MESSAGE: Overwrote X25 Addr/DDN
411 CLAS0003 CAUSE: While collecting configuration data for startup of an X25
network, NETCP found that a user had specified an X25 address for a
remote node was on a DDN Network, but had also supplied the actual
address. Instead, the X25 address should be derived from the IP
address by the Transport code (PARM = 0).
ACTION: Verify that the network interface started is actually for a
DDN Network. If the network is DDN, no action is required, since all
configured X25 addresses will be ignored. If not, reconfigure the DTC
(using the DTC manager), then stop and restart the network NI on the
host. This error message is only printed once per startup, even if
multiple X25 addresses have this problem.
MESSAGE: INTERNAL ERROR; Internal resource error
412 CLAS0002 CAUSE: NETCP received an unrecognized message on port subqueue 2
or 4, which are only designed for asynchronous event messages (PARM
= first 16 bits of message, which should give the message type.) NETCP
was expecting either a DCLDM event message (type 340) or an SDI
async event message (type 390)
ACTION: This error in itself was not fatal, and NETCP continued
operating. However, some other modules on the system may still be
waiting for a message exchange that mistakenly went to NETCP, and
this could cause problems in those other modules. If disc logging was
enabled, NETCP logged the entire received message to the current NM
logfile, which may aid in diagnosis. It may not have been a Transport
message at all. If necessary, see Appendix A, “Submitting an SR,” of this
manual.
MESSAGE: BUFFER MANAGER; Buffer manager error
413 CLAS0002 CAUSE: While collecting configuration data for startup of an X25
network, NETCP successfully obtained a buffer to hold the data, but
later on was unable to write data into that buffer (PARM = 32-bit status
returned by the call to bmgr_write_buffer).
ACTION: Not all the configuration data was collected, and startup of
that network failed. 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.
If the problem still cannot be isolated, see Appendix A, “Submitting an
SR,” of this manual.
MESSAGE: INTERNAL ERROR; Internal resource error
414 CLAS0002 CAUSE: NETCP received an asynchronous DCLDM event message, but
the device number in the message did not correspond to any known
device in NETCP’s tables (PARM = 16-bit internal ldev number from
the message).