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

494 Chapter21
Logging Location Codes
Control Process Logging Location Codes
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 a CR,” of this manual.
284 CLAS003 MESSAGE: Device restarting
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.
285 CLAS0003 MESSAGE: INTERNAL ERROR; NM Entry
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 a CR,” of this manual.
286 CLAS0003 MESSAGE: INTERNAL ERROR; NM Entry
CAUSE: Near the end of NETCP’s early initial startup, it was unable to
put its port number into a new entity named “NetCP” in the NS
Registry (PARM = 32-bit status returned by the call to
reg_add_entity).
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 (see error 285), or the Registry may be full. If
the message occurs every time, see Appendix A , “Submitting a CR,” of
this manual.