NS3000/iX Error Messages Reference Manual (36923-90043)

108 Chapter10
Network Transport Protocol (PMERR) Error Messages
ACTION: There are many possible reasons for a retransmission time out
to occur. Potential problems include severe network bottlenecks, remote
system CPU starvation, incorrect or improperly tuned configuration,
remote node failure, gateway or network failure, and servers which are
not processing new connection requests (or which are becoming
backlogged). Check for remote system and network failure first. If there
is no problem reaching the remote system, then the problem is most
likely a system or network load problem. Check CPU usage on remote
system and/or network traffic capacity especially at gateways or over
slow (non-LAN) links. Also, if the problem is at connect time, check that
the remote server is processing connection requests in a timely manner.
Also see the NS 3000/iX NMMGR Screens Reference Manual for a
discussion on tuning TCP retransmission parameters.
-81 MESSAGE: RETRANSMISSION TIMEOUT EXCEEDED
CAUSE: A TCP connection did not receive any acknowledgment from the
remote connection half for a data packet within the configured MAXIMUM
TIME TO WAIT FOR REMOTE RESPONSE.
ACTION: There are many possible reasons for a retransmission time out
to occur. Potential problems include severe network bottlenecks, remote
system CPU starvation, incorrect or improperly tuned configuration,
remote node failure, gateway or network failure, and servers which are
not processing new connection requests (or which are becoming
backlogged). Check for remote system and network failure first. If there
is no problem reaching the remote system, then the problem is most
likely a system or network load problem. Check CPU usage on remote
system and/or network traffic capacity especially at gateways or over
slow (non-LAN) links. Also, if the problem is at connect time, check that
the remote server is processing connection requests in a timely manner.
Also see the NS 3000/iX NMMGR Screens Reference Manual for a
discussion on tuning TCP retransmission parameters.
-82 MESSAGE: CONNECTION ASSURANCE TIMEOUT
CAUSE: A TCP connection has not received any acknowledgment from
the remote connection half within the configured number of connection
assurance retries; therefore we assume that the remote system half has
experienced an abrupt termination.
ACTION: Check for remote system failure or network failure. If both the
network and the remote system are intact, you may wish to readjust
the time out parameters, or disable the connection assurance function
by configuring a maximum of zero retries.
-90 MESSAGE: PATH FAILURE
CAUSE: The operation failed because TCP was unable to resolve a path
to the remote system.
ACTION: Check for proper network configuration. If the configuration
appears correct, enable Class 5 logging for NS Transport if not already