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

526 Chapter21
Logging Location Codes
Control Process Logging Location Codes
674 CLAS0002 MESSAGE: INTERNAL ERROR; Wrong autodial cable OUTBOUND;
occupied
CAUSE: NETCP received an asynchronous event message from the
DCLDM indicating that its LAPB PSI’s autodial operation was not
completed, because the cable attached to the PSI card is not the proper
cable required for autodial operations (PARM = 16-bit internal ldev
number of the device). Older versions of Transport may print different
messages for this error, such as “OUTBOUND; occupied” or
“INTERNAL ERROR; Auto dial failure”, though the actual problem is
the cable.
ACTION: Install the correct cable and retry the operation. If the
problem persists then see Appendix A , “Submitting a CR,” of this
manual.
677 CLAS0002 MESSAGE: Bad status
CAUSE: While awaiting Path Verify replies from all general protocols in
response to requests sent previously, NETCP received a new message
on the control or reply subqueues of its port, which was not one of the
expected replies. NETCP then encountered an error while trying to
requeue that request for later processing, by resending it to itself
(PARM = 32-bit status returned by the call to send_msg).
ACTION: The new request message has probably been lost, and
depending on the purpose of message, whatever module sent it may be
expecting a reply which will never come, so that module or session may
now be hung. For debugging purposes the message content was logged
in the NM logfile along with this error, which may aid in debugging any
hung modules. Check for other errors, and also check for Path Verify
storms by first enabling Class-5 Transport console logging in
NMCONFIG, then restarting Transport and retrying the operations.
Depending on the meaning of the error status PARM, the NETCP port
may have run out of message frames, in which case a system failure
may occur soon, though stopping and restarting Transport may be
possible, and may clear the problem until next time. See Appendix A ,
“Submitting a CR,” of this manual.
678 CLAS0002 MESSAGE: INTERNAL ERROR; Bad/unknown port message
CAUSE: While awaiting Path Verify replies from all general protocols in
response to multiple requests it sent previously, NETCP received a new
message on the reply subqueue of its port that either was not a reply or
whose length was not right for a reply (PARM.(0:16) = function code and
PARM.(16:16) = interface code of received message).
ACTION: This error may be followed by a timeout of up to 15 seconds,
which is normal. Possibly some module on the system sent a message to
the wrong place, and because whatever module sent it could be
expecting a reply which will never come, that module may now be hung.
Possibly one of NETCP’s previous reply waits timed out, but the
offending module has now decided to reply. For debugging purposes the