DLM strikes again.

Several days ago DLM decided once again that my line needed interleaving, this time at a depth of 1433. It was at the tail end of the recent storms, so may have been that or even OR working on the cab maybe disturbed my line.

My errors are not bad, I have 67 errored seconds in over 1.4 million, my other stats don't have large errors either. I wish that you could request that DLM be turned off.

Roll on the deployment of FTTPoD, that will get rid of DLM.

In reply to a post by TheHorseman:

Roll on the deployment of FTTPoD, that will get rid of DLM.

And your bank balance .

funny enough DLM doesnt want to interleave my line, I have FEC on fast path with crc errors coming in the 1000s

Below are my current stats, can anyone suggest why DLM thinks I need an interleave of 1433?

# xdslcmd info --show
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 32641 Kbps, Downstream rate = 83960 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 73187 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 15.2
Attn(dB): 14.0 0.0
Pwr(dBm): 13.1 4.3
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 51 237
M: 1 1
T: 64 42
R: 12 16
S: 0.0226 0.3781
L: 22648 5374
D: 1433 1
I: 64 127
N: 64 254
Counters
Bearer 0
OHF: 1025485681 3311373
OHFErr: 520 218
RS: 531154772 2382555
RSCorr: 3208647 1567
RSUnCorr: 26739 0

Bearer 0
HEC: 6605 0
OCD: 122 0
LCD: 122 0
Total Cells: 3459140466 0
Data Cells: 616454956 0
Drop Cells: 0
Bit Errors: 0 0

ES: 107 190
SES: 0 16
UAS: 24 24
AS: 1489538

Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 1.45 3.98
OR: 132.18 64.22
AgR: 73319.59 20063.54

Bitswap: 1095623/1095626 51348/51498

#

you didnt show the most important info FEC/CRC/ES/SES counts.

I can't see anything obvious.

Maybe it was a reaction to 'something' that happened 17 days ago, around the time the connection resynced.

It may be worth forcing a single resync now.
I wouldn't be at all surprised if it returned to fastpath.

For FEC, read the RSCorr data.

For CRC, read the OHFErr data.

ES & SES are actually shown in the posted log data extract.

Ok, full stats:

# xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 32641 Kbps, Downstream rate = 84192 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 73187 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.2
Attn(dB): 14.0 0.0
Pwr(dBm): 13.1 4.3
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 51 237
M: 1 1
T: 64 42
R: 12 16
S: 0.0226 0.3781
L: 22648 5374
D: 1433 1
I: 64 127
N: 64 254
Counters
Bearer 0
OHF: 1030930124 1076618
OHFErr: 530 218
RS: 1924932067 134404
RSCorr: 3227369 1575
RSUnCorr: 27953 0

Bearer 0
HEC: 6936 0
OCD: 125 0
LCD: 125 0
Total Cells: 277061155 0
Data Cells: 620460008 0
Drop Cells: 0
Bit Errors: 0 0

ES: 109 190
SES: 0 16
UAS: 24 24
AS: 1497447

Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 1.45 3.98
OR: 132.18 64.22
AgR: 73319.59 20063.54

Bitswap: 1101655/1101657 52135/52286

Total time = 1 days 7 hours 57 min 51 sec
FEC: 3227369 1575
CRC: 530 218
ES: 109 190
SES: 0 16
UAS: 24 24
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 12 min 51 sec
FEC: 3596 0
CRC: 3 0
ES: 1 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: 5603 0
CRC: 7 0
ES: 1 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 7 hours 57 min 51 sec
FEC: 220942 26
CRC: 253 5
ES: 42 5
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 172196 48
CRC: 50 11
ES: 10 9
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 17 days 7 hours 57 min 25 sec
FEC: 3227369 1575
CRC: 530 218
ES: 109 190
SES: 0 16
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#

Thanks, I did not think that the errors were that bad, I will leave it over night and if there is no change I'll do a single resync and see if that changes things.

I would only do that if your SNRM from the pbParams data is showing a healthy margin above the target SNRM of 6 dB at around noon. i.e. if it shows as say 8dB or more.

Edited by deleted (Sat 30-Aug-14 23:32:03)