sys-cmd traceroute

sys-cmd traceroute lists in order the intermediate routers that a packet going to a target from the route table selected in WEB-CLI passes through, and shows the latency of every step. It is used to find where the packet stops when the target cannot be reached.

Command Summary

TR7 WEB-CLI · sys-cmd traceroute

# type traceroute and press Tab: a free parameter

admin@TR7LBWAF01> sys-cmd traceroute

<traceroute-parameter-1>

 

admin@TR7LBWAF01> sys-cmd traceroute <parameters> <target>

admin@TR7LBWAF01>  

Everything written after the word traceroute is passed to the tool as it is. There is no mandatory field; the target address or name is written together with the parameters according to the tool's own syntax.

How It Works

Subject	Behavior
Context	The packets are sent from within the selected v-device and route table; the first step is the gateway of that route table.
Duration	It closes by itself when it reaches the target or when it comes to the maximum number of steps. Every step that does not respond lengthens it by the waiting time.
Stopping	Ctrl+C stops the tool.
Pipe	The output can be filtered with | or written to a file with to-file.
Recording	Every run is written to the user logs.

Frequently Used Parameters

Parameter	What it does	What is written after it
-n	Does not resolve the addresses to names; the output comes faster	—
-I	Uses ICMP as the probe packet; it is useful on networks that drop UDP probes	—
-m	Determines the maximum number of steps to be tried	A number (e.g. 15)
-w	Determines the response waiting time for each probe	Seconds
-q	Determines the number of probes to be sent at each step	A number (e.g. 1)

The table summarizes frequently used parameters; the full list and behavior depend on the version of the tool on the device.

Examples

TR7 WEB-CLI · A) A fast trace without name resolution

admin@TR7LBWAF01> sys-cmd traceroute -n 10.20.0.15

admin@TR7LBWAF01>  

TR7 WEB-CLI · B) With ICMP, at most 15 steps

admin@TR7LBWAF01> sys-cmd traceroute -n -I -m 15 192.0.2.10

admin@TR7LBWAF01>  

TR7 WEB-CLI · C) A single probe per step, a short wait

admin@TR7LBWAF01> sys-cmd traceroute -n -q 1 -w 2 198.51.100.20

admin@TR7LBWAF01>  

Things to Know

• The * * * lines. They mean that the router at that step does not respond to the probe packets; many firewalls do this deliberately. If the following steps continue to appear, the path is not cut. The probe type is changed with -I and tried again.
• The path is clean up to the last step but the target is silent. The problem is not on the path but in the target itself; it is tested at the port level with nmap or curl.
• An unexpected gateway at the first step. The selected route table may be wrong; the current context is verified with route-table show.