mtr on Juniper
Usually when you want to trace the path through the network that the packets take to reach a destination, you are using traceroute on Juniper devices.
However, this doesn’t give you the ability to see if there is any packet loss towards destination.
You can use ‘ping’ to check the packet loss, but you will not know where the packets are dropped.
root@r4> traceroute 172.27.255.6 traceroute to 172.27.255.6 (172.27.255.6), 30 hops max, 40 byte packets 1 172.27.0.25 (172.27.0.25) 25.162 ms 19.146 ms 18.079 ms 2 172.27.0.21 (172.27.0.21) 20.222 ms 19.328 ms 20.204 ms 3 172.27.255.6 (172.27.255.6) 30.143 ms 29.482 ms 30.406 ms root@r4>
To overcome this limitation, you can use ‘traceroute monitor’, which is something similar to mtr utility from Unix/Linux systems:
root@r4> traceroute monitor 172.27.255.6 My traceroute [v0.69] r4 (0.0.0.0)(tos=0x0 psize=64 bitpattern=0x00) Mon Sep 29 07:55:56 2014 Keys: Help Display mode Restart statistics Order of fields quit Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 1. 172.27.0.25 0.0% 3 20.1 20.2 20.1 20.2 0.1 2. 172.27.0.21 0.0% 3 30.0 27.3 21.3 30.4 5.1 3. 172.27.255.6 0.0% 3 30.4 30.5 30.4 30.5 0.1
Nice, isn’t it?
The following two tabs change content below.
Paris ARAU
Paris ARAU is a networking professional with strong background on routing and switching technologies. He is a holder of CCIE R&S and dual JNCIE(SP and ENT). The day to day work allows him to dive deeply in networking technologies. Part of the continuously training, he is focusing on Software Defined Network and cloud computing.
Latest posts by Paris ARAU (see all)
- Junos Fusion – Part IV – Satellite policies and uplink failure detection - 30 July 2018
- Junos Fusion – Part III – Satellite commands and traffic forwarding - 16 July 2018
- Junos Fusion – Part II – Configuration, Administration and Operation - 16 July 2018
- Junos Fusion – Part I – Overview, Components, Ports and Software - 11 July 2018
- Vagrant – Part IV – Network topology using Juniper and Cumulus - 26 April 2018
This is quite useful. It seems it’s available for some times on Junos.
MTR on Junos is nice but they’re stuck on a version from 2005 that doesn’t include UDP, MPLS, ASN, etc. support. It also doesn’t support routing instances so there’s no way to run it from a virtual router.
Yes Mark, you are right, there are some limitations with this feature.
No idea if there is any work in progress to overcome them.
Does it work with routing instance? I didn’t find any option for that
Hi,
It does not work in routing-instance.
Thanks,
Paris