Topic 'Re: TSI/HE.net performance/packet loss issue' in forum 'TekSavvy' - dslreports.com

Re: TSI/HE.net performance/packet loss issue

Mon, 03 Dec 2012 15:08:56 EDT

TSI Martin posted : It's probably to go from 3 to 4 Gig-E. Although I don't have specifics, our upgrade requests have always been for Gig-E.

Re: TSI/HE.net performance/packet loss issue

Mon, 03 Dec 2012 14:56:26 EDT

jmck posted : curious but what does St-Laurent currently have for capacity and what upgrade is happening, a single Gig-e?

Re: TSI/HE.net performance/packet loss issue

Mon, 03 Dec 2012 14:36:05 EDT

TSI Martin posted : It's to increase capacity.

Re: TSI/HE.net performance/packet loss issue

Mon, 03 Dec 2012 14:32:17 EDT

paul_ottawa posted : Thanks Martin - I guess I will be working from home that day after all.

Now for my uninformed self, when we're talking POI upgrades (since I never concerned myself with this in the past) are we talking new hardware to increase capacity, or hardware redundancy, or something totally different?

Re: TSI/HE.net performance/packet loss issue

Mon, 03 Dec 2012 12:51:40 EDT

jmck posted :

said by TSI Gabe:

the packet loss is occurring at the St-Laurent POI level. We've had an upgrade order on there for a while now and it's getting installed on December 11th (next week)

thanks for that.

Re: TSI/HE.net performance/packet loss issue

Mon, 03 Dec 2012 12:50:40 EDT

TSI Martin posted : As per past POI upgrades, no service interruptions occurred.

Re: TSI/HE.net performance/packet loss issue

Mon, 03 Dec 2012 11:43:36 EDT

paul_ottawa posted : Will the upgrade be seamless or can we expect an outage?

Re: TSI/HE.net performance/packet loss issue

Mon, 03 Dec 2012 07:54:56 EDT

TSI Gabe posted : the packet loss is occurring at the St-Laurent POI level. We've had an upgrade order on there for a while now and it's getting installed on December 11th (next week)

Re: TSI/HE.net performance/packet loss issue

Mon, 03 Dec 2012 03:13:50 EDT

Taylortbb posted : Yes, which is why I suggested Google. TekSavvy peers with them through Torix, so it would separate TekSavvy's network from HE's network (or any other transit provider). I don't see any pings to non-router destination's inside TekSavvy's network, and I know I frequently get packetloss when pinging TekSavvy routers (even when I've got zero loss to the end destination). If you saw packetloss from Google too that would suggest something wrong inside TekSavvy's network, if not it could be an HE issue. Both HE and Google appear to connect through Torix, so you'd be going through the same TekSavvy equipment.

I'm not seeing any packetloss from Google, and as we're both on cable we go through the same TSI equipment (different POIs connect through a shared Rogers connection). It could be a Rogers issue with your POI, which isn't TSI's or HE's network.

--- google.ca ping statistics ---
128 packets transmitted, 128 received, 0% packet loss, time 127159ms
rtt min/avg/max/mdev = 10.408/13.152/23.795/2.138 ms
--
Taylor Byrnes

Re: TSI/HE.net performance/packet loss issue

Mon, 03 Dec 2012 01:31:04 EDT

jmck posted : true, however you'll notice packet loss happening at the end points and so the conclusion can be made that there is an issue in between and both routes show its happening somewhere inside TSI.

that combined with slow speeds and other reports tonight indicates there is/was a problem, however I don't see TSI responding to this issue.

Re: TSI/HE.net performance/packet loss issue

Mon, 03 Dec 2012 01:16:25 EDT

Taylortbb posted : Routers are generally set to have pings as the lowest priority, so seeing packetloss on a traceroute doesn't mean too much. If you ping google.ca and let it run for ~200 packets do you get any loss?
--
Taylor Byrnes

TSI/HE.net performance/packet loss issue

Sun, 02 Dec 2012 20:52:24 EDT

jmck posted : I've started to notice some slight packet loss tonight and it seems to be between HE.net and TSI in Toronto or at the Ottawa POI, he's an MTR from both sides:

                                                   My traceroute  [v0.82]Zapp.local (0.0.0.0)                                                                               Sun Dec  2 20:50:07 2012Keys:  Help   Display mode   Restart statistics   Order of fields   quit                                                                                   Packets               Pings Host                                                                            Loss%   Snt   Last   Avg  Best  Wrst StDev 1. 192.168.1.1                                                                   0.0%   136    0.8   0.7   0.6   1.2   0.1 2. 10.125.77.1                                                                   0.0%   136    9.0   8.5   6.6  19.3   1.8 3. 24.156.149.213                                                                0.7%   136   20.3  20.5  14.6  45.0   5.8 4. stlaurent3.cable.teksavvy.com                                                 0.0%   136    8.6  12.1   7.5 106.9  12.0    stlaurent2.cable.teksavvy.com    stlaurent1.cable.teksavvy.com 5. stlaurent2.cable.teksavvy.com                                                 1.5%   136   28.6  20.7  13.6  75.5  11.5 6. 2120.ae0.bdr01.tor.packetflow.ca                                              0.7%   136   26.2  18.8  10.2  56.8   7.6 7. gw-he.torontointernetxchange.net                                              1.5%   136   31.2  25.1  16.6  42.8   4.8 8. 10gigabitethernet3-1.core1.nyc5.he.net                                        3.7%   136   29.2  33.5  27.3  49.3   4.5 9. 10gigabitethernet3-2.core1.nyc1.he.net                                        3.7%   136   42.2  38.9  31.4  57.4   5.010. 216.66.30.218                                                                 1.5%   136   35.9  36.7  31.1  52.9   2.911. rakis.net                                                                     1.5%   136   36.8  36.5  31.3  48.3   3.0

                                                                  My traceroute  [v0.75]waffle (0.0.0.0)                                                                                                                  Sun Dec  2 20:50:04 2012Resolver: Received error response 2. (server failure)er of fields   quit                                                                                                                  Packets               Pings Host                                                                                                           Loss%   Snt   Last   Avg  Best  Wrst StDev 1. nyc.rt2.cyberwarp.net                                                                                        0.0%   112    0.5   0.5   0.4   2.2   0.2 2. v103.core1.nyc1.he.net                                                                                       0.0%   112    6.8   2.4   0.4  11.8   3.2 3. 10gigabitethernet3-3.core1.nyc5.he.net                                                                       0.0%   112    7.0   2.8   0.4  11.3   3.3 4. 10gigabitethernet3-4.core1.tor1.he.net                                                                       0.0%   112   18.3  17.1  14.4  26.5   3.6 5. teksavvy-solutions-inc.10gigabitethernet1-1.core1.tor1.he.net                                                1.8%   112   15.6  16.9  14.5  55.5   7.6 6. 24.246.55.6                                                                                                  1.8%   112   26.3  30.2  22.3 120.5  14.3 7. 24.156.156.29                                                                                                3.6%   112   49.5  31.7  25.3  52.0   5.4 8. 10.125.77.1                                                                                                  0.9%   112   28.1  27.9  21.6  55.2   3.9 9. 24-212-154-201.cable.teksavvy.com                                                                            0.9%   111   37.6  36.7  31.0  52.7   3.9