Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: V_R on January 30, 2018, 11:21:41 AM
-
Hey guys,
Firstly I'm .Sam. on MDWS - https://www.mydslwebstats.co.uk/Container.htm
Just wondering if I could get some advice. I've been capping my line at 60/15 since late on the 25th January in an effort to try and get rid of Interleaving.
There's been no change so far, should I try capping it even lower?
Also, I'm just wondering if my FEC errors normal/high?
Thank you!
-
My line was capped at 35mbps and interleaved about 6 months ago. I limited the sync rate to 20mbps, and within 4 days DLM had reacted and removed the interleaving entirely. Unfortunately the capping has remained in place.
So yes, I would say reduce it further.
-
I'm definitely not an expert on this, but i've been having a near identical issue over the past few days. You may want to check my recent thread (http://forum.kitz.co.uk/index.php/topic,20911.0.html) for a bit more information.
Looking at your SNR, when you capped and resync there was only a very slight increase in downstream SNR. I capped mine a bit more aggressively (~55mbit down to 40mbit) and saw a big boost in SNR on the downstream. Just over 4 days later, DLM resynced me and removed downstream interleaving.
Definitely try a much more aggressive cap. It looks like you dropped it from ~65mbit to 60 - try going down to 45 or even 40 if you can cope with it for a few days.
-
As it happens your thread was the inspiration to start this one, rather than hijack yours. :)
Thats what I'm thinking, maybe 40/45Mb might make things move a little faster.
I'm away this weekend so now might be the best time as I won't have to suffer with it being so slow. :no:
-
With those FEC errors per minute on the downstream I would definitely say reduce the banding further.
I was recently on interleaving for about 20 days, though many of those days weren't capped. I switched back to the Zyxel so I could apply an aggressive banding and I think several days following that DLM returned me to fastpath at 5am a morning or two ago. My SNRM was around 12-13 dB when I was interleaved with the downstream banded to 50-55 Mbps. I've kept the banding in place for now since my line historically has a problem with higher speeds/lower SNRM. I'd rather have a reduction in speed than higher latency.
-
With those FEC errors per minute on the downstream I would definitely say reduce the banding further.
Don't remind me this FEC Errors on my downstream. So far after 1 day, 4 hours 25 mins my downstream FEC errors below:
Since Link time = 1 days 4 hours 25 min 23 sec
FEC: 17542
-
Don't remind me this FEC Errors on my downstream. So far after 1 day, 4 hours 25 mins my downstream FEC errors below:
Since Link time = 1 days 4 hours 25 min 23 sec
FEC: 17542
That's extremely low. I get that every minute and I'm not worried.
-
lol Max, your line is fine. Jesus. Its a lot better than a lot of people.... ::)
My FEC errors seem like a lot compared to others on MDWS... :|
Going to try capping lower either tonight or tomorrow.
-
lol Max, your line is fine. Jesus. Its a lot better than a lot of people.... ::)
My FEC errors seem like a lot compared to others on MDWS... :|
Going to try capping lower either tonight or tomorrow.
In my limited experience, the d/s SNRM needs to go above 10 to have any effect. Have a look at my stats, I got interleaved after my Billion 8800NL decided to lose all it's settings one day. Capping at 25000 had the SNRM at just under 10 & no DLM action, capping even lower had it at over 11 & DLM kicked in after just over 2 days. I'm keeping the cap in place for a bit as I was also banded from virtually day 1, to see if I can shift that too.
-
Interleaving has been removed! Now just need G.INP to kick back in...
-
That's great news. You have to wait for at least 2 or 3 days of stable before G.INP will come back on. :)
-
So I've just seen KingJ has had G.INP applied to his line due to him capping it.
I'm doing the same and I got bumped back to fastpath on the 4th, anyone fancy a guess (educated or other!) as to when/if I'll get G.INP on mine?! :D
-
I'm doing the same and I got bumped back to fastpath on the 4th, anyone fancy a guess (educated or other!) as to when/if I'll get G.INP on mine?! :D
I guess it will be anytime tomorrow for G.INP to be applied on your line
-
So I've just seen KingJ has had G.INP applied to his line due to him capping it.
I'm doing the same and I got bumped back to fastpath on the 4th, anyone fancy a guess (educated or other!) as to when/if I'll get G.INP on mine?! :D
Have you removed the cap?
I recommend removing the cap after fastpath returns.
Within a couple days interleaving should be applied.
7 days after that KingJ had G.INP applied.
I'm hoping we get a pattern/trend we can follow.
I'd guess the 14th or 15th?
-
The cap is still in place. I thought I should keep the cap until G.INP is applied?
-
Your cap is so harsh you have 0 ES.
You wanted DLM to relent so needed a harsh cap to trick it in to returning to fastpath.
Now you want to trigger DLM. If there's 0 ES DLM will leave the line as it's incredibly stable.
Let the line run at full sync, ES will increase considerably. It should trigger interleaving/INP, and G.INP shortly after.
That was my advice in the other thread, and it worked!
-
Right, I get you. Will remove the cap now. Ta!
-
Many Error Seconds so far. Pretty sure DLM will intervene tonight.
-
No DLM so far, to my surprise, despite all the ES.
-
Interleaving was just applied to my line.
-
Interleaving was just applied to my line.
That's a good sign! Hopefully now G.INP will follow through shortly as it did for me.
Interestingly, your DLM intervention was around the same time of day mine was. I originally put that down to the time delay from when I applied my actions, but now i'm wondering if it applies actions around about this time? I always thought it was meant to intervene overnight when the line typically isn't being used...
-
Interleaving was just applied to my line.
Your G.INP will applied in three days time (around lunch time on monday) just like mine did after interleave put on INP 3
-
I always thought it was meant to intervene overnight when the line typically isn't being used...
It used to run overnight. There are just so many lines being managed by DLM now that it can't process them all at night. I've had DLM resyncs about 6pm in the last couple months. A couple years ago they were always between midnight and 8am.
-
FFS.
Had a power cut this morning for a few hours from about 11:30.
Interleaving now up to 1503, but on the plus side I've somehow managed to sync at 76Mbps at 2.3dB.
Not sure how this will affect my chances of getting G.INP now....
-
Still no G.INP..... :(
The line is holding steady with a SNR of ~2.2dB though. Anyone think that is luck or xdB? I'm guessing luck as its a straight drop from 6 to 2.2.
-
Still no G.INP..... :(
The line is holding steady with a SNR of ~2.2dB though. Anyone think that is luck or xdB? I'm guessing luck as its a straight drop from 6 to 2.2.
That very much sounds like luck to me, xdB requires G.INP and is applied in 1dB decrements :(
Maybe it's worth leaving it for a few days, and the starting over again? The process definitely delivered results for me, so that power cut instability might have interfered.
-
Ah I didn't know xdB needs G.INP.... That answers that then.
Yeah I do wonder if that power cut might have scuppered my plans.... >:(
-
I do sometimes just wish DLM take notice of any power cut and will ignore it. Unlucky V_R.
-
Actually it doesn't have to be the result of any action by the DLM process, Max. :-\
I suspect that V_R's modem/router was one to train-up and synchronise quickly once the power was restored. It would have synchronised at the 6 dB target SNRM and only as other modem/routers trained-up & synchronised did the SNRM drop as a result of cross-talk from neighbouring circuits.
-
Ah now that's an interesting thought, I do think I've got a/some bad cross talker somewhere, I used to easily sync at full speed, and now I can only just manage it with G.INP and 5dB. My Attenuation is only 10.2 for goodness sake....
-
I seen some lines with Line Attenuation is over 14 dB and still getting full max sync rate with G.INP on it via MDWS (Quik UP)
-
Right then, there has still been no change. What should I do?
1. Leave the line as it is?
or
2. Re apply a cap of about 40Mb down and see if I can force G.INP again?
As per sig, I'm .Sam. on MDWS.
Cheers.
-
Leave it alone let the DLM do it
-
It's been almost a week since your powercut now, and the line hasn't resynced. I would think that if DLM was going to take action, it would have done so by now.
I would personally suggest waiting until Monday evening (so there's >7 days since the last resync), and then starting over again - reapplying the aggressive cap, waiting for fast path, uncapping, waiting for G.INP etc..
-
.Sam. UP - it look like DLM haven't decided yet on your line to get G.INP enabled as I do think the small power cut has ruined it. Maybe u try to get capped at 40Meg and what happen from there.
-
So I've left it alone for all this time and nothing has happened at all. No DLM, no G.INP. On the plus side, the connection has held at ~2dB all this time which is a result.