TCP Logging Locations

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.

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.

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.

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.

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.

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.

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.

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.

CAUSE: NWTM_RESET_FILE_EVENT returned a bad status while trying to reset the write bit for a connection due to becoming unwritable.

ACTION: PARM is NWTM error returned. Submit an SR.

CAUSE: NWTM_SET_FILE_EVENT returned a bad status while trying to set the write bit for a connection due to becoming writable.

ACTION: PARM is NWTM error returned. Submit an SR.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

CAUSE: The TCP SIP couldn't get a route to send an outbound reset after waiting for reply from paths.

ACTION: Informative message. No action required. Try to determine why route to remote host has failed. Possibilities include node/media failure and misconfiguration.

CAUSE: We verified a connection's route due to negative advice, and found that there is no longer a route to the remote host. The connection will abort.

ACTION: Informative message. No action required. Try to determine why route to remote host has failed. Possibilities include node/media failure and misconfiguration.

CAUSE: Nettmr_reset_timer call returned an error.

ACTION: PARM is nettmr error returned. Submit an SR.

CAUSE: Nettmr_free_timer call returned an error.

ACTION: PARM is nettmr error returned. Submit an SR.

CAUSE: Nettmr_get_timer call returned an error.

ACTION: PARM is nettmr error returned. Submit an SR.

CAUSE: Nettmr_reset_timer call returned an error.

ACTION: PARM is nettmr error returned. Submit an SR.

CAUSE: CB_INIT returned a bad status while initializing the hash table semaphore. CB_INIT was called during network startup.

ACTION: PARM is semaphores error returned. Submit an SR.

CAUSE: CB_INIT returned a bad status while initializing the global TCP semaphore. CB_INIT was called during network startup.

ACTION: PARM is semaphores error returned. Submit an SR.

CAUSE: CB_INIT returned a bad status while initializing a connection semaphore. CB_INIT was called during TCP connection establishment.

ACTION: PARM is semaphores error returned. Submit an SR.

CAUSE: Attempt to unfreeze user data vector failed.

ACTION: PARM is memory manager error returned. Submit an SR.

CAUSE: Attempt to freeze user data vector failed.

ACTION: PARM is memory manager error returned. Submit an SR.

CAUSE: Attempt to unfreeze user data vector failed.

ACTION: PARM is memory manager error returned. Submit an SR.

CAUSE: NMCLOSETRACE returned a bad status during an IPCCONTROL traceoff call.

ACTION: PARM is the NMS error returned. Submit an SR.

CAUSE: NMOPENLOG returned a bad status during network startup.

ACTION: PARM is the NMS error returned. Submit an SR.

CAUSE: NMMONSTARTREQ call returned a bad status during network startup.

ACTION: PARM is the NMS error returned. Submit an SR.

CAUSE: Bad status was returned in a message from the TCP SIP during network startup. The TCP SIP initialization has failed.

ACTION: PARM is TCP SIP initialization error. Look for a logging indication explaining TCP SIP initialization failure. Submit an SR.

CAUSE: Bad status was returned from NMCLOSELOG. This was called during system shutdown.

ACTION: PARM is the NMS error returned. Submit an SR.

CAUSE: Bad status was returned from NMMONDELETEID. This was called during system shutdown.

ACTION: PARM is the NMS error returned. Submit an SR.

CAUSE: Bad status was returned from NMCLOSELOG during network shutdown.

ACTION: PARM is the NMS error returned. Submit an SR.

CAUSE: NMWRITETRACE call returned a bad status while tracing a data packet

ACTION: PARM is the NMS error returned. Submit an SR.

CAUSE: NMWRITETRACE call returned a bad status while tracing a reset packet being sent out by the TCP SIP.

ACTION: PARM is the NMS error returned. Submit an SR.

CAUSE: NMWRITETRACE call returned a bad status while tracing an ICMP message.

ACTION: PARM is the NMS error returned. Submit an SR.

CAUSE: NMWRITETRACE call returned a bad status while tracing a resource interface.

ACTION: PARM is the NMS error returned. Submit an SR.

CAUSE: NMWRITETRACE call returned a bad status while tracing a resource interface.

ACTION: PARM is the NMS error returned. Submit an SR.

CAUSE: REG_DEL_ENTITY returned a bad status. It was called during network shutdown.

ACTION: PARM is the registry error returned. Submit an SR.

CAUSE: REG_ADD_ENTITY returned a bad status. It was called during network startup.

ACTION: PARM is the registry error returned. Submit an SR.

CAUSE: NWWRITETRACE returned a bad status while attempting to write a state trace record for a connection.

ACTION: PARM is NWS error returned. Submit an SR.

CAUSE: NWWRITETRACE returned a bad status while attempting to write a state trace record for the TCP SIP.

ACTION: PARM is NWS error returned. Submit an SR.

CAUSE: NWWRITETRACE returned a bad status while attempting to write a message or procedure call trace record for a connection.

ACTION: PARM is NWS error returned. Submit an SR.

CAUSE: NWWRITETRACE returned a bad status while attempting to write a message or procedure call trace record for the TCP SIP.

ACTION: PARM is NWS error returned. Submit an SR.

CAUSE: DICT_DELETE returned a bad status while attempting to remove the TCP SIP from the cm port dictionary during shutdown.

ACTION: PARM is the returned error. Submit an SR.

CAUSE: A call to an SDI driver failed.

ACTION: PARM is the call result status. Submit an SR.

CAUSE: TCP accepted a new ack, but no outstanding data was found on the retransmission queue. The connection is in an inconsistent state.

ACTION: Submit an SR.

CAUSE: HPGETSYSPLABEL call failed to get plabel of TCP's timer trap routine. This would occur during network startup.

ACTION: Network Transport installation looks suspicious. Verify Transport installed correctly. Submit an SR.

CAUSE: TCP received a packet in the syn_received state, but found that the internal IPC state was not consistent with this state.

ACTION: Submit an SR.

CAUSE: TCP received a packet in the syn_sent state, but found that the internal IPC state was not consistent with this state.

ACTION: Submit an SR.

CAUSE: TCP has entered a state (processing an inbound fin) which inconsistent with its internal IPC state. This is a software error.

ACTION: Submit an SR.

CAUSE: TCP internal timer state was inconsistent with actual timer activity.

ACTION: Submit an SR.

CAUSE: TCP wanted to adjust the length of data of a composite buffer beyond the end of the last buffer in the chain.

ACTION: Submit an SR.

CAUSE: Bad status returned from a call to the tcp_read_completor in the loopback send path.

ACTION: Submit an SR.

CAUSE: Bad status returned from a call to the tcp_read_completor in the loopback retransmissive send path.

ACTION: Submit an SR.

CAUSE: We received a reply from buffer manager containing a buffer that is not part of our buffer pool.

ACTION: Informative message. No action required. This may indicate a procedural error within TCP.

CAUSE: We received a reply from buffer manager when we weren't expecting one.This is a software error in TCP.

ACTION: This is a dangerous circumstance, as we are not keeping proper track of our resources. Submit an SR.

CAUSE: We received a reply from buffer manager but our buffer state indicated that we were not expecting one.

ACTION: This is a dangerous circumstance, as we are not keeping proper track of our resources. Submit an SR.

CAUSE: We had a problem resegmenting the retransmission queue.

ACTION: Submit an SR.

CAUSE: Attempt to add a network to TCP's IP list table when the table is full. Connection is added to temporary list.

ACTION: PARM is source IP address of connection. Check configuration for number of configured networks. If ok, then submit an SR.

CAUSE: Connection could not be found in TCP's IP list table when it is shutting down.

ACTION: PARM is source IP address of connection. Submit an SR.

CAUSE: Connection was removed from TCP's temporary IP list table. See location 11901.

ACTION: PARM is source IP address of connection. Check configuration for number of configured networks. If ok, then submit an SR.

CAUSE: A connection received a packet with a bad checksum.

ACTION: Informative message. No action required. Bad checksums usually indicate poor transmission quality.

CAUSE: A connection received a packet with a bad checksum.

ACTION: Informative message. No action required. Bad checksums usually indicate poor transmission quality.

CAUSE: A connection received a packet with a bad checksum.

ACTION: Informative message. No action required. Bad checksums usually indicate poor transmission quality.

CAUSE: The TCP SIP tossed an inbound packet due to a bad checksum.

ACTION: Informative message. No action required. Bad checksums usually indicate poor transmission quality.

CAUSE: A TCP connection received a packet with precedence or security options which do not match those of the connection. The connection will abort.

ACTION: Remote protocol error indication. Use tracing or line analysis to capture connection dialog. If precedence or security option of inbound packet changes report an error against the remote implementation. Otherwise, submit an SR.

CAUSE: A TCP connection received a packet with precedence or security options which do not match those of the connection. The connection will abort.

ACTION: Remote protocol error indication. Use tracing or line analysis to capture connection dialog. If precedence or security option of inbound packet changes report an error against the remote implementation. Otherwise, submit an SR.

CAUSE: A TCP connection received a packet with precedence or security options which do not match those of the connection. The connection will abort.

ACTION: Remote protocol error indication. Use tracing or line analysis to capture connection dialog. If precedence or security option of inbound packet changes report an error against the remote implementation. Otherwise, submit an SR.

CAUSE: The TCP SIP tossed an inbound packet due to unmatched precedence or security to the intended socket.

ACTION: Informative message. No action required.

CAUSE: A packet was received by a connection which had the syn flag set and was within window. This is a remote protocol violation. The connection will abort.

ACTION: Remote protocol error indication. Use tracing or line analysis to capture connection dialog. Report an error against remote implementation.

CAUSE: A packet was received by a connection which had the syn flag set and was within window. This is a remote protocol violation. The connection will abort.

ACTION: Remote protocol error indication. Use tracing or line analysis to capture connection dialog. Report an error against remote implementation.

CAUSE: A packet was received without the ACK flag set by a connection in a state in which such a packet is not acceptable. The packet will be ignored. This is a remote protocol violation.

ACTION: Remote protocol error indication. Use tracing or line analysis to capture connection dialog. Report an error against remote implementation.

CAUSE: A packet was received without the ACK flag set by a connection in a state in which such a packet is not acceptable. The packet will be ignored. This is a remote protocol violation.

ACTION: Remote protocol error indication. Use tracing or line analysis to capture connection dialog. Report an error against remote implementation.

CAUSE: A packet was received without the ACK flag set by a connection in a state in which such a packet is not acceptable. The packet will be ignored. This is a remote protocol violation.

ACTION: Remote protocol error indication. Use tracing or line analysis to capture connection dialog. Report an error against remote implementation.

CAUSE: A packet was received with an invalid ACK status. The packet will be ignored.

ACTION: Remote protocol error indication. Occasional occurrences are acceptable. Excessive occurrences indicate an error with either the remote or local connection half's tracking of current sequence number statuses. Submit an SR; report an error against the remote implementation.

CAUSE: A packet was received with an invalid ACK status. The packet will be ignored.

ACTION: Remote protocol error indication. Occasional occurrences are acceptable. Excessive occurrences indicate an error with either the remote or local connection half's tracking of current sequence number statuses. Submit an SR; report an error against the remote implementation.

CAUSE: A packet was received with an invalid ACK status. The packet will be ignored.

ACTION: Remote protocol error indication. Occasional occurrences are acceptable. Excessive occurrences indicate an error with either the remote or local connection half's tracking of current sequence number statuses. Submit an SR; report an error against the remote implementation.

CAUSE: The remote connection half has sent data with a sequence number which exceeds the fin sequence number which the remote sent previously. This is a remote protocol violation.

ACTION: Capture data traffic including offending fin and following data packet using tracing or a line analyzer. Report an error against the remote implementation.

CAUSE: The remote connection half has sent data with a sequence number which exceeds the fin sequence number which the remote sent previously. This is a remote protocol violation.

ACTION: Capture data traffic including offending fin and following data packet using tracing or a line analyzer. Report an error against the remote implementation.

CAUSE: The remote connection half has sent data with a sequence number which exceeds the fin sequence number which the remote sent previously. This is a remote protocol violation.

ACTION: Capture data traffic including offending fin and following data packet using tracing or a line analyzer. Report an error against the remote implementation.

CAUSE: The remote connection half has sent data with a sequence number which exceeds the fin sequence number which the remote sent previously. This is a remote protocol violation.

ACTION: Capture data traffic including offending fin and following data packet using tracing or a line analyzer. Report an error against the remote implementation.

CAUSE: The remote connection half has sent data with a sequence number which exceeds the fin sequence number which the remote sent previously. This is a remote protocol violation.

ACTION: Capture data traffic including offending fin and following data packet using tracing or a line analyzer. Report an error against the remote implementation.

CAUSE: The remote connection half has sent data with a sequence number which exceeds the fin sequence number which the remote sent previously. This is a remote protocol violation.

ACTION: Capture data traffic including offending fin and following data packet using tracing or a line analyzer. Report an error against the remote implementation.

CAUSE: The remote connection half has sent data with a sequence number which exceeds the fin sequence number which the remote sent previously. This is a remote protocol violation.

ACTION: Capture data traffic including offending fin and following data packet using tracing or a line analyzer. Report an error against the remote implementation.

CAUSE: A packet was received which contained a TCP header with a max tpdu option which had an incorrect option length in the option length field.

ACTION: Capture data traffic including offending data packet using tracing or a line analyzer. Report an error against the remote implementation.

CAUSE: TCP SIP sent out a reset for a packet with the ack flag set that was received on a socket in listen state.

ACTION: Informative message. No action required.

CAUSE: TCP SIP tossed a packet with the ack and syn flags set that was received for a socket in the listen state.

ACTION: Informative message. No action required.

CAUSE: Inbound packet received for a closed (not opened) sap, so the TCP SIP will send a reset.

ACTION: Informative message. No action required. Start service or open correct SAP if necessary. PARM is SAP for which packet is bound.

CAUSE: IPC called tcp_receive_reply, but TCP did not have any record of data outstanding to IPC.

ACTION: Submit an SR.

CAUSE: IPC called tcp_receive_reply, but TCP data indicates that IPC should not be in data receptive state.

ACTION: Submit an SR.

CAUSE: An attempt was made to start a TCP connection; however, the protocol was not active (i.e., was stopped).

ACTION: Informative message. Start the network if needed.

CAUSE: An attempt was made to open a TCP socket; however, the protocol was not active (i.e., was stopped).

ACTION: Informative message. Start the network if needed.

CAUSE: We received an inbound syn packet we will not process because the transport is not up.

ACTION: Informative message. Start the transport if needed.

CAUSE: The value in the KSO table for the TCP SIP data structure is nil when TCP_MODULE_DECONFIG is called.

ACTION: Look for startup errors. Submit an SR.

CAUSE: An attempt to create a TCP socket was made before the transport had been started.

ACTION: Informative message. Start the transport if needed.

CAUSE: An attempt to listen on a TCP socket was made before the transport had been started.

ACTION: Informative message. Start the transport if needed.

CAUSE: An attempt to shut down a TCP socket was made before the transport had been started.

ACTION: Informative message. Start the transport if needed.

CAUSE: An attempt to establish a TCP connection was made before the transport had been started.

ACTION: Informative message. Start the transport if needed.

CAUSE: User passed bad TCP control parameter through IPCCONTROL.

ACTION: PARM is value of offending control parameter. Fix offending program/service.

CAUSE: Number of configured retransmission retries exceeded. Connection will abort.

ACTION: Excessive retransmissions indicate a possible route/gate failure or possible end node failure or possible misconfiguration. Extreme network bottlenecks may also cause this type of problem although TCP should be able to adjust to most network conditions. A temporary work around may be to increase the configured number of maximum retransmissions. If a direct cause is not found consider further diagnosis with a line analyzer or submitting an SR.

CAUSE: The total retransmission time for a packet has exceeded the configured MAXIMUM TIME TO WAIT FOR REMOTE RESPONSE. Connection will abort.

ACTION: Excessive retransmission time indicates a possible route/gate/end node failure or possible misconfiguration. Extreme network bottlenecks may also cause this type of problem although TCP should be able to adjust to most network conditions. A temporary work around may be to increase the MAXIMUM TIME TO WAIT FOR REMOTE RESPONSE. If a direct cause is not found consider further diagnosis with a line analyzer or submitting an SR.

CAUSE: A valid reset packet was received on a connection. The connection will abort.

ACTION: Informative message. No action required. This message normally appears because the remote connection half was terminated abruptly by the user through an abortive IPC shutdown. Many services use this type of shutdown. Remote abortions also occur when errors are encountered on the remote system. In unexpected abortion situations inspection of the remote system for indications of error is suggested.

CAUSE: A valid reset packet was received on a connection. The connection will abort.

ACTION: Informative message. No action required. This message normally appears because the remote connection half was terminated abruptly by the user through an abortive IPC shutdown. Many services use this type of shutdown. Remote abortions also occur when errors are encountered on the remote system. In unexpected abortion situations inspection of the remote system for indications of error is suggested.

CAUSE: A valid reset packet was received on a connection. The connection will abort.

ACTION: Informative message. No action required. This message normally appears because the remote connection half was terminated abruptly by the user through an abortive IPC shutdown. Many services use this type of shutdown. Remote abortions also occur when errors are encountered on the remote system. In unexpected abortion situations inspection of the remote system for indications of error is suggested.

CAUSE: Connection Assurance timeout occurred for this connection. The remote node did not respond within the configured number of CA retries.

ACTION: Suspect remote node failure, or possible network failure.

CAUSE: BMGR_CREATE_POOL returned a bad status while trying to create the TCP control buffer pool. This would occur during network startup.

ACTION: PARM is BMGR error returned. Submit an SR.

CAUSE: BMGR_DELETE_POOL returned a bad status while trying to delete the TCP control buffer pool.

ACTION: PARM is BMGR error returned. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_process_inbound or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_read_completor or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_active_open or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_active_open or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_passive_open_reply or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_connection_shutdown or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_connection_shutdown or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_control or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_listen or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_socket_shutdown or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_create_socket or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_send or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_receive_reply or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_is_inbound_urgent or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_module_config or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_sip_main_loop or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure decipher_msg or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure decipher_ds_msg or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure decipher_ds_msg or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_sip_process_inbound or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_negative_advice or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_sip_icmp_req or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_sip_traceon or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_sip_traceoff or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_sip_net_stop or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_sip_route_valid or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_path_reply or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_pm_buffer_reply or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_passive_open or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_module_deconfig or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_driver_down or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_flush_sends or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_get_option or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: An unexpected escape occurred within the procedure tcp_set_option or some procedural unit called by it.

ACTION: PARM is escape code of escape. Submit an SR.

CAUSE: A TCP connection tossed a packet because it contained data which only duplicated data already received. This usually indicates an inbound retransmission for which the original has already been received.

ACTION: Informative message. No action required. Excessive retransmissions indicate either a faulty sending implementation or a noisy line.

CAUSE: A connection tossed a packet because of an invalid sequence number. May be caused by inbound retransmissions, connection assurance packets, or window probes.

ACTION: Informative message. No action required. Occasional occurrences normal. Excessive occurrences indicate abnormal software operation.

CAUSE: A connection tossed a packet because of an invalid sequence number. May be caused by inbound retransmissions, connection assurance packets, or window probes.

ACTION: Informative message. No action required. Occasional occurrences normal. Excessive occurrences indicate abnormal software operation.

CAUSE: A connection tossed a packet because of an invalid sequence number. May be caused by inbound retransmissions, connection assurance packets, or window probes.

ACTION: Informative message. No action required. Occasional occurrences normal. Excessive occurrences indicate abnormal software operation.

CAUSE: A connection tossed a packet because of an invalid sequence number. May be caused by inbound retransmissions, connection assurance packets, or window probes.

ACTION: Informative message. No action required. Occasional occurrences normal. Excessive occurrences indicate abnormal software operation.

CAUSE: A connection tossed a packet because of an invalid sequence number. May be caused by inbound retransmissions, connection assurance packets, or window probes.

ACTION: Informative message. No action required. Occasional occurrences normal. Excessive occurrences indicate abnormal software operation.

CAUSE: A packet was tossed because the connection it was destined for is no longer active.

ACTION: Informative message. No action required.

CAUSE: A TCP connection tossed a packet because it contained only out of window data. This may indicate strange behavior on the part of the sender or confusion on the part of the receiver.

ACTION: Informative message. No action required.

CAUSE: The TCP SIP tossed a packet from a half open connection because the TCP SIP was already processing another such packet.

ACTION: Informative message. No action required.

CAUSE: The TCP SIP tossed a packet from a half open connection because the TCP SIP was already processing another such packet.

ACTION: Informative message. No action required.

CAUSE: The TCP SIP tossed a packet from a half open connection because it couldn't get a route to send an outbound reset.

ACTION: Informative message. No action required. Possibly diagnose route resolution failure. Likely link/gate/nodal failure or configuration error.

CAUSE: The TCP SIP tossed a packet from a half open connection because it couldn't get a route, after waiting for a reply from paths, to send an outbound reset.

ACTION: Informative message. No action required. Possibly diagnose route resolution failure. Likely link/gate/nodal failure or configuration error.

CAUSE: The TCP SIP tossed a packet from a half open connection because it had the reset flag set.

ACTION: Informative message. No action required.

CAUSE: The TCP SIP tossed a packet because it had the reset flag set and destination socket was in the listen state.

ACTION: Informative message. No action required.

CAUSE: The retransmission interval for a packet has expired; however, a previous transmission of this packet has not yet left the node (or in loopback has not been released by the receiver).

ACTION: This indicates congestion within the node itself (e.g. the host running faster than the card can allow). Occasional occurrences are considered normal. Excessive occurrences (in other than loopback) indicate a more serious software problem.

CAUSE: An attempt was made to retransmit a packet in loopback.

ACTION: Repeated occurrences indicated a software problem.

CAUSE: The retransmission interval for a packet has expired without receipt of an acknowledgment from the remote connection half.

ACTION: This indicates network congestion, or a noisy or loss prone network. Occasional occurrences are considered normal. Excessive occurrences resulting in connection disconnects may indicate nodal/media failure, misconfiguration, severe network bottlenecks, or software failure.

CAUSE: An excessive number of retransmissions has caused a negative advice indication has been sent to the TCP SIP. The SIP will verify that our route to our destination is still correct.

ACTION: Informative message. No action required. This logging indicates that TCP has proactively detected potential route/link/gate/ring failure. If route validation fails and no new route to the remote host is found, diagnose route failure. Possibilities include node/media failure and misconfiguration.

CAUSE: A timer popped after it had already been released.

ACTION: Informative message. No action required. Occasional occurrences are normal. Excessive occurrences indicate the possibility of a software error.

CAUSE: An ICMP source quench packet has been processed for this TCP connection. The connection will treat the event as a Van Jacobson retransmission event.

ACTION: Informative message. No action required. Source quench indicates that some gateway in the path (or the receiving node) is running low on buffer space. Possibly increase gateway store and forward buffer pool size or receiving node's buffer pool size if configurable.

CAUSE: The user attempted to open a connection which already exists.

ACTION: User error. Isolate and correct offending program or service. Submit an SR if necessary.

CAUSE: We received an inbound syn for a connection that has already been established (same local and destination SAPS and IP addresses). We will ignore this SYN packet.

ACTION: Informative message. No action required.

CAUSE: The user or service (through IPC) has rejected the passive connection attempt, or an error has occurred on the connection since the passive open request was received.

ACTION: Informative message. PARM is rejection reason. If PARM is 0, user/service rejected the connection. Otherwise, an error condition has been detected by TCP. Look for logging indication of other error on same connection. (Remember that other logging classes may or may not be enabled.) Network/nodal shutdown processing may cause this error. If error is unexplainable, submit an SR.

CAUSE: TCP connection deactivated due to an error.

ACTION: Informative message. No action required. Error type may be normal or serious. Find matching error indication for connection and follow action text. (Remember that all classes of logging may not be enabled.)

CAUSE: User or service attempted to create TCP socket which already exists.

ACTION: Correct program/service in error or close previous socket incarnation.

CAUSE: TCP protocol start failed.

ACTION: Submit an SR.

CAUSE: Bad status returned in message from TCP SIP during a network startup. The TCP SIP wasn't created.

ACTION: PARM indicates status from message. Look for logging indication explaining TCP SIP initialization failure. Submit an SR.

CAUSE: TCP SIP portid was not found.

ACTION: Suspect error in protocol startup or protocol initialization. Look for logging indication explaining TCP SIP initialization failure. Submit an SR.

CAUSE: Error in protocol initialization.

ACTION: Look for logging indication explaining TCP SIP initialization failure. Submit an SR.

CAUSE: TCP KSO pointer value was NIL.

ACTION: Suspect error in protocol startup. Look for logging indication explaining TCP protocol startup failure. Submit an SR.

CAUSE: Bad port message of 'DS' type came to the TCP SIP.

ACTION: Submit an SR.

CAUSE: Bad port message of unknown type came to the TCP SIP.

ACTION: Submit an SR.

CAUSE: Inbound syn packet will not be processed because we will go over the TCP maximum connection limit if we do.

ACTION: Informative message. No action required. Increase configured TCP connection maximum if required and restart network.

CAUSE: The program TCPSIP.NET.SYS was invoked by a father process other than NMMON. The program will exit gracefully.

ACTION: Informative message. No action required.

CAUSE: An attempt was made to open more sockets than the maximum allowed on the system.

ACTION: Informative message. The maximum allowed sockets varies directly with the configured number of connections. Increase the configured number of connections and restart the network.

CAUSE: TCP connection (PM) activated.

ACTION: Informational message. No action required.

CAUSE: Graceful connection shutdown complete.

ACTION: Informational message. No action required.

CAUSE: TCP connection deactivated without error.

ACTION: Informational message. No action required.

CAUSE: TCP socket opened.

ACTION: Informational message. No action required.

CAUSE: TCP socket closed.

ACTION: Informational message. No action required.

CAUSE: TCP protocol started.

ACTION: Informational message. No action required.

CAUSE: The TCP SIP has been started.

ACTION: Informational message. No action required.

CAUSE: TCP protocol stopped.

ACTION: Informational message. No action required.

CAUSE: TCP SIP process stopped.

ACTION: Informational message. No action required.

CAUSE: TCP SIP process stopped.

ACTION: Informational message. No action required.

CAUSE: TCP protocol stopped.

ACTION: Informational message. No action required.

CAUSE: Network shut message processed for parm> ip_addr.

ACTION: Informational message. No action required.

CAUSE: Asynchronous driver error occurred for parm> ip_addr.

ACTION: Informational message. No action required.

CAUSE: Path_verify message from NETCP processed for parm> ip_addr.

ACTION: Informational message. No action required.

CAUSE: The global TCP statistics are being recorded.

ACTION: Statistical message. No action required.

CAUSE: Specific statistics related to the efficiency of the hash table are being recorded.

ACTION: Statistical message. No action required.

CAUSE: A TCP connection is shutting down and recording its statistics.

ACTION: Statistical message. No action required.