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:

Author Topic: New to FTTC...G.INP question  (Read 1171 times)

Ipswich

  • Just arrived
  • *
  • Posts: 4
New to FTTC...G.INP question
« on: June 30, 2020, 12:35:47 PM »

BT Fibre2 after years on Virgin. Unlocked HG612 modem (SP08 firmware) and Asus RT-AC86U. DSLstats below and have been activated on 12 June. Have both ECI and Huawei cabinets down the road judging by the cabinet photos on Kitz. The BDCM entry below implies Huawei cabinet and that I should have G.INP, however it hasn't been enabled. How long does it usually take to enable? Do I need to do anything?

Thanks.

Stats recorded 30 Jun 2020 12:23:18

DSLAM type / SW version:   BDCM:0xa49a (164.154) / v0xa49a
Modem/router firmware:     AnnexA version - A2pv6C038m.d24j
DSL mode:                  VDSL2 Profile 17a
Status:                    Showtime
Uptime:                     22 hours 13 min 48 sec
Resyncs:                   0 (since 30 Jun 2020 07:59:16)
         
            Downstream   Upstream
Line attenuation (dB):     14.9      0.0
Signal attenuation (dB):   Not monitored      
Connection speed (kbps):   69361      19999
SNR margin (dB):           6.2      15.4
Power (dBm):               13.9      6.5
Interleave depth:          1357      1
INP:                       3.00      0
G.INP:                     Not enabled      Not enabled
Vectoring status:          5 (VECT_UNCONFIGURED)      

RSCorr/RS (%):             0.0124      0.0019
RSUnCorr/RS (%):           0.0000      0.0000
ES/hour:                   0      0

Logged

tiffy

  • Kitizen
  • ****
  • Posts: 1326
Re: New to FTTC...G.INP question
« Reply #1 on: June 30, 2020, 01:19:35 PM »

Hi, welcome to the forum.

You do indeed appear to be on a Huawei DSLAM.
You line length is relatively short judging by the DS attenuation figure of 14.9 dB, should eventually achieve close to max. DS synch rate depending on the amount of crosstalk that is likely to effect your particular line.

By present day standards, DLM should have applied DS G.Inp by now but it can sometimes take much longer.
When I migrated from ADSL to VDSL 2 years ago I waited close to 9 weeks before DS G.Inp was applied, some forum patrons at that time waited even longer, however, by present day standards DLM should react within a few days of connection or after a DLM reset has been applied.

With the minimum stat's you have supplied it's not possible to tell how your line is performing in any detail, even so DS G.Inp should be applied by default regardless of performance.

From you router uptime hours looks like you have had or instigated a recent re-synch, at this stage I would avoid any manual re-connections if possible and just wait to see what happens with DLM, as your line is currently close to 70 Mbps DS and 20 Mbps US synch. speeds should be more than usable unless your needs are very specialised.
Logged
Vodafone FTTP 200/28, VF THG3000 Hub

Ipswich

  • Just arrived
  • *
  • Posts: 4
Re: New to FTTC...G.INP question
« Reply #2 on: June 30, 2020, 01:33:10 PM »

Many thanks @tiffy

Maybe the issue is I had an ECI modem from the 12 June until replacing it yesterday with the HG612. Will give it some time.

Other stats below if they can tell you (and by proxy me) anything useful...



xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason:   0
Last initialization procedure status:   0
Max:   Upstream rate = 28571 Kbps, Downstream rate = 79888 Kbps
Bearer:   0, Upstream rate = 19999 Kbps, Downstream rate = 69361 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       15.4
Attn(dB):    14.9       0.0
Pwr(dBm):    13.9       6.5
         VDSL2 framing
         Bearer 0
MSGc:      18      26
B:      51      237
M:      1      1
T:      64      42
R:      12      16
S:      0.0239      0.3781
L:      21464      5374
D:      1357      1
I:      64      127
N:      64      254
         Counters
         Bearer 0
OHF:      54899054      63247
OHFErr:      5      0
RS:      1169090573      943960
RSCorr:      60687      8
RSUnCorr:   58      0

         Bearer 0
HEC:      6      0
OCD:      1      0
LCD:      1      0
Total Cells:   2632241703      0
Data Cells:   1063695873      0
Drop Cells:   0
Bit Errors:   0      0

ES:      1      0
SES:      0      0
UAS:      28      28
AS:      84138

         Bearer 0
INP:      3.00      0.00
INPRein:   0.00      0.00
delay:      8      0
PER:      1.53      3.98
OR:      125.27      64.22
AgR:      69486.56   20063.54

Bitswap:   52279/52279      14/14

Total time = 23 hours 22 min 46 sec
FEC:      60687      8
CRC:      5      0
ES:      1      0
SES:      0      0
UAS:      28      28
LOS:      0      0
LOF:      0      0
LOM:      0      0
Latest 15 minutes time = 7 min 46 sec
FEC:      17      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:      169      0
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 = 23 hours 22 min 46 sec
FEC:      60687      8
CRC:      5      0
ES:      1      0
SES:      0      0
UAS:      28      28
LOS:      0      0
LOF:      0      0
LOM:      0      0
Previous 1 day time = 0 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
Since Link time = 23 hours 22 min 17 sec
FEC:      60687      8
CRC:      5      0
ES:      1      0
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
#
Logged

tiffy

  • Kitizen
  • ****
  • Posts: 1326
Re: New to FTTC...G.INP question
« Reply #3 on: June 30, 2020, 02:46:57 PM »

Quote
Maybe the issue is I had an ECI modem from the 12 June until replacing it yesterday with the HG612. Will give it some time.

Never had any experience with original BT issued ECI modems but I think they supported DS G.Inp, I'am sure some of the better informed patrons will correct me on this if I am wrong.
Have used a Huawei HG612 modem in the past, certainly a better bet for obtaining your line stat's, can even use DSLStats utility if you wish, lots of good information available on setting that up on the forum.

From the extended stat's you have provided it looks like you have a good low noise line, the ES's, SES's & CRC are currently very low or non existant.
When DS G.Inp finally comes along you will be able to determine if the profile applied is high or low, look at the Bearer 0 INPRein parameter, 0 = Re-Tx low profile, 1 = Re-Tx high profile.
Low is best meaning that your line DS BRAS IP profile should be approx. 97% of your synch. speed as apposed to approx. 92% with high profile, ie., higher data speed, should default to low profile but doesn't always.

Again, some of the better informed forum patrons will be able to offer more detailed information on the line stat's you have provided.
In the mean time I would sit tight and give DLM a chance to sort itself out.
Logged
Vodafone FTTP 200/28, VF THG3000 Hub

Ipswich

  • Just arrived
  • *
  • Posts: 4
Re: New to FTTC...G.INP question
« Reply #4 on: July 22, 2020, 10:52:38 PM »

OK, what I have noticed with the unlocked Huawei HG612 modem, BQM and DSLstats from 29 June is that I've had two broadband interruptions as shown in the attached BQM image. I thought it was a fault, rebooted both the modem and the router without any change, only to find out that when the service was finally restored, my IP didn't change. This got me thinking as I would always get a different IP when rebooting. What I finally concluded (could be wrong) is that the cabinet/exchange didn't notice me rebooting because it was busy doing something.

It wasn't G.INP as that is still not enabled, but suspect it was DLM because my interleave depth to start off with was 1357, then 1355 after the first service disruption like the one in the attached BQM graph, and is now 1351 after the second disruption. My line attenuation also changed from 14.9 to 14.8, SNR still in the range of 6.1 - 6.4. Errors are also very low and never over 10 per day. Won't post a bunch of stats as haven't noticed any other differences.

Is this the DLM doing its thing i.e still looking for the sweet spot or something completely different?

Apologies for the stupid questions as still getting my head around the whole DLM thing...

[Moderator edited to crop the attached image, thus removing the excess of white space.]
« Last Edit: July 23, 2020, 12:00:52 AM by burakkucat »
Logged

Alex Atkin UK

  • Addicted Kitizen
  • *****
  • Posts: 5272
    • Thinkbroadband Quality Monitors
Re: New to FTTC...G.INP question
« Reply #5 on: July 23, 2020, 03:45:21 AM »

If you IP changes or not is entirely down to your ISP, nothing to do with the DSL side of things.
Logged
Broadband: Zen Full Fibre 900 + Three 5G Routers: pfSense (Intel N100) + Huawei CPE Pro 2 H122-373 WiFi: Zyxel NWA210AX
Switches: Netgear MS510TXUP, Netgear MS510TXPP, Netgear GS110EMX My Broadband History & Ping Monitors

j0hn

  • Kitizen
  • ****
  • Posts: 4098
Re: New to FTTC...G.INP question
« Reply #6 on: July 23, 2020, 02:53:27 PM »

The Interleaving depth changes as sync changes.
If you resynced at the exact same rate then the Interleaving depth wouldn't have changed.

If a resync is quick enough then the PPP session won't time out and the IP won't change, simple as that.
That's ISP dependant though and unrelated to anything DSL.

[Moderator edited to insert the missing word, coloured green, above.]
« Last Edit: July 23, 2020, 08:29:46 PM by j0hn »
Logged
Talktalk FTTP 550/75 - Speedtest - BQM

Ipswich

  • Just arrived
  • *
  • Posts: 4
Re: New to FTTC...G.INP question
« Reply #7 on: July 23, 2020, 08:07:50 PM »

Many thanks both.
Logged