Topic: I have G.INP on ECI (Read 228482 times)

skyeci · « **Reply #285 on:** March 27, 2016, 12:48:37 PM »

Hi,

So wanted to update as requested. Following a drop in sync on both directions following g.inp on my billion 8800nl I had bt round who replaced the pair and isolated me in the cabinet away from other enabled lines just to see if it helped.

A couple of days ago I put an unlocked BT eci modem to see if it would help after seeing positive results.

Last night G.INP was re-applied with the unlocked eci attached- a whopping near on 10mb increase on the DS, US is the same. Latency is now 11ms instead of 21ms

The issue now is do I risk putting the billion back on to see if can perform the same and get my stats back or leave it all alone.

I have included stats from the billion post BT engineer and ECI modem post engineer and both with no G.INP applied. I have also included the ECI now with g.inp applied. The missing result is the billion with g.inp on the new pair.

Are results due to the modem or the new pair ?? Probably plugging in the billion again will be the only way to know for sure but do I risk it???

20:43pm - 23/03/16

Billion 8800nl following reset and new pair 24hours afterwards, no g.inp

adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 4
Last initialization procedure status: 0
Max: Upstream rate = 28191 Kbps, Downstream rate = 68453 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 57857 Kbps

Discovery Phase (Initial) Band Plan
US: (6,31) (882,1193) (1984,2770)
DS: (33,857) (1218,1959) (2795,4083)
Medley Phase (Final) Band Plan
US: (6,31) (882,1193) (1984,2770)
DS: (41,857) (1218,1959) (2795,4083)
VDSL Port Details Upstream Downstream
Attainable Net Data Rate: 28191 kbps 68453 kbps
Actual Aggregate Tx Power: 2.4 dBm 2.4 dBm
====================================================================================
VDSL Band Status U0 U1 U2 U3 U4
D1 D2 D3
Line Attenuation(dB): 1.1 14.4 24.3 N/A N/A 9.3 20.2 32.2
Signal Attenuation(dB): 1.0 14.4 24.3 N/A N/A 11.9 20.0 32.2
SNR Margin(dB): 11.1 9.6 10.2 N/A N/A 6.3 6.2 6.2
TX Power(dBm): -6.7 -30.8 1.8 N/A N/A 8.2 7.3 7.4

billion

adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 4
Last initialization procedure status: 0
Max: Upstream rate = 28087 Kbps, Downstream rate = 68461 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 57857 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.3 9.9
Attn(dB): 14.4 0.0
Pwr(dBm): 2.4 2.4

VDSL2 framing
Bearer 0
MSGc: 18 150
B: 51 236
M: 1 1
T: 64 5
R: 12 16
S: 0.0286 0.3771
L: 17904 5410
D: 1133 1
I: 64 255
N: 64 255

Counters
Bearer 0
OHF: 65963847 616935
OHFErr: 10 104
RS: 4001705061 1577288
RSCorr: 118917 927
RSUnCorr: 912 0

Bearer 0
HEC: 241 0
OCD: 0 0
LCD: 0 0
Total Cells: 600137824 0
Data Cells: 164942123 0
Drop Cells: 0
Bit Errors: 0 0

ES: 63 2073
SES: 56 0
UAS: 3610 3554
AS: 121221

Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 1.83 6.15
OR: 104.49 202.87
AgR: 57961.58 20203.27

Bitswap: 1564/1564 9/9

***ECI unlocked 20:42pm 23/03/16 - no g.inp***

Chipset:      Lantiq™ XWAY™ VRX268
Firmware Version:   5.7.4.3.0.6
API Version:      4.16.2.4
MEI Version:      1.4.8.4
Power Management Mode:   L0 - Synchronized
Line State:      UP [0x801: showtime_tc_sync]
Line Uptime:      34s
Resyncs:      1
DSLAM/MSAN VID:      IFTN
XTSE Capabilities:   0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x2
Annex:         B
Line Mode:      G.993.2 (VDSL2)
Profile:      17a
Trellis:      D: ON / U: ON
Bitswap:      D: ON / U: ON
G.INP:         D: Not Enabled / U: Not Enabled
Virtual Noise Support:   D: Not Supported / U: Not Supported
Attain Data Rate:   65.326 Mb/s / 29.202 Mb/s
Actual Data Rate:   56.458 Mb/s / 20.000 Mb/s
Impulse Noise Prot:   3.0 sym / 0.0 sym
Interleave Delay:   8.0 ms / 0.0 ms
NFEC:         85 / 255
RFEC:         16 / 16
LSYMB:         17469 / 5410
Interleave Depth:   823 / 1
Interleave Block:   85 / 255
LPATH:         0 / 0
Line Attenuation:   14.2dB / 14.0dB
Signal Attenuation:   14.2dB / 13.9dB
Noise Margin:      6.0dB / 12.2dB
Transmit power:      5.7dBm / 5.6dBm
FECS:         0 / 135499
ES:         0 / 11969
SES:         0 / 2
LOSS:         0 / 168
UAS:         299 / 299
HEC:         0 / 0
CRC_P:         0 / 0
CRCP_P:         0 / 0
15m Code Violations:   0 / 13874
15m FEC Errors:      0 / 135499
1d Code Violations:   0 / 13874
1d FEC Errors:      0 / 135499

24/03/16 - Open ECI modem - connected awiting g.inp to be re-applied
Chipset:      Lantiq™ XWAY™ VRX268
Firmware Version:   5.7.4.3.0.6
API Version:      4.16.2.4
MEI Version:      1.4.8.4
Power Management Mode:   L0 - Synchronized
Line State:      UP [0x801: showtime_tc_sync]
Line Uptime:      1m 32s
Resyncs:      1
DSLAM/MSAN VID:      IFTN
XTSE Capabilities:   0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x2
Annex:         B
Line Mode:      G.993.2 (VDSL2)
Profile:      17a
Trellis:      D: ON / U: ON
Bitswap:      D: ON / U: OFF
G.INP:         D: Not Enabled / U: Not Enabled
Virtual Noise Support:   D: Not Supported / U: Not Supported
Attain Data Rate:   65.355 Mb/s / 28.682 Mb/s
Actual Data Rate:   56.284 Mb/s / 20.000 Mb/s
Impulse Noise Prot:   3.0 sym / 0.0 sym
Interleave Delay:   8.0 ms / 0.0 ms
NFEC:         85 / 255
RFEC:         16 / 16
LSYMB:         17415 / 5410
Interleave Depth:   819 / 1
Interleave Block:   85 / 255
LPATH:         0 / 0
Line Attenuation:   14.2dB / 14.0dB
Signal Attenuation:   14.2dB / 14.1dB
Noise Margin:      6.1dB / 12.1dB
Transmit power:      5.8dBm / 5.7dBm
FECS:         109 / 136100
ES:         0 / 12023
SES:         0 / 2
LOSS:         0 / 180
UAS:         277 / 277
HEC:         0 / 0
CRC_P:         0 / 0
CRCP_P:         0 / 0
15m Code Violations:   0 / 13936
15m FEC Errors:      109 / 136100
1d Code Violations:   0 / 13936
1d FEC Errors:      109 / 136100

26/03/16 11.25am eci following re-sync as console not being responsive
root@OpenWrt:~# /etc/init.d/dsl_control status
Chipset: Lantiq™ XWAY™ VRX268
Firmware Version: 5.7.4.3.0.6
API Version: 4.16.2.4
MEI Version: 1.4.8.4
Power Management Mode: L0 - Synchronized
Line State: UP [0x801: showtime_tc_sync]
Line Uptime: 8s
Resyncs: 1
DSLAM/MSAN VID: IFTN
XTSE Capabilities: 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x2
Annex: B
Line Mode: G.993.2 (VDSL2)
Profile: 17a
Trellis: D: ON / U: ON
Bitswap: D: OFF / U: OFF
G.INP: D: Not Enabled / U: Not Enabled
Virtual Noise Support: D: Not Supported / U: Not Supported
Attain Data Rate: 65.016 Mb/s / 28.729 Mb/s
Actual Data Rate: 56.087 Mb/s / 20.000 Mb/s
Impulse Noise Prot: 3.0 sym / 0.0 sym
Interleave Delay: 8.0 ms / 0.0 ms
NFEC: 85 / 255
RFEC: 16 / 16
LSYMB: 17354 / 5410
Interleave Depth: 817 / 1
Interleave Block: 85 / 255
LPATH: 0 / 0
Line Attenuation: 14.3dB / 14.2dB
Signal Attenuation: 14.3dB / 14.1dB
Noise Margin: 6.1dB / 12.3dB
Transmit power: 6.0dBm / 5.9dBm
FECS: 0 / 136834
ES: 0 / 12077
SES: 0 / 2
LOSS: 0 / 186
UAS: 81 / 81
HEC: 0 / 0
CRC_P: 0 / 0
CRCP_P: 0 / 0
15m Code Violations: 0 / 13996
15m FEC Errors: 0 / 136834
1d Code Violations: 0 / 13996
1d FEC Errors: 0 / 136834

27/03/16 ECI - G.INP BACK ON

***09:47 27/03/2016 - ECI open modem after G.INP
***11 - 12 ms ping time*** 9mb approx improvement
Line Mode: G.993.2 (VDSL2) — Annex B — Profile 17a
Status & Uptime: UP — 10h 56m 23s — Resyncs: 3
Line State: showtime_tc_sync [0x801]
Power Mode: L0 - Synchronized

Downstream — Upstream

Attainable Line Speed: 66.130 Mb/s — 28.471 Mb/s
Actual Line Speed: 66.384 Mb/s — 20.000 Mb/s
Trellis: D: ON — U: ON
Bitswap: D: ON — U: ON
G.INP: D: Enabled — U: Not Enabled
Virtual Noise Support: D: Not Supported — U: Not Supported
Interleave Depth: 1 — 1
Interleave Block: 32 — 255
Interleave Delay: 0.21 ms — 0.0 ms
INP: 44.0 — 0.0
NFEC: 32 — 255
RFEC: 16 — 16
LSYMB: 16 — 5410
LPATH: 0 — 0
Line Attenuation: 14.3 dB / 14.1 dB
Noise Margin/SNR: 5.1 dB / 12.2 dB
Transmit Power: 6.0 dBm / 5.8 dBm

Errors Since Line Up
FECS: 0 — 86
ES: 2 — 12090
SES: 0 — 2
LOSS: 3 — 191
UAS: 163 — 163
HEC: 0 — 0
CRC_P: 1 — 0
CRCP_P: 0 — 0

Errors in 15 Minutes
Code Violations: 0 — 0
FECS: 0 — 2

Errors in 1 Day
Code Violations: 2 — 4
FECS: 0 — 56

Black Sheep · « **Reply #286 on:** March 27, 2016, 12:59:50 PM »

I don't know the answer to your question, I'm afraid ?? It all depends on whether there was a fault with your original pair I suppose. I have to say, I'm certainly not in the habit of changing pairs for changes sake, so do wonder if your engineer did indeed find some kind of service affecting fault ??

Also, I don't know how he can "isolate" you away from other workers in the actual Cab ?? The only way he could achieve anything near to this would be to move you to a different pair within the D-side cable (from Cab to DP ..... ie: telegraph pole).
He would check the pairs for 'noise' (disturbers) and go for the best dB reading ..... as near to -60dB as possible.

Either way, you have got a great result. Great news.

skyeci · « **Reply #287 on:** March 27, 2016, 01:02:51 PM »

Quote from: Black Sheep on March 27, 2016, 12:59:50 PM

I don't know the answer to your question, I'm afraid ?? It all depends on whether there was a fault with your original pair I suppose. I have to say, I'm certainly not in the habit of changing pairs for changes sake, so do wonder if your engineer did indeed find some kind of service affecting fault ??

Also, I don't know how he can "isolate" you away from other workers in the actual Cab ?? The only way he could achieve anything near to this would be to move you to a different pair within the D-side cable (from Cab to DP ..... ie: telegraph pole).
He would check the pairs for 'noise' (disturbers) and go for the best dB reading ..... as near to -60dB as possible.

Either way, you have got a great result. Great news.

I think he just moved me in the cab away from other enabled lines. To be fair he had been before and was happy to get involved once I showed him the results..

Do I risk the billion to get the stats to prove if my cab prefers eci modem lol..

daveesh1 · « **Reply #288 on:** March 27, 2016, 03:05:47 PM »

You can always try it if it makes it worse you can always go back.

Bald_Eagle1 · « **Reply #289 on:** March 27, 2016, 03:15:45 PM »

& if you do try the Billion & then revert to the ECI again, you could run the script that I've been developing with you for use with ECI modems to see what the stats are like with a fresh ECI reboot

.

If you do try the Billion & then go back to the ECI, it would be useful to also grab the Billion's stats just before disconnecting it again.

skyeci · « **Reply #290 on:** March 27, 2016, 03:17:22 PM »

I guess it might help the community 😊
Lol. Next question when is best. I leave about 30 mins from power off till power on. Is this too long or too little?
Cheers

Bald_Eagle1 · « **Reply #291 on:** March 27, 2016, 03:24:49 PM »

As DLM apparently looks at 15 minute stats windows, a 30 minute 'rest' should suffice as you will only be carrying out 2 resyncs fairly close together as a maximum.

daveesh1 · « **Reply #292 on:** March 27, 2016, 04:36:40 PM »

Then it might be possible to compare you billion stats to mine as I have lost a little bit of speed since G.inp has been enabled on my cab.

Chrysalis · « **Reply #293 on:** March 27, 2016, 04:37:25 PM »

skyeci before you was g.inp you was interleaved, so a sync speed increase is no surprise, it will very likely also see an increase on the 8800nl, but by the same amount? you wont know until you try it.

Its very important to check for and specify here if its apple vs apple comparison, apple vs apple been fast path vs g.inp.

skyeci · « **Reply #294 on:** March 27, 2016, 04:45:02 PM »

Quote from: daveesh1 on March 27, 2016, 04:36:40 PM

Then it might be possible to compare you billion stats to mine as I have lost a little bit of speed since G.inp has been enabled on my cab.

I lost 3mb on upload so it was a lot really. Just hoping the new pair bt did may of helped and help the billion. Just pondering doing it tonight.

skyeci · « **Reply #295 on:** March 27, 2016, 04:47:03 PM »

Quote from: Chrysalis on March 27, 2016, 04:37:25 PM

skyeci before you was g.inp you was interleaved, so a sync speed increase is no surprise, it will very likely also see an increase on the 8800nl, but by the same amount? you wont know until you try it.

Its very important to check for and specify here if its apple vs apple comparison, apple vs apple been fast path vs g.inp.

But when the billion first got g.inp I lost sync speed both ways hence getting bt out.

Black Sheep · « **Reply #296 on:** March 27, 2016, 05:01:37 PM »

Quote from: skyeci on March 27, 2016, 01:02:51 PM

Quote from: Black Sheep on March 27, 2016, 12:59:50 PM
I don't know the answer to your question, I'm afraid ?? It all depends on whether there was a fault with your original pair I suppose. I have to say, I'm certainly not in the habit of changing pairs for changes sake, so do wonder if your engineer did indeed find some kind of service affecting fault ??

Also, I don't know how he can "isolate" you away from other workers in the actual Cab ?? The only way he could achieve anything near to this would be to move you to a different pair within the D-side cable (from Cab to DP ..... ie: telegraph pole).
He would check the pairs for 'noise' (disturbers) and go for the best dB reading ..... as near to -60dB as possible.

Either way, you have got a great result. Great news.

I think he just moved me in the cab away from other enabled lines. To be fair he had been before and was happy to get involved once I showed him the results..

Do I risk the billion to get the stats to prove if my cab prefers eci modem lol..

He can't do that. We are at the behest of the DCoE (Diagnostic Centre of Excellence) regarding DSLAM port allocation. If they deem a 'Lift & Shift' (New port) is necessary, they will allocate the next available one their systems tell them. They would otherwise have to mark up all available ports as faulty on their systems for it to auto-allocate another port well away from the masses ................ believe me, they will never, ever do this.

skyeci · « **Reply #297 on:** March 27, 2016, 05:03:22 PM »

Ah well I believe what you say but I am only quoting what he told me..

Black Sheep · « **Reply #298 on:** March 27, 2016, 05:11:50 PM »

No worries. I feel duty-bound to put the relevant info out there, otherwise folk might think they can just ask the engineers to move them onto a different DSLAM card, and I wouldn't want them to be disappointed now.

g3uiss · « **Reply #299 on:** March 27, 2016, 05:46:48 PM »

Early this morning went onto G.Inp. Slight reduction in latency 10% increase in sync DS no change U/S as to be expected. ES DS gone to zero after daily average of circa 650.

All this bonus and still using SP06 firmware.

Long wait but initially seems worth it

News:

Author Topic: I have G.INP on ECI (Read 228482 times)

skyeci

Re: I have G.INP on ECI - update on skyeci line

Black Sheep

Re: I have G.INP on ECI

skyeci

Re: I have G.INP on ECI

daveesh1

Re: I have G.INP on ECI

Bald_Eagle1

Re: I have G.INP on ECI

skyeci

Re: I have G.INP on ECI

Bald_Eagle1

Re: I have G.INP on ECI

daveesh1

Re: I have G.INP on ECI

Chrysalis

Re: I have G.INP on ECI

skyeci

Re: I have G.INP on ECI

skyeci

Re: I have G.INP on ECI

Black Sheep

Re: I have G.INP on ECI

skyeci

Re: I have G.INP on ECI

Black Sheep

Re: I have G.INP on ECI

g3uiss

Re: I have G.INP on ECI