Forum Discussion
T0nyP
Cirrus
CirrusIs there a traceroute equivalent in F5 like the format of ping -I <source ip> <destination ip>
Hi F5 Community,
Is there a traceroute equivalent in F5 like the format of ping -I <source ip> <destination ip>?
Can I ask what is the exact command for traceroute or tracepath?
Or it is not possible?
Thanks much in advance.
Hi T0nyP,
Yes, this should work if the self IP is in route domain 0.
Cheers, Kai
Hi T0nyP ,
F5 is Linux based so you can use normal Linux traceroute and all of its switches :
check below urls contain Traceroute with more and more details , you can use it with F5 bash shell :https://www.computerhope.com/unix/utracero.htm
https://www.geeksforgeeks.org/traceroute-command-in-linux-with-examples/
I use it and it is very useful.
regards- T0nyP
Thank you and really appreciate the feedback.
Just want to check. I don't have a linux as of the moment.
Would this run using below command?
traceroute -s <source ip> -g <gateway ip> <destination ip or fqdn>
Hello T0nyP ,
No need to identify your gateway when performing traceroute ,
F5 does this path trace according to Routing table.
> you can force your F5 appliance to check the path by using "traceroute -s " as you did.> I checked this option in F5 bash and it doesn’t work as you said , but there is no need to identify the gateway or next hop , F5 uses ( the gateway or next hop from the "forced source ip " subnet that you identified in your command ".
> I want to say even if you specified the gateway , and overwrite the one which specified in f5 routing table/next hop , it is a wrong practise to use and it shouldn’t work.
> this is my explanation according to what I understood.
Kindly clarify more , I will follow up with you.
Regards
- Kai_Wilke
MVP
Hi T0nyP,
you need to start a SSH connection to your LTM using either the build-in "root" account or a custom user account with "advanced shell" permissions.
Then you could issue either a "PING" or "TRACEROUTE" command. To specifiy a source IP your have to use the command line switches outlined in the sample below:
[itacs@kw-f5-dev:Active:Standalone] ~ # traceroute -s 10.0.0.1 8.8.8.8 [itacs@kw-f5-dev:Active:Standalone] ~ # ping -I 10.0.0.1 8.8.8.8To understand the valid command line options of those commands you can read the man pages of the command via:
[itacs@kw-f5-dev:Active:Standalone] ~ # man ping [itacs@kw-f5-dev:Active:Standalone] ~ # man tracerouteSpecial Note: If you are working with route domains you may need to prefix the "ping" or "traceroute" command with the "rdexec" command. See the samples below how to execute command for e.g. Route-Domain 20:
[itacs@kw-f5-dev:Active:Standalone] ~ # rdexec 20 traceroute -s 10.0.0.1 8.8.8.8 [itacs@kw-f5-dev:Active:Standalone] ~ # rdexec 20 ping -I 10.0.0.1 8.8.8.8Cheers, Kai
mihaicyou should be able to do this:
run util traceroute -s self_non-floating_IP destination_IP
