Traceroute is a network test that enables an Agent to verify the network path traversed to reach a destination device. The test also measures the Round Trip Time (RTT) of each router in the path. For each router, NetBeez also reports the reverse DNS name (PTR) and MTU size (when UDP or ICMP is selected as protocol). The Traceroute function included in NetBeez can run TCP, UDP, and ICMP-based tests.
Traceroute tests are configured as part of a target, or can also run standalone as an ad-hoc test (please review ad-hoc testing).

How to create a traceroute test


Step 1 -  Traceroute tests are created as part of a target.
Step 2 - In the target setup form click on the TRCRT button and input the following information:
  1. Source (Ad-hoc only, required): The Agent that will conduct the test.
  2. Destination (Ad-hoc only, required): The IP address or hostname of the remote device.
  3. Interval (Target-based test only, required): The number of seconds between two consecutive Traceroute queries. By default, the interval is 60 seconds.
  4. Test type (required): Chose between UDP, TCP, and ICMP.
  5. Advanced options (optional): Click the checkbox if advanced options are required.
    1. PORT number (optional): For UDP and TCP, set the base port number used in probes.  The default value is 33434.
    2. Timeout per-hop (optional): The number of seconds that the Agent will wait for a response from the router(s) in the path. The default value is 2 seconds.
    3. Max hops (optional): The maximum number of routers traversed to reach the destination. The default value is 30 hops.
    4. Queries per-hop (ad-hoc only): The number of queries per hop. The default value is 3
    5. TOS DSCP/PHB Class (optional): The DSCP value to be applied to the Traceroute packets. There is no default value.
Have more questions? Submit a request


Article is closed for comments.