Tproxytrace is a RiOS specific command to probe for Steelhead appliances in the path to a remote server. It sends a SYN+ packet, and any Steelhead appliance in the path that answers the auto-discovery probe will have their information displayed.
The tproxytrace command does not support IPv6 destinations.
The following options are available for the tproxytrace command:
The option
-i <interface-name>
specifies the interface which outgoing packets will use and thus
which IP address will be used for them.
The tproxytrace command does not use the IP address of the primary
interface by default. Use the
-i
option to specify the outgoing interface:
Figure 3.47. Tproxytrace to a host via the primary interface
SH # tproxytrace -i primary 192.168.1.1:139 Probe from 10.0.1.5 (primary) to 192.168.1.1:139 depth 1 proxy 10.0.1.6:7800 depth 2 proxy 192.168.1.1:7800
Figure 3.48. Tproxytrace to a host via the in-path interface
SH # tproxytrace -i inpath0_0 192.168.1.1:139 Probe from 10.0.1.6 (inpath0_0) to 192.168.1.1:139 depth 1 proxy 192.168.1.1:7800
There could be various reasons, including:
The path the SYN+ takes doesn't have a Steelhead appliance in it.
The Steelhead appliances in the path are configured to not peer with the source specified.
The Steelhead appliances in the path cannot send the answer back to the source of the SYN+.
The auto-discovery TCP option number used in the SYN+ is different than the one used on the Steelhead appliances in the network.
The expected Steelhead appliances in the network are in admission control.