dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
7734
share rss forum feed

CarsonKT

join:2011-08-09
Hampstead, QC
reply to EdT

Re: slow 6M DSL Montreal (evening only?)

I am back again, and swap back with thomson tg784 and the speed drop back to 1M again.

So.....EdT, is this symptoms also helps in further determining the problem? thx



Guspaz
Guspaz
Premium,MVM
join:2001-11-05
Montreal, QC
kudos:23
reply to CarsonKT

Terrible speeds downtown; getting 10 meg down on a 50 meg bundle, but it's not stable, it's super bursty. Tried reconnecting a bunch of times, even saw a result of 3 megs.

Considering all the speed issues people are having recently, even in Ontario, it seems like it might be a TSI issue.
--
Developer: Tomato/MLPPP, Linux/MLPPP, etc »fixppp.org


CarsonKT

join:2011-08-09
Hampstead, QC
reply to CarsonKT

Here are some details from both modems

Bell 2wire

DSL Line (Wire Pair): Line 1 (inner pair)
Protocol:G.DMT Annex A
Downstream Rate:6016 kbps
Upstream Rate:512 kbps
Channel:Interleaved
Current Noise Margin:24.0 dB (Downstream) 6.0 dB (Upstream)
Current Attenuation:13.1 dB (Downstream) 4.5 dB (Upstream)
Current Output Power:9.8 dBm (Downstream) 12.3 dBm (Upstream)
DSLAM Vendor Information: Country: {0xB5} Vendor: {IKNS} Specific: {0x01}
PVC Info:0/35

Thomson TG784

Uptime:0 days, 0:02:11
DSL Type: G.992.1 annex A
Channel mode: Interleave
Maximum Bandwidth (Up/Down) [kbps/kbps]: 1.056 / 11.008
Bandwidth (Up/Down) [kbps/kbps]: 512 / 6.016
Data Transferred (Sent/Received) [kB/kB]:29,00 / 69,00
Output Power (Up/Down) [dBm]: 12,0 / 9,5
Line Attenuation (Up/Down) [dB]: 5,5 / 11,0
SN Margin (Up/Down) [dB]: 6,0 / 26,0
Vendor ID (Local/Remote): TMMB / IKNS
Loss of Framing (Local/Remote):11 / 0
Loss of Signal (Local/Remote):1 / 0
Loss of Power (Local/Remote):0 / 0
Loss of Link (Remote):0
Error Seconds (Local/Remote):1 / 0
FEC Errors (Up/Down):0 / 0
CRC Errors (Up/Down):0 / 0
HEC Errors (Up/Down):0 / 0



heyyahblah

join:2009-02-01
Mississauga, ON
reply to Guspaz

It seems like its a big problem regarding BELL and TSI is aware of it, like Guspaz said I have tried disconnecting/reconnecting several times and it hasn't seemed to have worked, so I guess I am going to just wait it out unfortunately ....

quote from TSI STAFF

Hi,

We've identified that there are problems with DSL links as Bell is doing some changes on the network. It's going to sound odd, but right now the only way to get this fixed is to disconnect, reconnect, run a speed test and see if things have improved, if not, repeat the process. It's taking about 6 or so intentional disconnects force a move of the link your connected to. We're working to get the situation resolved in a permanent way, but right now this will get you to a less congested link as the maintenance finishes.


--
Larry, Larry Laugher .. hehe


EdT

join:2009-06-12
Saint-Laurent, QC
reply to CarsonKT

What is the sync speed showing in your GUI "connection" tab ?
On a Thomson it should be 192.168.1.254 to access the GUI menu.

Download DMT to determine your attenuation and distance to CO, it will also tell you what your line is capable of.

Download version DMT v7.35 for Thomson modems. Don't worry you can select English when the program installs ...LoL

»dmt.mhilfe.de/


grunze510

join:2009-02-14
Cote Saint-Luc, QC
kudos:1
reply to Guspaz



I'm getting just under 3.9 Mbit/s downstream on a 6/0.8 Mbit/s sync. The downstream is normally about 5.1 Mbit/s (like everyone else on that profile).



Guspaz
Guspaz
Premium,MVM
join:2001-11-05
Montreal, QC
kudos:23
reply to CarsonKT

Yayyyyyyyyy


--
Developer: Tomato/MLPPP, Linux/MLPPP, etc »fixppp.org



EdT

join:2009-06-12
Saint-Laurent, QC
reply to CarsonKT

From what I can see, seems like BHell have you on a 6Mbs/800Kbps profile and you are getting the 6dB upstream constantly which suggest it is the IKNS bug !



Guspaz
Guspaz
Premium,MVM
join:2001-11-05
Montreal, QC
kudos:23
reply to CarsonKT

I kept reconnecting over and over again and did eventually get back to normal:



Still no upstream upgrades :P
--
Developer: Tomato/MLPPP, Linux/MLPPP, etc »fixppp.org


CarsonKT

join:2011-08-09
Hampstead, QC
reply to EdT

I assume you refer to this speed.
Bandwidth (Up/Down) [kbps/kbps]: 512 / 6.016



EdT

join:2009-06-12
Saint-Laurent, QC

1 edit

Yes, sync speed is one indication, but SNR is another.
I noticed on your Thomson they have you are on interleave, OMG that is horrible ! ...LoL

Once this settles, you should ask TSI to switch you to Fast Path !

EDIT: here we go, you my friend definitely have the IKNS bug, BHell has you on a remote IKNS DSLAM and they probably misdiagnosed your line and put you on interleave !

Vendor ID (Local/Remote): TMMB / IKNS


CarsonKT

join:2011-08-09
Hampstead, QC

1 edit
reply to CarsonKT

back from running a DMT....
unfortunately it does not support firmware 8.2.7.7.0 , I can see DMT is a powerful tool, but too bad cannot use it.

thx EdT for your help, I guess I have to start a thread in direct section to hopefully get the problem solved.

One thing still confuse me, now I swap back to Bell 2wire modem again, and.....it's back to normal speed.


in 2Wire MDC I found this DSL Line (Wire Pair): Line 1 (inner pair)
Protocol: G.DMT Annex A
DSL Channel: Interleaved
DSLAM: Country: {0xB5} Vendor: {IKNS} Specific: {0x01}
ATM PVC Info: 0/35
ATM Encapsulation: LLC

It's also Interleaved....and I am still digging other info. in it.


spacey

join:2008-04-02
Montreal, QC

Hrm, tonight my speeds were normal but no updates to my ticket. There was no slow down for me in Montreal. Shrug... I hope it stays like this!


CarsonKT

join:2011-08-09
Hampstead, QC

now, to me it becomes a modem issue.....
try to avoid the randomness of one works and the other doesn't, I sway my two modems back and forth, but every time I got the same result.

2wire modem works at normal speed
TG784 works at 2M top......


InvalidError

join:2008-02-03
kudos:5
reply to CarsonKT

said by CarsonKT:

One thing still confuse me, now I swap back to Bell 2wire modem again, and.....it's back to normal speed.

If you read the TSI quote and TSI post above, it seems the low speeds are due to Bell messing with their network configuration and re-connecting the PPPoE session to (hopefully) get on a different link routing from your BAS to TSI's ERX is the only way to "fix" it. TSI's post says this requires about six attempts on average.

Maybe you got lucky and got on a good route when your PPPoE session came up on the 2wire, which made it seem like switching modems "fixed" it.

jfn0106

join:2012-09-16
reply to CarsonKT

After doing the reset trick on my modem, for the time being all seems back to normal on my 6M service.




At least Teksavvy has now acknowledged there is an issue with congested links. Thanks for sharing that bit of insider info with the rest of us, hopefully everyone else's connections get back to normal soon too.


EdT

join:2009-06-12
Saint-Laurent, QC
reply to CarsonKT

Yes, different types of DSL modems uses different chipsets and behave differently with the IKNS bug, but what is funny is that the 2Wire 2701 is known to perform badly with the IKNS and the Thomson is the one that is suppose to be better !


InvalidError

join:2008-02-03
kudos:5
reply to jfn0106

said by jfn0106:

At least Teksavvy has now acknowledged there is an issue with congested links.

TSI only stated that they were having problems due to Bell shuffling things around on their end and that reconnecting to end up on a different AHSSPI seems to solve it, not that they actually had congestion issues at their end of things.

In any case, the problems are "initiated" from Bell's side of things so TSI has very little control over what happens.

CarsonKT

join:2011-08-09
Hampstead, QC
reply to InvalidError

I tend to agree with this theory that I just got lucky when I made the swap, coz the last time I tried before I went to bed last night I made a final swap to 2wire, and that time I only got 2.6M something.

but during the day time everything just works fine.

So to me the bottom line is we know the cause of the problem and we can expect an end and everything will be back to normal sometime


jfn0106

join:2012-09-16
reply to InvalidError

said by InvalidError:

said by jfn0106:

At least Teksavvy has now acknowledged there is an issue with congested links.

TSI only stated that they were having problems due to Bell shuffling things around on their end and that reconnecting to end up on a different AHSSPI seems to solve it, not that they actually had congestion issues at their end of things.

No. Quote from TSI verbatim :

said by heyyahblah:

"...We're working to get the situation resolved in a permanent way, but right now this will get you to a less congested link as the maintenance finishes."

So...they acknowledge congested links and clearly suggest a workaround to help mitigate winding up on a congested link.


heyyahblah

join:2009-02-01
Mississauga, ON

the solution hasn't worked for me, i've tried this numerous times and have just given up. I always seem to end up on a congested link and the download speeds here for files don't top 300kb/sec, i hope this is resolved soon .....
--
Larry, Larry Laugher .. hehe


jfn0106

join:2012-09-16

Sorry to hear that. I'm in the same boat as well, my connection dropped back to a congested link today and I'm at 2M-3M again.

A quick resolution would be nice, but I really just wish there was more transparency in these types of network issues from the outset.


InvalidError

join:2008-02-03
kudos:5
reply to jfn0106

said by jfn0106:

So...they acknowledge congested links and clearly suggest a workaround to help mitigate winding up on a congested link.

They did not say that they were seeing congestion from their end of things, only that Bell's shuffling seems to be causing congestion.

When people start complaining and TSI notices that AHSSPIs are congested, TSI usually responds stating that they had a load imbalance problem and are terminating L2TP sessions on over-burdened links to re-distribute the load. Since they are not doing it this time around, I take this as a hint that the current congestion issues are occurring somewhere within the Bell cloud so TSI cannot determine which links are misbehaving with their current tools.


lester2

join:2005-09-01
London, ON
reply to CarsonKT

This is horrible




Less than 1mbit right now, after resting my modem I got worse speeds

grunze510

join:2009-02-14
Cote Saint-Luc, QC
kudos:1

2 edits

My speed isn't nearly as bad as yours is, but it looks like I'm going to have to go through the reconnections for a bit.




EDIT1: Despite what InvalidError's speedtest shows, my internet is faster. 1 whole second faster.

EDIT2: I ran another speedtest and am practically getting full speed. I didn't even reconnect yet.

EDIT3: Back to normal.


InvalidError

join:2008-02-03
kudos:5
reply to lester2

I was getting ~3Mbps, reset my PPPoE session and now I am at a more reasonable 100kbps short of normal on download.



CarsonKT

join:2011-08-09
Hampstead, QC
reply to CarsonKT

tonight I got
for the whole evening, not the best I can get, but I can live with it for now.



heyyahblah

join:2009-02-01
Mississauga, ON

Click for full size
downloads aint doing any good still, lol wow
--
Larry, Larry Laugher .. hehe

jfn0106

join:2012-09-16
reply to InvalidError

said by InvalidError:

said by jfn0106:

So...they acknowledge congested links and clearly suggest a workaround to help mitigate winding up on a congested link.

They did not say that they were seeing congestion from their end of things, only that Bell's shuffling seems to be causing congestion.

No reason for you to disagree with me then, since I never suggested that they saw congestion "at their end":
said by jfn0106:

At least Teksavvy has now acknowledged there is an issue with congested links.

I'm not sure any of us really care where the congestion is. I do think what we'd all agree on, and like to see going forward is TSI providing transparency about the congestion problems and to post updates as progress is made towards a fix.

InvalidError

join:2008-02-03
kudos:5

said by jfn0106:

TSI providing transparency about the congestion problems and to post updates as progress is made towards a fix.

Except that if the congestion is indeed happening within Bell-land because Bell is re-arranging stuff at their end of things, there is very little that TSI can do to "fix it" since they have no control over what actually needs fixing and they won't know if their fix fixes anything until Bell is done fixing their own things first.

With some luck, maybe the reason Bell is busy re-arranging their network is to prepare for 10G AHSSPI.