When did you invent those figures?

In reply to a post by forafewbytesmore:

In reply to a post by MHC:

The SNR at 23.8dB is the major cause of the slowdown and you are going to have to wait for that to recover - unless there is a major occasional noise source that comes and goes.

It's persistent now for the past fortnight.

Using the SNR adjustment on the Vigor130 only gets the attainable rate to vary.

Openreach expressly say adjusting the SNR, (actually it is the SNRM), should not be done. Unlike on the BT Wholesale and LLU ADSLx where it was standard practice.

Also, given that it is SNRM, which way are you adjusting it? SNR needs to be as high as possible. SNRM as low as possible so long as stability is maintained and error rates acceptable.

I'm very suspicious you have increased this yourself, as both the sets of stats show you as on Fast Path with one showing a zero "delay".
Those are remarkable given those SNRMs. You should be on heavy interleaving with a substantial "delay".

Default setting on FTTC for SNRM is 6dB. With luck DLM will then lower it automatically over time.

In reply to a post by RobertoS:

I'm very suspicious you have increased this yourself, as both the sets of stats show you as on Fast Path with one showing a zero "delay".

Nope. Adjustments took place to fight the issue after it appeared (with no effect).

In reply to a post by RobertoS:

I'm very suspicious you have increased this yourself, as both the sets of stats show you as on Fast Path with one showing a zero "delay".
Those are remarkable given those SNRMs. You should be on heavy interleaving with a substantial "delay".

I'll need to read up to understand that.

In reply to a post by RobertoS:

With luck DLM will then lower it automatically over time.

For the original 34Mbps would the graph show a usage (in blue) from 2816 onwards OR more bits in use at the lower end?

TIA.

FTTC bins/frequencies aren't used like ADSLx where the upstream ones are on the left and the downstream on the right.

On VDSL2 (which is what actually reaches your premises) they are all mixed up in a number of bands. I can't show you what mine looks like as I ditched FTTC 18 months ago.

For a longer explanation of how SNR and SNRM interact, this oldish page is still a useful explanation.

In reply to a post by forafewbytesmore:

It's persistent now for the past fortnight.

Using the SNR adjustment on the Vigor130 only gets the attainable rate to vary.

Your line looks like it has been capped (banded), on both the downstream and the upstream.

Banding is usually applied when a line is resyncing too much.

This is sometimes caused by the end user troublesome with their modem and rebooting it over and over or swapping modems around.

If the sync rate stats the exact same between resyncs and the SNRM is always above 6dB then the line is definitely banded.

It needs stability (no resyncs) for DLM to gradually remove the banding.

In reply to a post by RobertoS:

I'm very suspicious you have increased this yourself, as both the sets of stats show you as on Fast Path with one showing a zero "delay".
Those are remarkable given those SNRMs. You should be on heavy interleaving with a substantial "delay".

Huawei cabinet, G.INP active on both downstream and upstream.
Delay should be zero.

Edited by j0hn83 (Mon 15-Jun-20 19:33:00)

It would not have those stats in that situation!

The shovel would be self-cleaning, everything would slide off it so fast.

In reply to a post by RobertoS:

It would not have those stats in that situation!

It would.

Actual INP: 54.0 symbols 55.0 symbols

DSLAM CHIPSET VENDOR : < BDCM >

Huawei cabinet, G.INP on both down and upstream.

Confusion might come from...

DS Path Mode : Fast US Path Mode : Fast

I think Drayteks report Path Mode: Fast any time the delay is 0, which includes G.INP.

In reply to a post by forafewbytesmore:

Reported to ISP and awaiting response.

ISP called about 48 hours after support ticket submitted. Impressive.

Line test passed.

Awaiting network team call or text regarding site visit.