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

Chapter 21 525
Logging Location Codes
Control Process Logging Location Codes
new autodial connections cannot be established, and sessions which
attempt it may hang. To clear this condition, first try a :NETCONTROL
DELLINK=linkname; NET=niname command against the affected link,
followed by a :NETCONTROL ADDLINK=linkname; NET=niname. If this
does not help, a system restart will probably be required to clear the
hang. If the problem occurs again, take a dump when the first error 669
is reported and before any attempts to recover, and see Appendix A ,
“Submitting a CR.”
670 CLAS0002 MESSAGE: Bad status
CAUSE: While bringing down a device because of a serious
asynchronous error, powerfail, or a :NETCONTROL DELLINK command,
NETCP encountered an error trying to send a Path Verify message to
the UDP protocol module (PARM = 32-bit status returned by the call to
send_msg). The message was to have told UDP to discard cached paths.
ACTION: In this case UDP will continue to function, but may be unable
to reach some destinations. If you cannot reach needed UDP
destinations then you will need to restart Transport. This is not
generally a fatal error, however some versions of Transport may
accidentally hang if this error appears. If the problem occurs
repeatedly, see Appendix A , “Submitting a CR.”
671 CLAS0002 MESSAGE: INTERNAL ERROR; Internal resource error
CAUSE: During startup of the SNMP module, the configuration file was
unlocked. But afterwards, NETCP tried for up to 2 minutes to lock the
file again without success (PARM = status from NMConflockfile). The
2-minute timeout is not configurable.
ACTION: Network startup was incomplete. Stop the network. Use
:LISTF NMCONFIG.PUB.SYS,3 to verify the NMCONFIG file exists and
is not opened. If any users are currently running NMMGR, ask them to
exit. Then restart the network. If the problem persists, see Appendix A ,
“Submitting a CR,” of this manual.
673 CLAS0002 MESSAGE: INTERNAL ERROR; Device close
CAUSE: While bringing down a device because of a serious
asynchronous error, powerfail, or a :NETCONTROL DELLINK command,
NETCP encountered an error when attempting to separate one of the
active protocols from the link driver (PARM = 32-bit status returned by
the call to ns_separate_from_driver).
ACTION: This in itself was not a fatal error, and other device stop
actions continued. However, either the DCLDM or the link driver may
have failed, which indicates a problem. No additional NETCP logging
or tracing information is available, though if problems continue,
DCLDM tracing and link tracing can be used to either follow the
separate request downward and locate the point where errors occur. If
the problem persists, see Appendix A , “Submitting a CR,” of this
manual.