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

334 Chapter19
Logging Location Codes
Control Process Logging Location Codes
ACTION: This error in itself was not fatal, and shutdown continued.
However, the NMCONFIG file may be inaccessible. If the problem
occurs repeatedly, see Appendix A, “Submitting an SR,” of this manual.
MESSAGE: INTERNAL ERROR; Bad/unknown port message
84 CLAS0002 CAUSE: A message with an unrecognized function code was received on
the NETCP port while NETCP was idle and waiting for new commands
(PARM = the 16-bit unknown message function code).
ACTION: The message was ignored and NETCP went back to waiting
for the next new command. However, some other modules on the system
are still waiting for the message exchange that mistakenly went to
NETCP, and this could cause problems in those other modules. If disk
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: INTERNAL ERROR; Write aborted by link
101 CLAS0002 CAUSE: NETCP received an asynchronous event message from the
DCLDM indicating that, in addition to some other error, one or more
queued outbound write operations were aborted by the LAPB PSI
driver (PARM = 16-bit internal ldev number of device whose writes
were aborted). This error is always preceded by another asynchronous
link error (for example, errors 257 and 259) indicating the original
cause of the failure that resulted in the aborts.
ACTION: None; this is an informative message only, and only serves to
indicate that queued outbound data was not sent when the error
occurred. Additional information may be gained by enabling logging
classes 10 and 12 for link subsystem 28 (LAPB) and class 0 for
subsystem 4 (DCLDM), then reproducing the problem. If this does not
reveal the cause, see Appendix A, “Submitting an SR,” of this manual.
MESSAGE: INTERNAL ERROR; Trace
106 CLAS0002 CAUSE: After successfully disabling tracing for an entity at the
Transport level, NETCP encountered an error trying to stop it at the
NMS subsystem level (PARM = 32-bit status returned by the call to
nmclosetrace).
ACTION: This error was not fatal, and NETCP continued running.
However, the trace file may not have been closed, and thus would not be
available for access until after the next system restart. If the problem
occurs every time, see Appendix A, “Submitting an SR,” of this manual.
MESSAGE: INTERNAL ERROR; Trace
118 CLAS0002 CAUSE: While attempting to enable tracing for an entity, NETCP
encountered an error attempting to get a trace ID from the NMS
subsystem (PARM = 32-bit status returned by the call to
nmgettraceid).