IP Logging Location Codes

CAUSE: Received a port message containing an invalid function code (PARM = complete function code).

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

CAUSE: Log IP port initiation (PARM = PDA ptr).

ACTION: Informative.

CAUSE: The length of the IP address alias list passed in an INFO message exceeds the space allocated for the list in the IP port (PARM = # of entries in the alias list).

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

CAUSE: Log IP statistics prior to port terminate (PARM unused).

ACTION: Informative.

CAUSE: Log IP port termination when a TERMINATE message is received (PARM unused).

ACTION: Informative.

CAUSE: Received a Probe or Dial reply with an error status (PARM = Probe/Dial reply status code in upper 16 bits; Probe/Dial ID in lower 16 bits).

ACTION: An occasional error may be tolerated. For persistent errors see Appendix A “Submitting an SR ” of this manual.

CAUSE: Probe reply ID does not match any probe ID on the IP Probe wait queue.

ACTION: Informative.

CAUSE: Received a buffer reply message on the wrong subqueue or not in a buffer reply wait state. This message indicates that this buffer was not allocated (PARM = buffer reply result code).

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

CAUSE: The packet length carried in the IP header is greater than the packet length supplied by the link device (PARM = upper 16 bits: header value; lower 16 bits: actual received).

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

CAUSE: Unable to deliver an inbound ICMP message to an upper layer protocol (TCP/PXP) (PARM = ULP SEND result code).

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

CAUSE: Discarded an inbound ICMP message because the ICMP checksum was bad (PARM = upper 16 bits = actual checksum; lower 16 bits = expected checksum).

ACTION: Frequent occurrences probably indicate hardware or transmission line problems.

CAUSE: Discarded an inbound ICMP message because the ICMP type code was unrecognized (PARM = ICMP type/code). To decode the PARM value, refer to the previous section, "ICMP Type/Code Words."

ACTION: Indicates that a non-HP 3000 node has implemented an ICMP type not prescribed by the ICMP RFC standard.

CAUSE: Indicates that log calls were suppressed for performance reasons. The following log message is the one that was suppressed (PARM = upper 16 bits: location suppressed; lower 16 bits: number of times suppressed).

ACTION: Informative.

CAUSE: Received a GGP protocol message. This is an unsupported protocol (PARM unused).

ACTION: Informative. A non-HP 3000 node which supports the GGP protocol is part of the network configuration.

CAUSE: An inbound data packet was discarded as undeliverable (PARM = ULP SEND result code).

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

CAUSE: An inbound packet was discarded because it failed IP header validation tests (PARM not significant).

ACTION: If this occurs frequently see Appendix A “Submitting an SR ” of this manual.

CAUSE: An inbound packet was discarded because the IP header checksum failed (PARM = upper 16 bits = actual checksum; lower 16 bits = expected checksum).

ACTION: Frequent occurrences probably indicate hardware or transmission line problems.

CAUSE: An inbound data packet was discarded because an error was detected in IP options (PARM = byte location in IP header of error).

ACTION: Check to see that the source node correctly formats the options stream.

CAUSE: An inbound packet was discarded because it was not addressed to this node and store and forward was not allowed from the inbound network interface (PARM unused).

ACTION: Configure store and forward buffers for the IP protocol on the inbound network interface.

CAUSE: An inbound message fragment was discarded because a reassembly data structure could not be allocated.

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

CAUSE: An inbound message fragment was discarded because it is a retransmission of a previously received last fragment and is no longer the last fragment (PARM is not significant).

ACTION: Indicates that someone is sending a duplicate message in error (that is, with the same message ID) but with a longer length.

CAUSE: A message fragment was discarded because of an internal failure of bmgr_append_buffer (PARM = bmgr_append_buffer result code).

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

CAUSE: A message fragment was discarded because of an internal failure of bmgr_append_buffer (PARM = bmgr_append_buffer result code).

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

CAUSE: A partially assembled message was discarded because the fragment assembly timer expired (PARM is not significant).

ACTION: This will happen occasionally when a fragment is lost or discarded. If it occurs often, it may indicate that a gateway is congested. Reconfigure to achieve a better load balance.

CAUSE: A store and forward packet was discarded because there were no store and forward buffers for the outbound network interface.

ACTION: This indicates that the gateway is congested. This can happen until congestion avoidance measures are applied at the sending source nodes. If this persistently occurs, there may be a runaway node on the network that is disregarding SOURCE QUENCH messages.

CAUSE: After processing a store and forward packet, congestion control thresholds have been reached (that is, 75% or more internal resources have been used). A Source Quench packet will be sent to the source.

ACTION: Informative.

CAUSE: A store and forward packet was discarded because no buffers were available in the store and forward buffer pool (PARM = bmgr_get_buffer result code).

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

CAUSE: A store and forward packet was discarded because an internal error was encountered in bmgr_write_buffer (PARM = bmgr_write_buffer result code).

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

CAUSE: A store and forward packet was discarded because the IP time to live expired (PARM unused).

ACTION: Informative.

CAUSE: A store and forward packet was discarded because the next local destination address supplied from the routing tables was not in the strict source route list in the IP header (PARM unused).

ACTION: Verify that the routing information about the destination node in the configuration file is correct. Verify that the links and NIs are started.

CAUSE: A store and forward packet was discarded because fragmentation was necessary but the "Don't Fragment" flag was set (PARM unused).

ACTION: Informative.

CAUSE: An store and forward packet was discarded because an outbound path could not be established (PARM = NS_PATH_RESOLVE result code).

ACTION: Indicates that network reachability information was not properly configured.

CAUSE: A packet was discarded because it had to wait for a probe reply and IP's internal queue was at the limit (PARM = queue max).

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

CAUSE: Outbound packet discarded because of an internal error in the IP/ULP interface. Specifically, the length of the options data was out of the valid range (PARM = outbound options length).

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

CAUSE: An outbound data packet that required fragmenting was discarded because of an internal error in bmgr_copy_buffer (PARM = bmgr_copy_buffer result code).

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

CAUSE: An outbound data packet that required fragmenting was discarded because of an internal error in bmgr_write_buffer (PARM = bmgr_write_buffer result code).

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

CAUSE: An outbound data packet that required fragmenting was discarded because an error occurred in a get buffer call (PARM = bmgr_get_buffer result code).

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

CAUSE: A store and forward packet was discarded because an error occurred creating a fragment with bmgr_copy_buffer (PARM = bmgr_copy_buffer result code).

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

CAUSE: A buffer reply message was received while IP was waiting to terminate.

ACTION: Informative.

CAUSE: Probe or dial reply was received while IP was waiting to terminate.

ACTION: Informative.

CAUSE: Encountered an error while attempting to read the number of address in the alias list (PARM = bmgr_read_buffer result).

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

CAUSE: Encountered an error while attempting to read an address from the alias list (PARM = bmgr_read_buffer result).

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

CAUSE: Unable to free the buffer that held the alias list (PARM = bmgr_free_buffer result).

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

CAUSE: An error was detected while trying to write the IP header to the outbound buffer (PARM = bmgr_write_buffer result).

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

CAUSE: The send by IP to NI for normal outbound data was unsuccessful (PARM = send_msg result).

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

CAUSE: Unable to read the IP header from the inbound buffer during normal inbound processing (PARM = bmgr_read_buffer result).

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

CAUSE: Unable to read additional header information if options were present during inbound processing (PARM = bmgr_read_buffer result).

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

CAUSE: Unable to get a table management object for expansion of IP memory space in case the context area overflows (PARM = new_create_table result).

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

CAUSE: An error was detected while IP was attempting to add itself to the intranet mapping table (PARM = map_add_entity result).

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

CAUSE: Unable to read the options from the outbound buffer during outbound fragmentation processing (PARM = bmgr_read_buffer result).

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

CAUSE: A failure was detected while attempting to send a message to NI during outbound fragmentation (PARM = send_msg result).

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

CAUSE: An error was detected while attempting to read the IP header from the inbound buffer after fragment reassembly had completed (PARM = bmgr_read_buffer result).

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

CAUSE: An error was detected while attempting to start a timer for inbound reassembly (PARM = get_timer result).

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

CAUSE: An inbound buffer could not be freed while processing a partial datagram (reassembly) (PARM = bmgr_free_buffer result).

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

CAUSE: An inbound buffer that was being held for reassembly could not be freed (PARM = bmgr_free_buffer result).

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

CAUSE: An inbound buffer could not be freed while processing a partial datagram (reassembly) (PARM = bmgr_free_buffer result).

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

CAUSE: An entry could not be allocated for managing a delayed reply from either probe or dial.

ACTION: This may occasionally happen. However, if it is happening frequently, the number of probe/dial wait queue elements may have to be increased. The disadvantage of doing this is that additional buffers are held while path resolution is under way. If the problem persists, see Appendix A “Submitting an SR ” of this manual.

CAUSE: Path resolution failure reported from a delayed probe/dial request (PARM = ns_path_resolve result).

ACTION: May indicate a misconfiguration of network or a failed link.

CAUSE: A failure was detected while attempting to send NI a message during outbound store and forward processing (PARM = send_msg result).

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

CAUSE: An error was detected while attempting to retrieve buffer pool information about a store and forward pool (PARM = bmgr_pool_info result).

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

CAUSE: IP was unable to add itself to the registry during initialization (PARM = reg_add_entity result).

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

CAUSE: IP was unable to terminate immediately because it has outstanding buffer or path resolution requests. When these complete IP will terminate.

ACTION: Informative.

CAUSE: A datagram was received that should be forwarded. However, the network portion of the destination address is a broadcast value. These datagrams will be discarded.

ACTION: Remote node is sending an illegal datagram.

CAUSE: A datagram was received that required forwarding, but the node that it was to be forwarded to was directly connected to the sending node. The datagram will be forwarded and a redirect message will also be sent to the source of the datagram.

ACTION: If this happens frequently the sending node should be reconfigured so that it does not send datagrams to this node to forward them to a node that it is directly connected to.

CAUSE: A failure was detected when IP sent a message to a peer IP during store and forwarding processing.

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

CAUSE: An error was detected while attempting to send a msg to IPU (PARM = send_msg result code).

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

CAUSE: IP received a broadcast packet not addressed to the local node.

ACTION: If this occurs frequently, analyze the network traffic for the sender of the broadcast packets.