How-To utilize MTR to help realize packet loss

MTR represents a branch of the traceroute functionality by providing a greater data sample, as if expanding traceroute with ping to obtain realtime results. This utility helps determine if there are potential network related issues in regards to packet loss or configuration problems with routers. In your streaming workflow, this may be incredibly enlightening in trying to determine delays/buffering and packet loss thereof.

To run a single report, please try the following:

mtr –report thewowza.guru

This will produce a single output similar to the following:

$ mtr --report thewowza.guru
Start: Sat Jun 21 09:09:44 2014
HOST: player.localhost            Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 192.168.0.1                0.0%    10    0.5   0.5   0.4   0.6   0.0
  2.|-- 142.254.xxx.xx             0.0%    10    7.6   7.8   6.6   9.4   0.7
  3.|-- unalloc-024-031-xxx-xxx.s  0.0%    10   15.3  14.5  12.5  18.5   1.5
  4.|-- xe-5-1-1.xxxx-xxx.s        0.0%    10   20.6  20.1  16.9  28.8   3.2
  5.|-- bu-ether34.xxxx-bc         0.0%    10   32.6  34.0  32.6  36.6   1.3
  6.|-- bu-ether11.xxxx-bc         0.0%    10   44.0  34.8  32.0  44.0   3.3
  7.|-- 107.14.xx.xxx              0.0%    10   30.7  32.3  30.1  41.7   3.3
  8.|-- usr115.bb588-02.uad.xx.xx  0.0%    10   30.4  30.9  29.9  32.1   0.5
  9.|-- ash-bb4-xxx.xxx.net        0.0%    10   31.0  31.7  31.0  32.6   0.0
 10.|-- nyk-bb2-xxx.xxx.net        0.0%    10   91.2  49.7  36.8  91.2  19.8
 11.|-- nyk-b6-xxx.xxx.net         0.0%    10   41.9  40.2  37.1  50.4   4.0
 12.|-- xxxx-ic-xxxx-ny    0.0%    10   40.7  39.1  37.7  42.9   1.6
 13.|-- 192.241.xxx.xxx            0.0%    10   37.9  38.2  37.3  39.3   0.3
 14.|-- thewowza.guru              0.0%    10   38.6  38.3  36.8  44.0   2.0

To run a test that is more real-time and ongoing (similar to ping in this regard), you can run the following command line:

mtr thewowza.guru

A similar output is produced and continually updated:

                                                                                                                                                                                                                                                                                                                                                                                                                              Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 192.168.0.1 0.0%   131    0.5   0.4   0.3   0.9   0.0
 2. 142.254.xxx.xx  0.0%   131    7.5   8.5   6.6  25.5   2.1
 3. unalloc-xxx-xxx-202-xxx.sc.xx.com  0.0%   131   14.8  14.6  12.4  57.5   4.0
 4. xe-5-1-1.xxx-rtr1.xxx.xx.com  0.0%   131   16.8  18.8  15.9  27.2   1.7
 5. bu-ether34.xxxx-xxx.xxx.xx.com  0.0%   131   32.5  34.6  30.4  42.9   2.8
 6. bu-ether11.xxx-xxx.tbone.xx.com  0.0%   131   31.5  33.4  30.0  39.7   1.7
 7. xxx.14.17.1xx  0.8%   131   30.4  32.5  29.7  93.0   6.9
 8. usr115.xxxx-02.uad.im.xxx.xxx.jp 0.0%   131   31.7  32.2  29.2  74.1   4.5
 9. ash-bb4-xxx.xxx.net 0.0%   131   31.7  32.5  30.4  63.7   3.4
10. nyk-xxx-link.xxxx.net  0.0%   131   37.4  48.5  36.8 124.5  21.6
11. nyk-xxx-link.xxx.net 0.0%   131   40.9  39.1  36.5  84.4   4.6
12. xxxx-ic-302768-nyk-b6.c.telia.net  0.8%   131   38.2  39.8  36.7  83.5   6.3
13. 192.xxx.xxx.xxx 0.0%   131   41.2  38.8  36.7  61.1   2.6
14. TheWowza.guru  0.0%   130   38.3  38.6  36.8  46.0   1.4

You’ll notice that at some points you may see >0% in packet loss (in one spot) of which may be more attributed to rate-limiting vs. packet loss. Generally if you see several servers increased, this may suggest packet loss.


Comments are closed.