|
|
On a Huawei cabinet here,previously had G.INP enabled, been having major work done on my line, this morning I now find that G.INP has been disabled, had a DSLStat email confirming this.
Once the connection has settled down will G.INP be enabled again.
DSLAM/MSAN type: BDCM:0xa44f / v0xa44f
Modem/router firmware: AnnexA version - A2pv6C038m.d24j
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 3 min 17 sec
Resyncs: 1 (since 19 Jun 2015 07:41:02)
Downstream Upstream
Line attenuation (dB): 19.3 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 63013 14141
SNR margin (dB): 1.7 5.0
Power (dBm): 13.8 7.4
Interleave depth: 1 1
INP: 0 0
G.INP: Not enabled
Edited by Nightglow (Fri 19-Jun-15 08:04:33)
|
|
|
|
That's rather odd to see from G.INP enabled and then turned off! How strange!
|
|
|
Has your DLM been reset by any chance.... doubt it will be back anytime soon from what some are reporting on other forums..
it was removed from my upstream in the last couple of weeks which is annoying considering it made a good improvement to my line.
Also can't help but notice your SNR is very low!
Minusnet 21CN 3500/800 @ 4.2Km > TP-Link TD-W8968v3
Minusnet Fibre 67000/19999 @ 450m > HG612 > Asus RT-AC87U BQM
|
|
Register (or login) on our website and you will not see this ad.
|
|
|
|
I agree over SNR is very low and that's not a good sign for Fibre. 1.7 dB is terrible low!
|
|
|
target is 6db... the only reason it would be that low is if it has been pushed that low using chipset telnet commands or if the attainable rates have plummeted
Minusnet 21CN 3500/800 @ 4.2Km > TP-Link TD-W8968v3
Minusnet Fibre 67000/19999 @ 450m > HG612 > Asus RT-AC87U BQM
|
|
|
On a Huawei cabinet here,previously had G.INP enabled, been having major work done on my line, this morning I now find that G.INP has been disabled, had a DSLStat email confirming this.
Once the connection has settled down will G.INP be enabled again.
If your cabling has been replaced as you suggest in the other thread, I would have thought that a DLM reset would be applied to all the lines affected.
In time DLM may decide ro re-enable G.INP, it depends on the error stats on the connection over the next few days.
--
Brian
Zen Fibre 2 - 80/20 sync
|
|
|
|
A DLM reset wouldn't be applied to all lines on that faulty cable. That's not how it works
If someone gets called out on a fault they can do a reset. But it's just assumed for everyone on that cable that DLM will do its thing, automatically.
|
|
|
|
I'm on copper right back to the cabinet now, engineer rerouted part of my line, & replaced it in copper & join it in to a exsisting newish copper cable.
Below are my latest stats.
Stats recorded 19 Jun 2015 18:25:34
DSLAM/MSAN type: BDCM:0xa44f / v0xa44f
Modem/router firmware: AnnexA version - A2pv6C038m.d24j
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 7 hours 49 min 9 sec
Resyncs: 0 (since 19 Jun 2015 18:23:30)
Downstream Upstream
Line attenuation (dB): 17.8 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 69383 17618
SNR margin (dB): 6.2 6.0
Power (dBm): 13.9 7.4
Interleave depth: 1 1
INP: 0 0
G.INP: Not enabled
RSCorr/RS (%): N/A 0.0031
RSUnCorr/RS (%): N/A 0.0000
ES/hour: 145 32.8
|
|
|
|
A DLM reset will disable G.INP. It should come back within 24-48 hours.
|
|
|
|
A drop of attenuation of 1.5dB is worth around 6mbps on lines in the 60-80Mbps, and yours seems to have gained that.
|
|
|
|
Well, connection been up 24 hours now, & not one resync, still getting a rock solid 69 /17.
|
|
|
A DLM reset wouldn't be applied to all lines on that faulty cable. That's not how it works
If someone gets called out on a fault they can do a reset. But it's just assumed for everyone on that cable that DLM will do its thing, automatically.
It seems to me that if a DLM reset is applied when an engineer makes some changes or repairs on a single line that it would make sense to do it if multiple pairs are repaired/replaced. If not, fair enough, but on ADSL the DLM process seemed very slow to respond and not all lines will be FTTC in a case like this.
--
Brian
Zen Fibre 2 - 80/20 sync
|
|
|
Looks like I had G.Inp enable on my line today:
http://www.thinkbroadband.com/ping/share-thumb/5877f...
Router confirms it's G.Inp, latency has doubled to ~20ms. Max attainable rate has jumped from 87Mb to 100Mb, so I'm not sure if it's a good thing or a bad thing..
My line had a minimal errors and a decent SNR - does G.Inp enable by default on all lines, regardless of quality?
|
|
|
It's very odd for latency to increase when G.INP is implemented. In all I've seen it has decreased it.
How often do you disconnect and reconnect normally? It's more likely the implementation was the full depth red at about 2am than when the latency jumped.
Is there anything else in the Sky router stats that might give us a clue what is happening?
The indispensable man or woman passes from the scene, and what happens next is more or less the same thing as was happening before.
My broadband basic info/help site - www.robertos.me.uk. Domains, site and mail hosting - Tsohost.
Connection - Plusnet UnLim Fibre (FTTC). Sync 58162/14182kbps @ 600m. - IPv4 BQM IPv6 BQM
|
|
|
Hardly ever disconnect/reconnect - aside from the red at 2am and 10am, the other red spikes are when I commit settings on my Billion 8800 as it mustn't reply to pings for a couple of seconds.
I do monitor downstream SNR via SNMP which you can see below:
http://killsta.co.uk/graph1.jpg
Which does tie in with the G.Inp and the TB graph I posted previously. Crosstalk I wonder? Still doesn't explain the random resync at 10am today though!
Edited by deleted (Tue 23-Jun-15 22:36:01)
|
|
|
It certainly doesn't look like G.INP... though it could be a G.INP on Downstream and then Interleaving has been applied on upstream...
specially as OR are now removing G.INP from existing G.INP enabled (both ways) lines and leaving them on with G.INP on downstream and Fast Path (or what ever is required) on Upstream
WBC 4400/800 @ 4.2Km > TP-Link TD-W8968v3
FTTC 66000/19999 @ 450m > HG612 > Asus RT-AC87U BQM
|
|
|
.
Edited by deleted (Tue 23-Jun-15 22:55:15)
|
|
|
And here be the relevant line stats:
http://www.killsta.co.uk/stats.jpg
Prior to yesterday, max attainable rate used to be 92Mb ish, with an SNR of 9.3 ish with no interleaving or G.Inp and was perfectly stable with minimal errors and no instability whatsoever. So it looks like G.Inp enabled, max attainable has risen, SNR has decreased and ping has increased. Very odd!
Edited by deleted (Tue 23-Jun-15 22:33:29)
|
|
|
Errmmmm.
That shows significant downstream interleaving - the normal initial depth oh FTTC is 500-800. (The D line).
Interleaving has also introduced its normal first step, Delay = 8ms.
Where does it tell you G.INP is on? The last line, INP (DMP) 3 is totally different.
Edit: See this page, where Impulse Noise Protection appears near the bottom. The stuff above and below it explains interleaving, but ignore the depths/delays etc. figures as they relate to BT Wholesale ADSL2+. Not necessarily FTTC.
The indispensable man or woman passes from the scene, and what happens next is more or less the same thing as was happening before.
My broadband basic info/help site - www.robertos.me.uk. Domains, site and mail hosting - Tsohost.
Connection - Plusnet UnLim Fibre (FTTC). Sync 58162/14182kbps @ 600m. - IPv4 BQM IPv6 BQM
Edited by RobertoS (Tue 23-Jun-15 22:54:09)
|
|
|
Yes that page doesn't say G.INP is on at all!
or if it is... your modem/router isn't compatible with it... or needs a firmware update at the very least!
WBC 4400/800 @ 4.2Km > TP-Link TD-W8968v3
FTTC 66000/19999 @ 450m > HG612 > Asus RT-AC87U BQM
|
|
|
|
Even more peculiar then, looks like I misunderstood the G.Inp - but I'm still confused at how severe interleaving was applied without any instability beforehand? Oh well.
|
|
|
It's not very severe. "Significant" in that it is higher than the normal first step.
INP is best explained in that link. G.INP is used to largely remove interleaving and INP, which are together part of error correction routines for corrupted packets, and instead use retransmission of such packets.
My stats:-
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 14383 Kbps, Downstream rate = 56564 Kbps
Bearer: 0, Upstream rate = 14182 Kbps, Downstream rate = 58162 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 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): 6.0 6.4
Attn(dB): 19.8 0.0
Pwr(dBm): 13.5 7.4
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 243 237
M: 1 1
T: 0 61
R: 10 16
S: 0.1336 0.5338
L: 15211 3807
D: 8 1
I: 254 127
N: 254 254
Q: 8 0
V: 0 0
RxQueue: 45 0
TxQueue: 15 0
G.INP Framing: 18 0
G.INP lookback: 15 0
RRC bits: 0 24
Bearer 1
MSGc: 122 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 8.0000 0.0000
L: 32 0
D: 1 0
I: 32 0
N: 32 0
Q: 0 0
V: 0 0
RxQueue: 0 0
TxQueue: 0 0
G.INP Framing: 0 0
G.INP lookback: 0 0
RRC bits: 0 0
Counters
Bearer 0
OHF: 0 1922893
OHFErr: 7 35
RS: 1801266576 1790645
RSCorr: 1087627 623
RSUnCorr: 0 0
Bearer 1
OHF: 39619486 0
OHFErr: 0 0
RS: 316955393 0
RSCorr: 397 0
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 179451 0
rtx_c: 17014 0
rtx_uc: 19 0
G.INP Counters
LEFTRS: 315 0
minEFTR: 58152 0
errFreeBits: 564471461 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 2459279171 0
Data Cells: 88758247 0
Drop Cells: 0
Bit Errors: 0 0
Bearer 1
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 0 0
Data Cells: 0 0
Drop Cells: 0
Bit Errors: 0 0
ES: 4 30
SES: 0 0
UAS: 24 24
AS: 636403
Bearer 0
INP: 47.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 8.17
OR: 0.01 31.32
AgR: 58221.14 14213.23
Bearer 1
INP: 2.00 0.00
INPRein: 2.00 0.00
delay: 0 0
PER: 16.06 0.01
OR: 63.75 0.01
AgR: 63.75 0.01
Bitswap: 394281/394281 8333/8353
Without G.INP the Bearer 1 info is absent throughout.
The indispensable man or woman passes from the scene, and what happens next is more or less the same thing as was happening before.
My broadband basic info/help site - www.robertos.me.uk. Domains, site and mail hosting - Tsohost.
Connection - Plusnet UnLim Fibre (FTTC). Sync 58162/14182kbps @ 600m. - IPv4 BQM IPv6 BQM
|
|
|
Thanks - are you on an ECI cab? I've done a quick google-fu and found that my cab is ECI - is G.Inp being rolled back out on these yet?
My full stats (Billion 8800NL which they say fully supports G.Inp):
| Text | 1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
2425
2627
2829
3031
3233
3435
3637
3839
4041
4243
4445
4647
4849
5051
5253
5455
5657
5859
6061
6263
6465
6667
6869
7071
7273
7475
7677
7879
8081
8283
8485
8687
8889
9091
9293
9495
9697
9899
100101
102103
104105
106107
108109
110111
112113
114115
116117
118119
120 | > xdslctl info --stats
xdslctl: ADSL driver and PHY statusStatus: Showtime
Last Retrain Reason: 0Last initialization procedure status: 0
Max: Upstream rate = 31665 Kbps, Downstream rate = 97764 KbpsBearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79994 Kbps
Link Power State: L0
Mode: VDSL2 Annex BVDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)Trellis: U:ON /D:ON
Line Status: No DefectTraining Status: Showtime
Down UpSNR (dB): 6.5 12.7
Attn(dB): 15.1 0.0Pwr(dBm): 12.6 4.8
VDSL2 framing
Bearer 0MSGc: 18 150
B: 55 236M: 1 1
T: 64 5R: 14 16
S: 0.0223 0.3771L: 25152 5410
D: 1419 1I: 70 255
N: 70 255
Counters Bearer 0
OHF: 16779185 200456OHFErr: 0 0
RS: 3221603486 2000601RSCorr: 77911 1
RSUnCorr: 0 0
Bearer 0HEC: 0 0
OCD: 0 0LCD: 0 0
Total Cells: 2769339612 0Data Cells: 9268054 0
Drop Cells: 0Bit Errors: 0 0
ES: 0 0
SES: 0 0UAS: 0 0
AS: 18005
Bearer 0INP: 3.00 0.00
INPRein: 0.00 0.00delay: 8 0
PER: 1.07 6.15OR: 178.95 202.87
AgR: 80173.22 20203.27
Bitswap: 433/433 1/1
Total time = 5 hours 5 secFEC: 77911 1
CRC: 0 0ES: 0 0
SES: 0 0UAS: 0 0
LOS: 0 0LOF: 0 0
LOM: 0 0Latest 15 minutes time = 5 sec
FEC: 4 0CRC: 0 0
ES: 0 0SES: 0 0
UAS: 0 0LOS: 0 0
LOF: 0 0LOM: 0 0
Previous 15 minutes time = 15 min 0 secFEC: 1577 0
CRC: 0 0ES: 0 0
SES: 0 0UAS: 0 0
LOS: 0 0LOF: 0 0
LOM: 0 0Latest 1 day time = 5 hours 5 sec
FEC: 77911 1CRC: 0 0
ES: 0 0SES: 0 0
UAS: 0 0LOS: 0 0
LOF: 0 0LOM: 0 0
Previous 1 day time = 0 secFEC: 0 0
CRC: 0 0ES: 0 0
SES: 0 0UAS: 0 0
LOS: 0 0LOF: 0 0
LOM: 0 0Since Link time = 5 hours 5 sec
FEC: 77911 1CRC: 0 0
ES: 0 0SES: 0 0
UAS: 0 0LOS: 0 0
LOF: 0 0LOM: 0 0
> |
Edited by deleted (Tue 23-Jun-15 23:18:33)
|
|
|
No... ECI cabs don't support G.INP currently and it looks like they never will.
It looks like DLM has decided your line needed some interleaving on the downstream and has added the normal 8ms step onto it..
If your line stays stable then DLM should remove this in time.
WBC 4400/800 @ 4.2Km > TP-Link TD-W8968v3
FTTC 66000/19999 @ 450m > HG612 > Asus RT-AC87U BQM
|
|
|
|
I thought I had G.inp disabled here, downstream rate too high, but the counters are populated.
Had a power cut yesterday though DLM appeared to intervene overnight.
Max: Upstream rate = 26943 Kbps, Downstream rate = 88420 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 79999 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 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): 2.8 8.7
Attn(dB): 17.1 0.0
Pwr(dBm): 13.9 7.2
LEFTRS: 5 0
minEFTR: 80015 0
errFreeBits: 170025470 0
Modem does seem pretty confused with life though - note the absurd attainable rate.
|
|
|
It's unclear whether or not G.INP is being rolled out to ECI cabs yet. The last I "know" of is that upstream G.INP on Huawei has been disabled to sort out two cockups.
1) Openreach/Contractor engineers handing out non-cabinet matching modems;
2) BT Home Hub 5A not handling upstream G.INP.
I'm on Huawei and HG612.
The indispensable man or woman passes from the scene, and what happens next is more or less the same thing as was happening before.
My broadband basic info/help site - www.robertos.me.uk. Domains, site and mail hosting - Tsohost.
Connection - Plusnet UnLim Fibre (FTTC). Sync 58162/14182kbps @ 600m. - IPv4 BQM IPv6 BQM
|
Pages in this thread: 
Print Thread
