Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Does the DLM always make the right decisions?
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Broadband
- :
- Re: Does the DLM always make the right decisions?
Does the DLM always make the right decisions?
16-10-2015 12:35 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
After some serious stability problems over winter, my connection has been pretty well behaved all summer, running reliably with interleaving off, target SNRM's 6dB up and down despite there being occasional bursts of noise on the line, usually affecting the upstream more than the downstream.
On Monday of this week, the DLM applied interleaving on the DS, presumably in response to increased noise and errors (connection still quite stable.)
Dropped sync a couple of times yesterday evening, but reconnected with 6dB margins.
Powered everything off overnight, and reconnected as soon as it was light this morning, and found the DS SNRM target had been reduced to 3dB.
Did another graceful disconnect and resync - nope, DS target still 3dB with a correspondingly higher DS connection rate (bad news on my connection.).
My DS SNRM drops at least 2dB at night now the days are shortening, the US SNRM is already all over the place a million FEC errors in one hour, so there isn't a snowflake's chance this target will prove to be stable after dark (or even before then.)
Current router stats:
Uptime: 0 days, 1:13:13
DSL Type: ITU-T G.992.5
Bandwidth (Up/Down) [kbps/kbps]: 1,227 / 12,541
Data Transferred (Sent/Received) [kB/MB]: 878.03 / 4.89
Output Power (Up/Down) [dBm]: 12.7 / 0.0
Line Attenuation (Up/Down) [dB]: 16.6 / 37.0
SN Margin (Up/Down) [dB]: 5.6 / 3.1
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / IFTN
Loss of Framing (Local/Remote): 0 / 0
Loss of Signal (Local/Remote): 0 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): -
Error Seconds (Local/Remote): 87 / 0
FEC Errors (Up/Down): 6 / 1,015,257
CRC Errors (Up/Down): 1 / 100
HEC Errors (Up/Down): 1 / 257
It obviously begs the question as to how the DLM can reduce the target SNRM on a line to which it has already recently applied interleaving because it's starting to suffer noise problems.
I'll let you know what happens next - I don't intend to resync manually or change anything in the immediate future.
On Monday of this week, the DLM applied interleaving on the DS, presumably in response to increased noise and errors (connection still quite stable.)
Dropped sync a couple of times yesterday evening, but reconnected with 6dB margins.
Powered everything off overnight, and reconnected as soon as it was light this morning, and found the DS SNRM target had been reduced to 3dB.
Did another graceful disconnect and resync - nope, DS target still 3dB with a correspondingly higher DS connection rate (bad news on my connection.).
My DS SNRM drops at least 2dB at night now the days are shortening, the US SNRM is already all over the place a million FEC errors in one hour, so there isn't a snowflake's chance this target will prove to be stable after dark (or even before then.)
Current router stats:
Uptime: 0 days, 1:13:13
DSL Type: ITU-T G.992.5
Bandwidth (Up/Down) [kbps/kbps]: 1,227 / 12,541
Data Transferred (Sent/Received) [kB/MB]: 878.03 / 4.89
Output Power (Up/Down) [dBm]: 12.7 / 0.0
Line Attenuation (Up/Down) [dB]: 16.6 / 37.0
SN Margin (Up/Down) [dB]: 5.6 / 3.1
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / IFTN
Loss of Framing (Local/Remote): 0 / 0
Loss of Signal (Local/Remote): 0 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): -
Error Seconds (Local/Remote): 87 / 0
FEC Errors (Up/Down): 6 / 1,015,257
CRC Errors (Up/Down): 1 / 100
HEC Errors (Up/Down): 1 / 257
It obviously begs the question as to how the DLM can reduce the target SNRM on a line to which it has already recently applied interleaving because it's starting to suffer noise problems.
I'll let you know what happens next - I don't intend to resync manually or change anything in the immediate future.
Message 1 of 9
(1,550 Views)
8 REPLIES 8
Re: Does the DLM always make the right decisions?
16-10-2015 3:23 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Hi,
Let us know if the line starts to become unstable, we can always set the target SNR up to 6db from here if needed.
Let us know if the line starts to become unstable, we can always set the target SNR up to 6db from here if needed.
Former Plusnet Staff member. Posts after 31st Jan 2020 are not on behalf of Plusnet.
Message 2 of 9
(717 Views)
Re: Does the DLM always make the right decisions?
18-10-2015 10:17 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Thanks Chris - one unforced resync at tea time on Friday - I think it's fair to say the connection has been hanging on grimly since then:
Uptime: 1 day, 16:37:45
DSL Type: ITU-T G.992.5
Bandwidth (Up/Down) [kbps/kbps]: 1,230 / 12,293
Data Transferred (Sent/Received) [MB/GB]: 792.94 / 1.64
Output Power (Up/Down) [dBm]: 12.9 / 0.0
Line Attenuation (Up/Down) [dB]: 16.7 / 37.0
SN Margin (Up/Down) [dB]: 4.9 / 3.0
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / IFTN
Loss of Framing (Local/Remote): 9 / 0
Loss of Signal (Local/Remote): 1 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): -
Error Seconds (Local/Remote): 27,580 / 0
FEC Errors (Up/Down): 831 / 174,054,885
CRC Errors (Up/Down): 186 / 93,551
HEC Errors (Up/Down): 289 / 337,473
Will revisit tomorrow when there are some CRT staff on duty - stats like this with a 3dB DS SNRM target are pretty unsustainable and still begs the question as to why the DLM should have opted to try it.
Uptime: 1 day, 16:37:45
DSL Type: ITU-T G.992.5
Bandwidth (Up/Down) [kbps/kbps]: 1,230 / 12,293
Data Transferred (Sent/Received) [MB/GB]: 792.94 / 1.64
Output Power (Up/Down) [dBm]: 12.9 / 0.0
Line Attenuation (Up/Down) [dB]: 16.7 / 37.0
SN Margin (Up/Down) [dB]: 4.9 / 3.0
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / IFTN
Loss of Framing (Local/Remote): 9 / 0
Loss of Signal (Local/Remote): 1 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): -
Error Seconds (Local/Remote): 27,580 / 0
FEC Errors (Up/Down): 831 / 174,054,885
CRC Errors (Up/Down): 186 / 93,551
HEC Errors (Up/Down): 289 / 337,473
Will revisit tomorrow when there are some CRT staff on duty - stats like this with a 3dB DS SNRM target are pretty unsustainable and still begs the question as to why the DLM should have opted to try it.
Message 3 of 9
(717 Views)
Re: Does the DLM always make the right decisions?
19-10-2015 10:50 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Current router stats:
Uptime: 2 days, 17:05:39
DSL Type: ITU-T G.992.5
Bandwidth (Up/Down) [kbps/kbps]: 1,230 / 12,293
Data Transferred (Sent/Received) [MB/GB]: 804.27 / 1.69
Output Power (Up/Down) [dBm]: 12.9 / 0.0
Line Attenuation (Up/Down) [dB]: 16.7 / 37.0
SN Margin (Up/Down) [dB]: 5.4 / 3.4
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / IFTN
Loss of Framing (Local/Remote): 9 / 0
Loss of Signal (Local/Remote): 1 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): -
Error Seconds (Local/Remote): 59,528 / 0
FEC Errors (Up/Down): 1,225 / 341,210,419
CRC Errors (Up/Down): 256 / 302,113
HEC Errors (Up/Down): 418 / 1,464,644
+ +
So, still hanging on by the skin of its teeth, with overnight SNR down to 1.2dB.
Would Chris or someone else from CRT change the DS SNRM target to 6dB please?
Will this be a fixed or minimum target?
Uptime: 2 days, 17:05:39
DSL Type: ITU-T G.992.5
Bandwidth (Up/Down) [kbps/kbps]: 1,230 / 12,293
Data Transferred (Sent/Received) [MB/GB]: 804.27 / 1.69
Output Power (Up/Down) [dBm]: 12.9 / 0.0
Line Attenuation (Up/Down) [dB]: 16.7 / 37.0
SN Margin (Up/Down) [dB]: 5.4 / 3.4
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / IFTN
Loss of Framing (Local/Remote): 9 / 0
Loss of Signal (Local/Remote): 1 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): -
Error Seconds (Local/Remote): 59,528 / 0
FEC Errors (Up/Down): 1,225 / 341,210,419
CRC Errors (Up/Down): 256 / 302,113
HEC Errors (Up/Down): 418 / 1,464,644
+ +
So, still hanging on by the skin of its teeth, with overnight SNR down to 1.2dB.
Would Chris or someone else from CRT change the DS SNRM target to 6dB please?
Will this be a fixed or minimum target?
Message 4 of 9
(717 Views)
Re: Does the DLM always make the right decisions?
19-10-2015 12:02 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Hi, I have reset the SNR top a 6db profile and this take effect shortly for you
Message 5 of 9
(717 Views)
Re: Does the DLM always make the right decisions?
19-10-2015 12:16 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Thanks Ben - just hope the DLM regards it as a slap on the wrist and keeps its interfering mitts in its pocket from now on...
New DSL stats after reset SNRM target:
Uptime: 0 days, 0:06:36
DSL Type: ITU-T G.992.5
Bandwidth (Up/Down) [kbps/kbps]: 1,235 / 11,005
Data Transferred (Sent/Received) [MB/GB]: 807.22 / 1.72
Output Power (Up/Down) [dBm]: 12.8 / 0.0
Line Attenuation (Up/Down) [dB]: 16.7 / 37.0
SN Margin (Up/Down) [dB]: 6.0 / 6.3
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / IFTN
Loss of Framing (Local/Remote): 26 / 0
Loss of Signal (Local/Remote): 3 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): -
Error Seconds (Local/Remote): 60,056 / 0
FEC Errors (Up/Down): 0 / 4,444
CRC Errors (Up/Down): 0 / 0
HEC Errors (Up/Down): 0 / 0
New DSL stats after reset SNRM target:
Uptime: 0 days, 0:06:36
DSL Type: ITU-T G.992.5
Bandwidth (Up/Down) [kbps/kbps]: 1,235 / 11,005
Data Transferred (Sent/Received) [MB/GB]: 807.22 / 1.72
Output Power (Up/Down) [dBm]: 12.8 / 0.0
Line Attenuation (Up/Down) [dB]: 16.7 / 37.0
SN Margin (Up/Down) [dB]: 6.0 / 6.3
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / IFTN
Loss of Framing (Local/Remote): 26 / 0
Loss of Signal (Local/Remote): 3 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): -
Error Seconds (Local/Remote): 60,056 / 0
FEC Errors (Up/Down): 0 / 4,444
CRC Errors (Up/Down): 0 / 0
HEC Errors (Up/Down): 0 / 0
Message 6 of 9
(717 Views)
Re: Does the DLM always make the right decisions?
19-10-2015 12:19 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Hahaha no problems, just keep us up to date if you need any further assistance and we'll be more than happy to help.
Message 7 of 9
(717 Views)
Re: Does the DLM always make the right decisions?
19-10-2015 12:42 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Quote from: JayG Thanks Ben - just hope the DLM regards it as a slap on the wrist and keeps its interfering mitts in its pocket from now on...
BT's DLM seems to have a mind of its own which doesn't necessarily follow reason in my experience.
Message 8 of 9
(717 Views)
Re: Does the DLM always make the right decisions?
21-10-2015 9:52 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Quote from: JayG Thanks Ben - just hope the DLM regards it as a slap on the wrist and keeps its interfering mitts in its pocket from now on...
In the event DLM only managed to restrain itself for about 2 hours, resynching soon after with a DS SNRM target of 9db.
Couple of evening and overnight drops since then, but I resynched and rebooted manually yesterday morning to reset the stats and try to get a DS rate of above rather than below 10Mbps.
Obviously not happy that a connection which behaved itself all spring and summer with a 6dB DS target and no interleaving now has interleaving and a 9dB target, but at least I can understand the logic of the DLM's actions this time, and up to now the connection seems to be generating few errors.
I fear a repeat of last winter's erratic behaviour, which started around this time (hopefully not - time will tell no doubt.)
Current DSL stats:
Uptime: 1 day, 0:04:49
DSL Type: ITU-T G.992.5
Bandwidth (Up/Down) [kbps/kbps]: 1,227 / 10,049
Data Transferred (Sent/Received) [MB/MB]: 10.28 / 86.87
Output Power (Up/Down) [dBm]: 12.9 / 0.0
Line Attenuation (Up/Down) [dB]: 16.6 / 37.0
SN Margin (Up/Down) [dB]: 5.6 / 8.4
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / IFTN
Loss of Framing (Local/Remote): 0 / 0
Loss of Signal (Local/Remote): 0 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): -
Error Seconds (Local/Remote): 102 / 0
FEC Errors (Up/Down): 423 / 163,682
CRC Errors (Up/Down): 104 / 142
HEC Errors (Up/Down): 150 / 1,156
Message 9 of 9
(717 Views)
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Broadband
- :
- Re: Does the DLM always make the right decisions?