HP 3000 Manuals HP 3000 Manuals
TCP Logging Locations
The following is an explanation of the general format of TCP logging
locations. An explanation of the individual TCP logging messages
follows.
Logging Location is a 5-digit decimal field with the following
sub-fields:
NMMMM where N is the transport module number and MMMM is defined by the
logging module
TCP designates MMMM as follows:
TTLL where TT is the type of error which occurred and LL is a unique
location tag used to differentiate between multiple occurrences of the
same error.
Module numbers (N)
1- TCP
Types (TT)
00-09 External errors - An error result was returned from
a procedure call to a module outside of TCP.
00- NWTM Error
01- NM Ports Error/CM dictionary
02- Table Management Error
03- Object Management Error
04- Path Error
05- NET Timers Error
06- Semaphores and HPGETSYSPLABEL
07- Memory Manager (Freeze, Unfreeze) Error
08- NMlog/NMtrace/NMmon/Registry
09- Dynamic call to driver (or driver) / HPGETSYSPLABEL
failed
10-19 Implementation Errors - These indicate a coding or
data state error somewhere within TCP or the
interfaces to TCP.
10- Attempted to delete from empty rtxq
11- Internal IPC State incorrect
12- Bad timer state
13- Data requested greater than buffer contents
14- Bad status from tcp_read_completor
15- Unmatched buffer pool in buffer reply
16- Unexpected Buffer reply
17- Bad buffer reply state
18- Resegmentation failure
20-29 Remote protocol errors - These errors indicate that
the remote TCP to which this implementation is
conversing has apparently generated a packet which
is in error or which violated the protocol or had
to be ignored due to the local state. (Note: Some
of these errors are minor - eg. Local SAP not
open).
20- Inbound Checksum Error
21- Inbound Precedence/Security
22- Unexpected Syn in window
23- No ACK
24- Invalid Ack
25- Data after Fin
26- Bad Max TPDU option length
27- Half Open Connection (SIP sent reset)
28- Local SAP Not Open
30-39 IPC / TCP synchronization errors - IPC has called
TCP with unexpected parameters or in an unexpected
state
30- IPC Receive Reply w/o data pending
31- IPC Receive Reply while not in data accepting state
32- TCP not started
33- Network not started
34- Bad (Unknown) IPCcontrol
40-49 standard connection lost/shutdown errors
40- RTX Timeout (# of retries)
41- RTX Threshold exceeded
42- Remote abort
43- Connection Assurance Timeout
50-59 More External Errors - An error result was returned
from a procedure call to a module outside of TCP.
50- Buffer Manager
59- Unexpected escape
60-79 standard informative errors (etc.)
60- Duplicate Packet received
61- Packet tossed
62- Retransmission suppressed
63- Packet Retransmitted
64- Negative Advice Passed
65- Late timer
66- Source Quench Received
70-79 Miscellaneous Errors
70- Duplicate connection name
71- Passive Connection Request rejected (or an error
occurred)
72- PM Deactivated w/ Error
73- Duplicate socket name
74- Protocol start failed
75- Bad Message Type/ Function Code
76- Max connections exceeded
77- Wrong Father Pin (Not NMMON)
78- Max sockets exceeded
80-89 standard informative messages - Nodal and
connection events
80- PM activated
81- PM Graceful released
82- PM Deactivated
83- Socket Created
84- Socket Deactivated
85- Protocol started
86- Protocol stopped
87- Network stopped
88- Driver Down Notification Complete
89- Path Verify Complete
98-99 Statistical Logging
98- SIP statistics
99- PM Statistics
10001 CLAS0002 Cause: NWTM_SEND_MSG returned a bad status
while trying to send the inbound connection shut
request (remote fin received indication) to IPC.
Action: PARM is NWTM error returned. Submit an
SR.
10002 CLAS0002 Cause: NWTM_SEND_MSG returned a bad status
while trying to send the inbound connection shut
request (remote fin received indication) to IPC.
Action: PARM is NWTM error returned. Submit an
SR.
10003 CLAS0002 Cause: NWTM_SEND_MSG returned a bad status
while trying to send an irrecoverable error
message to IPC.
Action: PARM is NWTM error returned. Submit an
SR.
10004 CLAS0002 Cause: NWTM_SET_FILE_EVENT returned a bad
status while trying to set the exception bit due
to received urgent data.
Action: PARM is NWTM error returned. Submit an
SR.
10005 CLAS0002 Cause: NTWM_SEND_MSG returned a bad status
while trying to notify IPC of received inbound
data.
Action: PARM is NWTM error returned. Submit an
SR.
10006 CLAS0002 Cause: NWTM_RESET_FILE_EVENT returned a bad
status while trying to reset the exception bit
due to coming to the end of inbound urgent data.
Action: PARM is NWTM error returned. Submit an
SR.
10007 CLAS0002 Cause: NWTM_SEND_MSG returned a bad status
while trying to send the inbound connection
shutdown request (remote FIN received) to IPC.
Action: PARM is NWTM error returned. Submit an
SR.
10008 CLAS0002 Cause: NWTM_RESET_FILE_EVENT returned a bad
status while trying to reset the write bit for a
socket due to coming to the end of inbound
connection requests.
Action: PARM is NWTM error returned. Submit an
SR.
10009 CLAS0002 Cause: NWTM_RESET_FILE_EVENT returned a bad
status while trying to reset the write bit for a
connection due to becoming unwriteable.
Action: PARM is NWTM error returned. Submit an
SR.
10010 CLAS0002 Cause: NWTM_SET_FILE_EVENT returned a bad
status while trying to set the write bit for a
connection due to becoming writeable.
Action: PARM is NWTM error returned. Submit an
SR.
10011 CLAS0002 Cause: NWTM_SEND_MSG returned a bad status
while trying to send a send completion
notification to IPC.
Action: PARM is NWTM error returned. Submit an
SR.
10012 CLAS0002 Cause: NWTM_SEND_MSG returned a bad status
while trying to send an irrecoverable error
message to a call socket.
Action: PARM is NWTM error returned. Submit an
SR.
10013 CLAS0002 Cause: NWTM_SEND_MSG returned a bad status
while trying to send a connection request
message to IPC. The inbound syn may not be able
to establish a connection.
Action: PARM is NWTM error returned. Submit an
SR.
10014 CLAS0002 Cause: NWTM_RESET_FILE_EVENT returned a bad
status while trying to reset the readable bit
during connection cleanup.
Action: PARM is NWTM error returned. Submit an
SR.
10015 CLAS0002 Cause: NWTM_RESET_FILE_EVENT returned a bad
status while trying to reset the readable bit
due to coming to the end of the currently
deliverable inbound data.
Action: PARM is NWTM error returned. Submit an
SR.
10016 CLAS0002 Cause: NWTM_SEND_MSG returned a bad status
while trying to send a connect reply message to
IPC.
Action: PARM is NWTM error returned. Submit an
SR.
10017 CLAS0002 Cause: NWTM_SET_FILE_EVENT returned a bad
status while trying to set the readable and
writable bits due to a connection shutting down.
Action: PARM is NWTM error returned. Submit an
SR.
10101 CLAS0002 Cause: Bad status returned from send_msg while
sending a negative advice message to the TCP
SIP.
Action: PARM is ports error returned. Submit
an SR.
10103 CLAS0002 Cause: Bad status returned from send_msg while
forwarding an inbound packet for an unknown
connection to the SIP.
Action: PARM is ports error returned. Submit
an SR.
10104 CLAS0002 Cause: Bad status returned from send_msg while
trying to send a cleanup request to the SIP.
Action: PARM is ports error returned. Submit
an SR.
10105 CLAS0002 Cause: Bad status returned from send_msg while
trying to send a timer popped message to the SIP
due to semaphore contention. The timer may be
dropped, the connection may hang indefinitely.
Action: PARM is ports error returned. Submit
an SR.
10106 CLAS0003 Cause: Bad status returned from a send_msg call
while trying to send an outbound data message to
an NI or X.25 port.
Action: PARM is ports error returned. Submit
an SR.
10109 CLAS0002 Cause: Bad status returned from extend_receive
while waiting for a message from the TCP SIP
indicating that it has started successfully.
This would occur during network startup.
Action: Check for other logging indicating the
reason that the SIP was unable to start. PARM
is ports error returned. Submit an SR.
10110 CLAS0002 Cause: Bad status returned from purge_pool
while trying to delete the TCP SIP message pool.
This was during a system shutdown.
Action: PARM is ports error returned. Submit
an SR.
10111 CLAS0002 Cause: Bad status returned from purge_port
while trying to delete the TCP SIP port. This
was during a system shutdown.
Action: PARM is ports error returned. Submit
an SR.
10112 CLAS0002 Cause: Bad status returned from create_pool
while trying to create a message pool for the
TCP SIP. This was during protocol start.
Action: PARM is ports error returned. Submit
an SR.
10113 CLAS0002 Cause: Bad status returned from create_port
while trying to create a port for the TCP SIP.
This was during protocol start.
Action: PARM is ports error returned. Submit
an SR.
10114 CLAS0002 Cause: Bad status returned from change_subqueue
while trying to enable a subset of subqueues for
TCP SIP's port.
Action: PARM is ports error returned. Submit
an SR.
10115 CLAS0002 Cause: Bad status returned from purge_pool
while trying to delete a message pool for the
TCP SIP. The reason for deleting the message
pool was that an error occurred while bringing
up the TCP SIP, so TCP was cleaning up its
resources.
Action: PARM is ports error returned. Submit
an SR.
10116 CLAS0002 Cause: Bad status returned from purge_port
while trying to delete a port for the TCP SIP.
The reason for deleting the port was an error
occurred while bringing up the TCP SIP, so TCP
was cleaning up its resources.
Action: PARM is ports error returned. Submit
an SR.
10117 CLAS0002 Cause: Bad status returned from send_msg while
trying to send a port message to NETCP, which is
waiting for reply from the TCP SIP indicating
that has successfully completed initialization.
NETCP is in 'TCP_MODULE_CONFIG' and may be hung.
Action: PARM is ports error returned. Submit
an SR.
10118 CLAS0002 Cause: Bad status returned from send_msg while
trying to send a path_verify reply to NETCP.
NETCP may be in a hung state, if so further
NETCONTROL commands will also hang.
Action: PARM is ports error returned. Submit
an SR. Reboot if necessary to restart transport.
10119 CLAS0002 Cause: Bad status returned from send_msg while
trying to send a traceoff_reply message to
NETCP. NETCP may be in a hung state, if so
further NETCONTROL commands will also hang.
Action: PARM is ports error returned. Submit
an SR. Reboot if necessary to restart transport.
10120 CLAS0002 Cause: Bad status returned from send_msg while
trying to send an outbound data message to the
IP port.
Action: PARM is ports error returned. Submit
an SR.
10121 CLAS0002 Cause: Bad status returned from send_msg while
trying to send a terminate reply message to
NETCP. NETCP may be in a hung state.
Action: PARM is ports error returned. Submit
an SR.
10122 CLAS0002 Cause: Bad status returned from receive_msg
while waiting for a message on the TCP SIP port.
Action: PARM is ports error returned. Submit
an SR.
10123 CLAS0002 Cause: Bad status returned from send_msg while
trying to forward an inbound packet to the SIP.
Packet is being forwarded tracing is active.
Action: PARM is ports error returned. Submit
an SR.
10124 CLAS0002 Cause: Bad status returned from send_msg while
trying to send a cleanup request message to the
SIP.
Action: PARM is ports error returned. Submit
an SR.
10201 CLAS0002 Cause: New_get_table_entry returned a bad
status while we were trying to allocate a
connection entry. This occurred while trying to
process an inbound syn. The connection attempt
will fail.
Action: PARM is table management error
returned. Submit an SR.
10202 CLAS0002 Cause: New_release_table_entry returned a bad
status while we were trying to deallocate a
connection entry.
Action: PARM is table management error
returned. Submit an SR.
10203 CLAS0002 Cause: New_release_table_entry returned a bad
status while we were trying to deallocate a
socket entry.
Action: PARM is table management error
returned. Submit an SR.
10204 CLAS0002 Cause: New_get_table_entry returned a bad
status while we were trying to allocate a socket
entry.
Action: PARM is table management error
returned. Submit an SR.
10205 CLAS0002 Cause: New_get_table_entry returned a bad
status while we were trying to allocate a vector
queue entry.
Action: PARM is table management error
returned. Submit an SR.
10206 CLAS0002 Cause: New_release_table_entry returned a bad
status while we were trying to deallocate a
vector queue entry.
Action: PARM is table management error
returned. Submit an SR.
10207 CLAS0002 Cause: There was a bad status returned from
new_create_table while creating the TCP
connection table. This would occur during
network startup.
Action: PARM is table management error
returned. Submit an SR.
10208 CLAS0002 Cause: There was a bad status returned from
new_create_table while creating the TCP socket
table. This would occur during network startup.
Action: PARM is table management error
returned. Submit an SR.
10209 CLAS0002 Cause: There was a bad status returned from
new_create_table while creating the TCP vector
table. This would occur during network startup.
Action: PARM is table management error
returned. Submit an SR.
10210 CLAS0002 Cause: There was a bad status returned from
delete_table while releasing the TCP connection
table. This would happen after network or
system shutdown.
Action: PARM is table management error
returned. Submit an SR.
10211 CLAS0002 Cause: There was a bad status returned from
delete_table while releasing the TCP socket
table. This would happen after network or
system shutdown.
Action: PARM is table management error
returned. Submit an SR.
10212 CLAS0002 Cause: There was a bad status returned from
delete_table while releasing the TCP vector
table. This would happen after network or
system shutdown.
Action: PARM is table management error
returned. Submit an SR.
10213 CLAS0002 Cause: New_get_table_entry returned a bad
status while we were trying to allocate a
connection entry. This occurred while trying to
process an inbound syn. The connection attempt
will fail.
Action: PARM is table management error
returned. Submit an SR.
10214 CLAS0002 Cause: New_release_table_entry returned a bad
status while we were trying to deallocate a
connection entry. The connection entry is being
deallocated because a duplicate connection
already exists.
Action: PARM is table management error
returned. Submit an SR.
10301 CLAS0002 Cause: There was a bad status received from
create_object. Create_object was called during
network startup in order to create the global
TCP data area.
Action: PARM is memory management error
returned. Submit an SR.
10302 CLAS0002 Cause: There was a bad status received from
release_object. Release_object was called
because we had a problem bringing up TCP during
network startup, so we were cleaning up its
resources.
Action: PARM is table management error
returned. Submit an SR.
10401 CLAS0005 Cause: PATHs failed to resolve a path to the
requested destination. The connection request
has failed.
Action: PARM is path resolution status.
Possible nodal/media failure or
misconfiguration. Diagnose path resolution
failure. Submit an SR if necessary.
10402 CLAS0005 Cause: PATHs failed to resolve a path to the
requested destination. The passive connection
attempt has failed.
Action: PARM is path resolution status.
Possible nodal/media failure or
misconfiguration. Diagnose path resolution
failure. Submit an SR if necessary.
10403 CLAS0005 Cause: The Path reply came back with a bad
status. We can't get a route to establish
connection.
Action: PARM is path reply error returned.
Possible nodal/media failure or
misconfiguration. Diagnose path resolution
failure. Submit an SR if necessary.
10404 CLAS0005 Cause: We have received numerous consecutive
path replies, but we still haven't received a
good route to establish the connection. We
assume that the path resolution mechanism has
entered a sick state for this route and is
unable to resolve our destination.
Action: Possible nodal/media failure or
misconfiguration. Diagnose path resolution
failure. Submit an SR if necessary.
10405 CLAS0005 Cause: The TCP SIP couldn't get a route to send
an outbound reset.
Action: Informative message. No action
required. Try to determine why route to remote
host has failed. Possibilities include
node/media failure and misconfiguration.