FTTC stats 2013 vs 2017

2013 Stats:

xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 13813 Kbps, Downstream rate = 64968 Kbps
Path: 0, Upstream rate = 13847 Kbps, Downstream rate = 64067 Kbps

Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 6.3 6.0
Attn(dB): 0.0 0.0
Pwr(dBm): 13.9 6.8
VDSL2 framing
Path 0
B: 239 237
M: 1 1
T: 21 62
R: 0 16
S: 0.1192 0.5467
L: 16105 3717
D: 1 1
I: 240 127
N: 240 254
Counters
Path 0
OHF: 377185 83960
OHFErr: 146 0
RS: 0 909379
RSCorr: 0 0
RSUnCorr: 0 0

Path 0
HEC: 14 0
OCD: 0 0
LCD: 0 0
Total Cells: 87556875 0
Data Cells: 10637 0
Drop Cells: 0
Bit Errors: 0 0

ES: 2 0
SES: 0 0
UAS: 18 18
AS: 713

Path 0
INP: 0.00 0.00
PER: 1.87 8.47
delay: 0.00 0.00
OR: 102.25 30.21

Bitswap: 105 45

#

2017 Stats with faceplate removed:

xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 16400 Kbps, Downstream rate = 58032 Kbps
Bearer: 0, Upstream rate = 14991 Kbps, Downstream rate = 53999 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): 7.4 5.9
Attn(dB): 16.8 0.0
Pwr(dBm): 13.9 6.9
VDSL2 framing
Bearer 0
MSGc: -6 29
B: 158 47
M: 1 1
T: 0 64
R: 10 2
S: 0.0935 0.1018
L: 14456 3928
D: 16 1
I: 169 50
N: 169 50
Q: 16 0
V: 7 0
RxQueue: 33 0
TxQueue: 11 0
G.INP Framing: 18 0
G.INP lookback: 11 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 21249
OHFErr: 0 0
RS: 7327680 2503025
RSCorr: 14840 0
RSUnCorr: 0 0
Bearer 1
OHF: 10770 0
OHFErr: 0 0
RS: 85665 0
RSCorr: 0 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 423 0
rtx_c: 0 0
rtx_uc: 0 0

G.INP Counters
LEFTRS: 0 0
minEFTR: 54001 0
errFreeBits: 142492 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 17925684 0
Data Cells: 422 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: 0 0
SES: 0 0
UAS: 27 27
AS: 173

Bearer 0
INP: 47.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 8.17
OR: 0.01 34.23
AgR: 54190.77 15024.82

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: 0/0 12/12

Total time = 3 min 20 sec
FEC: 14840 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 27 27
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 3 min 20 sec
FEC: 14840 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 27 27
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 = 3 min 20 sec
FEC: 14840 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 27 27
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 = 2 min 53 sec
FEC: 14840 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0

Nearly a 11 mbps difference over 4 years! Can anyone offer any insight into why this could be the case from looking at the two statistics provided above?

TIA!

Edited by Bobby_Valentino (Tue 04-Apr-17 14:37:58)

I would say a combination of crosstalk and due to instability on the line, downstream banding. To get the banding removed, you'll need to organise a broadband boost engineer with your ISP.

Edited by deleted (Tue 04-Apr-17 14:35:39)

As you say, it looks like banding, but a boost engineer doesn't look appropriate to me at this stage, given the interleaving depth of 16 on G.INP rather than the default 8. I'd like to see those error stats after a while to see what is upsetting DLM. Both sets were taken very soon after reboots of the modem.

That's a point and I didn't spot that, Bob. I was commenting on why the speeds had dropped. But, yes maybe a SFI engineer would be more appropriate so they could see what is causing the problem and then once they've fixed it, they can reset the DLM.

Interestingly, something I've only just noticed, the Bearer 1 depth is 1, (Fast Path) where I think we usually see 3.

Hmm, I've had upstream G.INP with interleaver depth of 1.

You are talking about Bearer 0. I'm talking about Bearer 1 downstream.

I was talking about my connection not the OP's.

I suspect an SFI engineer would say line is within tolerance and the visit would be chargeable as no fault found. BT won't do visits when there is essentially no visible fault - loss of speed through crosstalk is normal and BT will not hunt down minor issues on lines.

Permanent banding isn't common though Ian. So far as we know, that is. Especially with an interleaving depth of 16. New stats each 24 hours for three to four days are needed so we can see the error rates. Better still, some monitoring such as DSLStats and MyDSLStats.