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

Login with username, password and session length
Advanced search  

News:

Author Topic: Interleaved in 2017  (Read 1197 times)

mbb

  • Member
  • **
  • Posts: 33
Interleaved in 2017
« on: December 09, 2017, 06:40:36 PM »

Hi All its been a while scince posting here after i was perscribed a dose of GINP on my line to help subside my latency nightmares. But alas after a house move there back and worse than before.

I had bt infinity1 installed at our new house 1st Dec but due to having boxes stacked evrywhere only just got my desk up on the 7th. Straight away i ran a few ping tests and it was obvious my line was interleaved gettting 24ms to bbc. For no other reason apart from a laugh i did a line fault test on bts website and to my surprise it flashed up saying there was a fault on my line. Even more to my surprise yesterday morning at 8:45 am two Openreach vans turned up and were here till 13:30 testing every junction underground, my kit, drop wire, master sockets until the fault was apparently found on the grey box at the top of the pole. They said it was damp and was jam packed with cables that were stripped back and new grease applied. He also fitted a new socket for me.They told me the voltage on my line should be no more than 6 but it was apparently 30 and possibly drawing volts from another line. After they fixed it he showed me his little tester thingy and all the green ticks showing my line had passed all his tests.  I asked him to do a dlm rest but he needed some number from the job which he didn't have and would try his best (i never got a dlm reset).

today same 24 pings but at around 3pm i got a 'internet connection is down' message on my browser. i looked at my hub and it was all blue evrything looked fine but i am now getting 38ms to bbc multiplay evrywhere from the early hops!! 38 ping i never thought interleaving would be that bad. My hg612 is hacked from my last troubling interleaving times so i am able to get some stats. Im guessing it will be a matter of days before G.INP is applied on my line?? Does anything look funny in these stats ive no idea myself. Thanks for reading

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason:   1
Last initialization procedure status:   0
Max:   Upstream rate = 7538 Kbps, Downstream rate = 40436 Kbps
Bearer:   0, Upstream rate = 6182 Kbps, Downstream rate = 37954 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       6.1
Attn(dB):    23.8       0.0
Pwr(dBm):    12.3      -0.5
         VDSL2 framing
         Bearer 0
MSGc:      18      42
B:      111      47
M:      1      1
T:      44      64
R:      16      16
S:      0.0939      0.2465
L:      10904      2077
D:      685      131
I:      128      64
N:      128      64
         Counters
         Bearer 0
OHF:      2516425      496344
OHFErr:      4      0
RS:      332126501      2480357
RSCorr:      40738      2440
RSUnCorr:   6      0

         Bearer 0
HEC:      0      0
OCD:      0      0
LCD:      0      0
Total Cells:   570913118      0
Data Cells:   2164218      0
Drop Cells:   0
Bit Errors:   0      0

ES:      65      87
SES:      28      0
UAS:      2134      2110
AS:      7830

         Bearer 0
INP:      4.00      4.00
INPRein:   0.00      0.00
delay:      16      8
PER:      3.11      15.83
OR:      61.71      24.24
AgR:      38015.50   6206.75

Bitswap:   6226/6226      255/255

Total time = 1 days 7 hours 24 min 27 sec
FEC:      687027      2532
CRC:      9134      96
ES:      65      87
SES:      28      0
UAS:      2134      2110
LOS:      1      0
LOF:      19      0
LOM:      11      0
Latest 15 minutes time = 9 min 27 sec
FEC:      2012      1
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:      4726      674
CRC:      0      0
ES:      0      0
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Latest 1 day time = 7 hours 24 min 27 sec
FEC:      81393      2461
CRC:      3132      21
ES:      15      18
SES:      10      0
UAS:      40      30
LOS:      1      0
LOF:      6      0
LOM:      0      0
Previous 1 day time = 24 hours 0 sec
FEC:      605634      71
CRC:      6002      75
ES:      50      69
SES:      18      0
UAS:      2094      2080
LOS:      0      0
LOF:      13      0
LOM:      11      0
Since Link time = 2 hours 10 min 29 sec
FEC:      40738      2440
CRC:      4      0
ES:      2      0
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
#
Logged

mbb

  • Member
  • **
  • Posts: 33
Re: Interleaved in 2017
« Reply #1 on: December 09, 2017, 07:09:50 PM »

Stats recorded 09 Dec 2017 19:09:29

DSLAM/MSAN type:           BDCM:0xa48c / v0xa48c
Modem/router firmware:     AnnexA version - A2pv6C038m.d24j
DSL mode:                  VDSL2 Profile 17a
Status:                    Showtime
Uptime:                     2 hours 41 min 0 sec
Resyncs:                   0 (since 09 Dec 2017 17:33:25)
         
            Downstream   Upstream
Line attenuation (dB):     23.8      0.0
Signal attenuation (dB):   Not monitored      
Connection speed (kbps):   37954      6182
SNR margin (dB):           6.2      6.2
Power (dBm):               12.3      -0.5
Interleave depth:          685      131
INP:                       4.00      4.00
G.INP:                     Not enabled      Not enabled
Vectoring status:          5 (VECT_UNCONFIGURED)      

RSCorr/RS (%):             0.0119      0.1599
RSUnCorr/RS (%):           0.0000      0.0000
ES/hour:                   1.24      0
Logged

j0hn

  • Kitizen
  • ****
  • Posts: 1511
Re: Interleaved in 2017
« Reply #2 on: December 09, 2017, 09:02:30 PM »

It can take a few weeks for DLM to apply g.inp on a new line. That time might have restarted if the engineer performed a DLM reset (he should if he made repairs to the network). It's more than likely all will be well in a couple weeks time.
Logged
BT FTTC 55/10 ECI now Huawei cab
Zyxel VMG1312-B10A bridge mode with 1508 MTU + Asus RT-AC68U running Asuswrt-Merlin

NewtronStar

  • Kitizen
  • ****
  • Posts: 4811
Re: Interleaved in 2017
« Reply #3 on: December 09, 2017, 11:56:22 PM »

If I'm right a line which had broadband and then was ceased by the previous owner the new owner of the premises would need to place a new order to reactivate the line this would be classed as a New line, if from passed knowledge it can take upto 8 weeks for a line to be G.INP enabled  :-\

Interleaving on FTTC can add about 10ms onto your pings though the further north you go in the UK the ping ms will increase the best I can get these days is 18ms it used to be 32 - 42ms when Interleaved on FTTC.
« Last Edit: December 10, 2017, 12:00:00 AM by NewtronStar »
Logged

ejs

  • Kitizen
  • ****
  • Posts: 1665
Re: Interleaved in 2017
« Reply #4 on: December 10, 2017, 08:39:06 AM »

The stats show a total of 24ms delay from the interleaving, presumably it's operating at the high level of interleaving on at least the downstream. Presumably the DLM was not happy about something, perhaps the fault that has now been fixed.
Logged

mbb

  • Member
  • **
  • Posts: 33
Re: Interleaved in 2017
« Reply #5 on: December 10, 2017, 05:19:58 PM »

Thanks ever so much for the replies guys.

Interleaving on FTTC can add about 10ms onto your pings though the further north you go in the UK the ping ms will increase the best I can get these days is 18ms it used to be 32 - 42ms when Interleaved on FTTC.

Ive literally just moved round the corner in salford and at my old property after g.inp was enabled on my line i had 11ms to bbc for almost 3 years. Now thats a ping to be proud of :P

However im now on a diff cab which is also a broadcomm one and it seems to be one of the oldest cabs in the village thats runs right the way through, turns off the main road and right down the row of terraces were at. passing about 4 new estates each with cabs at the start


The stats show a total of 24ms delay from the interleaving, presumably it's operating at the high level of interleaving on at least the downstream. Presumably the DLM was not happy about something, perhaps the fault that has now been fixed.

Interleave depth:          685      131

The crazy high interleave depth was applied around 4pm after the engineers left at 13:30. My hub must have resynced about 20 times while they were here testing every junction possible. I can only hope this is why and the new depth was applied just after it was fixed.

Is there any reason G.INP will NOT be applied to my line? or is it 100% just a matter of time as i thought interleaving was a thing of the past. And does anything stand out to anyone in my stats that would indicate any other problems or possible any advice on what stats to look at. My snr margin graph is like constant ever so slight jitter untill 1am then completly flat until 7:15am. 1hr or slight jitter then flat till 13:00 and its been slight jitter ever scince
Logged

ejs

  • Kitizen
  • ****
  • Posts: 1665
Re: Interleaved in 2017
« Reply #6 on: December 10, 2017, 05:36:21 PM »

The interleave depth figure itself doesn't really tell you very much, the INP and delay values are more meaningful. I think INP=3 and delay=8 is the usual low setting.

Also, I thought the voltage on a phone line was supposed to be 50, so perhaps they were talking about something else.
Logged

mbb

  • Member
  • **
  • Posts: 33
Re: Interleaved in 2017
« Reply #7 on: December 10, 2017, 05:55:47 PM »

The interleave depth figure itself doesn't really tell you very much, the INP and delay values are more meaningful. I think INP=3 and delay=8 is the usual low setting.

Also, I thought the voltage on a phone line was supposed to be 50, so perhaps they were talking about something else.

INP:      4.00      4.00
INPRein:   0.00      0.00
delay:      16      8

not so good then  :-[
Logged

burakkucat

  • Global Moderator
  • Senior Kitizen
  • *
  • Posts: 22575
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Interleaved in 2017
« Reply #8 on: December 10, 2017, 06:20:24 PM »

But if you leave it alone to "do its own thing" all should eventually be resolved.
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.

mbb

  • Member
  • **
  • Posts: 33
Re: Interleaved in 2017
« Reply #9 on: December 11, 2017, 04:08:11 PM »

INP:      3.00      0.00
INPRein:   0.00      0.00
delay:      8      0

INP and delay has been reduced back to 22 instead of 38 ping to bbc. Fingers crossed for G.INP sooner rather than later
Logged

mbb

  • Member
  • **
  • Posts: 33
Re: Interleaved in 2017
« Reply #10 on: January 11, 2018, 07:04:39 PM »

dslstats showing 34 days modem uptime and 31 days dsl uptime now with g.inp nowhere to be seen as of yet with interleaving still active. i have been keeping track a little of my errors and they seem quite low but around 4pm everyday the internet is completely unresponsive for 5 minutes or so but the modem stays in sync??. Also my connection speed hasn't moved i dont think since the 1st week of install. is it possible its banded? 35728      7010. is it worth doing 1 modem reboot as it hasn't been rebooted since my line fault was fixed. how is best to do it? leave it off for 5 mins or 20 mins? i have purchased a decent twisted pair 0.5m rj11 cable from tandy (yes they still exist:)) and need to a little re wiring but i am holding off so the modem can have some uptime. i read something about dlm doing things in 8 day cycles so in a couple of days i may turn the modem off do all the wiring etc

if people are interested or could provide some insight into my line mydslwebstats username is: markb

best regards. mark

Stats recorded 11 Jan 2018 18:56:30

DSLAM/MSAN type:           BDCM:0xa48c / v0xa48c
Modem/router firmware:     AnnexA version - A2pv6C038m.d24j
DSL mode:                  VDSL2 Profile 17a
Status:                    Showtime
Uptime:                    31 days 8 hours 36 min 15 sec
Resyncs:                   0 (since 01 Jan 2018 14:58:56)
         
            Downstream   Upstream
Line attenuation (dB):     23.7      0.0
Signal attenuation (dB):   Not monitored      
Connection speed (kbps):   35728      7010
SNR margin (dB):           5.9      6.5
Power (dBm):               12.3      -0.5
Interleave depth:          699      1
INP:                       3.00      0
G.INP:                     Not enabled      Not enabled
Vectoring status:          5 (VECT_UNCONFIGURED)      

RSCorr/RS (%):             1.8926      0.0722
RSUnCorr/RS (%):           0.1036      0.0000
ES/hour:                   2.31      0.47
Logged

jaydub

  • Reg Member
  • ***
  • Posts: 213
Re: Interleaved in 2017
« Reply #11 on: January 11, 2018, 08:32:01 PM »

Fairly certain you are not banded.  Just the impact of some significant interleaving.

I prefer to drop the connection session in the router GUI, before disconnecting and haven't overly worried about how long the router is down for.  I would have thought 5 mins was more than sufficient.
Logged

mbb

  • Member
  • **
  • Posts: 33
Re: Interleaved in 2017
« Reply #12 on: January 11, 2018, 08:36:47 PM »

I must have watched the router reboot 30 times when the engineers were doing ther testing so i did have really heavy interleaving applied for about 7 days after and i have since gone down to the standard 8ms. yes i will 'disconnect' the internet from the router 1st.
Logged
 

anything