Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: boost on January 31, 2019, 01:30:47 AM
-
Noticed my ping had increased tonight.
11ms -> 19ms
Had a peek at the modem to find I am now synched at 70 something instead of 40. Vaguely remember Sky saying I was getting upgraded several months ago and it would be cheaper. OK, cool.
Stats appear to be:
Stats recorded 31 Jan 2019 01:27:32
DSLAM type / SW version: BDCM:0xb12d (177.45) / v0xb12d
Modem/router firmware: AnnexA version - A2pv6C038m.d24j
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 0 hour 47 min 28 sec
Resyncs: 0 (since 31 Jan 2019 01:23:30)
Downstream Upstream
Line attenuation (dB): 12.7 0.0
Signal attenuation (dB): Not monitored
Connection speed (kbps): 71814 20000
SNR margin (dB): 6.3 13.2
Power (dBm): 13.3 -2.7
Interleave depth: 1196 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 0
Interleave depth: 1196 1
INP: 3.00 0
G.INP: Not enabled Not enabled
I hope this is temporary? :)
-
Has it been DLM resetted by Sky?
-
You have been upgraded to 80/20 FTTC, this change causes a DLM reset so G.INP is removed but should come back on in a couple of days. You should then get near full (80 Mbps) download sync speed.
-
Cheers chaps.
Some more stats since I plugged dslstats in, more as a reminder to myself I guess.
Looks like I get a few (8) upstream CRCs/ES per hour. My internal wiring perhaps?
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 31711 Kbps, Downstream rate = 82404 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 71814 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.1 13.5
Attn(dB): 12.7 0.0
Pwr(dBm): 13.3 -2.7
VDSL2 framing
Bearer 0
MSGc: 15 20
B: 60 239
M: 1 1
T: 64 64
R: 14 0
S: 0.0270 0.3819
L: 22200 5028
D: 1196 1
I: 75 120
N: 75 240
Counters
Bearer 0
OHF: 46505394 1675352
OHFErr: 0 144
RS: 338954914 3079184
RSCorr: 12148 0
RSUnCorr: 0 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 4069339151 0
Data Cells: 275554871 0
Drop Cells: 0
Bit Errors: 0 0
ES: 0 133
SES: 0 0
UAS: 22 22
AS: 60568
Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 1.30 6.13
OR: 128.99 33.91
AgR: 71942.97 20033.74
Bitswap: 27173/27173 42/42
Total time = 16 hours 49 min 50 sec
FEC: 12148 0
CRC: 0 144
ES: 0 133
SES: 0 0
UAS: 22 22
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 4 min 50 sec
FEC: 315 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: 379 0
CRC: 0 3
ES: 0 3
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 16 hours 49 min 50 sec
FEC: 12148 0
CRC: 0 144
ES: 0 133
SES: 0 0
UAS: 22 22
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 0 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
Since Link time = 16 hours 49 min 27 sec
FEC: 12148 0
CRC: 0 144
ES: 0 133
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
I've also had the landline plugged in this week which is never normally attached so I guess that may have not helped. Detached since this monitoring started, though.
-
DLM will turn on your G.INP within next few days. Usually after 2-3 days of remain stable. You should see full 80Meg no problem.
-
4 days since last resync. No change.
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 31900 Kbps, Downstream rate = 82176 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 71814 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.1 13.5
Attn(dB): 12.7 0.0
Pwr(dBm): 13.3 -2.7
VDSL2 framing
Bearer 0
MSGc: 15 20
B: 60 239
M: 1 1
T: 64 64
R: 14 0
S: 0.0270 0.3819
L: 22200 5028
D: 1196 1
I: 75 120
N: 75 240
Counters
Bearer 0
OHF: 266322442 1851371
OHFErr: 61 1662
RS: 3889122463 4059231
RSCorr: 154901 0
RSUnCorr: 3363 0
Bearer 0
HEC: 928 0
OCD: 10 0
LCD: 10 0
Total Cells: 655396671 0
Data Cells: 2541586608 0
Drop Cells: 0
Bit Errors: 0 0
ES: 9 1453
SES: 0 0
UAS: 22 22
AS: 346856
Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 1.30 6.13
OR: 128.99 33.91
AgR: 71942.97 20033.74
Bitswap: 177803/177803 244/245
Total time = 1 days 21 min 18 sec
FEC: 154901 0
CRC: 61 1662
ES: 9 1453
SES: 0 0
UAS: 22 22
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 6 min 18 sec
FEC: 0 0
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 667 0
CRC: 0 2
ES: 0 2
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 21 min 18 sec
FEC: 667 0
CRC: 0 3
ES: 0 3
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 37990 0
CRC: 41 323
ES: 5 292
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 4 days 20 min 55 sec
FEC: 154901 0
CRC: 61 1662
ES: 9 1453
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
-
Resync. No difference.
Resync capped. Worse? :P
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 31771 Kbps, Downstream rate = 83140 Kbps
Bearer: 0, Upstream rate = 14997 Kbps, Downstream rate = 59993 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): 9.3 16.4
Attn(dB): 12.7 0.0
Pwr(dBm): 13.3 -2.9
VDSL2 framing
Bearer 0
MSGc: 14 29
B: 47 31
M: 1 1
T: 64 64
R: 14 2
S: 0.0255 0.0678
L: 19480 4009
D: 1273 1
I: 62 34
N: 62 34
Counters
Bearer 0
OHF: 494513 106484
OHFErr: 0 0
RS: 126440281 451723
RSCorr: 1 0
RSUnCorr: 0 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 93252937 0
Data Cells: 2246053 0
Drop Cells: 0
Bit Errors: 0 0
ES: 0 2
SES: 0 0
UAS: 53 53
AS: 810
Bearer 0
INP: 3.50 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 1.63 7.62
OR: 97.80 36.70
AgR: 60090.43 15033.97
Bitswap: 179/179 0/0
Total time = 36 min 54 sec
FEC: 122 0
CRC: 0 2
ES: 0 2
SES: 0 0
UAS: 53 53
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 6 min 54 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: 122 0
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 30 30
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 36 min 54 sec
FEC: 122 0
CRC: 0 2
ES: 0 2
SES: 0 0
UAS: 53 53
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 0 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
Since Link time = 13 min 29 sec
FEC: 1 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
-
I'm guessing this is not going to have any immediate effect. Kinda annoying. I also changed the power source tonight (removed it from a shared bank).
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 31636 Kbps, Downstream rate = 82912 Kbps
Bearer: 0, Upstream rate = 10997 Kbps, Downstream rate = 47993 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): 13.3 19.2
Attn(dB): 12.7 0.0
Pwr(dBm): 13.2 -2.8
VDSL2 framing
Bearer 0
MSGc: 18 36
B: 31 31
M: 1 1
T: 64 64
R: 10 2
S: 0.0212 0.0925
L: 15840 2941
D: 1537 1
I: 42 34
N: 42 34
Counters
Bearer 0
OHF: 43531 8597
OHFErr: 0 0
RS: 16529700 3850547
RSCorr: 0 0
RSUnCorr: 0 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 8184553 0
Data Cells: 1207 0
Drop Cells: 0
Bit Errors: 0 0
ES: 0 2
SES: 0 0
UAS: 84 84
AS: 89
Bearer 0
INP: 3.50 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 2.04 10.39
OR: 93.91 32.31
AgR: 48086.44 11028.91
Bitswap: 5/5 0/0
Total time = 40 min 17 sec
FEC: 122 0
CRC: 0 2
ES: 0 2
SES: 0 0
UAS: 84 84
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 10 min 17 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 31 31
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 122 0
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 30 30
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 40 min 17 sec
FEC: 122 0
CRC: 0 2
ES: 0 2
SES: 0 0
UAS: 84 84
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 0 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
Since Link time = 1 min 29 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
#
-
Are you rebooting the modem yourself or is it DLM taking action?
Something isn't looking right there.
-
How many times have you resynced/restarted the modem?
-
Are you deliberately capping the speed or does it now sync like that without capping, as if so it's looking like it's banded and you really need to stop re-syncing as it's only making things worse.
I'd leave it alone (like don't touch it at all) for a few days and if nothing changes I'd ask for a DLM reset as you've "had problems with a faulty router" ;)
-
I'll chip in the same as others.
DLM will never ever make a positive change to the line from you performing a resync.
It treats resyncs as instability and will apply banding (capping the line) if you resync too often.
You've gone from a normal 71Mb sync, to what appears 60Mb capped, then 48Mb capped.
Is this a manual cap placed by you?
If not...oh dear. That's some of the harshest banding I've seen in a short period of time.
Banding sticks. DLM adds it easy but takes months to lower it in small steps or it just never removes at all.
If it's a manual cap, why? That won't speed up G.INP.
edit: looks like a manual cap. Just noticed the upstream.
Why is the upstream capped at 11Mb? DLM treats upstream/downstream as separate entities. Capping the upstream won't affect downstream G.INP either.
IMO you are more like to prevent G.INP being applied by messing with the line than just leading it alone.
For most people it will take 2 days for G.INP to be applied.
It took 11 weeks for my line, 7 weeks for Tiffy's line.
My advice is uncap the line and leave it alone.
-
They were all manual caps. I suppose I have an irrational desire to see my latency return to normal, I've never cared about throughput.
Patience is not one of my virtues, I suppose.
-
OK, back we go:
Stats recorded 04 Feb 2019 13:04:19
DSLAM type / SW version: BDCM:0xb12d (177.45) / v0xb12d
Modem/router firmware: AnnexA version - A2pv6C038m.d24j
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 0 hour 1 min 20 sec
Resyncs: 0 (since 04 Feb 2019 13:03:16)
Downstream Upstream
Line attenuation (dB): 12.8 0.0
Signal attenuation (dB): Not monitored
Connection speed (kbps): 71866 20000
SNR margin (dB): 6.2 13.1
Power (dBm): 13.3 -2.8
Interleave depth: 1196 1
INP: 3.00 0
G.INP: Not enabled Not enabled
Vectoring status: 5 (VECT_UNCONFIGURED)
RSCorr/RS (%): 0.0000 0.0000
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 0 0
As an aside, what is the rationale in not starting from 'the best point' on a DLM reset?
8ms of delay is ridiculous. Openreach are better than this.
[Moderator edited to remove the postcode.]
-
I guess it depends on what you consider to be the best point. ;)
My brothers line took many weeks, possibly even a couple of months before g.inp was applied, although I think this was before they applied interleaving as standard.
-
I imagine interleaving is applied by default because it will give a working start position for the majority of lines. Your line looks somewhat better than most so will (if you leave it alone ;)) hopefully soon decide that it's not required.
Only time will tell.
:)
-
leave the line alone, thats my advise
-
Yes best to leave it alone or DLM will bite your line alots worsen.
-
Yep, you're right. As of yesterday, I've stopped poking it :D
Just posting some stats here for future reference.
Stats
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 31067 Kbps, Downstream rate = 82912 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 71866 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.2 13.1
Attn(dB): 12.8 0.0
Pwr(dBm): 13.3 -2.7
VDSL2 framing
Bearer 0
MSGc: 15 20
B: 60 239
M: 1 1
T: 64 64
R: 14 0
S: 0.0270 0.3819
L: 22216 5028
D: 1196 1
I: 75 120
N: 75 240
Counters
Bearer 0
OHF: 72828517 1783658
OHFErr: 3 235
RS: 1098027165 715736
RSCorr: 25393 0
RSUnCorr: 3 0
Bearer 0
HEC: 1 0
OCD: 0 0
LCD: 0 0
Total Cells: 213809108 0
Data Cells: 219824869 0
Drop Cells: 0
Bit Errors: 0 0
ES: 1 228
SES: 0 0
UAS: 23 23
AS: 94783
Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 1.30 6.13
OR: 129.08 33.91
AgR: 71994.82 20033.74
Bitswap: 47472/47472 33/33
Total time = 1 days 2 hours 20 min 6 sec
FEC: 25393 0
CRC: 3 235
ES: 1 228
SES: 0 0
UAS: 23 23
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 5 min 6 sec
FEC: 0 0
CRC: 0 2
ES: 0 2
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 248 0
CRC: 0 2
ES: 0 2
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 2 hours 20 min 6 sec
FEC: 517 0
CRC: 0 22
ES: 0 22
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 24876 0
CRC: 3 213
ES: 1 206
SES: 0 0
UAS: 23 23
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 1 days 2 hours 19 min 43 sec
FEC: 25393 0
CRC: 3 235
ES: 1 228
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
pbParams
xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 31067 Kbps, Downstream rate = 82912 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 71866 Kbps
Discovery Phase (Initial) Band Plan
US: (7,32) (871,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3959)
Medley Phase (Final) Band Plan
US: (7,32) (871,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3959)
VDSL Port Details Upstream Downstream
Attainable Net Data Rate: 31067 kbps 82912 kbps
Actual Aggregate Tx Power: - 2.7 dBm 13.3 dBm
====================================================================================
VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
Line Attenuation(dB): 4.3 12.6 19.4 N/A N/A 8.2 17.3 23.9
Signal Attenuation(dB): 4.3 11.9 19.0 N/A N/A 11.7 17.4 23.9
SNR Margin(dB): 13.2 13.1 13.0 N/A N/A 6.2 6.2 6.2
TX Power(dBm): -17.2 -31.8 -3.0 N/A N/A 10.2 7.7 7.1
#
U1 shows the highest SNRM fluctuation (10.2 - 13.7).
-
Do you know if you are on an ECI or Huawei cabinet?
-
BDCM so Huawei, I guess?
Stats recorded 05 Feb 2019 17:55:01
DSLAM type / SW version: BDCM:0xb12d (177.45) / v0xb12d
Modem/router firmware: AnnexA version - A2pv6C038m.d24j
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 1 day 4 hours 52 min 3 sec
Resyncs: 0 (since 05 Feb 2019 17:53:59)
Downstream Upstream
Line attenuation (dB): 12.8 0.0
Signal attenuation (dB): Not monitored
Connection speed (kbps): 71866 20000
SNR margin (dB): 6.2 13.1
Power (dBm): 13.3 -2.7
Interleave depth: 1196 1
INP: 3.00 0
G.INP: Not enabled Not enabled
Vectoring status: 5 (VECT_UNCONFIGURED)
RSCorr/RS (%): 0.0012 0.0000
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 0 30.3
Suspect the ES/hour number is misreported there too? My connection has been up just under 29 hours with the upstream ES counter showing 255, atm.
255 / 29 = 8.79
Is that how it works? I'm terrible at maths :D
-
I was looking back to last year when openreach has resetted my line and g.inp has disappear for 2 days before it come back.
Connection stats
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 26797 Kbps, Downstream rate = 80556 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 67526 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.2 15.1
Attn(dB): 12.0 0.0
Pwr(dBm): 12.5 0.9
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 51 237
M: 1 1
T: 64 42
R: 12 16
S: 0.0245 0.3781
L: 20896 5374
D: 1321 1
I: 64 127
N: 64 254
Counters
Bearer 0
OHF: 138477 54774
OHFErr: 0 0
RS: 35450023 2299498
RSCorr: 0 0
RSUnCorr: 0 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 28308888 0
Data Cells: 12256 0
Drop Cells: 0
Bit Errors: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
AS: 218
Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 1.57 3.98
OR: 121.96 64.22
AgR: 67647.75 20063.54
Bitswap: 0/0 0/0
Total time = 7 min 0 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
Latest 15 minutes time = 7 min 0 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 = 0 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
Latest 1 day time = 7 min 0 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 1 day time = 0 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
Since Link time = 7 min 0 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
________________________________________________________________________________________
xDSL
Mode VDSL2
Traffic Type PTM
Status Up
Link Power State L0
Downstream Upstream
Line Coding (Trellis) On On
SNR Margin (dB) 6.2 15.1
Attenuation (dB) 12.0 0.0
Output Power (dBm) 12.5 0.9
Attainable Rate (Kbps) 80556 26797
Rate (Kbps) 67526 19999
B (# of bytes in Mux Data Frame) 51 237
M (# of Mux Data Frames in an RS codeword) 1 1
T (# of Mux Data Frames in an OH sub-frame) 64 42
R (# of redundancy bytes in the RS codeword) 12 16
S (# of data symbols over which the RS code word spans) 0.0245 0.3781
L (# of bits transmitted in each data symbol) 20896 5374
D (interleaver depth) 1321 1
I (interleaver block size in bytes) 64 127
N (RS codeword size) 64 254
Delay (msec) 8 0
INP (DMT symbol) 3.00 0.00
OH Frames 217243 85573
OH Frame Errors 0 0
RS Words 55614255 3611371
RS Correctable Errors 0 0
RS Uncorrectable Errors 0 0
HEC Errors 0 0
OCD Errors 0 0
LCD Errors 0 0
Total Cells 44411191 0
Data Cells 14932 0
Bit Errors 0 0
Total ES 0 0
Total SES 0 0
Total UAS 0 0
________________________________________________________________________________________
Stats recorded 21 Aug 2018 11:33:00
DSLAM type / SW version: BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware: AnnexA version - A2pv6F039g1.d24m
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 0 hour 7 min 0 sec
Resyncs: 0 (since 21 Aug 2018 11:33:00)
Downstream Upstream
Line attenuation (dB): 12.0 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 67526 19999
SNR margin (dB): 6.2 15.1
Power (dBm): 12.5 0.9
Interleave depth: 1321 1
INP: 3.00 0
G.INP: Not enabled Not enabled
Vectoring status: 5 (VECT_UNCONFIGURED)
RSCorr/RS (%): 0.0000 0.0000
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 0 0
_________________________________________________________________________________________
80556 26797 Attainable Rate (Kbps)
67526 19999 Sync Rate (Kbps)
6.2 15.1 SNR Margin (dB)
12.0 0.0 Line Attenuation (dB)
12.5 0.9 Output Power (dBm)
1321 1 Interleave Depth
3.00 0.00 INP
Not enabled Not enabled G.INP
5 (VECT_UNCONFIGURED) Vectoring status
Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 1.57 3.98
OR: 121.96 64.22
AgR: 67647.75 20063.54
Bitswap: 0/0 0/0
2 days later G.INP come back ON
Downstream Upstream
Line attenuation (dB): 11.9 0.0
Signal attenuation (dB): Not available on VDSL2
Attenuation rate (kbps): 79191 27652
Connection speed (kbps): 78461 19999
SNR margin (dB): 6.4 15.1
Power (dBm): 12.4 0.9
Interleave depth: 8 1
INP: 49.00 0
G.INP: Enabled Not Enabled
-
BDCM so Huawei, I guess?
Correct.
-
;D ;D ;D :P :P :P Love the Huawei cabinet rather than ECI.
-
I was looking back to last year when openreach has resetted my line and g.inp has disappear for 2 days before it come back.
Nice.
This is South Wales, though. A half-assed job is perfectly acceptable here, it seems.
-
Yes, sorry. I was just up, I should have looked back at your previous posts. With any luck, hopefully DLM tries to lower your target SNR to bump the speed up further. After a reset or line change, this can take a few weeks.
The first time my line was reset it took about 6 days to running at optimum. The second time it took 12 days. Others have waited a lot longer.
-
Day 3. Again :D
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 30990 Kbps, Downstream rate = 82684 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 71866 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.1 13.0
Attn(dB): 12.8 0.0
Pwr(dBm): 13.2 -2.7
VDSL2 framing
Bearer 0
MSGc: 15 20
B: 60 239
M: 1 1
T: 64 64
R: 14 0
S: 0.0270 0.3819
L: 22216 5028
D: 1196 1
I: 75 120
N: 75 240
Counters
Bearer 0
OHF: 202745918 1997713
OHFErr: 10 665
RS: 272364333 2301163
RSCorr: 73848 0
RSUnCorr: 269 0
Bearer 0
HEC: 76 0
OCD: 2 0
LCD: 2 0
Total Cells: 2105574738 0
Data Cells: 483388664 0
Drop Cells: 0
Bit Errors: 0 0
ES: 2 626
SES: 0 0
UAS: 23 23
AS: 263865
Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 1.30 6.13
OR: 129.08 33.91
AgR: 71994.82 20033.74
Bitswap: 134531/134531 73/73
Total time = 1 days 1 hours 18 min 8 sec
FEC: 73848 0
CRC: 10 665
ES: 2 626
SES: 0 0
UAS: 23 23
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 3 min 8 sec
FEC: 5 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: 46 0
CRC: 0 2
ES: 0 2
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 1 hours 18 min 8 sec
FEC: 1458 0
CRC: 0 8
ES: 0 8
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 23798 0
CRC: 0 190
ES: 0 177
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 3 days 1 hours 17 min 43 sec
FEC: 73848 0
CRC: 10 665
ES: 2 626
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
-
Leave it alone let DLM decided when to put G. INP enabled but keeping resync won't help it and make it lots longer to wait for the G. INP to be switching on.
-
You'll hopefully start seeing the SNR adjustments coming in around day 9.
-
ON THE NINTH DAY OF CHRISTMAS, MY TRUE LOVE GAVE TO ME...
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 31268 Kbps, Downstream rate = 82912 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 71866 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.2 13.2
Attn(dB): 12.8 0.0
Pwr(dBm): 13.3 -2.7
VDSL2 framing
Bearer 0
MSGc: 15 20
B: 60 239
M: 1 1
T: 64 64
R: 14 0
S: 0.0270 0.3819
L: 22216 5028
D: 1196 1
I: 75 120
N: 75 240
Counters
Bearer 0
OHF: 613171582 1552343
OHFErr: 97 1986
RS: 1764680564 1179816
RSCorr: 249756 0
RSUnCorr: 3307 0
Bearer 0
HEC: 920 0
OCD: 20 0
LCD: 20 0
Total Cells: 2909210962 0
Data Cells: 2521041725 0
Drop Cells: 0
Bit Errors: 0 0
ES: 17 1846
SES: 0 0
UAS: 23 23
AS: 798014
Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 1.30 6.13
OR: 129.08 33.91
AgR: 71994.82 20033.74
Bitswap: 409969/409969 290/290
Total time = 1 days 5 hours 40 min 37 sec
FEC: 249756 0
CRC: 97 1986
ES: 17 1846
SES: 0 0
UAS: 23 23
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 10 min 37 sec
FEC: 337 0
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 487 0
CRC: 0 4
ES: 0 3
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 5 hours 40 min 37 sec
FEC: 4129 0
CRC: 0 79
ES: 0 66
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 23339 0
CRC: 10 232
ES: 2 219
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 9 days 5 hours 40 min 13 sec
FEC: 249756 0
CRC: 97 1986
ES: 17 1846
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
...NOTHING FROM GEEEEEEE AYE EN PEEEEEE!
-
Maybe someone can answer this but why does the total time only show as 1 day and 5hrs? Your link time shows the 9 days.
I guess it is just a waiting game and hope DLM decides to start lowering the SNR target.
-
Good spot!
Just checked the Windows client and it shows the same. One more day before all faith in the system is lost :P
-
Maybe someone can answer this but why does the total time only show as 1 day and 5hrs? Your link time shows the 9 days.
I guess it is just a waiting game and hope DLM decides to start lowering the SNR target.
The total is 11 days and 5 hours.
It misses the first 1 on some devices.
A bug that had been noticed in the past.
-
I see. I didn't know that. Handy to know, Thanks!
-
Still interleaved all shapes.
-
So, this finally got fixed this morning!
The delay is mostly my own fault as I couldn't get time off work. Long story short:
OR booking 1: No show but I showed a resynch that morning.
OR booking 2: A very helpful chap turned up (thanks Mark) and found that I had always had a bridge tap within my extension wiring (I rent). He fixed that and put a shiny new faceplate thing on the wall (Master Socket 5C). My ping was still double what it should be but I noticed my attenuation was now 3dB less than before. Seeing there was a visible improvement to the line, I let him go and crossed my fingers that the cab would notice things were looking tip top.
That was Thursday morning.
It's now Saturday.
I game every day and habitually check base latency before I start - so I have nothing to blame but myself for my poor performance :)
I checked just now and I'm finally back to 10ms UK RTT.
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=10ms TTL=124
Reply from 8.8.8.8: bytes=32 time=10ms TTL=124
Reply from 8.8.8.8: bytes=32 time=10ms TTL=124
Reply from 8.8.8.8: bytes=32 time=10ms TTL=124
Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 10ms, Average = 10ms
I still have the SR102 attached atm but I am now also showing full sync, as it always should have:
Broadband Link Downstream Upstream
Connection Speed 79999 kbps 20000 kbps
Line Attenuation 9.7 dB 0.0 dB
Noise Margin 6.6 dB 14.14 dB
Speedtest looks good too, attached.
Funny thing is, I saw an article posted the other day that Sky had somehow tied bottom place in some ISP ranking.
I didn't believe it for a second.
-
Sounds like the engineer performed a DLM reset.
As it should DLM applied G.INP 2 days later, knocking 8ms off the base latency.
-
in what scenario would g.inp not get enabled? i had a regrade from 40 to 80, interleaving was applied for 48 hours as expected then removed (all i really care about as a gamer)
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=7ms TTL=123
Reply from 8.8.8.8: bytes=32 time=7ms TTL=123
Reply from 8.8.8.8: bytes=32 time=8ms TTL=123
Reply from 8.8.8.8: bytes=32 time=7ms TTL=123
g.inp is enabled on upstream but not downstream. sorry to hijack the thread, seems kinda the same situation though.
just interested to know why g.inp isnt on downstream and what advantage would it being enabled give me?
stats attached
-
The Draytek retx status is the wrong way around. You've got g.inp on the downstream and not on the upstream.
-
aha thankyou! is that a common Draytek thing?
-
It's what Draytek have done. The first three items, trellis, bitswap and retx don't really belong under "near end" and "far end" - the generic Lantiq command uses upstream and downstream for them.
-
thanks for info!
-
line reconnected in the night and now it says on for both upstream and down, attainable rate risen too from it. strange!
-
The default for lines connected to Huawei cabinets is G.INP/ReTx is enabled on the downstream.
It's enabled on the upstream if there is a high number of upstream errors.
It looks like you had over 6000 upstream ES between the 2 sets of stats you posted.
If the upstream ES persist then ReTx will remain enabled.
If the upstream ES drop to a considerably lower level then DLM will remove ReTx from the upstream.
-
in what scenario would g.inp not get enabled? i had a regrade from 40 to 80, interleaving was applied for 48 hours as expected then removed (all i really care about as a gamer)
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=7ms TTL=123
Reply from 8.8.8.8: bytes=32 time=7ms TTL=123
Reply from 8.8.8.8: bytes=32 time=8ms TTL=123
Reply from 8.8.8.8: bytes=32 time=7ms TTL=123
g.inp is enabled on upstream but not downstream. sorry to hijack the thread, seems kinda the same situation though.
just interested to know why g.inp isnt on downstream and what advantage would it being enabled give me?
stats attached
Loving the 7ms!
What ISP? Whereabouts are you? :D
-
sorry did not see this.
I'm in south leicestershire and my isp is voicehost (i resell phone systems and leased lines for them so have my fibre but it seems great for latency)
only downside is sometimes it auths via manchester and pings are 20ms but a few redials normally hits london and 7/8ms again