Openreach DLM Banding Profile

bulldog147

bulldog147

bulldog147

Soldato
Joined
22 Mar 2009
Posts
5,768
Hi everyones

Do you think there is possible chance of DLM has a problem with system stuck with a banding profile at openreach system. I do believed it does. Need to raise this with isp's to chase this up with Openreach because the downstream still banding at 74Meg capped wouldn't go back to 80Meg as the result of losing 6Meg off:



Code: 
1st resync:

Downstream   Upstream
Line attenuation (dB):     11.5      0.0
Signal attenuation (dB):   Not available on VDSL2    
Connection speed (kbps):   79999      20000
SNR margin (dB):           8.3      13.9
Power (dBm):               12.4      -0.6
Interleave depth:          8      8
INP:                       46.00      47.00
G.INP:                     Enabled      Enabled

2nd resync:

Downstream   Upstream
Line attenuation (dB):     11.5      0.0
Signal attenuation (dB):   Not available on VDSL2    
Connection speed (kbps):   73998      20000
SNR margin (dB):           10.1      14.0
Power (dBm):               12.5      -0.6
Interleave depth:          8      4
INP:                       52.00      55.00
G.INP:                     Enabled      Enabled

3rd resync:

Downstream   Upstream
Line attenuation (dB):     11.5      0.0
Signal attenuation (dB):   Not available on VDSL2    
Connection speed (kbps):   74000      20000
SNR margin (dB):           10.0      14.4
Power (dBm):               12.4      -0.6
Interleave depth:          16      8
INP:                       49.00      47.00
G.INP:                     Enabled      Enabled

4th resync:

Downstream   Upstream
Line attenuation (dB):     11.4      0.0
Signal attenuation (dB):   Not available on VDSL2    
Connection speed (kbps):   74000      19999
SNR margin (dB):           9.9      15.1
Power (dBm):               12.5      -0.9
Interleave depth:          16      1
INP:                       49.00      0
G.INP:                     Enabled      Not enabled
 
If you are forcing resyncs then you are making things worse. DLM will see the resyncs as instability and slow it down to stabilise. It would creep back up after a period of stability.
 
Pretty much what @Steveocee is saying if those are manual. That'll also be the reason why when you do manual forced resyncs you need to have a downtime of 30 minutes for each resync, as DLM won't take those ones into account.

Think DLM takes a screenshot of issues on the line every 15 minutes. But because you could be on the end of a screenshot by DLM when you lose connection to resync and resync 15 minutes exactly, DLM will take it as an error on the line rather than just a resync attempt. So that's why 30 minutes to be safe between each manual resync should be applied.

As you're very close to max speeds already, unless there's another fault that BTOR needs to correct, I'm pretty sure any call out will also cost you the engineer call out fee. So you may just need to be patient here and wait for DLM to do it's job. Some DLM are known to be stubborn however, give it around 3 months clean connection (no disconnections or resync attempts; not within 30 minutes anyway). And it it's still like that, you might be able to make a case then. But as g.inp only come on recently for you, you should give DLM an attempt to do something about those speeds first.
 
I didn't force it. It resync itself by DLM.

1st resync: 11th Nov 2017

Downstream Upstream
Line attenuation (dB): 11.5 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 79999 20000
SNR margin (dB): 8.3 13.9
Power (dBm): 12.4 -0.6
Interleave depth: 8 8
INP: 46.00 47.00
G.INP: Enabled Enabled

2nd resync: 12th Nov 2017

Downstream Upstream
Line attenuation (dB): 11.5 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 73998 20000
SNR margin (dB): 10.1 14.0
Power (dBm): 12.5 -0.6
Interleave depth: 8 4
INP: 52.00 55.00
G.INP: Enabled Enabled

3rd resync: 22nd Nov 2017

Downstream Upstream
Line attenuation (dB): 11.5 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 74000 20000
SNR margin (dB): 10.0 14.4
Power (dBm): 12.4 -0.6
Interleave depth: 16 8
INP: 49.00 47.00
G.INP: Enabled Enabled

4th resync: 26th Nov 2017

Downstream Upstream
Line attenuation (dB): 11.4 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 74000 19999
SNR margin (dB): 9.9 15.1
Power (dBm): 12.5 -0.9
Interleave depth: 16 1
INP: 49.00 0
G.INP: Enabled Not enabled
 
When it did the resync, did you notice if the line was down or not? (Home Hub series would be the orange flashing light) As this would be a line loss, and DLM ironically counts it against you (DLM sees it as a full error; even though it was the one who initiated the error. Applies to HH series and some other devices).
 
There doesn't look to be too much wrong with that. It re-syncs now and again, get over that, it's DSL and it's not a guaranteed online or faultless product.
Are you really going to lose sleep over that few Mb at the top end missing? Probably not. DLM has slowed the line down to probably instill stability. This time of year, the copper may be suffering a bit or there may be some damp somewhere.

Have you called your ISP and asked them to check the line?
 
You must log in or register to reply here.
Back
Top Bottom