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 4 ... 6

Author Topic: G.INP Mk2 - Line stats.  (Read 21770 times)

Dray

  • Kitizen
  • ****
  • Posts: 2361
Re: G.INP Mk2 - Line stats.
« Reply #15 on: May 31, 2015, 07:36:28 PM »

How do you know that G.INP on ECI cabs is any good at all?

If it's as poor as claimed, there may be further compromises needed to be added to Huawei cabs.
Logged

underzone

  • Reg Member
  • ***
  • Posts: 442
Re: G.INP Mk2 - Line stats.
« Reply #16 on: May 31, 2015, 08:13:58 PM »

It is a shame the DSLAM's can't figure out the maximum that each connected modem/router can use, and just let them use it!
Logged

NewtronStar

  • Kitizen
  • ****
  • Posts: 4898
Re: G.INP Mk2 - Line stats.
« Reply #17 on: May 31, 2015, 08:36:08 PM »

It is a shame the DSLAM's can't figure out the maximum that each connected modem/router can use, and just let them use it!

Yes it is underzone it's kind of like having a Quad core processor then find the OS is only able to use 2 out of 4 cores.
Logged

tommy45

  • Reg Member
  • ***
  • Posts: 627
Re: G.INP Mk2 - Line stats.
« Reply #18 on: May 31, 2015, 09:33:43 PM »

Sorry i forgot to ask Tommy45 which FTTC modem they are using at the moment.

The HG Huawei HG612 3B modem , in use since G.inp was first rolled out back in March, and has an uptime of  iirc 54days  not that that means jack to  these fools,
« Last Edit: May 31, 2015, 09:39:05 PM by tommy45 »
Logged

tommy45

  • Reg Member
  • ***
  • Posts: 627
Re: G.INP Mk2 - Line stats.
« Reply #19 on: June 01, 2015, 08:54:54 PM »

Well i just noticed that my SNR has suddenly plummeted to below 6 db and lotts of FECS BT you fix has broken my connection you muppets!!!""!!!!!!!!
Logged

KIAB

  • Reg Member
  • ***
  • Posts: 201
Re: G.INP Mk2 - Line stats.
« Reply #20 on: June 02, 2015, 08:03:46 AM »

I presume that I have just had the update applied to my Huawei cabinet here in Bath, lost over 10Mb, might recovered  a bit, interleave has gone from 8 down to 4.

Code: [Select]
Stats recorded 02 Jun 2015 07:59:18

DSLAM/MSAN type:           BDCM:0xa44f / v0xa44f
Modem/router firmware:     AnnexA version - A2pv6C038m.d24j
DSL mode:                  VDSL2 Profile 17a
Status:                    Showtime
Uptime:                    6 hours 52 min 59 sec
Resyncs:                   0 (since 02 Jun 2015 07:57:45)
         
            Downstream   Upstream
Line attenuation (dB):     20.1      0.0
Signal attenuation (dB):   Not available on VDSL2     
Connection speed (kbps):   31370      4999
SNR margin (dB):           12.4      9.9
Power (dBm):               13.5      5.3
Interleave depth:          4      4
INP:                       51.00      55.00
G.INP:                     Enabled     

RSCorr/RS (%):             0.0966      62.5924
RSUnCorr/RS (%):           0.0000      0.0000
ES/hour:                   234      130

[Edit by admin: I've put code tags round your stats to improve the formatting]

Thanks, still half asleep. :)
« Last Edit: June 02, 2015, 08:35:09 AM by KIAB »
Logged

kitz

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 33883
  • Trinity: Most guys do.
    • http://www.kitz.co.uk
Re: G.INP Mk2 - Line stats.
« Reply #21 on: June 02, 2015, 09:18:01 AM »

I presume that I have just had the update applied to my Huawei cabinet here in Bath, lost over 10Mb, might recovered  a bit, interleave has gone from 8 down to 4.

Ive just tried to compare your before and after stats, have you only just started using MDWS?
Logged
Please do not PM me with queries for broadband help as I may not be able to respond.
-----
How to get your router line stats :: ADSL Exchange Checker

kitz

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 33883
  • Trinity: Most guys do.
    • http://www.kitz.co.uk
Re: G.INP Mk2 - Line stats.
« Reply #22 on: June 02, 2015, 10:28:43 AM »

But why does it reduce the upstream attainable  which in some cases will result in loss of some actual sync speed on the US ? it would seem to do this by ramping up the US signal and line attenuation levels somehow, though this doesn't impact the US SNR levels, IMO they have botched it again as the US attainable should increase not decrease if it is fast path

Because as mentioned previously the fix appears to be turning off interleaving, but applying Error correction?   - See update and further explanation
We really must now differentiate between interleaving and error correction.  Interleaving causes delay.  Error correction causes overheads and reduced sync speed.  The two are totally independent of each other and we can no longer assume that because Interleaving is switched off that there isnt any error correction. 
Logged
Please do not PM me with queries for broadband help as I may not be able to respond.
-----
How to get your router line stats :: ADSL Exchange Checker

kitz

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 33883
  • Trinity: Most guys do.
    • http://www.kitz.co.uk
Re: G.INP Mk2 - Line stats.
« Reply #23 on: June 02, 2015, 11:18:30 AM »

Well going by my stats I just had the so called G.inp rollout fix, G.inp was switched off on my upstream for some reason, my stats show a slight gain in DS attainable, SNR is no higher than it has been whilst fully g.inped US SNR  back to the higher level but surprisingly the us attainable is slightly lower ???? it should have increased!!! I guess this is going to pee some off as they may lose full us sync speed  the inp value increased on the ds by 1 to 48 and us power increased a little as did the signal & line attenuation levels,why?

Sorry I missed a couple of these what may be important posts in the midst of some others which Ive now split off. It is indeed beginning to look like the 'fix' may be a one solution fits all scenario. :(

Previously g.inp worked or if a non g.inp modem was identified it got stupid latency and an extremely high level of Error Correction which caused massive overheads. Now theyve tweaked something on the upstream that appears to have removed upstream G.INP for all, removed any interleaving but applied Error Correction. I'd already suspected a couple of weeks ago that this would perhaps be the case.

I'd seen on the likes of the BTcommunity forums that people were cheering because they had their latency back and the one thing that Ive been harping on about for a few weeks that they didnt appear to have received the return of any lost sync speed  :-\
I bet Openreach are amused that the likes of Homehub users are praising their fix which is a bodge,  but just wait until it hits the mainstream users who have more than half a clue if it does affect all.  :no:

I was really hoping that it wasn't going to be a one solution fits all, but we shall see if things do stabilise after a few days and wait to see if things do return to normal.   We need to see a bit more evidence yet before jumping to conclusions.

Tommy can I see your full stats please. [connection xdsl --stats] I want to look at things like your 'R' value - ie these for both bearers.  The easiest way to get them may be from DSLstats > Telnet data > Connection stats.

Code: [Select]
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    0
Last initialization procedure status:   0
Max:    Upstream rate = 31468 Kbps, Downstream rate = 84772 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79987 Kbps

Link Power State:       L0
Mode:                   VDSL2 Annex B
VDSL2 Profile:          Profile 17a
TPS-TC:                 PTM Mode
Trellis:                U:ON /D:ON
Line Status:            No Defect
Training Status:        Showtime
                Down            Up
SNR (dB):        7.0             13.7
Attn(dB):        0.0             0.0
Pwr(dBm):        14.3            6.3
                        Bearer 0
MSGc:           18              150
B:              239             236
M:              1               1
T:              23              5
R:              0               16
S:              0.0955          0.3771
L:              20104           5410
D:              1               1
I:              240             255
N:              240             255

Same with KIAB please.


Logged
Please do not PM me with queries for broadband help as I may not be able to respond.
-----
How to get your router line stats :: ADSL Exchange Checker

KIAB

  • Reg Member
  • ***
  • Posts: 201
Re: G.INP Mk2 - Line stats.
« Reply #24 on: June 02, 2015, 12:36:25 PM »

I presume that I have just had the update applied to my Huawei cabinet here in Bath, lost over 10Mb, might recovered  a bit, interleave has gone from 8 down to 4.

Ive just tried to compare your before and after stats, have you only just started using MDWS?

Sorry Kitz, a over sight by me, all sorted now, just registered. :-[

And here is the info you need

Code: [Select]
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 7972 Kbps, Downstream rate = 43984 Kbps
Bearer: 0, Upstream rate = 5000 Kbps, Downstream rate = 39999 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): 7.2 8.4
Attn(dB): 19.9 0.0
Pwr(dBm): 13.5 4.6
VDSL2 framing
Bearer 0
MSGc: -6 -6
B: 81 73
M: 1 1
T: 0 0
R: 8 14
S: 0.0647 0.4662
L: 11120 1510
D: 8 8
I: 90 88
N: 90 88
Q: 8 8
V: 4 5
RxQueue: 136 12
TxQueue: 34 6
G.INP Framing: 18 18
G.INP lookback: 31 6
RRC bits: 24 24
Bearer 1
MSGc: 90 58
B: 0 0
M: 2 2
T: 2 2
R: 16 16
S: 10.6667 16.0000
L: 24 16
D: 1 1
I: 32 32
N: 32 32
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 0
OHFErr: 610 110
RS: 565651760 1559523
RSCorr: 297678 101228
RSUnCorr: 0 0
Bearer 1
OHF: 572326 574578
OHFErr: 5 363
RS: 3433588 2298313
RSCorr: 287 1170
RSUnCorr: 8 0

Retransmit Counters
rtx_tx: 12466815 1355735
rtx_c: 9147766 438749
rtx_uc: 8612455 278988

G.INP Counters
LEFTRS: 5807 2831
minEFTR: 40005 4997
errFreeBits: 52963075 278880082

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 706285387 0
Data Cells: 2094391 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: 2848 1629
SES: 1667 680
UAS: 918 648
AS: 9193

Bearer 0
INP: 52.00 41.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 0.00
OR: 0.01 0.01
AgR: 40368.53 5059.32

Bearer 1
INP: 2.50 4.00
INPRein: 2.50 4.00
delay: 0 0
PER: 16.06 16.06
OR: 47.81 31.87
AgR: 47.81 31.87

Bitswap: 1239/1239 209/209

Total time = 1 days 3 hours 6 min 54 sec
FEC: 155183142 4316779
CRC: 81647 6434
ES: 2848 1629
SES: 1667 680
UAS: 918 648
LOS: 12 64
LOF: 102 64
LOM: 40 0
Latest 15 minutes time = 6 min 54 sec
FEC: 126734 32029
CRC: 170 13
ES: 5 8
SES: 3 5
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 41 29
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 = 3 hours 6 min 54 sec
FEC: 297749 101843
CRC: 1201 110
ES: 42 44
SES: 23 24
UAS: 34 23
LOS: 1 0
LOF: 10 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 154484369 3976817
CRC: 79914 6156
ES: 2731 1535
SES: 1635 646
UAS: 861 602
LOS: 11 61
LOF: 92 61
LOM: 40 0
Since Link time = 2 hours 33 min 13 sec
FEC: 297678 101228
CRC: 610 110
ES: 31 44
SES: 12 24
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#


« Last Edit: June 02, 2015, 12:40:40 PM by KIAB »
Logged

tommy45

  • Reg Member
  • ***
  • Posts: 627
Re: G.INP Mk2 - Line stats.
« Reply #25 on: June 02, 2015, 01:06:41 PM »

Both before the botch and after it for easy comparison
Logged

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7390
  • VM Gig1 - AAISP L2TP
Re: G.INP Mk2 - Line stats.
« Reply #26 on: June 02, 2015, 02:10:10 PM »

But why does it reduce the upstream attainable  which in some cases will result in loss of some actual sync speed on the US ? it would seem to do this by ramping up the US signal and line attenuation levels somehow, though this doesn't impact the US SNR levels, IMO they have botched it again as the US attainable should increase not decrease if it is fast path

Because as mentioned previously the fix appears to be turning off interleaving, but applying Error correction?   - See update and further explanation
We really must now differentiate between interleaving and error correction.  Interleaving causes delay.  Error correction causes overheads and reduced sync speed.  The two are totally independent of each other and we can no longer assume that because Interleaving is switched off that there isnt any error correction. 

kitz did you miss my post? you seem to have forgotten error correction has always been enabled on US FTTC.

We both have FEC stats on our fast path connections.

Or is it you mean the new error correction is higher than the old default?

Here is the R value on my fast path connection.

R:              0               16
« Last Edit: June 02, 2015, 02:14:01 PM by Chrysalis »
Logged

tommy45

  • Reg Member
  • ***
  • Posts: 627
Re: G.INP Mk2 - Line stats.
« Reply #27 on: June 02, 2015, 02:30:10 PM »

But why does it reduce the upstream attainable  which in some cases will result in loss of some actual sync speed on the US ? it would seem to do this by ramping up the US signal and line attenuation levels somehow, though this doesn't impact the US SNR levels, IMO they have botched it again as the US attainable should increase not decrease if it is fast path

Because as mentioned previously the fix appears to be turning off interleaving, but applying Error correction?   - See update and further explanation
We really must now differentiate between interleaving and error correction.  Interleaving causes delay.  Error correction causes overheads and reduced sync speed.  The two are totally independent of each other and we can no longer assume that because Interleaving is switched off that there isnt any error correction. 

kitz did you miss my post? you seem to have forgotten error correction has always been enabled on US FTTC.

We both have FEC stats on our fast path connections.

Or is it you mean the new error correction is higher than the old default?

Here is the R value on my fast path connection.

R:              0               16
attached are my stats from when i was fast path again the R value on the upstream is 16
« Last Edit: June 02, 2015, 02:34:06 PM by tommy45 »
Logged

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7390
  • VM Gig1 - AAISP L2TP
Re: G.INP Mk2 - Line stats.
« Reply #28 on: June 02, 2015, 02:33:07 PM »

yeah so imo tommy, your US is exactly back how it was before on fast path.  With D set to 1 and R set to 16.

So openreach did what I told them to do a month ago.  Leave US on fast path config.
Logged

tommy45

  • Reg Member
  • ***
  • Posts: 627
Re: G.INP Mk2 - Line stats.
« Reply #29 on: June 02, 2015, 02:39:20 PM »

yeah so imo tommy, your US is exactly back how it was before on fast path.  With D set to 1 and R set to 16.

So openreach did what I told them to do a month ago.  Leave US on fast path config.
If they had done this correctly then, I shouldn't be having issues, and shouldn't have loss some attainable, Something isn't right with this botched profile,They should just  offer 2 profiles fully g.inp or fully fast path and have done with it, so then those that have service affecting error rates  can buy a modem that is G.inp/ vectoring compatible

I hate to think what mcrea and co will "fix" next
« Last Edit: June 02, 2015, 02:45:36 PM by tommy45 »
Logged
Pages: 1 [2] 3 4 ... 6