Kitz Forum

Broadband Related => FTTC and FTTP Issues => Topic started by: 1kmFTTC on August 10, 2023, 01:19:41 PM

Title: DLM behaviour on new FTTC installation (1km line)
Post by: 1kmFTTC on August 10, 2023, 01:19:41 PM
ISP: Now Broadband (Sky)
Product: 40/10 Openreach FTTC
Line length: Around 1km + 50m from PCP to FTTC cab
GEA Stability Profile: Standard (assumed)
FTTC DSLAM type: Huawei (BDCM:0xa4a1)
Routers: Now Hub 2 and Zyxel VMG3925-B10C (both Broadcom)
Local plant: NTE5C + Mk4 faceplate, external cable direct into back of NTE. One join (jelly crimps in BT16A) from drop cable to CW1308 cable which goes into NTE. RJ45 to RJ11 Cat5e cable from Mk4 faceplate to router.

Day 1: No speed band, 6db DS target, downstream retransmit low, upstream error protection off.
Upstream rate = 3943 Kbps, Downstream rate = 28257 Kbps
Day 2: No speed band, 6db DS target, downstream retransmit low, upstream error protection off.
Day 3: Resync at around 3am, no visible change to stats (reason 2: RDI detector).
Day 4: No change
Day 5: No change
Day 6: DLM resync at 6am: 6db DS target, downstream retransmit high, upstream error protection off.
Upstream rate = 3355 Kbps, Downstream rate = 26744 Kbps
Day 7: DLM resync at 2am: Downstream: banded 25M, retransmit high, upstream: banded 3.2M, error protection off.
Day 8: 3am: Downstream: banded 22.5M, upstream: banded 2.8M, error protection off.
Day 9: No change
Day 10: Downstream: banded 20M, upstream: banded 2.3M, error protection off.
Day 11: Downstream: banded 18M, upstream: banded 2M, error protection off.

On day 10: ISP line test failed with "Impairment in copper joint detected".
On day 11, Openreach Engineer attended:
First new port allocation dropped sync after 2 mins.
Second set didn't sync in the PCP at all.
Third set requested on a different 'block', synced at 40/10 following a DLM reset.

No other changes made to line, same D-side, just different FTTC port and tie cables from PCP to FTTC cab (around 50m).
VDSL2 link up, Bearer 0, us=5075, ds=28077
VDSL2 link up, Bearer 1, us=0, ds=0

So appears to be back to unbanded, DS retx low, US error protection off (assumed, as back to where we started on da 1). No detailed stats as using ISP supplied router (Now Hub 2). I will update this thread with the timeline now that the line has been fixed.

Observations:

Day 1 stats:
Code: [Select]
ZySH> xdslctl info --stats
Max: Upstream rate = 3947 Kbps, Downstream rate = 29212 Kbps
Bearer: 0, Upstream rate = 3943 Kbps, Downstream rate = 28257 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps

Down Up
SNR (dB): 6.8 6.2
Attn(dB): 30.3 0.0
Pwr(dBm): 11.3 6.9

Bearer 0
INP: 43.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 9.02
OR: 0.01 28.36
AgR: 28285.72 3971.68

Bearer 1
INP: 2.50 0.00
INPRein: 2.50 0.00
delay: 0 0
PER: 16.06 0.01
OR: 47.81 0.01
AgR: 47.81 0.01

Day 2 stats:
Code: [Select]
ZySH> xdslctl info --stats
xdslctl: ADSL driver and PHY status
Max: Upstream rate = 3455 Kbps, Downstream rate = 29285 Kbps
Bearer: 0, Upstream rate = 3455 Kbps, Downstream rate = 27881 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps

Down Up
SNR (dB): 6.8 6.3
Attn(dB): 30.3 0.0
Pwr(dBm): 11.3 6.9


Bearer 0
INP: 43.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 9.04
OR: 0.01 28.31
AgR: 27925.43 3483.00

Bearer 1
INP: 2.50 0.00
INPRein: 2.50 0.00
delay: 0 0
PER: 16.06 0.01
OR: 47.81 0.01
AgR: 47.81 0.01

Day 6 stats:

Code: [Select]
ZySH> xdslctl info --stats
Max: Upstream rate = 3239 Kbps, Downstream rate = 27038 Kbps
Bearer: 0, Upstream rate = 3355 Kbps, Downstream rate = 26744 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps

Down Up
SNR (dB): 6.4 4.6
Attn(dB): 30.7 0.0
Pwr(dBm): 11.3 6.9

Bearer 0
INP: 55.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 9.07
OR: 0.01 28.19
AgR: 26803.10 3383.70

Bearer 1
INP: 2.50 0.00
INPRein: 2.50 0.00
delay: 0 0
PER: 16.06 0.01
OR: 47.81 0.01
AgR: 47.81 0.01
Title: Re: DLM behaviour on new FTTC installation (1km line)
Post by: 1kmFTTC on August 10, 2023, 04:25:14 PM
Timeline of events since fault fixed and DLM reset:

Day 1: No speed band, 6db DS target, downstream retransmit low, upstream error protection off (assumed).

Bearer 0, us=5075, ds=28077
Bearer 1, us=0, ds=0


Day 2: No change
Day 3: No change
Day 4: Early morning resync, suspect retx high + 5db target

Bearer 0, us=4665, ds=29205
Bearer 1, us=0, ds=0


Day 5: Swap from Now router to Zyxel, still retx high + 5db target

Now: us=4665, ds=29205
Zyxel: Upstream rate = 4666 Kbps, Downstream rate = 30839 Kbps (full stats below)


Day 6: Early morning resync, slight increase in INP depth, retx high + 5db target
Day 7: No resync/change. Today is day 7 :)

Observations:


Hopefully this info is useful to anyone wondering how DLM operates on a long-ish FTTC circuit using an ISP that provisions with the Standard stability profile.

Day 5 stats:
Code: [Select]
ZySH> xdslctl info --stats
Max: Upstream rate = 4706 Kbps, Downstream rate = 31928 Kbps
Bearer: 0, Upstream rate = 4666 Kbps, Downstream rate = 30839 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps

Down Up
SNR (dB): 5.6 6.6
Attn(dB): 29.6 0.0
Pwr(dBm): 11.4 7.1

Bearer 0
INP: 49.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 8.83
OR: 0.01 28.98
AgR: 30906.43 4695.38

Bearer 1
INP: 2.50 0.00
INPRein: 2.50 0.00
delay: 0 0
PER: 16.06 0.01
OR: 47.81 0.01
AgR: 47.81 0.01

Day 6 stats:
Code: [Select]
ZySH>  xdslctl info --stats
Max: Upstream rate = 4568 Kbps, Downstream rate = 32847 Kbps
Bearer: 0, Upstream rate = 4637 Kbps, Downstream rate = 31379 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps

Down Up
SNR (dB): 4.8 5.6
Attn(dB): 29.7 0.0
Pwr(dBm): 11.5 7.0

Bearer 0
INP: 51.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 8.64
OR: 0.01 29.62
AgR: 31448.44 4666.32

Bearer 1
INP: 2.50 0.00
INPRein: 2.50 0.00
delay: 0 0
PER: 16.06 0.01
OR: 47.81 0.01
AgR: 47.81 0.01

Day 7 full stats:

Code: [Select]
ZySH> xdslctl info --stats
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 4550 Kbps, Downstream rate = 32709 Kbps
Bearer: 0, Upstream rate = 4637 Kbps, Downstream rate = 31379 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): 4.6 5.5
Attn(dB): 29.7 0.0
Pwr(dBm): 11.5 7.1

VDSL2 framing
Bearer 0
MSGc: -6 26
B: 227 143
M: 1 1
T: 0 35
R: 10 14
S: 0.2311 0.9837
L: 8239 1285
D: 4 1
I: 238 79
N: 238 158
Q: 4 0
V: 0 0
RxQueue: 76 0
TxQueue: 19 0
G.INP Framing: 18 0
G.INP lookback: 19 0
RRC bits: 0 24
Bearer 1
MSGc: 90 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 10.6667 0.0000
L: 24 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 16128938
OHFErr: 30 3
RS: 2392478664 564348898
RSCorr: 35188192 283
RSUnCorr: 0 0
Bearer 1
OHF: 8639003 0
OHFErr: 1 0
RS: 51833650 0
RSCorr: 524 0
RSUnCorr: 1 0

Retransmit Counters
rtx_tx: 36061 0
rtx_c: 30203 0
rtx_uc: 1098 0

G.INP Counters
LEFTRS: 14 0
minEFTR: 31381 0
errFreeBits: 89993096 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 4078255363 0
Data Cells: 573144263 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: 27 4
SES: 11 0
UAS: 75 65
AS: 138797

Bearer 0
INP: 51.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 8.64
OR: 0.01 29.62
AgR: 31448.44 4666.32

Bearer 1
INP: 2.50 0.00
INPRein: 2.50 0.00
delay: 0 0
PER: 16.06 0.01
OR: 47.81 0.01
AgR: 47.81 0.01

Bitswap: 97936/97937 976/977

Total time = 2 days 4 hours 34 min 0 sec
FEC: 50833900 304
CRC: 39 4
ES: 27 4
SES: 11 0
UAS: 75 65
LOS: 1 0
LOF: 7 0
LOM: 0 0
Retr: 1
HostInitRetr: 0
FailedRetr: 0
Latest 15 minutes time = 4 min 0 sec
FEC: 101751 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
Previous 15 minutes time = 15 min 0 sec
FEC: 236234 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
HostInitRetr: N/A
FailedRetr: N/A
Latest 1 day time = 4 hours 34 min 0 sec
FEC: 2903981 257
CRC: 11 0
ES: 6 0
SES: 1 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
Previous 1 day time = 24 hours 0 sec
FEC: 27851652 21
CRC: 7 1
ES: 3 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
Since Link time = 1 days 14 hours 33 min 17 sec
FEC: 35188192 283
CRC: 30 3
ES: 14 3
SES: 1 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
ZySH>
Title: Re: DLM behaviour on new FTTC installation (1km line)
Post by: 1kmFTTC on August 10, 2023, 04:34:11 PM
Speedtest showing around 93.4% of sync rate downstream:

https://www.thinkbroadband.com/speedtest/1691681473496995455
Title: Re: DLM behaviour on new FTTC installation (1km line)
Post by: g3uiss on August 10, 2023, 07:46:03 PM
That’s about right isn’t it
Title: Re: DLM behaviour on new FTTC installation (1km line)
Post by: 1kmFTTC on August 11, 2023, 09:02:16 AM
That’s about right isn’t it

Yep, and (maybe) surprisingly, we haven't noticed much difference to the things we do day-to-day compared to the 250Mb Virgin connection that this has replaced.

In other news, DLM is the gift that keeps on giving! Today is day 8 and another target SNR drop this morning, down to 4dB:

Max:   Upstream rate = 4466 Kbps, Downstream rate = 34339 Kbps
Bearer:   0, Upstream rate = 4466 Kbps, Downstream rate = 32541 Kbps

                  Down      Up
SNR (dB):    4.1       6.3


And it seems to be running reasonably cleanly so far.

Full day 8 stats:

Code: [Select]
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 4466 Kbps, Downstream rate = 34339 Kbps
Bearer: 0, Upstream rate = 4466 Kbps, Downstream rate = 32541 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): 4.1 6.3
Attn(dB): 29.8 0.0
Pwr(dBm): 11.7 7.1

VDSL2 framing
Bearer 0
MSGc: -6 26
B: 227 127
M: 1 1
T: 0 38
R: 10 12
S: 0.2228 0.9076
L: 8544 1234
D: 4 1
I: 238 70
N: 238 140
Q: 4 0
V: 0 0
RxQueue: 76 0
TxQueue: 19 0
G.INP Framing: 18 0
G.INP lookback: 19 0
RRC bits: 0 24
Bearer 1
MSGc: 90 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 10.6667 0.0000
L: 24 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 3249199
OHFErr: 23 0
RS: 500722036 123447345
RSCorr: 15891472 3
RSUnCorr: 0 0
Bearer 1
OHF: 1743564 0
OHFErr: 1 0
RS: 10461012 0
RSCorr: 44 0
RSUnCorr: 1 0

Retransmit Counters
rtx_tx: 12395 0
rtx_c: 9781 0
rtx_uc: 629 0

G.INP Counters
LEFTRS: 2 0
minEFTR: 32539 0
errFreeBits: 118501362 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 1752410909 0
Data Cells: 19860565 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: 52 5
SES: 21 0
UAS: 117 97
AS: 28013

Bearer 0
INP: 49.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 8.65
OR: 0.01 29.57
AgR: 32612.64 4495.35

Bearer 1
INP: 2.50 0.00
INPRein: 2.50 0.00
delay: 0 0
PER: 16.06 0.01
OR: 47.81 0.01
AgR: 47.81 0.01

Bitswap: 21270/21270 114/114

Total time = 2 days 20 hours 51 min 27 sec
FEC: 91831949 310
CRC: 65 5
ES: 52 5
SES: 21 0
UAS: 117 97
LOS: 2 0
LOF: 16 0
LOM: 0 0
Retr: 2
HostInitRetr: 0
FailedRetr: 0
Latest 15 minutes time = 6 min 27 sec
FEC: 86751 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
Previous 15 minutes time = 15 min 0 sec
FEC: 300325 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
HostInitRetr: N/A
FailedRetr: N/A
Latest 1 day time = 20 hours 51 min 27 sec
FEC: 43902030 263
CRC: 37 1
ES: 31 1
SES: 11 0
UAS: 42 32
LOS: 1 0
LOF: 9 0
LOM: 0 0
Retr: 1
HostInitRetr: 0
FailedRetr: 0
Previous 1 day time = 24 hours 0 sec
FEC: 27851652 21
CRC: 7 1
ES: 3 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
Since Link time = 7 hours 46 min 51 sec
FEC: 15891472 3
CRC: 23 0
ES: 12 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
ZySH>
Title: Re: DLM behaviour on new FTTC installation (1km line)
Post by: kitz on August 14, 2023, 12:00:39 AM
Quote
DLM is the gift that keeps on giving! Today is day 8 and another target SNR drop this morning, down to 4dB:
Hopefully another soon to 3dB with an increase in sync.
Title: Re: DLM behaviour on new FTTC installation (1km line)
Post by: adslmax on August 14, 2023, 12:04:02 AM
Hopefully another soon to 3dB with an increase in sync.

It's did happen to my line as SNR target 5dB to put my speed back to 80Meg from 78Meg




Title: Re: DLM behaviour on new FTTC installation (1km line)
Post by: Alex Atkin UK on August 14, 2023, 01:57:12 AM
It's did happen to my line as SNR target 5dB to put my speed back to 80Meg from 78Meg

Your line is very short.
Title: Re: DLM behaviour on new FTTC installation (1km line)
Post by: adslmax on August 14, 2023, 02:00:12 AM
Your line is very short.

Yes I know
Title: Re: DLM behaviour on new FTTC installation (1km line)
Post by: kitz on August 14, 2023, 12:59:05 PM
I think the increases still happen even though the increase SNRM takes the max attainable to over 80Mbps.
Obviously it cant increase the sync speed to over 80Mbps (sorry I didn't make that clear in my last post), but your max attainable speed will still show an increase.
Title: Re: DLM behaviour on new FTTC installation (1km line)
Post by: Alex Atkin UK on August 14, 2023, 03:50:07 PM
I'm still curious why OR decided to cap at 80, on Digital Region I got a flat 99 down, ~35 up.  I'd say it was a band plan thing but surely they still had to block out the same frequencies and power limits to avoid interfering with ADSL as OR do?
Title: Re: DLM behaviour on new FTTC installation (1km line)
Post by: kitz on August 14, 2023, 05:15:34 PM
>> I'd say it was a band plan thing

Correct.
Title: Re: DLM behaviour on new FTTC installation (1km line)
Post by: Alex Atkin UK on August 15, 2023, 05:01:59 AM
Still when the cabinet first appeared my attainable was something like 105/25 which would reflect that change (I think DR was 130/35).

Obviously pinch of salt with attainable and 80/20 is more realistically attainable once crosstalk rears its head.  But still, why cap the downstream at all?
Title: Re: DLM behaviour on new FTTC installation (1km line)
Post by: 1kmFTTC on August 18, 2023, 01:08:13 PM
Hopefully another soon to 3dB with an increase in sync.

Indeed, although not sure if the standard profile will hold me back. That said, I decided to do a quick daytime resync.


Code: [Select]
Max: Upstream rate = 4597 Kbps, Downstream rate = 35260 Kbps
Bearer: 0, Upstream rate = 4597 Kbps, Downstream rate = 34400 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps

Down Up
SNR (dB): 3.6 6.1
Attn(dB): 29.8 0.0
Pwr(dBm): 11.9 7.1

I'd guess with the 3.6dB margin straight after a resync (Since Link time = 15 sec), the target is already 3dB, so I must have missed that.

Up until this resync that I just did, it's been solid for 4 days. Given the pre-resync stats, what are thoughts on trying to get back to retx low, so I can make better use of that sync speed? It would be painful to run at sub 25ish Mbit for a couple of weeks but potentially managable, but I wouldn't be surprised if this line needs retx high. Thoughts?

Stats before resync:

Code: [Select]
ZySH> xdslctl info --stats
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 4598 Kbps, Downstream rate = 34970 Kbps
Bearer: 0, Upstream rate = 4656 Kbps, Downstream rate = 33608 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.8 6.0
Attn(dB): 29.5 0.0
Pwr(dBm): 11.7 7.1

VDSL2 framing
Bearer 0
MSGc: -6 26
B: 227 143
M: 1 1
T: 0 36
R: 10 14
S: 0.2158 0.9798
L: 8824 1290
D: 4 1
I: 238 79
N: 238 158
Q: 4 0
V: 0 0
RxQueue: 80 0
TxQueue: 20 0
G.INP Framing: 18 0
G.INP lookback: 20 0
RRC bits: 0 24
Bearer 1
MSGc: 90 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 10.6667 0.0000
L: 24 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 41348490
OHFErr: 229 23
RS: 2434980332 1488073069
RSCorr: 260262952 109
RSUnCorr: 0 0
Bearer 1
OHF: 22689992 0
OHFErr: 0 0
RS: 136139580 0
RSCorr: 655 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 454977 0
rtx_c: 410901 0
rtx_uc: 3126 0

G.INP Counters
LEFTRS: 121 0
minEFTR: 33602 0
errFreeBits: 186568931 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 2073642121 0
Data Cells: 1286068967 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: 95 22
SES: 2 0
UAS: 33 33
AS: 364545

Bearer 0
INP: 50.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 8.85
OR: 0.01 28.91
AgR: 33681.40 4684.48

Bearer 1
INP: 2.50 0.00
INPRein: 2.50 0.00
delay: 0 0
PER: 16.06 0.01
OR: 47.81 0.01
AgR: 47.81 0.01

Bitswap: 269887/269896 1485/1491

Total time = 4 days 5 hours 16 min 18 sec
FEC: 260262952 109
CRC: 229 23
ES: 95 22
SES: 2 0
UAS: 33 33
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
Latest 15 minutes time = 1 min 18 sec
FEC: 3872 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
Previous 15 minutes time = 15 min 0 sec
FEC: 126715 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
HostInitRetr: N/A
FailedRetr: N/A
Latest 1 day time = 5 hours 16 min 18 sec
FEC: 11655852 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
Previous 1 day time = 24 hours 0 sec
FEC: 61216360 14
CRC: 5 5
ES: 4 5
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
Since Link time = 4 days 5 hours 15 min 45 sec
FEC: 260262952 109
CRC: 229 23
ES: 95 22
SES: 2 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
ZySH>

Stats after this resync:

Code: [Select]
ZySH> xdslctl info --state
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 2000
Last initialization procedure status: 0
Max: Upstream rate = 4597 Kbps, Downstream rate = 35360 Kbps
Bearer: 0, Upstream rate = 4597 Kbps, Downstream rate = 34400 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
ZySH> xdslctl info --stats
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 2000
Last initialization procedure status: 0
Max: Upstream rate = 4597 Kbps, Downstream rate = 35260 Kbps
Bearer: 0, Upstream rate = 4597 Kbps, Downstream rate = 34400 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): 29.8 0.0
Pwr(dBm): 11.9 7.1

VDSL2 framing
Bearer 0
MSGc: -6 26
B: 227 143
M: 1 1
T: 0 35
R: 10 14
S: 0.2108 0.9922
L: 9032 1274
D: 4 1
I: 238 79
N: 238 158
Q: 4 0
V: 0 0
RxQueue: 84 0
TxQueue: 21 0
G.INP Framing: 18 0
G.INP lookback: 21 0
RRC bits: 0 24
Bearer 1
MSGc: 90 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 10.6667 0.0000
L: 24 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 1732
OHFErr: 0 0
RS: 264612 60618
RSCorr: 7912 0
RSUnCorr: 0 0
Bearer 1
OHF: 933 0
OHFErr: 0 0
RS: 5230 0
RSCorr: 0 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 17 0
rtx_c: 22 0
rtx_uc: 0 0

G.INP Counters
LEFTRS: 0 0
minEFTR: 34388 0
errFreeBits: 186832790 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 991939 0
Data Cells: 2666 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: 95 22
SES: 2 0
UAS: 78 78
AS: 15

Bearer 0
INP: 52.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 8.71
OR: 0.01 29.37
AgR: 34475.34 4626.38

Bearer 1
INP: 2.50 0.00
INPRein: 2.50 0.00
delay: 0 0
PER: 16.06 0.01
OR: 47.81 0.01
AgR: 47.81 0.01

Bitswap: 8/9 0/0

Total time = 4 days 5 hours 25 min 38 sec
FEC: 260356274 109
CRC: 229 23
ES: 95 22
SES: 2 0
UAS: 78 78
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 1
HostInitRetr: 1
FailedRetr: 0
Latest 15 minutes time = 10 min 38 sec
FEC: 97194 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 45 45
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 1
HostInitRetr: 1
FailedRetr: 0
Previous 15 minutes time = 15 min 0 sec
FEC: 126715 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
HostInitRetr: N/A
FailedRetr: N/A
Latest 1 day time = 5 hours 25 min 38 sec
FEC: 11749174 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 45 45
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 1
HostInitRetr: 1
FailedRetr: 0
Previous 1 day time = 24 hours 0 sec
FEC: 61216360 14
CRC: 5 5
ES: 4 5
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
Since Link time = 15 sec
FEC: 7912 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
ZySH>
Title: Re: DLM behaviour on new FTTC installation (1km line)
Post by: j0hn on August 18, 2023, 01:29:46 PM
A cap on the sync speed for a few days should see retx low return. It won't take anywhere near 2 weeks unless they have changed how the DLM works.
Title: Re: DLM behaviour on new FTTC installation (1km line)
Post by: 1kmFTTC on August 18, 2023, 01:32:35 PM
A cap on the sync speed for a few days should see retx low return. It won't take anywhere near 2 weeks unless they have changed how the DLM works.

Cheers. I did try it on my Mum's line as a test and it did take a couple of weeks. That is an odd one though as was banded at 35Mbit for a good 2 years, but then after a thunderstorm took her router out it came back up unbanded retx high, so I capped down about 2 weeks ago and got retx low this morning.

Back to my line though, based on the stats, do you think it's just one of those lines where retx high is actually needed? Also, what cap would you recommend, 25Mbit ish?