Show TOC

Background documentationConnection Setup Errors Locate this document in the navigation structure

 

The following errors can occur during the connection setup:

  • Connect fails because the server is not running

  • TCP/IP connect takes too long (longer than the timeout -W value)

  • Route setup takes too long (longer than the timeout -W value)

  • No route permission for the connection

  • Error on the subsequent host

These errors are described below with possible solutions.

Connect fails (server not running)

The log file contains the following entries:

SAProuter Log File

Thu Jun 14 13:18:22 2007 CONNECT FROM C9/- host 10.66.66.90/35169 (host2.company.corp)

Thu Jun 14 13:18:22 2007 CONNECT TO S9/17 host 10.66.66.91/3299 (host1)

Thu Jun 14 13:18:22 2007 CONNECT ERR S9/17 connection refused

Thu Jun 14 13:18:22 2007 DISCONNECT S9/17 host 10.66.66.91/3299 (host1)

The client issues the error message below.

Syntax Syntax

SAProuter Error Message
  1. ***********************************************************************
    *  LOCATION    SAProuter 39.1 (SP3) on 'ld8060'
    *  ERROR       partner '10.66.66.91:3299' not reached
    *
    *  TIME        Thu Jun 14 13:18:22 2007
    *  RELEASE     710
    *  COMPONENT   NI (network interface)
    *  VERSION     39
    *  RC          -92
    *  MODULE      nixxi.cpp
    *  LINE        3068
    *  DETAIL      NiPConnect2: 10.66.66.91:3299
    *  SYSTEM CALL connect
    *  ERRNO       111
    *  ERRNO TEXT  Connection refused
    *  COUNTER     4
    ***********************************************************************
    
End of the code.
Background and Further Analysis

On the server side, there is no program running that listens to the IP address 10.66.66.91 and port 3299 (LISTEN). Check that the host name/IP address and server name/port number are correct. If they are correct, the right server is being reached but it appears that the program to which the connection should be established is not running. Check that the SAProuter and the system or corresponding program on the server is running and is using the correct port (OS command netstat -an).

TCP/IP connect takes too long (longer than the timeout -W value)

The log file contains the following entries:

SAProuter Log File

Thu Jun 14 13:22:01 2007 CONNECT FROM C10/- host 10.66.66.90/41060 (host2.company.corp)

Thu Jun 14 13:22:01 2007 CONNECT TO S10/18 host 1.1.1.1/3299 (1.1.1.1)

Thu Jun 14 13:22:06 2007 CONNECT ERR S10/18 could not establish connection within 5s

Thu Jun 14 13:22:06 2007 DISCONNECT S10/18 host 1.1.1.1/3299 (1.1.1.1)

The client issues the error message below.

Syntax Syntax

SAProuter Error Message
  1. ***********************************************************************
    *  LOCATION    SAProuter 39.1 (SP3) on 'ld8060'
    *  ERROR       connection to 1.1.1.1:3299 timed out
    *
    *  TIME        Thu Jun 14 13:22:06 2007
    *  RELEASE     710
    *  COMPONENT   NI (network interface)
    *  VERSION     39
    *  RC          -5
    *  MODULE      nirout.cpp
    *  LINE        6548
    *  DETAIL      RTPENDLIST::timeoutPend: could not establish connection within
    *              5s (ROUTED)
    *  COUNTER     6
    ***********************************************************************
    
End of the code.
Background and Further Analysis

In this example, the TCP/IP connection from the SAProuter to the next node (the next SAProuter, a system, or another network component) could not be established within a specified timeout period. This error can occur if the server host is down or the IP address of the host cannot be reached. It can also be due to the network failing to establish the TCP/IP connection within 5 seconds (the timeout value defined in option -W). You might be able to solve this problem by using a greater value for option -W.

For more information, see: Expert Options in SAProuter Options.

Route setup takes too long

The SAProuter is able to connect to the next host using TCP/IP, but the next host takes too long to establish the route to the destination. It receives no NI_PONG (confirmation that the route has been established) within the -W timeout period.

The log file contains the following entries:

SAProuter Log File

Thu Jun 14 13:34:19 2007 CONNECT FROM C15/- host 10.66.66.90/41070 (host2.company.corp)

Thu Jun 14 13:34:19 2007 CONNECT TO S15/23 host 10.21.72.60/3299 (host3)

Thu Jun 14 13:34:24 2007 CONNECT ERR S15/23 no route completion within 5s; check SAProuter on 'host3'

Thu Jun 14 13:34:24 2007 DISCONNECT S15/23 host 10.21.72.60/3299 (host3)

The client issues the error message below.

Syntax Syntax

SAProuter Error Message
  1. ***********************************************************************
    *  LOCATION    SAProuter 39.1 (SP3) on 'ld8060'
    *  ERROR       connection to host3:3299 timed out
    *
    *  TIME        Thu Jun 14 13:34:24 2007
    *  RELEASE     710
    *  COMPONENT   NI (network interface)
    *  VERSION     39
    *  RC          -5
    *  MODULE      nirout.cpp
    *  LINE        6537
    *  DETAIL      RTPENDLIST::timeoutPend: no route completion within 5s
    *              (ROUTED)
    *  COUNTER     17
    ***********************************************************************
    
End of the code.
Background and Further Analysis

Find out why the subsequent SAProuter was unable to establish the connection within 5 seconds (in this example). It might be due to slow name resolution, for example. The log and trace files should provide further information on this. In the case of connections using multiple SAProuters in a WAN environment, increase option -W. If multiple SAProuters are involved in setting up a connection and the network response times are relatively high, the default value of 5 seconds is not sufficient to enable the connection to the target system to be established.

For more information, see: Expert Options in SAProuter Options.

No route permission for the connection

The SAProuter rejects the connection because the route permission table does not allow it.

The log file contains the following entries:

SAProuter Log File

Thu Jun 14 14:18:20 2007 CONNECT FROM C10/- host 10.66.66.90/63669 (host2.company.corp)

Thu Jun 14 14:18:20 2007 PERM DENIED C10/- host 10.66.66.90 (host2.company.corp) to host1/3254

Thu Jun 14 14:18:20 2007 DISCONNECT C10/- host 10.66.66.90/63669 (host2.company.corp)

The client issues the error message below.

Syntax Syntax

SAProuter Error Message
  1. ************************************************************************  
    *  LOCATION    SAProuter 39.1 (SP3) on 'ld8060'
    *  ERROR       ld8060: route permission denied (host2.company.corp to
    *              host1, 3254)
    *
    *  TIME        Thu Jun 14 14:18:20 2007
    *  RELEASE     710
    *  COMPONENT   NI (network interface)
    *  VERSION     39
    *  RC          -94
    *  COUNTER     5
    ***********************************************************************
    
End of the code.
Background and Further Analysis

Checking the Route Permission Table

Error on the subsequent host

This error does not occur on the local SAProuter. Instead, it occurs on a subsequent host. Messages of the following type appear in the log of the local SAProuter:

SAProuter Log File

Thu Jun 14 14:42:53 2007 CONNECT FROM C10/- host 10.66.66.90/30005 (host2.company.corp)

Thu Jun 14 14:42:53 2007 CONNECT TO S10/18 host 10.21.72.60/3299 (host3)

Thu Jun 14 14:42:54 2007 CONNECT ERR S10/18 NIEROUT_INTERN on 'SAProuter 37.15 on hs0126'

Thu Jun 14 14:42:54 2007 DISCONNECT S10/18 host 10.21.72.60/3299 (host3)

The client issues the error message below.

Syntax Syntax

SAProuter Error Message
  1. ************************************************************************  LOCATION    SAProuter 37.15 on hs0126
    *  ERROR       partner not reached (host 10.66.66.91, service 3298)
    *
    *  TIME        Thu Jun 14 14:42:54 2007
    *  RELEASE     640
    *  COMPONENT   NI (network interface)
    *  VERSION     37
    *  RC          -93
    *  MODULE      nixxi.cpp
    *  LINE        8724
    *  DETAIL      NiPConnect2
    *  SYSTEM CALL SiPeekPendConn
    *  ERRNO       239
    *  ERRNO TEXT  Connection refused
    *  COUNTER     5
    ***********************************************************************
    
End of the code.

Or

SAProuter Log File

Thu Jun 14 14:40:28 2007 CONNECT FROM C9/- host 10.66.66.90/24016 (host2.company.corp)

Thu Jun 14 14:40:28 2007 CONNECT TO S9/17 host 10.21.72.60/3299 (host3), *** NATIVE ROUTING ***

Thu Jun 14 14:40:28 2007 CONNECT ERR S9/17 NIEROUT_PERM_DENIED on 'SAProuter 39.0 on 'host3'', *** NATIVE ROUTING ***

Thu Jun 14 14:40:28 2007 DISCONNECT S9/17 host 10.21.72.60/3299 (host3), *** NATIVE ROUTING ***

Syntax Syntax

SAProuter Error Message
  1. ***********************************************************************
    *  LOCATION    SAProuter 39.0 on 'host3'
    *  ERROR       host3: route permission denied (host2.company.corp to
    *              host1, 3253)
    *
    *  TIME        Thu Jun 14 14:40:28 2007
    *  RELEASE     710
    *  COMPONENT   NI (network interface)
    *  VERSION     39
    *  RC          -93
    *  COUNTER     3
    **********************************************************************
    
End of the code.
Background and Further Analysis

Check the log and trace files on the SAProuter where the error occurred if the information already provided is not sufficient. The SAProuter error message that is normally displayed on the client contains information on the error. The LOCATION line tells you the location of the error.