Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: 1 2 [3]

Author Topic: ISP Change Over  (Read 4323 times)

nfxcr3w

  • Member
  • **
  • Posts: 98
Re: ISP Change Over
« Reply #30 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
#
Logged
BT FTTC @3db 80/20 Zyxel VMG1312-B10A bridged + 1508 MTU + OpenWrt 19.07.2 Huawei Cab

Postal

  • Member
  • **
  • Posts: 37
Re: ISP Change Over
« Reply #31 on: September 29, 2019, 04:12:34 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.
Logged

nfxcr3w

  • Member
  • **
  • Posts: 98
Re: ISP Change Over
« Reply #32 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.
Logged
BT FTTC @3db 80/20 Zyxel VMG1312-B10A bridged + 1508 MTU + OpenWrt 19.07.2 Huawei Cab

gt94sss2

  • Kitizen
  • ****
  • Posts: 1281
Re: ISP Change Over
« Reply #33 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.
Logged

nfxcr3w

  • Member
  • **
  • Posts: 98
Re: ISP Change Over
« Reply #34 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.
Logged
BT FTTC @3db 80/20 Zyxel VMG1312-B10A bridged + 1508 MTU + OpenWrt 19.07.2 Huawei Cab

ejs

  • Kitizen
  • ****
  • Posts: 2078
Re: ISP Change Over
« Reply #35 on: September 29, 2019, 06:54:42 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.
Logged

nfxcr3w

  • Member
  • **
  • Posts: 98
Re: ISP Change Over
« Reply #36 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.  ;)
Logged
BT FTTC @3db 80/20 Zyxel VMG1312-B10A bridged + 1508 MTU + OpenWrt 19.07.2 Huawei Cab
Pages: 1 2 [3]