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

374 Chapter19
Logging Location Codes
Control Process Logging Location Codes
ACTION: The second error in itself was not fatal, and Transport should
continue to run. However, ifthe sessionwhich issued the :NETCONTROL
STATUS command still exists, that session will now be hung. If the
session does not exist, this also indicates a bug since supported HP
commands to abort the session should have been disabled by NETUI. A
system restart will be required to clear the session's hang. If the session
is on the system console, a :CONSOLE command may be attempted to
temporarily move the logical console to another terminal until a system
restart is convenient. If the problem persists, issue a :NETCONTROL
TRACEON=MHDSBN command beforehand, to enable NETCP tracing
which may capture the problem. When the problem occurs, issue a
:NETCONTROL TRACEOFF command from another terminal, then take a
system dump and send in the dump and the resulting trace file; see
Appendix A, “Submitting an SR,” of this manual.
MESSAGE: Bad status
669 CLAS0002 CAUSE: While processing a request sent by the DIAL protocol module
because a LAPB autodial link is being connected, NETCP encountered
some kind of error (such as errors 315, 316, 322), then encountered a
second error trying to send the bad reply message back to DIAL to
report the first error (PARM = 32-bit status returned by the call to
send_msg).
ACTION: Since DIAL never received its reply, it may take up to 30
minutes for DIAL to time out and reset itself, and during this delay,
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 “Submitting
an SR” in appendix A of this manual.
MESSAGE: Bad status
670 CLAS0002 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 an SR,” of this manual.
MESSAGE: INTERNAL ERROR; Internal resource error