Basic checks

Basic sanity checks such as network port health, DNS health, and external communications can be run from a JACE.

Network port health

Log into the JACE through the USB port (see the JACE-8000 Install and Startup Guide) and enter sh to get a shell.
Run ifconfig to see if the JACE has an IP address. Output should be similar to that shown.
Figure 11. Network port health

Line 6 starts the display of information about the primary network port and line 12 starts the display of the secondary network interface.

Line 8 indicates that the primary interface is currently connected where as line 14 indicates that the secondary interface is not connected. Lines 9 and 10 show the v4 and v6 IP address of the primary interface.

DNS health

To test that DNS is working you can attempt to ping your favorite web site and see if it is able to get an IP address for it.

NOTE: Most web sites will not respond to ping requests but for DNS testing you should get a response.

Figure 12. Using ping to test DNS health

In the example above we know DNS is working since www.google.com is resolved to an IP address, in this case 216.58.216.4.

Below is an example where DNS lookup failed. Note that it usually takes a short time for the test to fail since the JACE needs to time-out waiting for the DNS server to respond.

Figure 13. DNS health2

External communication

To test that we can establish a secure connection to the outside world we can use serial shell (ssh) and attempt a connection to the Device Registration Service. For this test enter the host name of the Device Registration URL in your CloudConnector.

Figure 14. External communication

You will need to use the fully qualified path to the ssh command. You will also need to specify the -v verbose flag to see what is happening.

Line 4 shows that we were able to successfully connect to the Device Registration Service. Since we are connecting to a web server and not a sshd server the connection will hang and you will need to enter Ctrl+C to get out of the command.