Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: andyfitter on April 24, 2018, 12:24:46 AM
-
I switched providers in early January, having had g.inp right from the start. However, after the DLM reset when I switched, I’ve been waiting for g.inp to come back.
After nearly 4 months I still have fastpath downstream, interleaved upstream and no g.inp. Very few ES or SES either. Only want g.inp back as I’m sure my line will support xDb and the speed increase it will give me.
Has anybody waited longer than this and still had it eventually applied?
-
I think its random, before I moved, at my old address, when I switched providers it took an age to be applied.
At my new address on my brand new line that only went live on Friday morning just gone, G.INP was suddenly applied yesterday morning at about 4am.
YMMV. :)
-
My line has not had G.INP enabled since I moved to Zen at the end of January this year. It was previously enabled when I was with Plusnet.
-
My line took just over 7 weeks to apply DS G.Inp after migration from ADSL2 to VDSL with Plusnet, Hiuawei cab. obviously, quite a few cases of longer times have appeared on the forums, most much shorter, can be a bit of a lottery with DLM it would appear.
-
I had G.INP enabled for months/years before I had DLM reset in January 2017, since then it's stuck on non-interleave. I am guessing that because I've not hit the error threshold it's quite happy to leave me on non-interleave?
-
If it is the case that DLM thinks your line is 'too stable' to need g.inp, then that makes no logical sense, in terms of it being a requirement to have g.inp applied before you can get xdB.
If your line is that stable, then surely you should be able to have xdB without g.inp, or be given g.inp *automatically*, as a means to getting xdB?
I'm more inclined to believe that the people with 'stuck' lines that don't get g.inp are on cabinets that have the DLM reporting issues that were discussed many months ago. If that issue does still exist, and it only takes a single modem on a cab containing hundreds of lines to 'break' DLM for the whole cabinet, then I'm pretty sure that many cabinets are affected.
-
If your line is that stable, then surely you should be able to have xdB without g.inp, or be given g.inp *automatically*, as a means to getting xdB?
In my case, because I'm syncing at the full speed, it has probably decided that I don't need G.INP at all (and by extension, <6dB SNRM).
# xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 23203 Kbps, Downstream rate = 83816 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 79987 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 7.4 7.1
Attn(dB): 11.3 0.0
Pwr(dBm): 14.0 -3.3
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 239 237
M: 1 1
T: 23 42
R: 0 16
S: 0.0955 0.3781
L: 20104 5374
D: 1 1
I: 240 127
N: 240 254
Counters
Bearer 0
OHF: 779918050 3732886
OHFErr: 1846 739
RS: 0 3569521
RSCorr: 0 23592
RSUnCorr: 0 0
Bearer 0
HEC: 4710 0
OCD: 100 0
LCD: 100 0
Total Cells: 753230276 0
Data Cells: 1343811393 0
Drop Cells: 0
Bit Errors: 0 0
ES: 626 339
SES: 0 0
UAS: 24 24
AS: 1289884
Bearer 0
INP: 0.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 1.65 3.98
OR: 116.09 64.22
AgR: 80103.09 20063.54
Bitswap: 430019/430019 1366/1366
Total time = 1 days 22 hours 18 min 28 sec
FEC: 0 23592
CRC: 1846 739
ES: 626 339
SES: 0 0
UAS: 24 24
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 3 min 28 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 0 0
CRC: 2 0
ES: 1 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 22 hours 18 min 28 sec
FEC: 0 1763
CRC: 17 21
ES: 11 21
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 0 261
CRC: 18 27
ES: 14 21
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 14 days 22 hours 18 min 3 sec
FEC: 0 23592
CRC: 1846 739
ES: 626 339
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
The max attainable on my line jumps to around 95 Mbps with G.INP enabled.
-
I've been waiting for 2 years for it to be reapplied but I am on an ECI cab!
-
Looks like I finally got g.inp applied overnight. No obvious reason, no burst of errors. Only took 4 months or so!
Appears to be on both up and down stream.