Connectivity Validation

Connectivity validation allows the execution of connectivity tests between a specific gateway pool and backends. The test can be executed by means of an address, domain or IP.

There are three validation commands available:

  • Ping: validates if the gateway can "reach" the backend.

  • Netcat: tests de TCP connection and checks if there is connectivity between the gateway pool and a specific backend communication port.

  • Traceroute: tracks the path that data takes across the internet when it leaves the gateway until it reaches its destination. It prints a list of addresses through which data has passed.

connectivity test
Figure 1. Connectivity test

How to use it

To validate if there is a connection:

  1. Select the command in the Command field;

  2. Type the destination address in the Address field;

  3. In case you selected the Netcat command, add the communication port in the Port field;

  4. Click Run and wait.

validation
Figure 2. Validation in progress
After validation runs, you can see the result at the bottom of the form.

See more information in the examples below:

Ping

Example 1

Validate if the destination sensedia.com is available from the gateway pool.

  • Result: positive validation. The destination is accessible.

ping ex 1
Example 2

Validate if the destination alias.xxxx-gateway-123.sensedia.net is available from the gateway pool.

  • Result: connectivity validation failed.

  • Possible causes:

    • There is no route to the address;

    • ICMP protocol blocked by firewall.

ping ex 2
Example 3

Validate the connection between the gateway pool and the address destino-inexistente.com.

  • Result: the address doesn’t exist.

  • Action: check the address and retest.

ping ex 3

Netcat

Example 1

Validate whether there is connectivity between the gateway pool and port 443 of the address sensedia.com.

  • Result: positive validation. There is connectivity.

netcat ex 1
Example 2

Validate whether there is connectivity between the gateway pool and port 222 of the address sensedia.com.

  • Result: negative validation. The Netcat command couldn’t find a connection with the address sensedia.com in the port 222.

  • Possible causes:

    • There is no route to the address;

    • Port closed by firewall;

    • Service disconnected in the destination.

netcat ex 2
Example 3

Validate if there is connectivity between the gateway pool and the address destino-inexistente.com.

  • Result: the address doesn’t exist.

  • Action: check the address and retest.

netcat ex 3

Traceroute

Example 1

Validate the data route from the gateway pool to the destination sensedia.com.

  • Result: the route validation to the destination sensedia.com was positive. No connectivity issues.

traceroute ex 1
Example 2

Validate if there is a route between the gateway pool and the address destino-inexistente.com.

  • Result: the address doesn’t exist.

  • Action: check the address and retest.

traceroute ex 2
Thanks for your feedback!
EDIT

Share your suggestions with us!
Click here and then [+ Submit idea]