Wednesday, May 20, 2009

Tool of the Day: MTR

MTR is a great little tool for running sequential traceroutes and presenting a readable format for analysis. MTR stands for My TraceRoute and I just used it to prove the "expert" engineers at one of the top 3 ISP's in South Africa where problems on our ADSL system were.

A sample output from running MTR produces:

[root@nas ~]# mtr -c 25 -r 66.212.227.1
HOST: nas Loss% Snt Last Avg Best Wrst StDev
1. nas 0.0% 25 0.7 0.8 0.7 2.7 0.4
2. 196.213.232.169 0.0% 25 15.8 15.8 14.5 24.7 2.0
3. cdsl1-rba-vl144.isdsl.net 0.0% 25 15.1 15.7 14.4 18.2 1.1
4. core1b-rba-gi1-0-5.ip.isnet. 0.0% 25 15.8 25.5 14.5 196.5 37.5
5. mi-za-rba-p6-gi0-1-6.ip.isne 0.0% 25 188.3 189.6 188.3 196.7 2.0
6. mi-uk-dock-p2-po2-3.ip.isnet 0.0% 25 188.4 191.4 187.9 248.8 12.0
7. core1a-dock-gi1-0-19-24.ip.i 0.0% 25 188.3 195.2 188.1 272.8 22.5
8. cp1-dock-gi0-1.ip.isnet.net 4.0% 25 363.7 266.3 188.7 379.1 64.0
9. 0.ge-2-1-0.rt1.lthn.mohawk.c 12.0% 25 435.6 442.4 378.1 517.7 39.9
10. 0.so-0-0-2.cr2.kdca.mohawk.c 12.0% 25 525.0 525.0 468.1 587.4 34.2
11. t13-2.dr2.kdca.mohawk.ca 20.0% 25 512.1 505.8 486.0 524.4 10.3
12. pix 4.0% 25 556.2 528.2 466.6 597.5 30.9

Basically it pings the hops sequentially so you can spot at which point packet loss occurs, or high latency kicks in. Our ISP engineers were squawking about upgrading router IOS, etc.. but this conclusively proved that the problem as at the far end in the USA landing sites.

If you aren't lucky enough to use Linux or FreeBSD (Its in the ports system) there is a Windows 2000/XP/2003 implementation here: http://winmtr.sourceforge.net/

Anyways this saved me a lot of time and effort in fighting with my ISP, hope it helps you...

No comments:

Post a Comment