Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[S.Stephenson]

Earlier I logged a fault for my line, it took a lot of effort and firmness to get sky support to accept it.

But the fault is logged as broken g.inp.  I am just one guy , and it probably wont do anything, but I call on all us non g.inp's to register faults with our isp's to make the numbers grow as much as possible.

If you've never had G.INP activated i'm pretty sure it isn't a fault, that's like me claiming Vectoring is broken because i'm not on one of the very few cabinets that have it activated.

It's just a matter of patience if you truly need faster speeds do what I've done and put your money where your mouth is. In my case I require >100mbps for my needs therefore I have a 2nd FTTC line on order due to be activated on Tuesday.

[ktz392837]

It should not take a genius to work out that I'm becoming sick of it and wonder why I bother. 

I certainly appreciate your work and I am sure the majority of other users do also.  It can just be infuriating at times on why BT do what they do.

Take ECI Ginp BT may have worked relentlessly for over 12m to get this to work as it is but unless they are a bit more open it just looks like they have cobbled something half baked together at the last minute and then still not got it right. 

[Chrysalis]

its just to add to the data.

From an ISP perspective they probably requested openreach to do the halt based on support calls logged, so I thought I would add one in the other direction.

Yes one single fault wont do jack, but I did it anyway.

--edit--

Just read your entire post.

Kitz there is no moaning at you, the issue is with how they managed to bodge up two rollouts.

My previous comment has been edited out as it came across in an offensive manner.

[NewtronStar]

But the fault is logged as broken g.inp.  I am just one guy , and it probably wont do anything, but I call on all us non g.inp's to register faults with our isp's to make the numbers grow as much as possible.

If I can't have it then I am going to make sure no one else can. Is that what your saying ?

[Chrysalis]

No.

I got no issue with others who still have it enabled, and they should keep it enabled.

Its more so to put pressure for a quicker fix, as I am concerned this will be left alone for several months with only a small amount of end users been affected.

Newt, I believe you was supportive of this predicament, have you done a U turn?  As you yourself was impacted by the hauwei delay last year.  but back then openreach had bad PR from it and it affected a lot more users.

I think its wrong to tell someone affected "tough luck its not part of your service spec, live with it".

[NewtronStar]

The change from the G.INP MK1 to MK2 took just under 3 months to be resolved before it was rolled out again and I was one of those people that had to wait for the fix, did I call my ISP or ask others to rally up with the same issue NO

[Chrysalis]

Why is the NO bolded?

[NewtronStar]

Why is the NO bolded?

To make sure you noticed it, let say Vectoring  comes are way next year and I have issues with it would you like me to call my ISP and complain and the result could cause others on that same  cabinet to lose Vectoring and it was working well for them the answer is no i'll wait until its fix for all.

[Chrysalis]

I took it as you was shouting NO at me, and quite rude.

I already said to you I dont expect and want others to have it disabled, yet you still think that.

The difference between now and last year, is there is last year there was a lot of fuss made about it and as such openreach were compelled to act, now its just a very small part of the userbase and not a single media site has picked up on a story, you cannot compare the two situations.  Also last year they had stated they identified the cause and was working on a fix, so you knew it was coming.

If you had issues with vectoring, yes you should call your isp, why? because they the only people you can call, you have no direct relationship with openreach.

[Craig]

I think G.INP has been enabled on my line. I am defiantly on an ECI cab.

Code: [Select]

> adsl info --vendor
ChipSet Vendor Id:      IFTN:0xb204
ChipSet VersionNumber:  0xb204
ChipSet SerialNumber:   5502075242

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 = 27192 Kbps, Downstream rate = 94915 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79999 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):        9.6             9.6
Attn(dB):        15.5            0.0
Pwr(dBm):        13.6            4.9

                        VDSL2 framing
                        Bearer 0
MSGc:           -6              150
B:              178             236
M:              1               1
T:              0               5
R:              6               16
S:              0.0712          0.3771
L:              20780           5410
D:              1               1
I:              185             255
N:              185             255
Q:              16              0
V:              2               0
RxQueue:                42              0
TxQueue:                14              0
G.INP Framing:          18              0
G.INP lookback:         14              0
RRC bits:               0               24
                        Bearer 1
MSGc:           186             -6
B:              0               0
M:              2               0
T:              2               0
R:              16              0
S:              5.3333          0.0000
L:              48              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               77146
OHFErr:         277             213
RS:             3202382816              2193489
RSCorr:         90816           3823
RSUnCorr:       0               0
                        Bearer 1
OHF:            41801027                0
OHFErr:         0               0
RS:             501611580               0
RSCorr:         134             0
RSUnCorr:       0               0

                        Retransmit Counters
rtx_tx:         28653           0
rtx_c:          34587           0
rtx_uc:         785             0

                        G.INP Counters
LEFTRS:         5               0
minEFTR:        79982           0
errFreeBits:    2762619456              0

                        Bearer 0
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    215463798               0
Data Cells:     915143465               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:             40              361
SES:            11              12
UAS:            45              45
AS:             671545

                        Bearer 0
INP:            46.00           0.00
INPRein:        0.00            0.00
delay:          0               0
PER:            0.00            6.15
OR:             0.01            202.87
AgR:            80111.28        20203.27

                        Bearer 1
INP:            4.00            0.00
INPRein:        4.00            0.00
delay:          3               0
PER:            16.06           0.01
OR:             95.62           0.01
AgR:            95.62   0.01

Bitswap:        152138/152138           0/0

Total time = 14 days 4 hours 28 min 59 sec
FEC:            152213          16945
CRC:            444             427
ES:             40              361
SES:            11              12
UAS:            45              45
LOS:            0               0
LOF:            0               0
LOM:            0               0
Latest 15 minutes time = 13 min 59 sec
FEC:            14              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:            26              2
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 = 4 hours 28 min 59 sec
FEC:            274             55
CRC:            0               5
ES:             0               5
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Previous 1 day time = 24 hours 0 sec
FEC:            1340            347
CRC:            0               24
ES:             0               23
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Since Link time = 7 days 18 hours 32 min 41 sec
FEC:            90816           3823
CRC:            277             213
ES:             19              168
SES:            8               5
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0

[burakkucat]

ChipSet Vendor Id:      IFTN:0xb204

Yes, an ECI equipped cabinet.

Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79999 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps

Yes, G.Inp has been enabled for your circuit. 

[les-70]

  A question or two before I try out some old devices on an ECI DSLAM.  What is the expected or known consequence of attaching a non g.inp device?  A sync failure with no DLM action or DLM action back to fast path or interleaved.  If there is a DLM action is a quick recovery likely when a g.inp device is put back?

 From what I can read I think just a simple resync failure with no DLM action is expected?  I am intending to try an HG622, an HG630 and a HG658 the later two are vector ready so I expect g.inp as well.  I am not sure about the HG622.

[dambuilder]

I seem to have both G.INP and FastPath (Interleave Depth = 1) enabled. Or am I reading this wrong?

Stats recorded 19 Apr 2016 09:28:27

DSLAM/MSAN type:           IFTN:0xb204 / v0xb204
Modem/router firmware:     AnnexA version - A2pv6C038m.d24j
DSL mode:                  VDSL2 Profile 17a
Status:                    Showtime
Uptime:                    4 days 23 hours 41 min 37 sec
Resyncs:                   0 (since 15 Apr 2016 08:47:47)
         
            Downstream   Upstream
Line attenuation (dB):     17.2      0.0
Signal attenuation (dB):   Not available on VDSL2      
Connection speed (kbps):   58844      16218
SNR margin (dB):           6.1      6.0
Power (dBm):               13.2      6.9
Interleave depth:          1      1
INP:                       50.00      0
G.INP:                     Enabled      Not enabled

RSCorr/RS (%):             0.0483      0.1782
RSUnCorr/RS (%):           0.0000      0.0000
ES/hour:                   0      2.89

[underzone]

http://www.ispreview.co.uk/index.php/2016/04/bt-briefly-start-stop-g-inp-roll-eci-fibre-broadband-cabinets.html

An Openreach Spokesperson told ISPreview.co.uk:

“Openreach constantly monitors its fibre network and this identified some lines which would perform better without retransmission.

We’ve returned these lines to a pre-retransmission state, so that customers continue to receive the optimum speed. All other lines on the platform remain enabled with retransmission.

We’re investigating options to apply retransmission for all customers, and we’re working closely with equipment vendors. Openreach has communicated this position to all fibre CPs and we continue to provide regular updates to them.”

[Bowdon]

Is G.INP needed when G.fast comes in or are they seperate technologies?

I'm unsure of the answer so thought I'd ask you guys.

Because if they are seperate technologies then if they prioritise ECI cabinets for G.fast then its not long to wait (I'm on an ECI cabinet).

If G.INP needs to be used for G.fast then I think its time BT/OR started to make some noise either at ECI or its time to bring in another cabinet maker. It seems ECI cabinets and modems/routers have been a big stumbling block for the past few years in anything that OR tries to do.