Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: plank101 on January 23, 2017, 10:44:30 PM
-
Noticed some interesting things with my connection in the past 10-15 days or so.
Unfortunately I'm not logging things yet to MDWS but the timeline has been the following:
2 years ago: 80/20 fastpath.
~1-1.5 years ago: Steady drop in sync to ~70-80, possibly due to crosstalk,etc (or perhaps just power cuts or my VMG8924 having problems last year causing many restarts in a short period of time). G.INP kicked in at 50 (i think) with an interleaved depth of 8 to stabilise things.
10-15 days ago: Possible power cut (or something else?) caused interleaved to go up to 1283 and G.INP to come off. Sync was at 65mb (down from 75mb).
This morning at 9am: Back to fast path on the downstream. Sync at 71mb.
Anyone know the potential background or story as to why this is happening?
I do like being on fastpath, pings are back to 7-8ms to Central London. Question is, how long will it be before my line is considered for G.INP to be have any possible improvement? (Understood that it only gets turned on past a certain level of errors).
-----------------
Current stats:
Stats recorded 23 Jan 2017 22:43:38
DSLAM/MSAN type: BDCM:0xa48c / v0xa48c
Modem/router firmware: AnnexA version - A2pv6F039v.d26a
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 16 hours 53 min 21 sec
Resyncs: 0 (since 23 Jan 2017 22:27:05)
Downstream Upstream
Line attenuation (dB): 13.6 0.0
Signal attenuation (dB): Not monitored
Connection speed (kbps): 70784 20000
SNR margin (dB): 6.2 5.9
Power (dBm): 13.0 4.8
Interleave depth: 1 1
INP: 0 0
G.INP: Not enabled Not enabled
Vectoring status: 5 (VECT_UNCONFIGURED)
RSCorr/RS (%): N/A 0.1723
RSUnCorr/RS (%): N/A 0.0000
ES/hour: 4.65 2.42
-
(Understood that it only gets turned on past a certain level of errors).
It's default enabled on downstream for all lines(if the modem supports it). Was there any work done to your line the day it removed G.INP? Or did you change package/provider? It's usually only removed with a DLM reset or product change. After that it's roughly 10-15 days till it comes back on. I have no idea what will happen with your line though as I don't recall such an occurrence.
-
I had DLM reset 15 days ago, and GINP has still not been re-enabled, although at the time of DLM reset the enginner called up someone who then removed the "default" interleave. It's been on fastpath ever since (and no resync, yet).
-
It is not a exact science when predicting when G.INP will return after a line reset, it did return after 11 days on my line and some others saw similar times, have taken a look MDWS and your on the 15th day since your DLM was reset so give it a few more days :fingers:
-
It's no big deal at the moment since I am not interleaved, but just seems a bit silly that I am GINP capable and yet it's not enabled.
I really cannot understand why BT will not make their [DLM] algorithms public, at least then people might know what to expect.
I have actually worked at a BT site (BT Eldon House exchange in central Sheffield), and it's like going back in time to the 1980's, Fecking Unions, jobs worth staff, everything done as cheap as possible..... in fact probably the worst place I have ever worked. Sorry, but BT is full of overpaid fatcats at the top and the people on the ground doing actual real work are paid the bare minimum.
-
BT are just like any other company it's all about profit and no profit = job losses + less investment into infrastructure schemes and that results in a poor service and sure look at the drop of BT shares after the Italian corruption scandal 530 million lost, at some point we are all going to feel the effect of this
-
Just had another resync lol, right i'm of to do a bit of shappen ( it's the way we talk) at tescos and later on this evening after a few beers i'll disconnect the VF 2500 and see how far I can throw it down the back field how far do you reckon 20-25 meters ;D
-
It's default enabled on downstream for all lines(if the modem supports it). Was there any work done to your line the day it removed G.INP? Or did you change package/provider? It's usually only removed with a DLM reset or product change. After that it's roughly 10-15 days till it comes back on. I have no idea what will happen with your line though as I don't recall such an occurrence.
I was not aware that any work was done on my line on the day that it removed G.INP. I haven't changed package or provider either. Just an update, G.INP returned last Wednesday (25th Jan) at 5-6am in the morning.
Stats recorded 31 Jan 2017 00:00:49
DSLAM/MSAN type: BDCM:0xa48c / v0xa48c
Modem/router firmware: AnnexA version - A2pv6F039v.d26a
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 5 days 18 hours 17 min 42 sec
Resyncs: 0 (since 30 Jan 2017 23:57:16)
Downstream Upstream
Line attenuation (dB): 13.7 0.0
Signal attenuation (dB): Not monitored
Connection speed (kbps): 76167 20000
SNR margin (dB): 6.4 6.1
Power (dBm): 13.0 5.1
Interleave depth: 8 1
INP: 48.00 0
G.INP: Enabled Not enabled
Vectoring status: 5 (VECT_UNCONFIGURED)
RSCorr/RS (%): 0.0060 0.9287
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 0 0
-
So how long was G.INP disabled for?
Mine is still disabled after 20 days of sync.
-
Somewhere between 10-17 days. Definitely less than 20 days.
-
not sure whats going on with mine then, still not had G.INP enabeld after 23 days sync time. I guess:
1. not enough errors on fastpath to cause G.INP to kick in (about 500 per day)
2. G.INP disabled at the DLM (when they manually removed interleave during DLM reset)
3. G.INP may become enabled but only when modem re-syncs
I just hope I do not get interleaved, that is all I really care about.
-
Can only go on what I see on my line after DLM or change of ISP resets my DS errored seconds are two high on fastpath 2000+ on standard DLM profile and after two days it's then interleaved for 11 days then G.INP is turned on.
Does it need to enter the interleaved state for G.INP to then become active as after all it's just another type of error correction tool with good inpluse noise protection for me it does
-
May have to amend my previous post, since the last DLM reset done by OR over two weeks ago G.INP has not returned, and I did loose G.INP before that DLM reset due to constant disconnects it seems to default to interleaving in cases like this.
So I am wondering if G.INP will come back quickly (11 days) after changing ISP or will it take a few months :-\
-
The same has just happened to me today at a few minutes past 12:00. I've not changed provider, hard any work done or asked for a DLM reset. Is there any way check by looking at the data from DSLstats or mydslwebstats if it was caused by a DLM reset?
With any luck I'll get my sync rate of 75 Mbps back in a few weeks.
EDIT: I'm using a Billion 8900AX modem
Just for info,
DSLAM/MSAN type: BDCM:0xa48c / v0xa48c
Modem/router firmware: AnnexA version - A2pv6F039v.d26m
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 5 hours 55 min 15 sec
Resyncs: 1 (since 11 Feb 2017 17:09:26)
Downstream Upstream
Line attenuation (dB): 15.9 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 56280 19999
SNR margin (dB): 6.3 15.1
Power (dBm): 14.0 6.8
Interleave depth: 1101 1
INP: 3.00 0
G.INP: Not enabled Not enabled
Vectoring status: 5 (VECT_UNCONFIGURED)
RSCorr/RS (%): 0.0001 0.0000
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 0.56 0.50
-
If you happen to be in Devon & Somerset area then that could explain it, if not no idea. That whole area is part of the 3,4,5dB snrm trial and quite a few lines seem to keep getting reset.
-
Thank you J0hn, that probably explains it then as I live in the area. A few weeks back when I started using DSLstats again, I noticed my downstream SNRM going down from 5dB to 3dB in steps of 1.
Cheers
-
In that case you should have G.INP enabled again in 48 hours :fingers:
-
Then your part of the target SNRM trial. Looking at MDWS you did indeed have a target SNRM of 3dB before the resync.
From my observations of other lines in the trial they seem to revert your line to interleaving for a few days, then G.INP returns. Your line will then likely start back up in the trial.
-
If you ever wondered what a perfect SNRM looks like then BigJ's your man ;)
-
I rather naively thought I'd caused it by shuffling things about and plugging the second cable into the HG612 :) Thanks for the additional info J0hn and NewtronStar, I'll keep an eye on it.
-
Spot on guys. G.INP was enabled again around 5:00 this morning.
-
That's good, I,m guessing they are making sure the DSLAM will change automatically to interleaving if a theoretical issue comes up when on a SNRM of 3dB that is what trials are for debugging the beast.
-
Spot on guys. G.INP was enabled again around 5:00 this morning.
:thumbs:
-
What is nice with BigJ line is he gains 9 Mbps with G.INP and 10 Mbps on the 3dB SNR margin a gain of 19 Mbps that is impressive
-
You've made me think about how my speeds have changed over the years. I dug up the earliest btwholesale speedtest from 4 years ago about 3 months after I got fibre. Back then I had an IP profile of 65 Mbps. So it looks like G.INP has done a fine job keeping my speeds up :)
-
I've really got my fingers crossed for the 3dB roll-out!
Without G.INP my 20.5dB attenuated line wants to be around 45Mbit with lots of interleaving. With G.INP that's a steady 50Mbit with 9/10ms ping, with zero severely-errored seconds and only ~50 errored seconds per day.
After a recent power cut, my modem synced when there was little crosstalk and it held 59Mbit with a steady-ish 3dB margin. Errored seconds climb to about 120 per day, but the line was solid for 40-odd days until a household-only power cut caused a resync.
My line's clearly happy at 3dB, and I'm really hoping the new DLM scheme lets me have it!
-
You've made me think about how my speeds have changed over the years. I dug up the earliest btwholesale speedtest from 4 years ago about 3 months after I got fibre. Back then I had an IP profile of 65 Mbps. So it looks like G.INP has done a fine job keeping my speeds up :)
I did the same and dug out sample from four years ago when using Hg612_Modem_stats well before G.INP arrived ;)