Does the DLM have a VINDICTIVE setting (joke) ?

[#1]

Sorry if I upset the mod by starting another thread!!

I did only post this for fun, it just feels like it sometimes

I keep getting these weird disconnects, tonight after running a whole 24 hours the DLM ? jumped on me, disconnected the downlink and restarted it with snr 4dB higher with a consequent loss in sync speed, so I hit back and disconnected it, result back to previous snr and rate, so why does it do it, just to be vindictive ?

See attached snr plot and here are the stats

adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Max: Upstream rate = 864 Kbps, Downstream rate = 6172 Kbps
Path: 0, Upstream rate = 864 Kbps, Downstream rate = 4920 Kbps

Link Power State: L0
Mode: ADSL2+
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 4.3 7.8
Attn(dB): 53.5 31.1
Pwr(dBm): 0.0 12.8
ADSL2 framing
MSGc: 60 64
B: 151 13
M: 1 8
T: 1 2
R: 12 16
S: 0.9820 4.0000
L: 1336 256
😧 32 8
Counters
SF: 121570 112514
SFErr: 95 0
RS: 8023674 1969004
RSCorr: 240090 0
RSUnCorr: 555 0

HEC: 79 0
OCD: 0 0
LCD: 0 0
Total Cells: 22861935 1243665
Data Cells: 489027 4588
Drop Cells: 0
Bit Errors: 0 0

ES: 38582 0
SES: 5354 0
UAS: 806 4294966700
AS: 1970

INP: 1.14 2.00
PER: 16.20 17.50
delay: 7.85 8.00
OR: 32.58 32.00

Bitswap: 298 1

Total time = 1 days 3 hours 20 min 53 sec
FEC: 162955363 0
CRC: 350333 0
ES: 38582 0
SES: 5354 0
UAS: 806 4294966700
LOS: 20 4294967268
LOF: 79 4294967268
Latest 15 minutes time = 5 min 53 sec
FEC: 39464 0
CRC: 9 0
ES: 9 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 98004 0
CRC: 53 0
ES: 39 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Latest 1 day time = 3 hours 20 min 53 sec
FEC: 2012367 0
CRC: 10233 0
ES: 925 0
SES: 160 0
UAS: 72 4294967254
LOS: 2 4294967293
LOF: 9 4294967293
Previous 1 day time = 24 hours 0 sec
FEC: 13500945 0
CRC: 8329 0
ES: 6958 0
SES: 18 0
UAS: 26 4294967272
LOS: 1 4294967295
LOF: 9 4294967295
Since Link time = 32 min 49 sec
FEC: 240090 0
CRC: 95 0
ES: 76 0
SES: 0 0
UAS: 0 4294967182
LOS: 0 4294967293
LOF: 0 4294967293
>

[#2]

Looking at those stats your line seems to be getting quite a few errored seconds (ES), which is likely the reason the DLM is intervening.

[#3]

Hello Chris, thank you for your reply, that's exactly what I am trying to find out somewhere, a list of things that will provoke the DLM to react in real-time instead of its daily number crunch in the early hours.

The odd thing is after this event one would have expected it to change the target snr or interleaving yet a subsequent line disconnect a few minutes later by me immediately restores the situation to the previous operating snr hence I am becoming suspicions this is not a DLM event at all, and as someone commented on another thread the fall time and rise time of snr doesn't exactly equate to a disconnect and restar by the DLM/DSLAMt, it being far to slow, several minutes in each case (the graph sample rate is every 30secs)!

Mystified moi!

I am presently improving the router (W8960) cooling assuming the chipset may be overheating as it did measure 40C in Tamb 23C at the top of the case and it's started turning brown from its old white, long line, 24/7, clutching at straws lols

Roger

[#4]

I reserve my comments for the other thread where all the relevant information is