This topic

Line capped by DLM - what can I do?

beach_comber — Mon, 01 Jun 2020 10:11:06 GMT

Morning Folks

Just renewed contract with BT and thought I'd check my line stats as I hadn't done it for a while. It looks like DLM has applied a banded cap to my d/s speed - I presume in response to a fault that's occurred at some point. Got a new laptop set-up a few months ago and didn't get round to monitoring line stats unfortunately so no idea when fault(s) occurred or how long ago. From what I can see the last re-sync occurred around 10 days ago with only 2 errored seconds so line looks good now at least.

Telnet stats show I should be able to sync at approx. 61Mbps (line stats reported at 60808Kbps) but my current downstream rate is only 44Mbps (line stats reported at 43998Kbps).

So how do I go about getting the banding removed and/or get a DLM reset done? Thanks.

Re: Line capped by DLM - what can I do?

imjolly — Mon, 01 Jun 2020 10:46:09 GMT

in order for the forum members to help please can you post the stats from your router (if hub enter 192.168.1.254 in your browser) and if HH5 then go to troubleshooting then helpdesk and if HH6/SH2 then advanced settings then technical log information .

enter your phone number and post results remember to delete number https://www.broadbandchecker.btwholesale.com/#/ADSL

it can take a few weeks for the DLM to see you line as stable and start to release any banding

Re: Line capped by DLM - what can I do?

beach_comber — Mon, 01 Jun 2020 12:00:48 GMT

Thanks for the reply. I have an Openreach HG612 set-up not a HH. Already ran the checker with results below:

Telnet stats are as follows:

xdslcmd info --stats xdslcmd: ADSL driver and PHY status Status: Showtime Retrain Reason: 1 Last initialization procedure status: 0 Max: Upstream rate = 20547 Kbps, Downstream rate = 60808 Kbps Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 43998 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): 9.9 4.0 Attn(dB): 19.5 0.0 Pwr(dBm): 13.3 7.5 VDSL2 framing Bearer 0 MSGc: -6 20 B: 179 239 M: 1 1 T: 0 64 R: 12 0 S: 0.1295 0.3819 L: 11861 5028 D: 4 1 I: 192 120 N: 192 240 Q: 4 0 V: 3 0 RxQueue: 135 0 TxQueue: 27 0 G.INP Framing: 18 0 G.INP lookback: 27 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 2182150 OHFErr: 6 680 RS: 3362090568 1353667 RSCorr: 96958543 0 RSUnCorr: 0 0 Bearer 1 OHF: 41565447 0 OHFErr: 0 0 RS: 249392312 0 RSCorr: 1 0 RSUnCorr: 0 0 Retransmit Counters rtx_tx: 2247900 0 rtx_c: 990187061 0 rtx_uc: 423542 0 G.INP Counters LEFTRS: 170957 0 minEFTR: 43966 0 errFreeBits: 2992172332 0 Bearer 0 HEC: 0 0 OCD: 0 0 LCD: 0 0 Total Cells: 631146120 0 Data Cells: 604599903 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: 5178 7117 SES: 83 33 UAS: 705 653 AS: 667644 Bearer 0 INP: 55.00 0.00 INPRein: 1.00 0.00 delay: 0 0 PER: 0.00 6.13 OR: 0.01 33.91 AgR: 44305.68 20033.74 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: 322871/322871 15174/15213 Total time = 1 days 5 hours 14 min 26 sec FEC: 128088088 20307 CRC: 9968 11850 ES: 5178 7117 SES: 83 33 UAS: 705 653 LOS: 5 0 LOF: 46 0 LOM: 0 0 Latest 15 minutes time = 14 min 26 sec FEC: 142982 0 CRC: 0 0 ES: 0 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: 104826 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 = 5 hours 14 min 26 sec FEC: 2195045 0 CRC: 0 4 ES: 0 4 SES: 0 0 UAS: 0 0 LOS: 0 0 LOF: 0 0 LOM: 0 0 Previous 1 day time = 24 hours 0 sec FEC: 19013718 0 CRC: 0 69 ES: 0 59 SES: 0 0 UAS: 0 0 LOS: 0 0 LOF: 0 0 LOM: 0 0 Since Link time = 7 days 17 hours 27 min 23 sec FEC: 96958543 0 CRC: 6 680 ES: 2 466 SES: 0 1 UAS: 0 0 LOS: 0 0 LOF: 0 0 LOM: 0 0 #

Re: Line capped by DLM - what can I do?

imjolly — Mon, 01 Jun 2020 11:59:56 GMT

can't see dsl uptime

Re: Line capped by DLM - what can I do?

beach_comber — Mon, 01 Jun 2020 12:25:23 GMT

The last section has the DSL uptime (stats are from Fri afternoon). Current DSL uptime is 10 days 13 hrs.

Re: Line capped by DLM - what can I do?

pippincp — Mon, 01 Jun 2020 14:07:06 GMT

Any noise on your line? 17070 option 2 best with corded phone.

Re: Line capped by DLM - what can I do?

beach_comber — Mon, 01 Jun 2020 16:56:40 GMT

Don't have access to a corded phone, plus my hearing isn't the greatest either tbh. Did the test and can hear some faint 'white noise' is the best way I can describe it. I can't really say there was presence of much in the way of audible noise though.

Re: Line capped by DLM - what can I do?

pompey1898 — Mon, 01 Jun 2020 21:07:15 GMT

@beach_comberwrote:
Don't have access to a corded phone, plus my hearing isn't the greatest either tbh. Did the test and can hear some faint 'white noise' is the best way I can describe it. I can't really say there was presence of much in the way of audible noise though.
The comments in blue are contradictory.

The comments in blue are contradictory. Is there noise or not. Should be silent.

Re: Line capped by DLM - what can I do?

Carlusha — Tue, 02 Jun 2020 00:35:56 GMT

@beach_comberwrote:
Don't have access to a corded phone, plus my hearing isn't the greatest either tbh. Did the test and can hear some faint 'white noise' is the best way I can describe it. I can't really say there was presence of much in the way of audible noise though.

I feel for you for I cannot even use a phone - far too deaf!

Re: Line capped by DLM - what can I do?

beach_comber — Tue, 02 Jun 2020 08:26:44 GMT

@pompey1898wrote:
The comments in blue are contradictory. Is there noise or not. Should be silent.

Thanks for replying - but they really aren't, I did have a qualifier in there i.e. "... much in the way of audible noise though."

So let me clarify, I didn't hear anything that I would class as distinct noise on the line - no humming, crackles, pops etc that I could make out. So in that respect the line was silent.

But as I was trying to point out this isn't going to be a particularly objective test for me as 1) my hearing isn't 100% and 2) I only have access to a cordless phone.

Re: Line capped by DLM - what can I do?

beach_comber — Tue, 02 Jun 2020 09:48:30 GMT

@Carlusha thanks I feel for you too, count myself lucky that one ear is much better than the other.

Re: Line capped by DLM - what can I do?

imjolly — Tue, 02 Jun 2020 09:56:22 GMT

you need longer than 10 days stable before the DLM will relent and start reducing banding - any line noise will cause a delay in DLM action

Re: Line capped by DLM - what can I do?

beach_comber — Tue, 02 Jun 2020 11:51:23 GMT

Ok, maybe I'm misunderstanding this. I know DLM doesn't work on the fly but I understood it would assess line quality/performance every 24hrs and thus make adjustments based on the quality/performance metrics. My d/l speed has now been a flat-line at 43998 Kbps for 11 days, with 2 error seconds in that time. I get that DLM takes time but I thought there would be some variation in d/l connection speed over 11 days. This what prompted my post as it seems that no matter if my line quality improves over time, there has been no change in connection speed.

Re: Line capped by DLM - what can I do?

imjolly — Tue, 02 Jun 2020 12:03:12 GMT

DLM is constantly monitoring your line but it takes an unstable connection with many drops before being in banded profile it take more than just 10 days for DLM to relent and start reducing banding

this may help

https://community.plus.net/t5/Library/FTTC-DLM-What-it-is-How-it-works/ba-p/1322799

Re: Line capped by DLM - what can I do?

beach_comber — Tue, 02 Jun 2020 12:38:28 GMT

Thanks, yes have already read through that post amongst others to gain a better understanding of how to interpret my line stats.

As I said before it's unfortunate but i don't know what fault(s) occurred or when they occurred that caused DLM to implement the banding cap. So rhetorical question I know but I'm then left wondering how long it may take DLM to adjust again (assuming line stays 'clean')?

And then back to the question if DLM doesn't relent how do i get a reset done?