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

Chapter 21 493
Logging Location Codes
Control Process Logging Location Codes
280 CLAS0002 MESSAGE: INTERNAL ERROR; Configuration file error
CAUSE: While processing a :NETCONTROL command to start or update a
network or add a link, NETCP was unable to open the NMCONFIG file
(PARM = 32-bit status returned by the call to nmconfopen).
ACTION: The command did not execute. Check that the NMCONFIG
file exists and is not already opened by some other user, such as
someone running NMMGR. If this is not the problem and the message
persists, see Appendix A , “Submitting a CR,” of this manual.
281 CLAS0002 MESSAGE: INTERNAL ERROR; Internal resource error
CAUSE: NETCP received a dial request message but the entity whose
reply port was in the message was not one of the network specific
protocols known to NETCP for this NI (PARM = 0).
ACTION: Some entity other than DIAL may be attempting dial requests.
See Appendix A , “Submitting a CR,” of this manual.
282 CLAS0003 MESSAGE: Device Startup Warning
CAUSE: An attempt to physically start a device was successful, but
returned a positive status meaning some sort of unexpected warning
occurred (PARM = 32-bit status returned by the call to nslopenlink).
ACTION: None. This is an informative error message, and exists for
pre-5.0 systems only. If you want more information, try enabling
additional logging for the link subsystem corresponding to the type of
NI for the network reporting the warning, then reproduce the message.
If this still does not reveal the cause, see Appendix A , “Submitting a
CR,” of this manual.
283 CLAS0003 MESSAGE: Device Shutdown Warning
CAUSE: An attempt to physically stop a device failed with a positive
nonzero status meaning an unexpected warning (not an error) 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 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