Post by: nfxcr3w on September 23, 2019, 09:14:58 PM
DSL uptime:
0 Days, 1 Hours 29 Minutes 12 Seconds
Data rate:
20.00 Mbps / 59.91 Mbps
Maximum data rate:
23560 / 71163
Noise margin:
7.8 dB / 6.2 dB
Line attenuation:
13 dB
Signal attenuation:
VPI / VCI:
0/38
Modulation:
G_993_2_ANNEX_B
Latency type:
Fast Path
Post by: 8062282 on September 23, 2019, 09:22:10 PM
Post by: burakkucat on September 23, 2019, 09:25:21 PM
[I see 8062282's fingers were faster than my paws . . . ]
Post by: nfxcr3w on September 23, 2019, 09:25:54 PM
Hi - As painful as it sounds, you'll probably have to wait for the line to stabilise over the next 10 days or so. The DLM will be monitoring the line & will make adjustments as it assesses your line.
Cheers I'll do :fingers: that, I thought that 10 day thing was a myth which only existed on ADSL Broadband. Not for Fibre?
Post by: nfxcr3w on September 23, 2019, 09:27:23 PM
I would recommend that you allow 24 hours to pass -- without disconnecting or rebooting the modem (or modem/router) -- and then re-check. Being so soon after the circuit has been newly provisioned, the DLM process will not have yet attempted to optimise the connection.
[I see 8062282's fingers were faster than my paws . . . ]
I'll do that thank you burakkucat ;)
Post by: j0hn on September 23, 2019, 10:17:28 PM
Cheers I'll do :fingers: that, I thought that 10 day thing was a myth which only existed on ADSL Broadband. Not for Fibre?
It is a myth.
It can take 24-48 hours for DLM to swap between fastpath /interleaving or to enable G.INP on Huawei lines.
It can take longer on some lines.
This isn't a 10 day training period though.
DLM does its normal thing from the get go.
The Smart Hub has very limited stats so who knows what's happening.
I wouldn't upset the DLM by doing anything that involves resyncing multiple times.
Post by: nfxcr3w on September 23, 2019, 10:53:00 PM
It is a myth.
It can take 24-48 hours for DLM to swap between fastpath /interleaving or to enable G.INP on Huawei lines.
It can take longer on some lines.
This isn't a 10 day training period though.
DLM does its normal thing from the get go.
The Smart Hub has very limited stats so who knows what's happening.
I wouldn't upset the DLM by doing anything that involves resyncing multiple times.
Thanks John so would it be safe to put back the HG612 after 48hrs?
Post by: 8062282 on September 24, 2019, 08:26:53 AM
Post by: dee.jay on September 24, 2019, 08:34:47 AM
Post by: 8062282 on September 24, 2019, 08:37:49 AM
I believe if you turn off your current router/modem and leave it off for at least 15 minutes before turning the other one on then DLM will not worry about it.
I would leave it for 30 mins to be on the safe side. The DLM works in 15 minute cycles. Half an hour should cover at least one of the 15 mins..
Post by: dorzb on September 24, 2019, 09:05:25 AM
To cut the long story short I was with BT before where I was getting 6ms ping and 74mb down but slow down in the evenings which I think they fixed that now so I moved to talktalk got a 6ms ping even when I did with BT but talktalk were horrible for gaming now I changed back to BT but my ping has increased to 14ms and im supposed to be on the highest package activation was today is this normal?. im currently using there smarthub at the moment. :(
DSL uptime:
0 Days, 1 Hours 29 Minutes 12 Seconds
Data rate:
20.00 Mbps / 59.91 Mbps
Maximum data rate:
23560 / 71163
Noise margin:
7.8 dB / 6.2 dB
Line attenuation:
13 dB
Signal attenuation:
VPI / VCI:
0/38
Modulation:
G_993_2_ANNEX_B
Latency type:
Fast Path
May I ask why TalkTalk were horrible for gaming with such a low ping?
Post by: dee.jay on September 24, 2019, 09:52:48 AM
I would leave it for 30 mins to be on the safe side. The DLM works in 15 minute cycles. Half an hour should cover at least one of the 15 mins..
Ah - wasn't sure, I knew 15 mins had something to do with it! Thanks
Post by: tiffy on September 24, 2019, 12:50:16 PM
https://kitz.co.uk/adsl/DLM.htm (https://kitz.co.uk/adsl/DLM.htm)
Quote from "BT's DLM Process" (link above)
Quote
Because we know that the DLM collects data bins every 15 mins and that it monitors traffic count to see if the line is in use, it is therefore recommended if possible to try to leave the router switched off for 30 mins to ensure that the DLM sees at least one complete period of inactivity prior to the resync.
I have always observed at least 35 min's. down time on any planned modem outages to ensure at least two consecutive DLM monitor cycles, over cautious perhaps but I have the time and it's worked for me to date avoiding any unwanted negative DLM intervention.
Post by: nfxcr3w on September 24, 2019, 02:30:47 PM
May I ask why TalkTalk were horrible for gaming with such a low ping?
There would be a lot of ping spikes and packet loss and when pasting my ip in to the browser it would take me to the router page which i found was unsecure i never had any of them issues with BT hence why i went back playing call of duty it would always feel like im always being seen first before like they've seen me before I've seen them. and also TalkTalk use standard profile instead of just Speed that BT use which is what you want has a gamer.
Post by: nfxcr3w on September 24, 2019, 02:32:37 PM
Sorry, seen so many people & ISP pages state 10 days approx for DLM to stabilise. Seems even the ISPs can’t give valid info out
That's ok had to double check to make sure since it might have changed but it looks like it hasn't. ;)
Post by: nfxcr3w on September 26, 2019, 07:22:38 AM
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 23603 Kbps, Downstream rate = 67752 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 68329 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): 6.2 7.8
Attn(dB): 12.5 0.0
Pwr(dBm): 12.4 -1.7
VDSL2 framing
Bearer 0
MSGc: -6 20
B: 243 239
M: 1 1
T: 0 64
R: 10 0
S: 0.1137 0.3819
L: 17870 5028
D: 8 1
I: 254 120
N: 254 240
Q: 8 0
V: 0 0
RxQueue: 56 0
TxQueue: 14 0
G.INP Framing: 18 0
G.INP lookback: 14 0
RRC bits: 0 24
Bearer 1
MSGc: 154 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 6.4000 0.0000
L: 40 0
D: 3 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 2171609
OHFErr: 0 24
RS: 464844472 1534704
RSCorr: 85 0
RSUnCorr: 0 0
Bearer 1
OHF: 825960 0
OHFErr: 0 0
RS: 8258988 0
RSCorr: 0 0
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 149515 0
rtx_c: 1 0
rtx_uc: 0 0
G.INP Counters
LEFTRS: 0 0
minEFTR: 68307 0
errFreeBits: 13824420 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 1743263667 0
Data Cells: 5809235 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: 13 299
SES: 10 0
UAS: 64 54
AS: 13267
Bearer 0
INP: 50.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 6.13
OR: 0.01 33.91
AgR: 68398.64 20033.74
Bearer 1
INP: 4.50 0.00
INPRein: 4.50 0.00
delay: 3 0
PER: 16.06 0.01
OR: 79.68 0.01
AgR: 79.68 0.01
Bitswap: 2032/2032 20/20
Total time = 1 days 16 hours 4 min 38 sec
FEC: 22347 0
CRC: 5845 473
ES: 13 299
SES: 10 0
UAS: 64 54
LOS: 1 0
LOF: 9 0
LOM: 0 0
Latest 15 minutes time = 4 min 38 sec
FEC: 0 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: 6 0
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 16 hours 4 min 38 sec
FEC: 1723 0
CRC: 5827 142
ES: 10 116
SES: 10 0
UAS: 36 26
LOS: 1 0
LOF: 9 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 20624 0
CRC: 18 331
ES: 3 183
SES: 0 0
UAS: 28 28
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 3 hours 41 min 7 sec
FEC: 85 0
CRC: 0 24
ES: 0 22
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
Post by: tubaman on September 26, 2019, 07:50:06 AM
To get more speed now you need to wait for DLM to drop the DS SNR from 6dB to hopefully 3dB if your line can support it. This'll happen in 1dB steps over a number of days.
Be patient and it should get there.
:)
Post by: nfxcr3w on September 26, 2019, 08:21:07 AM
Good news that G.INP has kicked in quite quickly.
To get more speed now you need to wait for DLM to drop the DS SNR from 6dB to hopefully 3dB if your line can support it. This'll happen in 1dB steps over a number of days.
Be patient and it should get there.
:)
Thank you I've seen my SNR drop on the downstream with my previous ISP to 2.2 SNR is that good? it took almost a year to drop down that low. It was stable on that low of a SNR
Post by: dee.jay on September 26, 2019, 08:38:01 AM
Post by: nfxcr3w on September 26, 2019, 08:46:26 AM
2.2 is a bit too low, 3dB is where it's at.
Thank you do you know what causes it to drop too low?
Post by: tubaman on September 26, 2019, 11:36:37 AM
Thank you do you know what causes it to drop too low?
It should have synced at 3dB but may then have dropped over time - or it may have been the time of day you looked at it as it does vary a bit throughout the day.
As long as it is stable with low errors then DLM should leave it alone.
:)
Post by: dee.jay on September 26, 2019, 12:57:35 PM
Post by: j0hn on September 26, 2019, 01:23:14 PM
Thank you do you know what causes it to drop too low?
The target SNRM is 3, 4, 5 or 6dB.
Broadcom modems tend to sync with a slightly higher SNRM at 3.3, 4.3, 5.3 or 6.3dB.
Although your target SNRM may have been 3dB, the actual SNRM can go up and down after sync is achieved as noise comes and goes on the line.
The target is never below 3dB though.
DLM moves the target SNRM in 1dB steps.
It requires G.INP to be active to go below a 6dB target.
Now that G.INP is active hopefully the DLM will start to lower your target SNRM down towards 3dB.
It usually drops to 5dB around 48 hours after G.INP is enabled, and 4dB after another 48 hours, etc.
Stability is key so best not to fiddle if you want back to 3dB.
Post by: nfxcr3w on September 26, 2019, 01:46:48 PM
It should have synced at 3dB but may then have dropped over time - or it may have been the time of day you looked at it as it does vary a bit throughout the day.
As long as it is stable with low errors then DLM should leave it alone.
:)
Thanks DLM is been good to me now i remember it was a bit harsh in the passed.
Post by: nfxcr3w on September 26, 2019, 01:47:59 PM
Yes mine recently dropped to 2.5 and it was stable, but has since returned to 3 by itself.
Nice i think the longer you leave it alone the more forgiving the DLM is on the SNR :)
Post by: nfxcr3w on September 26, 2019, 01:54:48 PM
The target SNRM is 3, 4, 5 or 6dB.
Broadcom modems tend to sync with a slightly higher SNRM at 3.3, 4.3, 5.3 or 6.3dB.
Although your target SNRM may have been 3dB, the actual SNRM can go up and down after sync is achieved as noise comes and goes on the line.
The target is never below 3dB though.
DLM moves the target SNRM in 1dB steps.
It requires G.INP to be active to go below a 6dB target.
Now that G.INP is active hopefully the DLM will start to lower your target SNRM down towards 3dB.
It usually drops to 5dB around 48 hours after G.INP is enabled, and 4dB after another 48 hours, etc.
Stability is key so best not to fiddle if you want back to 3dB.
Thank you J0hn, I have a question about the Huawei Chipset I've noticed that the Broadcom DSLAM SW version got updated last year from BDCM:0xa48c (164.140) / v0xa48c to BDCM:0xc014 (192.20) / v0xc014 any reason for the change? Since i feel im the only one with this updated version.
Post by: j0hn on September 26, 2019, 06:03:58 PM
My DSLAM firmware updated when the Huawei 288 > 384 expansion was added.
I believe it may be reporting line card version which changes with a larger line card.
Though I haven't seen the version you report before now.
Post by: nfxcr3w on September 26, 2019, 06:07:48 PM
Has your cabinet had an extension added?
My DSLAM firmware updated when the Huawei 288 > 384 expansion was added.
I believe it may be reporting line card version which changes with a larger line card.
Though I haven't seen the version you report before now.
Yes it has I've seen the extension on the side of the cabinet which it never had before. Is this line card added for extra connections?
Post by: j0hn on September 27, 2019, 12:59:11 AM
They swap out the current line cards for ones with more ports.
Swapping 32 port line cards for 64 port cards on the smaller cabinets or on the large Huawei cabinets it's swapping 48 port cards for 64 port cards.
The smaller Huawei cabinets have evolved through 24 > 32 > 48 and more recently 64 port line cards.
I believe the larger Huawei cabinets started with 48 ports.
Capacity upgrades are only done when necessary.
Post by: nfxcr3w on September 27, 2019, 02:38:45 AM
Basically yes.
They swap out the current line cards for ones with more ports.
Swapping 32 port line cards for 64 port cards on the smaller cabinets or on the large Huawei cabinets it's swapping 48 port cards for 64 port cards.
The smaller Huawei cabinets have evolved through 24 > 32 > 48 and more recently 64 port line cards.
I believe the larger Huawei cabinets started with 48 ports.
Capacity upgrades are only done when necessary.
Thanks J0hn for the explanation I think the Capacity needed to be upgraded since the last time i was with bt about a year ago around Christmas time it slowed down from 75mb all the way to 11mb BTW changed my SVLAN so many times that it didn't make a blind bit of difference till they gave up with me so it must of been a Capacity problem at the Huawei cabinet?
Post by: nfxcr3w on September 29, 2019, 01:56:31 PM
The target SNRM is 3, 4, 5 or 6dB.
Broadcom modems tend to sync with a slightly higher SNRM at 3.3, 4.3, 5.3 or 6.3dB.
Although your target SNRM may have been 3dB, the actual SNRM can go up and down after sync is achieved as noise comes and goes on the line.
The target is never below 3dB though.
DLM moves the target SNRM in 1dB steps.
It requires G.INP to be active to go below a 6dB target.
Now that G.INP is active hopefully the DLM will start to lower your target SNRM down towards 3dB.
It usually drops to 5dB around 48 hours after G.INP is enabled, and 4dB after another 48 hours, etc.
Stability is key so best not to fiddle if you want back to 3dB.
J0hn still hasn't dropped the SNR after 48hrs been connected for just over 48hrs now here's the stats below
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 23392 Kbps, Downstream rate = 67752 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 68329 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): 6.2 7.7
Attn(dB): 12.5 0.0
Pwr(dBm): 12.4 -1.7
VDSL2 framing
Bearer 0
MSGc: -6 20
B: 243 239
M: 1 1
T: 0 64
R: 10 0
S: 0.1137 0.3819
L: 17870 5028
D: 8 1
I: 254 120
N: 254 240
Q: 8 0
V: 0 0
RxQueue: 56 0
TxQueue: 14 0
G.INP Framing: 18 0
G.INP lookback: 14 0
RRC bits: 0 24
Bearer 1
MSGc: 154 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 6.4000 0.0000
L: 40 0
D: 3 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 1778318
OHFErr: 0 847
RS: 1784583992 441077
RSCorr: 14371 0
RSUnCorr: 0 0
Bearer 1
OHF: 18432684 0
OHFErr: 0 0
RS: 184326225 0
RSCorr: 0 0
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 149664 0
rtx_c: 127 0
rtx_uc: 0 0
G.INP Counters
LEFTRS: 0 0
minEFTR: 68307 0
errFreeBits: 308514666 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 249831033 0
Data Cells: 1143295683 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: 13 894
SES: 10 3
UAS: 64 54
AS: 296079
Bearer 0
INP: 50.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 6.13
OR: 0.01 33.91
AgR: 68398.64 20033.74
Bearer 1
INP: 4.50 0.00
INPRein: 4.50 0.00
delay: 3 0
PER: 16.06 0.01
OR: 79.68 0.01
AgR: 79.68 0.01
Bitswap: 124328/124328 1335/1335
Total time = 1 days 22 hours 38 min 10 sec
FEC: 36633 0
CRC: 5845 1296
ES: 13 894
SES: 10 3
UAS: 64 54
LOS: 1 0
LOF: 9 0
LOM: 0 0
Latest 15 minutes time = 8 min 10 sec
FEC: 1 0
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 4 0
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 22 hours 38 min 10 sec
FEC: 590 0
CRC: 0 255
ES: 0 180
SES: 0 1
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 1445 0
CRC: 0 321
ES: 0 213
SES: 0 2
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 3 days 10 hours 14 min 37 sec
FEC: 14371 0
CRC: 0 847
ES: 0 617
SES: 0 3
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
Post by: Postal on September 29, 2019, 04:12:34 PM
I think the answer is patience and it will come right eventually.
Post by: nfxcr3w on September 29, 2019, 05:53:44 PM
Changed ISP last year. Original connection had a target SNR of 6dB. The new connection lost G.INP and knocked sync down from 66999 to 62459 at the same 6dB SNR. Downstream G.INP kicked in after 48 hours and the sync went to 72233. After a further week there was a silent re-connect when the G.INP went up a couple of notches from 48 and the re-sync was 75314. This was still at 6dB. After a further 3 weeks (the router was powered down for one of those weeks as we were away) the SNR dropped in one leap to 3dB and re-synced at 79230. So changing ISP to a rather more pro-active supplier moved my download sync up from 66999 to 79230 in just about a month.
I think the answer is patience and it will come right eventually.
Thanks yeah it was my mistake on listening to BT they told me to leave the smart hub in then it will connect once the move over has completed. The hub was trying to connect and the DLM must of thought i was having stability problems i should of just left the hg612 3b in then it would of automatically changed over. Now i have to play the waiting game took a year to get that 3db back so god knows how long it will take to get 3db back again that's if BT has a 3db setting cause im still on 6db.
Post by: gt94sss2 on September 29, 2019, 06:03:27 PM
So changing ISP to a rather more pro-active supplier moved my download sync up from 66999 to 79230 in just about a month.
I agree with the point about patience. It doesn't matter which ISP you use as DLM is automatically controlled by Openreach - and ISPs have no control over the process.
Post by: nfxcr3w on September 29, 2019, 06:19:20 PM
I agree with the point about patience. It doesn't matter which ISP you use as DLM is automatically controlled by Openreach - and ISPs have no control over the process.
True but i think Plusnet have more control over the process then any other ISP's has they can reset the DLM which i think is wrong since BT is Plusnet's parent company. BT should allow that process.
Post by: ejs on September 29, 2019, 06:54:42 PM
Post by: nfxcr3w on September 29, 2019, 07:57:22 PM
I think Plusnet have no more ability to reset the FTTC DLM than any other ISP. Any apparent difference may actually be in the willingness of Plusnet staff to do it for no other reason than the line being banded and you wanting it reset.
That's good to know thank you for that. ;)