IP Logging Location Codes [ NS3000/iX Error Messages Reference Manual ] MPE/iX 5.0 Documentation
NS3000/iX Error Messages Reference Manual
IP Logging Location Codes
101 CLAS0002 Cause: Received a port message containing an invalid
function code (PARM = complete function code).
Action: See "Submitting an SR" in appendix A of this
manual.
102 CLAS0004 Cause: Log IP port initiation (PARM = PDA ptr).
Action: Informative.
103 CLAS0002 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 "Submitting an SR" in appendix A of this
manual.
104 CLAS0006 Cause: Log IP statistics prior to port terminate
(PARM unused).
Action: Informative.
105 CLAS0004 Cause: Log IP port termination when a TERMINATE
message is received (PARM unused).
Action: Informative.
106 CLAS0003 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 "Submitting an SR" in appendix A
of this manual.
107 CLAS0005 Cause: Probe reply ID does not match any probe ID on
the IP Probe wait queue.
Action: Informative.
109 CLAS0002 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 "Submitting an SR" in appendix A of this
manual.
111 CLAS0003 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 "Submitting an SR" in appendix A of this
manual.
112 CLAS0003 Cause: Unable to deliver an inbound ICMP message to
an upper layer protocol (TCP/PXP) (PARM = ULP SEND
result code).
Action: See "Submitting an SR" in appendix A of this
manual.
113 CLAS0003 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.
114 CLAS0003 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.
115 CLAS0002 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.
116 CLAS0003 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.
118 CLAS0002 Cause: An inbound data packet was discarded as
undeliverable (PARM = ULP SEND result code).
Action: See "Submitting an SR" in appendix A of this
manual.
121 CLAS0003 Cause: An inbound packet was discarded because it
failed IP header validation tests (PARM not
significant).
Action: If this occurs frequently see "Submitting an
SR" in appendix A of this manual.
122 CLAS0003 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.
123 CLAS0003 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.
124 CLAS0002 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.
125 CLAS0002 Cause: An inbound message fragment was discarded
because a reassembly data structure could not be
allocated.
Action: See "Submitting an SR" in appendix A of this
manual.
128 CLAS0002 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.
130 CLAS0002 Cause: A message fragment was discarded because of an
internal failure of bmgr_append_buffer (PARM =
bmgr_append_buffer result code).
Action: See "Submitting an SR" in appendix A of this
manual.
133 CLAS0002 Cause: A message fragment was discarded because of an
internal failure of bmgr_append_buffer (PARM =
bmgr_append_buffer result code).
Action: See "Submitting an SR" in appendix A of this
manual.
137 CLAS0003 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.
139 CLAS0003 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.
141 CLAS0003 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.
142 CLAS0002 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 "Submitting an SR" in appendix A of this
manual.
144 CLAS0002 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 "Submitting an SR" in appendix A of this
manual.
145 CLAS0003 Cause: A store and forward packet was discarded
because the IP time to live expired (PARM unused).
Action: Informative.
147 CLAS0003 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.
148 CLAS0003 Cause: A store and forward packet was discarded
because fragmentation was necessary but the "Don't
Fragment" flag was set (PARM unused).
Action: Informative.
149 CLAS0002 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.
151 CLAS0002 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 "Submitting an SR" in appendix A of this
manual.
157 CLAS0002 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 "Submitting an SR" in appendix A of this
manual.
160 CLAS0002 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 "Submitting an SR" in appendix A of this
manual.
161 CLAS0002 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 "Submitting an SR" in appendix A of this
manual.
162 CLAS0002 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 "Submitting an SR" in appendix A of this
manual.
165 CLAS0002 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 "Submitting an SR" in appendix A of this
manual.
176 CLAS0004 Cause: A buffer reply message was received while IP
was waiting to terminate.
Action: Informative.
177 CLAS0004 Cause: Probe or dial reply was received while IP was
waiting to terminate.
Action: Informative.
178 CLAS0002 Cause: Encountered an error while attempting to read
the number of address in the alias list (PARM =
bmgr_read_buffer result).
Action: See "Submitting an SR" in appendix A of this
manual.
179 CLAS0002 Cause: Encountered an error while attempting to read
an address from the alias list (PARM =
bmgr_read_buffer result).
Action: See "Submitting an SR" in appendix A of this
manual.
180 CLAS0002 Cause: Unable to free the buffer that held the alias
list (PARM = bmgr_free_buffer result).
Action: See "Submitting an SR" in appendix A of this
manual.
181 CLAS0002 Cause: An error was detected while trying to write
the IP header to the outbound buffer (PARM =
bmgr_write_buffer result).
Action: See "Submitting an SR" in appendix A of this
manual.
182 CLAS0002 Cause: The send by IP to NI for normal outbound data
was unsuccessful (PARM = send_msg result).
Action: See "Submitting an SR" in appendix A of this
manual.
183 CLAS0002 Cause: Unable to read the IP header from the inbound
buffer during normal inbound processing (PARM =
bmgr_read_buffer result).
Action: See "Submitting an SR" in appendix A of this
manual.
184 CLAS0002 Cause: Unable to read additional header information
if options were present during inbound processing
(PARM = bmgr_read_buffer result).
Action: See "Submitting an SR" in appendix A of this
manual.
186 CLAS0002 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 "Submitting an SR" in appendix A of this
manual.
187 CLAS0002 Cause: An error was detected while IP was attempting
to add itself to the intranet mapping table (PARM =
map_add_entity result).
Action: See "Submitting an SR" in appendix A of this
manual.
188 CLAS0002 Cause: Unable to read the options from the outbound
buffer during outbound fragmentation processing (PARM
= bmgr_read_buffer result).
Action: See "Submitting an SR" in appendix A of this
manual.
189 CLAS0002 Cause: A failure was detected while attempting to
send a message to NI during outbound fragmentation
(PARM = send_msg result).
Action: See "Submitting an SR" in appendix A of this
manual.
190 CLAS0002 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 "Submitting an SR" in appendix A of this
manual.
191 CLAS0002 Cause: An error was detected while attempting to
start a timer for inbound reassembly (PARM = get_timer
result).
Action: See "Submitting an SR" in appendix A of this
manual.
192 CLAS0002 Cause: An inbound buffer could not be freed while
processing a partial datagram (reassembly) (PARM =
bmgr_free_buffer result).
Action: See "Submitting an SR" in appendix A of this
manual.
193 CLAS0002 Cause: An inbound buffer that was being held for
reassembly could not be freed (PARM = bmgr_free_buffer
result).
Action: See "Submitting an SR" in appendix A of this
manual.
194 CLAS0002 Cause: An inbound buffer could not be freed while
processing a partial datagram (reassembly) (PARM =
bmgr_free_buffer result).
Action: See "Submitting an SR" in appendix A of this
manual.
195 CLAS0002 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 "Submitting an SR" in appendix A
of this manual.
196 CLAS0003 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.
197 CLAS0002 Cause: A failure was detected while attempting to
send NI a message during outbound store and forward
processing (PARM = send_msg result).
Action: See "Submitting an SR" in appendix A of this
manual.
198 CLAS0002 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 "Submitting an SR" in appendix A of this
manual.
199 CLAS0002 Cause: IP was unable to add itself to the registry
during initialization (PARM = reg_add_entity result).
Action: See "Submitting an SR" in appendix A of this
manual.
200 CLAS0004 Cause: IP was unable to terminate immediately because
it has outstanding buffer or path resolution requests.
When these complete IP will terminate.
Action: Informative.
201 CLAS0003 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.
202 CLAS0003 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.
203 CLAS0002 Cause: A failure was detected when IP sent a message
to a peer IP during store and forwarding processing.
Action: See "Submitting an SR" in appendix A of this
manual.
204 CLAS0002 Cause: An error was detected while attempting to send
a msg to IPU (PARM = send_msg result code).
Action: See "Submitting an SR" in appendix A of this
manual.
205 CLAS0003 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.
MPE/iX 5.0 Documentation