Applicable Delphix Versions
This article applies to the following versions of the Delphix Engine:
|5.3||22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168 22.214.171.124, 126.96.36.199|
|5.2||188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206|
220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206
The Delphix Engine establishes connections to databases and host environments in a number of ways including JDBC and ssh.
Delphix documentation has a comprehensive list of incoming and outgoing ports that need to be accessible for each of the data platforms supported (search the documentation site for the key words "Network and Connectivity Requirements"). Very often when setting up new environments it is necessary to test connectivity between the Delphix Engine and a listening port on another host. Customers can easily test connectivity to ports listening on the Delphix Engine from their own hosts using various tests (telnet, mconnect, netcat, nc, etc.). Since customers do not have access to operating system commands on the Delphix Engine, connectivity to ports on other hosts can be tested from the Delphix Command Line Interface (CLI).
Troubleshooting Connectivity to a Specific TCP Port
Most frequently this error presents itself when adding a new environment or linking a new dSource with an error message indicating a failure to connect to a specific port:
The TCP/IP connection to the host 10.12.0.6, port 1433 has failed. Error: "Connection timed out: no further information. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.".
It is also possible to see this type of error message in existing environments for various reasons (database is down, firewall or networking changes, et cetera).
If you know the listening port number (or it is displayed in the error message), the "ssh" test from the Delphix Command Line Interface (CLI) using an Admin login (delphix_admin or admin, by default, but any Admin user is permissible) can be used to exercise a connection to the desired host and port. Unless you are testing connectivity to an actual ssh port, it is perfectly acceptable to use a dummy user name and password.
The "jdbc" test is only compatible with Oracle at the time of this writing.
The "connector" test is used for testing connectivity to the Delphix Connector running on Windows hosts.
Configuring the test parameters
$ ssh email@example.com Password: 10.120.1.50> connectivity 10.120.1.50 connectivity> ls Operations connector jdbc ssh 10.120.1.50 connectivity> ssh 10.120.1.50 connectivity ssh *> ls Properties type: SSHConnectivity address: (required) credentials: type: KerberosCredential port: 22 (*) username: (required) 10.120.1.50 connectivity ssh *> set address=10.124.0.6 10.120.1.50 connectivity ssh *> set port=12345 10.120.1.50 connectivity ssh *> set username=dummyuser 10.120.1.50 connectivity ssh *> set credentials.type=PasswordCredential 10.120.1.50 connectivity ssh *> set credentials.password=dummypassword
Test Results - Pre-Delphix 5.3.x
In Delphix 5.1.x-5.2.x, the "Diagnoses" indicates whether the Delphix engine can successfully reach the port on the specified host.
5.1.x-5.2.x Connection failed
10.120.1.50 connectivity ssh *> commit Error: Unable to SSH to host "10.124.0.6". Action: Make sure "10.124.0.6" is running and is reachable via SSH from the Delphix Engine. Diagnoses: Failure:Could not connect on SSH port 12345 on host "10.124.0.6".
5.1.x-5.2.x Successful connection (Reached a server process listening on the specified port)
10.120.1.50 connectivity ssh *> set port=1433 10.120.1.50 connectivity ssh *> commit Error: Unable to SSH to host "10.124.0.6". Action: Make sure "10.124.0.6" is running and is reachable via SSH from the Delphix Engine. Diagnoses: Success:Reached a server listening on port 1433 on host "10.124.0.6" from the Delphix Engine.
Test Results - Delphix 5.3.x
In Delphix versions 5.3.x, Diagnoses is now Output, and the possible results are:
5.3.x Successful connection (remote server closes connection, confirming we reached a remote service)
delphix connectivity ssh *> commit Error: An error occurred when attempting to connect to remote host "localhost". Action: Check connectivity to the host and try again. Verify the host address is correct for the environment. Output: net.schmizz.sshj.transport.TransportException: Server closed connection during identification exchange
5.3.x Connection failure (remote server is not listening on the given port but the test did reach it successfully)
delphix connectivity ssh *> set port=800 delphix connectivity ssh *> commit Error: An error occurred when attempting to connect to remote host "localhost". Action: Check connectivity to the host and try again. Verify the host address is correct for the environment. Output: java.net.ConnectException: Connection refused (Connection refused)
5.3.x Connection failure (cannot reach the address/port specified)
This result can indicate an unreachable address provided, bad routing configuration, or a firewall connection failure.
delphix connectivity ssh *> commit Error: An error occurred when attempting to connect to remote host "220.127.116.11". Action: Check connectivity to the host and try again. Verify the host address is correct for the environment. Output: java.net.ConnectException: Connection timed out (Connection timed out)
If it is unable to successfully reach the port, make sure that there is a process listening on the port by logging in directly to the specified host and issuing the netstat command:
UNIX: netstat -an | grep 5400 tcp 0 0 10.43.16.80:5400 0.0.0.0:* LISTEN Windows: netstat -an | find "1433" TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING
If you are able to confirm that the port is listening on the IP (or ANY 0.0.0.0) address but Delphix cannot reach the host, please raise a ticket with your network/firewall team to request connectivity be granted between the two hosts.