Dial ID Logging Location Codes

CAUSE: A port message was received containing an invalid function code (PARM = function code).

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Dial ID protocol started.

ACTION: Informational message.

CAUSE: The room allocated for the node name and path report is too small (PARM = required number of bytes needed).

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: The packet received was not a valid Dial ID message type. The packet is discarded (PARM = message type of received packet).

ACTION: Enable data trace for the Dial ID protocol when this log message is generated. See Appendix A “Submitting an SR ” of this manual.

CAUSE: The sending of a 'dial' message to the Control Process using DICTSEND failed (PARM = result code of DICTSEND call).

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Dial ID protocol stopped.

ACTION: Informational message.

CAUSE: A port timer message was received with no matching request (PARM = timer request ID).

ACTION: Informational message.

CAUSE: Retransmission has occurred (PARM = index of device over which retransmission has occurred).

ACTION: Informational message.

CAUSE: The sending of a link shut message to the Control Process using DICTSEND failed (PARM = result code of DICTSEND call).

ACTION: Informational message.

CAUSE: The status returned from the Control Process attempting to download the phone number to the device (PARM = result of NMLINKDIAL call).

ACTION: Verify that the phone number is correct in the configuration file. See Appendix A “Submitting an SR ” of this manual.

CAUSE: A port message was received on the timer subqueue but was not a timer message (PARM = function code of received message).

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: The maximum number of retransmissions has occurred over a link (PARM = index of the device that retransmission had occurred).

ACTION: Verify why the remote node is not responding to the Dial ID packets. It is also possible that the remote node could be so congested that either the number of retransmissions or the retransmission interval configured for the Dial ID protocol is too short. Increase one of these values if the problem persists.

CAUSE: A Dial ID transaction has been initiated over a device from the local node (PARM = index of the device).

ACTION: Informational message.

CAUSE: A Dial ID transaction has completed over a device (PARM = completion code and index of the device). The completion code is contained in the 4 upper bits of the PARM. (Completion codes are: (0) successful completion; (1) Retries exhausted; (3) PDX'NAME'CACHE failed; (5) Request rejected by either the local or remote node; (6) internal error. The index of the device is contained in the lower 12 bits).

ACTION: Informational message.

CAUSE: A remote node is attempting connection and has failed because of one of the following reasons: (1) There is no mapping entry configured for the node attempting connection on a particular device; (2) There is a dial request outstanding to a node with a different IP address than the one attempting connection. A reply rejecting the request is sent to the remote node.

ACTION: Verify that there is a valid mapping entry in the configuration file for the remote node.

CAUSE: A remote node is attempting connection and the network number of its IP address does not match the network number of the network interface over which the Dial ID protocol is active. A reply rejecting the request is sent to the remote node.

ACTION: Reconfigure either the remote node or local node so that the network number of their IP addresses match. It is also possible that the remote node is calling the wrong phone number, therefore getting routed to the wrong link and network interface.

CAUSE: A packet was received that did not contain a correct value for the version in the Dial ID header (PARM = version of received packet).

ACTION: Verify that the remote node has Dial ID configured for its link and is sending valid Dial ID packets. If the problem persists, enable data trace for the Dial ID protocol while this log message is generated. See Appendix A “Submitting an SR ” of this manual.

CAUSE: Two nodes are initiating connection over a link simultaneously but the IP address of the remote is not what the local node expected. A reply rejecting the request is sent to the remote node.

ACTION: Initiate the connections either over separate links or at separate times.

CAUSE: A Dial ID transaction has been initiated over a device from a remote node (PARM = index of the device).

ACTION: Informational message.

CAUSE: The IP address of the remote node did not match the IP address that the local node intended to call (PARM = low word of IP address of the remote node). An acknowledgment rejecting the reply is sent to the remote node (PARM = result of BFMREADEBUF).

ACTION: Verify that the local node is using the correct link for the intended remote node and verify that the IP address in the mapping entry is correct.

CAUSE: The sequence number of a reply packet sent from a remote node does not match sequence number sent in the request packet sent from the local node. Either the reply packet has been corrupted or the remote node is not responding correctly to the Dial ID request packet (PARM = sequence number received in the reply message)

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: A reply packet was received but the Dial ID protocol was not in the correct internal state to receive a reply (PARM = state of the Dial ID protocol).

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: A remote node is attempting connection and the network number of its IP address does not match the network number of the network interface over which the Dial ID protocol is active. An acknowledgment rejecting the reply is sent to the remote node.

ACTION: Reconfigure either the remote node or local node so that the network number of their IP addresses match. It is also possible that the local node is calling the wrong phone number, therefore getting routed to the wrong link and network interface.

CAUSE: The status field in a Dial ID reply packet was non-zero, meaning the remote node has rejected the local node's request packet (IE. rejected the connection attempt). (PARM = reason for rejection: (1) The security string was invalid; (2) Format of the packet is bad; (3) The IP addresses contained in the Path Report was invalid; (4) Rejected for unknown reasons).

ACTION: Based upon the PARM value, verify that the configuration is correct. It may be helpful to find the matching log message on the remote node that prompted the rejection.

CAUSE: The status field of a Dial ID acknowledgment packet was non-zero, meaning the remote node has rejected the local node's reply packet (i.e., rejected the connection attempt). (PARM = reason for rejection: (1) The security string was invalid; (2) Format of the packet is bad; (3) The IP address contained in the Path Report was invalid; (4) Rejected for unknown reasons).

ACTION: Based upon the PARM value, verify that the configuration is correct. It may be helpful to find the matching log message on the remote node that prompted the rejection.

CAUSE: An acknowledgment packet was received but the Dial ID protocol was not in the correct internal state to receive an ack (PARM = state of the Dial ID protocol)

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: The sequence number of an acknowledgment packet does not match sequence number sent in the reply packet. Either the acknowledgment packet has been corrupted or the remote node is not responding correctly to the Dial ID reply packet (PARM = sequence number received in the ack message)

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Dial ID is logging statistics prior to its port termination.

ACTION: Informational message.

CAUSE: There is no matching internal Dial ID queue element for the device in which an acknowledgment packet was just received (PARM = index of device).

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.

CAUSE: There is no matching internal Dial ID queue for the device in which a reply packet was just received (PARM = index of device).

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 ” at the beginning of this manual.

CAUSE: A call to the internal procedure PDX'NAME'CACHE failed.

ACTION: None.

CAUSE: The security string contained in the remote node's reply packet does not match any of the strings configured at the local node.

ACTION: Verify that the security string configured under the Dial ID protocol at the local node matches the one sent by the remote node.

CAUSE: The security string contained in the remote node's request packet does not match any of the strings configured at the local node.

ACTION: Verify that the security string sent by the remote node matches one in the list of security strings configured under the Dial ID protocol at the local node.

CAUSE: A duplicate (retransmitted) request packet has been received, but the sequence number of the packet does not match the sequence number of the previous request packet. The packet is discarded (PARM = sequence number contained in the duplicate packet).

ACTION: Either the packet was corrupted in transit or the remote node is not transmitting packets correctly. If thought to be the latter case see Appendix A “Submitting an SR ” of this manual.

CAUSE: The Dial ID protocol has detected that the configured link size is too small for the largest packet that may be sent by Dial ID (PARM = smallest link size acceptable to Dial ID in octal).

ACTION: Reconfigure so that the link is larger than the value contained in the PARM.

CAUSE: A duplicate (retransmitted) request packet has been received while two nodes are attempting connection simultaneously, but the sequence number of the packet does not match the sequence number of the previous request packet. The packet is discarded (PARM = sequence number contained in the duplicate packet).

ACTION: Either the packet was corrupted in transit or the remote node is not transmitting packets correctly. If thought to be the latter case see Appendix A “Submitting an SR ” of this manual.

CAUSE: A port message was received on the getbuf reply subqueue but was not a getbuf reply message (PARM = function code of received message).

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: There is no matching internal Dial ID queue element for the device in which an ack-ack packet was just received (PARM = index of device).

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.

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.

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.

CAUSE: Dial attempted to start a retransmission timer while one was still pending.

ACTION: None.

CAUSE: A call to BFMSHAREBUF failed.

ACTION: None.

CAUSE: Dial is processing either a duplicate request (PARM = 0) or a simultaneous request (PARM = $4000).

ACTION: None. Informational only.

CAUSE: Dial is processing a duplicate request, and no reply has been received from the original request.

ACTION: None. Informational only.

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.

CAUSE: Dial is entering the TIME WAIT state after a normal ack-ack message.

ACTION: None. Informational only.

CAUSE: A link failure occurred, and Dial is cleaning up the resources (PARM = status).

ACTION: None. Informational only.

CAUSE: A call to BFMGETBUF failed when attempting to get an outbound buffer for a reply packet (PARM = result of BFMGETBUF).

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: A call to BFMGETBUF failed when attempting to get an outbound buffer for an acknowledgment packet (PARM = result of BFMGETBUF).

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: A call to BFMGETBUF failed when attempting to get an outbound buffer for an ack-ack packet (PARM = result of BFMGETBUF).

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: The Dial ID protocol has waited for approximately five minutes for transmission of a packet. The connection attempt is aborted.

ACTION: If the link is a manual dial link, then the operator probably never dialed the phone or replied to the console request. If the link is an autodial link, then there could be failure with the autocall unit or the remote node is not answering the phone.

CAUSE: Received an inbound dial request for a route that is already connected.

ACTION: None.

CAUSE: Timer expired but no matching queue element could be found.

ACTION: None.

CAUSE: Received a CP reply message after the start request timer has expired.

ACTION: None.

CAUSE: MAP_CM_DIAL_INBOUND call failed with a MAP internal error. The MAP result code is in the parm field.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: MAP_CM_DIAL_INBOUND call failed with an unknown error code. The error code is in the parm field.

ACTION: See Appendix A “Submitting an SR ” of this manual.