And from those latest stats you are on the 55/10 Openreach product.

Your DLM profile has been the same throughout.

Downstream 3dB Retransmission High - Upstream 6dB Error Protection Off.

The small changes in the upstream stats you quoted is just the amount of RS/FEC used on the upstream.
They don't affect the upstream sync speed.

Login in via Telnet and running "xdslcmd info --stats" will give a bit more detail, particularly the Retx/G.INP framing and error counters.

No idea what caused the low upstream sync you saw in your original post but it was very unlikely to be DLM related. Much more likely to be a line fault or an external factor affecting the line (interference, a crosstalker, etc).

A resync between midnight and 2am resulting in an increase in sync on both the downstream and upstream, accompanied by a drop in SNRM, is almost always the DSLAM rebooting. Sync speeds go back to normal on the next resync.

Thanks j0hn83, pluralist

The line re-synched last night. Downstream has dropped a little but upstream hasn't changed. These are the stats. I struggled to see or make sense of the the Retx/G.INP counters. I xdslcmd wasn't available through telnet so I have shown adsl output

adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 10643 Kbps, Downstream rate = 51144 Kbps
Bearer: 0, Upstream rate = 9998 Kbps, Downstream rate = 51211 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): 3.9 6.4
Attn(dB): 21.7 0.0
Pwr(dBm): 12.1 7.6

VDSL2 framing
Bearer 0
MSGc: -6 42
B: 227 79
M: 1 1
T: 0 64
R: 10 8
S: 0.1416 0.2542
L: 13446 2769
D: 4 1
I: 238 88
N: 238 88
Q: 4 0
V: 0 0
RxQueue: 125 0
TxQueue: 25 0
G.INP Framing: 18 0
G.INP lookback: 25 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 2065527
OHFErr: 0 2
RS: 709246056 396539124
RSCorr: 6087906 2
RSUnCorr: 0 0
Bearer 1
OHF: 1569307 0
OHFErr: 0 0
RS: 12553961 0
RSCorr: 2453 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 12537 0
rtx_c: 12442 0
rtx_uc: 0 0

G.INP Counters
LEFTRS: 0 0
minEFTR: 51167 0
errFreeBits: 3223409792 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 2482283815 0
Data Cells: 4406788 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: 5254 155
SES: 317 0
UAS: 849 543
AS: 25207

Bearer 0
INP: 56.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 12.25
OR: 0.01 31.34
AgR: 51323.68 10029.91

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: 13920/14682 772/775

Total time = 46 days 4 hours 47 min 37 sec
FEC: 3456684499 5874
CRC: 32287 172
ES: 5254 155
SES: 317 0
UAS: 849 543
LOS: 7 0
LOF: 27 0
LOM: 3 0
Retr: 7
FailedRetr: 0
FailedFastRetr: 0
Latest 15 minutes time = 2 min 37 sec
FEC: 38586 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
FailedRetr: 0
FailedFastRetr: 0
Previous 15 minutes time = 15 min 0 sec
FEC: 205249 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: N/A
FailedRetr: N/A
FailedFastRetr: N/A
Latest 1 day time = 4 hours 47 min 37 sec
FEC: 4176796 2
CRC: 0 2
ES: 0 2
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
FailedRetr: 0
FailedFastRetr: 0
Previous 1 day time = 24 hours 0 sec
FEC: 176827717 24
CRC: 11965 9
ES: 4703 9
SES: 34 0
UAS: 91 60
LOS: 2 0
LOF: 9 0
LOM: 0 0
Retr: 2
FailedRetr: 0
FailedFastRetr: 0
Since Link time = 7 hours 5 sec
FEC: 6087906 2
CRC: 0 2
ES: 0 2
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
FailedRetr: 0
FailedFastRetr: 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
>

That looks like DLM wasn't happy with the error rates, (neither was I from your last set of stats but they needed assessing over time so I didn't comment), so it raised the downstream SNR(Margin) to 4db.

With luck it will stabilise there. Watch for it going down over time however, as that could presage a further adjustment. It is normal for it to fluctuate by 0.2 or 0.3 over 24 hours, higher at night.

Openreach has told ISPs new ruling on DLM resetted:

They will not resetted DLM remotely if the line still drop or isn't stable for the last ten days! They will accept DLM resetted if the line was banded and no drop out with remain stable for 10 days or more.

Edited by adslmax (Sun 26-Sep-21 11:52:16)

Thank you pluralist,

Just had a resync just before 1pm. On lunch break so didn't notice it. Not much has changed. I'm very happy with the current rates.

adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 10715 Kbps, Downstream rate = 50991 Kbps
Bearer: 0, Upstream rate = 9995 Kbps, Downstream rate = 51577 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): 3.6 6.1
Attn(dB): 21.7 0.0
Pwr(dBm): 12.1 7.6

VDSL2 framing
Bearer 0
MSGc: -6 42
B: 227 79
M: 1 1
T: 0 64
R: 10 6
S: 0.1406 0.2543
L: 13542 2705
D: 4 1
I: 238 86
N: 238 86
Q: 4 0
V: 0 0
RxQueue: 126 0
TxQueue: 21 0
G.INP Framing: 18 0
G.INP lookback: 21 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 295816
OHFErr: 0 0
RS: 102303356 56787199
RSCorr: 910359 0
RSUnCorr: 0 0
Bearer 1
OHF: 224809 0
OHFErr: 0 0
RS: 1797976 0
RSCorr: 773 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 3168 0
rtx_c: 3139 0
rtx_uc: 0 0

G.INP Counters
LEFTRS: 0 0
minEFTR: 51560 0
errFreeBits: 3306090983 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 358116343 0
Data Cells: 3766438 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: 5266 165
SES: 327 0
UAS: 1078 762
AS: 3611

Bearer 0
INP: 58.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 12.25
OR: 0.01 31.33
AgR: 51690.11 10025.95

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: 932/960 67/67

Total time = 47 days 10 hours 15 min 47 sec
FEC: 3493994237 5910
CRC: 32827 182
ES: 5266 165
SES: 327 0
UAS: 1078 762
LOS: 8 0
LOF: 30 0
LOM: 3 0
Retr: 8
FailedRetr: 0
FailedFastRetr: 0
Latest 15 minutes time = 47 sec
FEC: 12767 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
FailedRetr: 0
FailedFastRetr: 0
Previous 15 minutes time = 15 min 0 sec
FEC: 233653 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: N/A
FailedRetr: N/A
FailedFastRetr: N/A
Latest 1 day time = 10 hours 15 min 47 sec
FEC: 12426309 6
CRC: 536 1
ES: 10 1
SES: 10 0
UAS: 229 219
LOS: 1 0
LOF: 3 0
LOM: 0 0
Retr: 1
FailedRetr: 0
FailedFastRetr: 0
Previous 1 day time = 24 hours 0 sec
FEC: 29060225 32
CRC: 4 11
ES: 2 11
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
FailedRetr: 0
FailedFastRetr: 0
Since Link time = 1 hours 11 sec
FEC: 910359 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
FailedRetr: 0
FailedFastRetr: 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
>

Another resync last night...but not much change.

However, Billion seems to be showing conflicting info....

Summary page says:
Line Rate - Upstream (Kbps) 9995
Line Rate - Downstream (Kbps) 51577
Default Gateway / IPv4 Address ppp1.1 (DSL) / 81.147.xxx.yyy
Connection Time 06:15:02

Logs support connection time

Sep 30 01:33:55 daemon crit syslog: Received valid IP address from server. Connection UP.

But the DSLstats stats page shows :

Status: Showtime
Uptime: 2 days 18 hours 51 min 26 sec

And this is from the --stats command

Since Link time = 2 days 18 hours 51 min 25 sec
FEC: 114522837 57
CRC: 0 19
ES: 0 19
SES: 0 0
UAS: 0 0

Perhaps it was a different type of resync?

The uptime there is the time the router has been powered up, (possibly the time since the connection to the exchange), and the connection time is how long the PPP session has been up. The PPP uptime being reset at each re-sync.

The PPP is the working connection between your router and the ISP's gateway.

My line is stable and currently achieving speeds around 50/10 which matches my BT package

Thanks for all those that gave advice.

Happy new year

Paul