Diagnostics

Use the tools provided to help diagnose communication or connection issues, trace network packets, or capture network packets.

Automatic diagnostic tests

Manual diagnostic tests

Automatic diagnostic tests

By default, the page opens to the Automatic tab. Click Run Diagnostics to execute all of the tests listed in the table. Connectivity is tested from the Content Gateway host machine to each of the servers listed under Test. In addition, the availability of the DNS servers is confirmed.

The IPv4 default gateway

The IPv6 default gateway

Your primary DNS server

Your secondary DNS server

download.forcepoint.com (a download server)

ddsdom.websense.com (a download server)

ddsint.websense.com (a download server)

my.websense.com (customer account portal)

Once the diagnostics are run, additional information is provided:

Result indicates whether the test is running, passed, failed, or could not complete.

Latency provides the round-trip latency of the Ping command used to test the connection. The value, reported in milliseconds, is the amount of time between the command being sent and the response being received from the server.

An empty latency value does not necessarily indicate a problem. Rather, it indicates either (a) that the test passed, but the packet that holds the value was banned by something in the network, or (b) that the test failed, and thus no latency value could be obtained.

If the value seems high (a full 10 seconds, for example) when compared to other latency values, it may indicate a problem in the network.

Details offers additional information for any test that failed or could not complete.

Below the table, the Last update information reflects the date and time the connections were last tested. Each time you access the page, the results of the last test will display.

Manual diagnostic tests

The Manual tab offers 4 commands typically run from the Linux command line.

Ping, used to determine if a remote device can be reached across the network.

Traceroute, used to determine the path network packets take and measure delays across the network.

NSlookup, used to obtain domain name or IP address mapping.

TCPDump, used to analyze network packets.

Click the radio button next to the command you want to execute and enter parameters for the command in the entry field provided.

Enter a server name or IP address for Ping or Traceroute.

Enter a server name for NSlookup.

Enter valid parameters for TCPDump. For additional information about using TCPDump with Content Gateway, see this article.

Click the Run button next to your selected command to execute the test. The results for Ping, Traceroute, and NSlookup display in the Test Results section at the bottom of the pane.

Test results for TCPDump are typically too long to easily display and review in the Test Results window. When TCPDump is run, the Test Results window simply indicates the success or failure of the command.

As TCPDump runs, output is written to /opt/WCG/logs/tcpdump.pcap. This file is overwritten each time TCPDump is executed. When a test is successful, a link is provided so that you can download and view or save a copy of the most recent file.

To avoid disk space problems, tcpdump.pcap is limited to 10,000 packets. Once that limit is reached, no additional output is written to the file.


	Important TCPDump uses a lot of system resources. Try to avoid using it during peak hours when the system is busy.

As each command executes, the Run button becomes a Stop button. Click Stop to abort the command.