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

Chapter 19 343
Logging Location Codes
Control Process Logging Location Codes
ACTION: This problem in itself was not fatal, and link shutdown
continued. However, there may be a problem with the link driver
software or hardware.
Most shutdown problems are warnings, not errors (see error 54).
Usually the link driver failed to release a resource, possibly due to a
previous error, or the link hardware failed to stop in an orderly manner
resulting in a driver or module configurator timeout or other problem,
or an attempt to close logging resulted in a warning which was
incorrectly reported as an error. If the link hardware is suspect, use
SYSDIAG to check it. For X25 networks, verify the X25 switch has not
failed.
If you wish to pursue the cause further, stop Transport and enable all
available logging for the link subsystem corresponding to the NI type of
the network reporting the error, then restart and stop the same
network again to reproduce the problem, monitoring logged data for
any problems. If this does not reveal the cause, link tracing may be
attempted on the affected link to collect even more data, though
because the device is shutting down, keep in mind the system may
automatically stop the tracing before the point at which the problem is
detected.
If the problem persists after investigating all these causes, see
Appendix A, “Submitting an SR,” of this manual.
MESSAGE: Device restarting
284 CLAS003 CAUSE: NETCP received an asynchronous event message from the
DCLDM indicating that its LAPB PSI link received a second SABM
frame after a connection was already established, meaning the link has
connected again (PARM = 0).
ACTION: None. This is an informative error message only, of interest to
operators who wish to know when new connections occur. Handling a
second SABM is a normal part of the LAPB protocol.
MESSAGE: INTERNAL ERROR; NM Entry
285 CLAS0003 CAUSE: During NETCP’s early initial startup, immediately after
attempting to create the NS Registry, NETCP was unable to add
Transport’s subsystem number to it (PARM = 32-bit status returned by
the call to reg_add_subsys).
ACTION: This error was not fatal, and startup continued; use of the
Registry here is not critical. However, creation of the NS Registry by
NETCP may have failed, in which case all subsequent calls to it will
also result in errors being logged. If this message occurs every time, see
Appendix A, “Submitting an SR,” of this manual.