Test Targets for Wired and Wi-Fi AutoTest

AutoTest Target tests are user-assignable endpoints to which EtherScope nXG attempts to connect each time the AutoTest profile runs. These tests ensure availability of internal or external websites, servers, and devices to users of your network.

Tap a link below to go to the test's topic:

Ping

TCP Connect

HTTP

FTP

Adding and Managing Test Targets

To add test targets to AutoTest profiles and manage your saved targets, open the Test Targets screen from either the Wired or Wi-Fi Profile Settings or by tapping the FAB on the Wired or Wi-Fi Profile results screens.

The Test Targets screen lists all of the defined and saved Test Targets. Checked boxes indicate the targets enabled in the current Profile. (Test Targets can be added to and used in any number of Wired or Wi-Fi Profiles.)

On the Test Targets screen, you can perform these actions:

• Select the checkboxes for each Target you want to include in the current profile.

• Tap the up and down arrows to reorder the saved Test Targets on this screen and the main AutoTest Profile screen.

• Tap the action overflow icon to Duplicate or Delete a target test.
  CAUTION! When you delete a Test Target, you delete it from all Profiles. To remove a Test Target from the current profile, simply uncheck it.

• Tap the FAB icon to add a new target test: Ping, TCP Connect, HTTP, or FTP.

  

• Tap any target test name to open that test's settings. You can then enter a custom test name, target address, or thresholds. For more information on settings, see:

  • Ping Test

  • TCP Connect Test

  • HTTP Test

  • FTP Test

Target Test Results Screens

The Target Test type icons display green, yellow, or red to indicate the status (or grade) of the completed test portions: Success/Warning/Fail.

As an example, in the Ping test image below, the entire Ping test is graded with a Warning because the third Ping was not returned within the Timeout Threshold configured in the settings.

The third Response Time displays two dashes -- to indicate that no response was received, and under the Results heading, the yellow dot points out the third Response Time as the reason for the Warning. Additionally, the third Result Code lists "Timeout error" as the reason for the Warning.

Additional Target Test Actions

After the Target test has completed, tap any of the blue links to perform additional actions, including opening other testing apps.

• Tap the blue linked Device Name to open a Discovery Details app screen for the selected device. From there, you can open other apps and run additional tests.

• Tap TEST AGAIN to run just the target test again.

• Tap PATH ANALYSIS to open the Path Analysis to app with the path destination configured with the current target.

• Tap the action overflow icon to open the listed apps or tools with the target pre-populated, for example:

  • Ping or TCP Connect to open the Ping/TCP app with the current target address.

  • Capture traffic from the test target.

  • Browse to the target URL on the internet with your web browser app.

  • Telnet or SSH to open the Telnet/SSH tools with the current target address.