NI Logging Location Codes

CAUSE: Device was idle for configured Idle Timeout and timer was enabled for this device. Device will be disconnected (PARM = device ldev).

ACTION: None.

CAUSE: Protocol ID in Protocol Stop message was not found in NI's PID table (PARM = Protocol ID).

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

CAUSE: PID table is too small for the number of protocols being started for this NI (PARM = Protocol ID which could not be started).

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

CAUSE: CP asked NI to stop a device which NI could not locate in its device tables (PARM = device ID).

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

CAUSE: Device table is too small for the number of devices being started for this NI, or a device was started twice by CP (PARM = Device ID).

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

CAUSE: NI received data on a Protocol ID which has no match in PID table (PARM = Protocol ID).

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

CAUSE: Dial Protocol owns the device, but another protocol was sent data from the remote node (PARM = Violating Protocol ID).

ACTION: If this happens frequently, carefully check the configurations on both the local and remote systems. See Appendix A “Submitting an SR ” of this manual.

CAUSE: On arrival of inbound data, a send_msg to the upper layer protocol failed (PARM = status from send_msg).

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

CAUSE: The NI received an inbound data message from a device that is not in the device table for this NI (PARM = LDEV).

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

CAUSE: A bad or unexpected message was received by the NI (PARM = Message Function Code).

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

CAUSE: While trying to send outbound loopback data back, a send_msg failed (PARM = status from send_msg).

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

CAUSE: While trying to send outbound data to a router driver via DC/LDM, a send_msg failed (PARM = status from send_msg).

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

CAUSE: Transport sent outbound data to NI for a Protocol ID which has no match in the PID table for this NI (PARM = Protocol ID).

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

CAUSE: While attempting to send outbound data, NI discovered the route ID in the message was out of date, so the outbound packet was discarded (PARM = route ID from route table).

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

CAUSE: A protocol other than PROBE attempted to send a multicast packet, disallowed by the NI (PARM = Protocol ID).

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

CAUSE: The protocol attempted to send data when no devices were active (PARM = Protocol ID).

ACTION: Error should be preceded by other errors or a DELLINK message. If not, see Appendix A “Submitting an SR ” of this manual.

CAUSE: Network Interface Started (PARM = NI port data address).

ACTION: None.

CAUSE: Network Interface Stopped (PARM = NI port data address).

ACTION: None.

CAUSE: Trouble starting the idle device timer of the NI (PARM = status from get_timer).

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

CAUSE: While trying to send a connect request to a driver, a send_msg failed (PARM = status from send_msg).

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

CAUSE: CP asked NI to disconnect a device which NI could not find in its device table (PARM = connect ID).

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

CAUSE: While trying to send a disconnect request to a driver, a send_msg failed (PARM = status from send_msg).

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

CAUSE: CP asked NI to connect a device which NI could not find in its device table (PARM = link ID).

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

CAUSE: After receiving a connect confirmation event from a driver, NI could not find the protocol for that device type, either X.25 or SNA, in its PID table.

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

CAUSE: After receiving a connect confirmation event from a driver, send_msg failed trying to forward a similar message to the protocol (PARM = status from send_msg).

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

CAUSE: A driver acknowledged disconnection of a link which NI could not find in its tables (PARM = Protocol ID).[

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

CAUSE: After receiving a disconnect confirmation event from a driver, NI could not find the protocol for that device type, either X.25 or SNA, in its PID table.

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

CAUSE: After receiving a disconnect confirmation event from a driver, send_msg failed trying to forward a similar message to the protocol (PARM = status from send_msg).

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

CAUSE: After receiving a connect reply from a driver, send_msg failed trying to forward a similar message to the sender of the original connect (PARM = status from send_msg).

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

CAUSE: After receiving a disconnect reply from a driver, NI could not locate information about the original request in its tables (PARM = message ID).

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

CAUSE: After receiving a disconnect reply from a driver, send_msg failed trying to forward a similar message to the sender of the original disconnect (PARM = status from send_msg).

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

CAUSE: While trying to send outbound data to a driver, send_msg failed (PARM = status from send_msg).

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

CAUSE: NI received inbound data from a driver, for a link which NI could not find in its tables (PARM = link ID).

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

CAUSE: While processing inbound data from a driver, send_msg failed trying to forward the data to the protocol (PARM = status from send_msg).

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

CAUSE: CP asked NI to connect a device which NI could not find in its device table (PARM = device ID).

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

CAUSE: When attempting to create a free pool of device and protocol entries, new_create_table failed (PARM = status from new_create_table).

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

CAUSE: When attempting to create a table to hold information about outstanding X.25 requests, new_create_table failed (PARM = status from new_create_table).

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

CAUSE: While processing inbound data from a driver, NI was able to locate the input device in its device table, but then could not locate the corresponding protocol in the protocol table.

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

CAUSE: Bad or unexpected function code received by NI port in a control reply message from driver (PARM = function code).

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

CAUSE: NI request table is too small to hold information for the number of outstanding connect requests being attempted (PARM = request ID which was not connected).

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

CAUSE: NI request table is too small to hold information for the number of outstanding disconnect requests being attempted (PARM = request ID which was not disconnected).

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

CAUSE: While trying to delete one of NI's tables during shutdown, delete_table failed (PARM = status from delete_table).

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

CAUSE: After receiving a connect reply from a driver, NI could not locate information about the original request in its tables (PARM = message ID).

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

CAUSE: Bad or unexpected function code received by NI port in a async event message from driver (PARM = function code).

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

CAUSE: Bad or unknown message received by NI port on inbound data subqueues (PARM = message descriptor).

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

CAUSE: During error recovery processing of a failed disconnect request, send_msg failed trying to report the problem back to the sender of the original disconnect (PARM = status from send_msg).

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

CAUSE: During error recovery processing of a failed connect request, send_msg failed trying to report the problem back to the sender of the original connect (PARM = status from send_msg).

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

CAUSE: While stopping a protocol or device, or after completing an outstanding request, NI attempted to free a request block, device- or protocol-table entry, but new_release_table_entry failed (PARM = status from new_release_table_entry).

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

CAUSE: During error recovery following a failure during transmission of outbound X.25 data, netfc_release failed (PARM = status from netfc_release).

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

CAUSE: During error recovery following a failure during reception of inbound X.25 data, netfc_release failed (PARM = status from netfc_release).

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

CAUSE: When attempting to create a table to hold information about outstanding SNA requests, new_create_table failed (PARM = status from new_create_table).

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

CAUSE: While starting an FDDI device, NI was unable to read the FDDI station address.

ACTION: The station address should be available any time the FDDI driver has been started. See Appendix A “Submitting an SR ” of this manual.

CAUSE: An attempt was made to send a packet over a LAPB link which did not have extended addressing specified in the packet.

ACTION: Extended addressing is always required for LAPB links. See Appendix A “Submitting an SR ” of this manual.

CAUSE: After forming the extended address for an outbound LAPB packet, NI encountered an error trying to write that address into the packet.

ACTION: Something is wrong with the outbound buffer. See Appendix A “Submitting an SR ” of this manual.

CAUSE: After building a header for an outbound FDDI or Token Ring packet, NI encountered an error trying to write that header into the packet.

ACTION: Something is wrong with the outbound buffer. See "Submitting an SR" in appendix A of this manual.

CAUSE: When NI attempted to send an outbound LAN, FDDI, or Token Ring packet by calling the driver's outbound write initiator routine, that routine reported an error.

ACTION: Something is wrong with the driver or the SDI address passed with the packet. See Appendix A “Submitting an SR ” of this manual.