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

Chapter 19 401
Logging Location Codes
Dial ID Logging Location Codes
ACTION: It is possible that if the remote node is heavily congested the
queue element can be deleted before the late packet arrives. This can be
considered normal. If the problem does not appear to be related to this
then see Appendix A, “Submitting an SR,” of this manual.
MESSAGE: None
55 CLAS0002 CAUSE: The sequence number of an ack-ack packet does not match
sequence number sent in the acknowledgment packet. Either the
ack-ack packet has been corrupted or the remote node is not
responding correctly to the Dial ID acknowledgment packet (PARM =
sequence number received in the ack-ack message).
ACTION: See Appendix A, “Submitting an SR,” of this manual.
MESSAGE: None
56 CLAS0002 CAUSE: An ack-ack packet was received but the Dial ID protocol was
not in the correct internal state to receive an ack-ack (PARM = state of
the Dial IP protocol).
ACTION: See Appendix A, “Submitting an SR,” of this manual.
MESSAGE: None
76 CLAS0002 CAUSE: Dial attempted to start a retransmission timer while one was
still pending.
ACTION: None.
MESSAGE: None
82 CLAS0002 CAUSE: A call to BFMSHAREBUF failed.
ACTION: None.
MESSAGE: None
83 CLAS0003 CAUSE: Dial is processing either a duplicate request (PARM = 0) or a
simultaneous request (PARM = $4000).
ACTION: None. Informational only.
MESSAGE: None
84 CLAS0003 CAUSE: Dial is processing a duplicate request, and no reply has been
received from the original request.
ACTION: None. Informational only.
MESSAGE: None
85 CLAS0002 CAUSE:
A call to BFMGETBUF failed when attempting to get an outbound
buffer for a request packet (PARM = result of BFMGETBUF).
ACTION: See Appendix A, “Submitting an SR,” of this manual.