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

484 Chapter21
Logging Location Codes
Control Process Logging Location Codes
protocols. This message does not imply that Transport is completely
down, nor does it imply successful shutdown, only that there is very
little cleanup left to do. It is possible that another instance of Transport
can be successfully started before this message appears.
54 CLAS0002 MESSAGE: INTERNAL ERROR; Device close
CAUSE: An attempt to physically stop a device failed with a negative
nonzero status meaning an unexpected error (not a warning) occurred
(PARM = 32-bit status returned by the call to nslcloselink). Physical
stop includes all shutdown and deletion of a link driver and its
dependent modules and any connections to the NMS subsystem or the
operating system, reset of link hardware, plus optional deletion of a
DCLDM, so any error along the way will be detected here by NETCP.
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 283).
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 a CR,” of this manual.
58 CLAS0002 MESSAGE: INTERNAL ERROR; Configuration file error
CAUSE: At the beginning of NETCP shutdown due to a system
shutdown, a :NETCONTROL STOP command, or an error during initial
startup, NETCP encountered an error trying to close the NMCONFIG
file it had previously opened (PARM = 32-bit status returned by the call
to nmconfclose).
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 a CR,” of this manual.