[AusNOG] Latency Issue

arun arunramprasad at ymail.com
Tue Aug 2 10:11:38 EST 2016


Try to run a wireshark capture and check for TCP retransmissions. You might get some hint there.

Arun

> On 2 Aug 2016, at 8:55 AM, Bruce Forster <bruce at tubes.net.au> wrote:
> 
> id have to agree sounds like an mtu issue or something else is giving you problems i dont think a traceroute/mtr will give you much information regarding the pages not loading...
> 
> this document is really useful when trying to interpret mtr/traceroute data: https://www.nanog.org/meetings/nanog47/presentations/Sunday/RAS_Traceroute_N47_Sun.pdf
> 
> 
>> On Tue, Aug 2, 2016 at 8:10 AM, QCS Group - Infrastructure <Infrastructure at qcsgroup.com.au> wrote:
>> Web pages seems to timeout on first load attempt sometimes. Refresh and jumps through ok. Once loaded no issues at all. Just wondering if this could cause it or something else in the works
>> 
>> 
>> 
>> Sent from my Samsung device
>> 
>> 
>> -------- Original message --------
>> From: Philip Loenneker <Philip.Loenneker at tasmanet.com.au> 
>> Date: 2/08/2016 08:03 (GMT+10:00) 
>> To: ausnog at lists.ausnog.net 
>> Subject: Re: [AusNOG] Latency Issue 
>> 
>> Hi Marius,
>> 
>>  
>> 
>> Are you seeing “real world” traffic or performance issues, or only on the traceroute? A lot of routers dedicate resources to throughput rather than responding to ICMP, so it could be the specific hardware on AAPT’s network or their configuration. The fact that the later hops have consistent ping times, including all 3 paths being within 1ms of each other for the last hop, implies that traffic is flowing ok.
>> 
>>  
>> 
>> Regards,
>> 
>> Philip Loenneker | Network Engineer | TasmaNet
>> 
>> 40-50 Innovation Drive, Dowsing Point, Tas 7010, Australia
>> 
>> P: 03 6165 2542 | M: 0404 097 816
>> 
>> philip.loenneker at tasmanet.com.au
>> 
>> www.tasmanet.com.au
>> 
>>  
>> 
>> From: AusNOG [mailto:ausnog-bounces at lists.ausnog.net] On Behalf Of QCS Group - Infrastructure
>> Sent: Tuesday, 2 August 2016 7:55 AM
>> To: ausnog at lists.ausnog.net
>> Subject: [AusNOG] Latency Issue
>> 
>>  
>> 
>> Hi All,
>> 
>>  
>> 
>> Hoping someone could push me in the right direction, we have a rack in NextDC B1.
>> 
>>  
>> 
>> I am getting some strange latency issues when doing trace routes, we have 2 x BGP routes through AAPT, each one on a different AG Access, and also 1 BGP with Pipe networks.
>> 
>>  
>> 
>> Issue seems to be on the AAPT stuff, ping doesn’t seem so spike a lot but the traceroute is really an issue as sometimes it will actually timeout. Anyone ever seen this or have some guidance? Below is some logs
>> 
>>  
>> 
>> Using AAPT link 1
>> 
>> [admin at BGP1.DC1.QCSGROUP.COM.AU] > tool traceroute 8.8.8.8 routing-table=AAPT
>> 
>>  # ADDRESS                          LOSS SENT    LAST     AVG    BEST   WORST
>> 
>> 1 61.69.105.161                    7.6%  145   1.4ms    20.2     0.9   802.7
>> 
>> 2 203.131.62.32                      0%  145   0.7ms     2.1     0.7    71.7
>> 
>> 3 202.10.12.25                       0%  145   0.8ms     1.1     0.7     9.1
>> 
>> 4 202.10.12.18                       0%  145   0.7ms     2.9     0.6    85.4
>> 
>> 5 202.10.14.39                       0%  145   1.2ms     1.3     1.1       3
>> 
>> 6 203.219.107.209                    0%  145  13.9ms    14.1    13.8    14.4
>> 
>> 7 203.219.166.193                    0%  145  13.6ms    17.9    13.5   258.3
>> 
>> 8 203.219.107.113                    0%  145  16.2ms      15      13    16.8
>> 
>> 9 203.219.35.132                     0%  145  25.3ms    20.4    13.6    25.5
>> 
>> 10 203.219.107.6                      0%  144    14ms    14.6    13.9    40.7
>> 
>> 11 72.14.237.11                       0%  144  14.4ms    14.4    14.3    14.9
>> 
>> 12 216.239.40.255                     0%  144  14.4ms    14.4    14.3    16.2
>> 
>> 13 8.8.8.8                            0%  144  13.9ms    13.9    13.8    14.4
>> 
>>  
>> 
>> Using AAPT Link 2
>> 
>> [admin at BGP1.DC1.QCSGROUP.COM.AU] > tool traceroute 8.8.8.8 routing-table=AAPT1   
>> 
>>  # ADDRESS                          LOSS SENT    LAST     AVG    BEST   WORST
>> 
>> 1 59.100.211.221                    34%   54 timeout   102.7     0.8     822
>> 
>> 2 203.131.62.22                      0%   53   0.5ms       1     0.4    22.2
>> 
>> 3 202.10.14.39                       0%   53     1ms     1.2     0.9     2.3
>> 
>> 4 203.219.107.209                    0%   53  13.3ms    13.3    13.1    15.3
>> 
>> 5 203.219.166.129                    0%   53  12.9ms    15.6    12.8    85.8
>> 
>> 6 203.219.107.113                    0%   53  14.8ms    14.7    12.9    16.6
>> 
>> 7 203.219.35.132                     0%   53  22.7ms    19.3    14.6    24.5
>> 
>> 8 203.219.107.6                      0%   53  13.9ms    14.4    13.8      26
>> 
>> 9 216.239.41.51                      0%   53  14.3ms    14.3    14.2    14.4
>> 
>> 10 216.239.41.83                      0%   53  14.9ms    14.8    14.8    14.9
>> 
>> 11 8.8.8.8                            0%   53  13.8ms    13.8    13.7    14.4
>> 
>>  
>> 
>> Ping from AAPT
>> 
>> 112 61.69.105.161                              56  64 0ms 
>> 
>>   113 61.69.105.161                              56  64 1ms 
>> 
>>   114 61.69.105.161                              56  64 0ms 
>> 
>>   115 61.69.105.161                              56  64 0ms 
>> 
>>     sent=116 received=116 packet-loss=0% min-rtt=0ms avg-rtt=0ms max-rtt=2ms
>> 
>>  
>> 
>> Using Pipe
>> 
>> [admin at BGP1.DC1.QCSGROUP.COM.AU] > tool traceroute 8.8.8.8 routing-table=pipe-netw
>> 
>> ork
>> 
>>  # ADDRESS                          LOSS SENT    LAST     AVG    BEST   WORST
>> 
>> 1 203.192.85.233                     0%  150   0.7ms     1.1     0.2    36.9
>> 
>> 2 121.101.138.4                      0%  150  13.1ms    13.1    13.1    13.2
>> 
>> 3 121.101.138.230                    0%  150  13.1ms    13.2    13.1    24.2
>> 
>> 4 121.101.138.149                    0%  150  15.4ms    13.5    13.1    16.6
>> 
>> 5 218.100.2.97                       0%  150  13.6ms      14    13.6    44.4
>> 
>> 6 216.239.41.77                      0%  150  13.8ms    13.8    13.7    13.9
>> 
>> 7 209.85.244.15                      0%  150  13.6ms    13.6    13.6    13.7
>> 
>> 8 8.8.8.8                            0%  150  13.5ms    13.5    13.5    13.6
>> 
>>  
>> 
>> Thanks
>> 
>> Marius
>> 
>>  
>> 
>>  
>> 
>>  
>> 
>>  
>> 
>>  
>> 
>>  
>> 
>>  
>> 
>> Thinking of updating your phone system?
>> Ask us about our "Cloud Based PABX" solution before you do anything.
>> 
>>  
>> 
>> 
>> _______________________________________________
>> AusNOG mailing list
>> AusNOG at lists.ausnog.net
>> http://lists.ausnog.net/mailman/listinfo/ausnog
> 
> 
> 
> -- 
> Regards,
> 
> Bruce
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20160802/a2032e9d/attachment.html>


More information about the AusNOG mailing list