At a Glance
|Description:||This page describes how to test and troubleshoot a failed Masking Connector using the CLI (and other commands).
The tests below are to verify that the host is reachable and that the port accepts connections. For detailed tests, it is recommended to use a SQL Editor Tool or FTP/SFTP client.
|CLI:||To test a connection using the CLI - (see below for example):
CLI> connectivity shh
|Success:||Successfully connect to host and service (shh login fails with the error):
Server closed connection during identification exchange
|Failure - port:||Successfully connect to host. Error, the port is not listening:
Connection refused (Connection refused)
|Failure - host:||Error: Cannot reach the host.
Connection timed out (Connection timed out)
|Other commands:||Other tools/commands that can be used to test the connection are:
SQL Editor | FTP | SFTP Client
Command Line: ping
Command Line: telnet
telnet [IP_Addr|Hostname] [port]
Command Line: nc
nc -zv [IP_Addr|Hostname] [port]
|Verify host port:||The commands below can be used to verify that the port is listening on the host:
netstat -an | grep [port]
netstat -an | find "[port]"
|Troubleshooting:||For details on how to review errors in logs and other topics, see the Related Topics section.|
If a Masking Connector is failing with a timeout or other connectivity error - one way to isolate the issue can be to verify that the host can be reached and the port accepts connections.
Since the 'Command-Line' is not accessible, this KBA describes an alternative method that uses a tool available in the Delphix Engine CLI (Command Line Interface).
Applicable Delphix Versions
- Click here to view the versions of the Delphix engine to which this article applies
Major Release All Sub Releases 6.0 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, 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, 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, 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, 220.127.116.11, 18.104.22.168, 22.214.171.124
The following CLI command can be accessed using the Continuous Data Engine (formerly Virtualization Engine) admin user. In order to test this, you need a Continuous Data Engine admin user and password (on the Continuous Compliance Engine (formerly Masking Engine)).
- ssh (or use PuTTY) to the engine.
- Login using a engine admin user.
- Go to 'connectivity' and then 'ssh'.
- Specify host address and port.
- Specify dummy for user and password (we are using dummy as we are only testing the host and the port).
- Type commit to start the test.
$ ssh VE_admin@Your_DCCE Password: Your_DCCE> connectivity Your_DCCE connectivity> ssh Your_DCCE connectivity ssh *> set address=[IP_Addr|Hostname] Your_DCCE connectivity ssh *> set port=[Port] Your_DCCE connectivity ssh *> set username=dummy Your_DCCE connectivity ssh *> set credentials.type=PasswordCredential Your_DCCE connectivity ssh *> set credentials.password=dummy Your_DCCE connectivity ssh *> commit
Use this to exit when done:
Your_DCCE connectivity ssh *> discard Your_DCCE connectivity> exit
All test connections will fail (as we are using SSH and dummy user). This is acceptable. We are going to use the response code to determine if the host can be reached and the port accepts connections.
The first two lines (Error and Actions) should be ignored. Example below:
Your_DCCE connectivity ssh *> commit Error: An error occurred when attempting to connect to remote host "[IP_Addr|Hostname]". Action: Check connectivity to the host and try again. Verify the host address is correct for the environment.
This message indicates the host can be reached and the port accepts connections. The output is an error message when the connection failed to log in to the (ssh) service.
Output: ...: Server closed connection during identification exchange
Failure - port not listening
If the test fails to connect to the port the following message is shown:
Output: ...: Connection refused (Connection refused)
Failure - host cannot be reached
If the host cannot be reached, then the connection fails with a timeout (the connection test will try x minutes and then timeout the connection):
Output: ...: Connection timed out (Connection timed out)
The following articles may provide more information or related information to this article: