When might Eircom to enable vectoring on their eFibre/VDSL service?

Nonoperational

Praetorian wrote: »

So I got an update from a very nice fella from Vodafone and my cabinet isn't actually vectored. I did get a bump in snr from 9-13 and I did get the ping improvements. Could be q4 before I'm vectored then hopefully I can get 90-100m/bit!

Q4 as in next October? Jesus what's the delay I wonder?

KIERAN1

It may change over time, but Eircom is hinting G. Fast potentially could be the next upgrade?

We continue to work closely with our Global vendors, such as Huawei, to explore further hugely exciting technological developments in this area such as G.Fast, which offers the potential of future step changes in both upload and download
broadband speeds by driving fibre further out into
our network.”


The ITU has begun the process of approving G.fast, a new standard that will allow for access speeds of 1,000 megabits per second (1000Mbps, 1Gbps) over copper telephone lines. G.fast (full name ITU-T G.9701) is expected to be a cheaper and easier-to-deploy alternative than FTTH and FTTC (fiber to the home and cabinet). G.fast is the technology that will finally bring super-fast broadband speeds to the masses who are stuck with copper wires for the dreaded last mile.

There are generally three ways of getting internet access to your house: Telephone lines (twisted-pair copper wires), coaxial cable (shared with the cable TV infrastructure), and fiber (either to your house or fairly close). Because of the massive installed base of telephones and cable TV, the first two options are by far the cheapest. Fiber, because it generally has to be installed specifically for internet access, is much more expensive to deploy. The problem with telephone wire and cable internet access is that you can only squeeze so much data down a thin, low-grade piece of copper. This is where DSL, VDSL, and now G.fast enter the equation.

http://www.extremetech.com/computing/172990-1000mbps-over-copper-telephone-lines-itu-begins-work-on-g-fast-successor-to-dsl

Praetorian

Nonoperational wrote: »

Q4 as in next October? Jesus what's the delay I wonder?

Again from a man in the know:

Some cabs require a type of vectoring known as "system" level vectoring as it needs to vector over multiple DSLAMS. i.e. over 192 ports per cabinet.

This technology is only being tested and wont be ready until Q3 with a Q4 launch...

Nonoperational

Praetorian wrote: »

Again from a man in the know:

Some cabs require a type of vectoring known as "system" level vectoring as it needs to vector over multiple DSLAMS. i.e. over 192 ports per cabinet.

This technology is only being tested and wont be ready until Q3 with a Q4 launch...

Interesting. Thanks for that. A bit disappointing all the same!

PeadarB

I can't complain. My connection has remained rock solid since higher G.INP was implemented - the last ten days have seen an increase to 100/20'ish. My attenuation is still relatively high but SNR is steady now at 11/11. Looks as if DSLAM is updating frequently and adjusting within good tight parameters, as needed. Speed test is averaging 94/18 with a slight slip in Tx over the past fortnight - seems to be a slight off-set giving Rx gain but compensating with a small Tx loss.



======================================================
VDSL Port Details Upstream Downstream
Line Rate: 19.479 Mbps 102.395 Mbps
Actual Net Data Rate: 19.480 Mbps 102.396 Mbps
Trellis Coding: ON ON
SNR Margin: 11.0 dB 11.1 dB
Actual Delay: 0 ms 0 ms
Transmit Power: -13.6 dBm 12.3 dBm
Receive Power: -24.4 dBm -2.5 dBm
Actual INP: 29.0 symbols 29.0 symbols
Total Attenuation: 10.8 dB 14.8 dB
Attainable Net Data Rate: 22.533 Mbps 108.476 Mbps
======================================================


Pinging boards.ie [89.234.66.108] with 32 bytes of data:
Reply from 89.234.66.108: bytes=32 time=11ms TTL=60
Reply from 89.234.66.108: bytes=32 time=10ms TTL=60
Reply from 89.234.66.108: bytes=32 time=11ms TTL=60
Reply from 89.234.66.108: bytes=32 time=11ms TTL=60

Ping statistics for 89.234.66.108:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 11ms, Average = 10ms

Deagol

Praetorian wrote: »

Again from a man in the know:

Some cabs require a type of vectoring known as "system" level vectoring as it needs to vector over multiple DSLAMS. i.e. over 192 ports per cabinet.

This technology is only being tested and wont be ready until Q3 with a Q4 launch...

That sounds very likely the reason my cab hasn't been vectored. Looking at the map, it looks like it serves probably 300-400 houses. Q4 is a long way away from now when I'm seeing what vectored people are getting

jca

Deagol wrote: »

That sounds very likely the reason my cab hasn't been vectored. Looking at the map, it looks like it serves probably 300-400 houses. Q4 is a long way away from now when I'm seeing what vectored people are getting

My cabinet is the same, it has an extension on top and probably serves in excess of 300 houses. Do Q3 and Q4 mean July August September and October November December of this year? I'm getting the high 40's dl consistently so I'm happy enough but if Eircom want to give me more:pac::pac:

Praetorian

It's possible Eircom are Huawei's guinea pigs on this new implementation! So I reckon there is a lot of testing going on. Considering how long I waited for ISDN, and then dsl, and then adsl2+ and then vdsl2+ I can wait a few months for vectoring my 70m/bit line upto 100m/bit!

ED E

Praetorian wrote: »

It's possible Eircom are Huawei's guinea pigs on this new implementation! So I reckon there is a lot of testing going on. Considering how long I waited for ISDN, and then dsl, and then adsl2+ and then vdsl2+ I can wait a few months for vectoring my 70m/bit line upto 100m/bit!

They are. As BK has posted before we're one of the first in europe to get 100Mb VDSL, BT max it out at 40. G.Vectoring is the cool new toy that nobody is 100% sure how to play with yet :P

AlanS181824

What are FEC errors and why do I have so many of them? :P

Nonoperational

They are nothing to worry about. How many are you getting?

AlanS181824

Nonoperational wrote: »

They are nothing to worry about. How many are you getting?

I have...
Downstream FEC 10903
Upstream FEC 14464
My internet has been on for several days though so maybe that's why?

ED E

AlanS181824 wrote: »

I have...
Downstream FEC 10903
Upstream FEC 14464
My internet has been on for several days though so maybe that's why?

For several days a 10k is nothing. You'd only worry if that was for a 20 minute period.

AlanS181824

ED E wrote: »

For several days a 10k is nothing. You'd only worry if that was for a 20 minute period.

Ah that's good.

Thanks for that!

red_bairn

ED E wrote: »

For several days a 10k is nothing. You'd only worry if that was for a 20 minute period.

Are they like CRC errors?

ED E

CRC is cyclic redundancy check, FEC is forward error correction. They're different error checking schemes but with VDSL you'll see the counters for both tick up on both as signalling rates are way higher than DSL. As long as they arent happening at a very high rate its nothing to be concerned with(reboot and check after 5 mins of sync, if you have more than a few thousand you might have an issue).

bloodyhawk

ED E wrote: »

CRC is cyclic redundancy check, FEC is forward error correction. They're different error checking schemes but with VDSL you'll see the counters for both tick up on both as signalling rates are way higher than DSL. As long as they arent happening at a very high rate its nothing to be concerned with(reboot and check after 5 mins of sync, if you have more than a few thousand you might have an issue).

Here is mine.

Downstream Upstream
Since Link time = 37 min 35 sec
FEC: 6017 3954
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 8 min 57 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
Previous 15 minutes time = 15 min 0 sec
FEC: 76 16
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 = 14 hours 38 min 57 sec
FEC: 2624 1792
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 3393 2162
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 81 81
LOS: 0 0
LOF: 0 0
LOM: 0 0
Total time = 1 days 14 hours 38 min 57 sec
FEC: 6017 3954
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 81 81
LOS: 0 0
LOF: 0 0
LOM: 0 0

Is it bad?

ED E

Few thousand in 38hrs? Grand.

Basically, unless you're performance is unreliable you can ignore error counters.

bloodyhawk

ED E wrote: »

Few thousand in 38hrs? Grand.

Basically, unless you're performance is unreliable you can ignore error counters.

Grand, thanks ED

Nate--IRL--

Just noticed I got a speed bump today from 50\10



Nate

LFCFan

I seem to be getting a lot of errors

Total time = 1 days 5 hours 46 min 25 sec
FEC: 39397 528
CRC: 2897 0
ES: 23 0
SES: 21 0
UAS: 228 207
LOS: 2 0
LOF: 16 0
LOM: 0 0

These are my stats. Does the Attainable Net Data rate mean the rate I should be able to get?

VDSL Port Details Upstream Downstream
Line Rate: 7.167 Mbps 25.597 Mbps
Actual Net Data Rate: 7.168 Mbps 25.598 Mbps
Trellis Coding: ON ON
SNR Margin: 16.0 dB 18.8 dB
Actual Delay: 0 ms 0 ms
Transmit Power: 6.3 dBm 14.3 dBm
Receive Power: -11.0 dBm -5.9 dBm
Actual INP: 30.0 symbols 30.0 symbols
Total Attenuation: 17.3 dB 20.2 dB
Attainable Net Data Rate: 17.434 Mbps 44.008 Mbps

AlanS181824

LFCFan wrote: »

I seem to be getting a lot of errors

Total time = 1 days 5 hours 46 min 25 sec
FEC: 39397 528
CRC: 2897 0
ES: 23 0
SES: 21 0
UAS: 228 207
LOS: 2 0
LOF: 16 0
LOM: 0 0

These are my stats. Does the Attainable Net Data rate mean the rate I should be able to get?

VDSL Port Details Upstream Downstream
Line Rate: 7.167 Mbps 25.597 Mbps
Actual Net Data Rate: 7.168 Mbps 25.598 Mbps
Trellis Coding: ON ON
SNR Margin: 16.0 dB 18.8 dB
Actual Delay: 0 ms 0 ms
Transmit Power: 6.3 dBm 14.3 dBm
Receive Power: -11.0 dBm -5.9 dBm
Actual INP: 30.0 symbols 30.0 symbols
Total Attenuation: 17.3 dB 20.2 dB
Attainable Net Data Rate: 17.434 Mbps 44.008 Mbps

I've had my modem connected for around 18 hours and I have

Downstream FEC: 630
Upstream FEC: 682

I think yours are so high due to your distance but then again I'm sure someone on here can help you.

ED E

LFCFan wrote: »

I seem to be getting a lot of errors

Total time = 1 days 5 hours 46 min 25 sec
FEC: 39397 528
CRC: 2897 0
ES: 23 0
SES: 21 0
UAS: 228 207
LOS: 2 0
LOF: 16 0
LOM: 0 0

These are my stats. Does the Attainable Net Data rate mean the rate I should be able to get?

VDSL Port Details Upstream Downstream
Line Rate: 7.167 Mbps 25.597 Mbps
Actual Net Data Rate: 7.168 Mbps 25.598 Mbps
Trellis Coding: ON ON
SNR Margin: 16.0 dB 18.8 dB
Actual Delay: 0 ms 0 ms
Transmit Power: 6.3 dBm 14.3 dBm
Receive Power: -11.0 dBm -5.9 dBm
Actual INP: 30.0 symbols 30.0 symbols
Total Attenuation: 17.3 dB 20.2 dB
Attainable Net Data Rate: 17.434 Mbps 44.008 Mbps

Attainables are just a "guesstimate". You'll never get the full attainable speed, that'd be like asking your car to drive at 100% revs the full time, but it is an indication of room for improvement. The other factor here is your down SNR, 16dB. The target for VDSL is 10db, so your signal "strength" is 4x the minimum right now(each 3dB is a doubling, so 2x2). Thats enough to allow you go faster without becoming unstable as all hell. Have your ISP profile you to 30Mb and see how you get on from there. If you're unvectored you might well make the 40Mb mark when that hits your cab.

The errors, again, big numbers, little meaning. Rounded off thats 30hrs and 40k FEC, 1300/hr. Its higher than some posters here, thats expected. Take Alan vs you say, the Cab for him is practically sitting in his driveway, where as yours is probably around 800m away(from memory here). That's 700+ extra meters where yours runs alongside a load of other lines, all inducing noise. As long as you arent seeing a sync speed of 25 and speed testing at like 19 or 20 consistently there isnt a performance issue. Just means the modem is doing what its supposed to.

lmimmfn

ED E wrote: »

Attainables are just a "guesstimate". You'll never get the full attainable speed, that'd be like asking your car to drive at 100% revs the full time, but it is an indication of room for improvement. The other factor here is your down SNR, 16dB. The target for VDSL is 10db, so your signal "strength" is 4x the minimum right now(each 3dB is a doubling, so 2x2). Thats enough to allow you go faster without becoming unstable as all hell. Have your ISP profile you to 30Mb and see how you get on from there. If you're unvectored you might well make the 40Mb mark when that hits your cab.

The errors, again, big numbers, little meaning. Rounded off thats 30hrs and 40k FEC, 1300/hr. Its higher than some posters here, thats expected. Take Alan vs you say, the Cab for him is practically sitting in his driveway, where as yours is probably around 800m away(from memory here). That's 700+ extra meters where yours runs alongside a load of other lines, all inducing noise. As long as you arent seeing a sync speed of 25 and speed testing at like 19 or 20 consistently there isnt a performance issue. Just means the modem is doing what its supposed to.

This is mine:
Downstream line rate (kbit/s) 51198
Upstream line rate (kbit/s) 20477
Downstream attainable data rate(kbit/s) 69724
Upstream attainable data rate(kbit/s) 20047
This messed up attainable is since the INP changes a month or 2 ago.

ED E

lmimmfn wrote: »

This is mine:
Downstream line rate (kbit/s) 51198
Upstream line rate (kbit/s) 20477
Downstream attainable data rate(kbit/s) 69724
Upstream attainable data rate(kbit/s) 20047
This messed up attainable is since the INP changes a month or 2 ago.

Thats unusual. I should have been clearer above though. The way the profiles are designed usually the downstream channel is maxxed out way more than upstream, so my comments were in regards to downsteam sync vs attainables.

Your sync may not be stable, and if it is performance may not be what it should be. What are your SNR values? Upstream SNR is very likely at or below the threshold. Unless you have a fritzbox.

lmimmfn

ED E wrote: »

Thats unusual. I should have been clearer above though. The way the profiles are designed usually the downstream channel is maxxed out way more than upstream, so my comments were in regards to downsteam sync vs attainables.

Your sync may not be stable, and if it is performance may not be what it should be. What are your SNR values? Upstream SNR is very likely at or below the threshold. Unless you have a fritzbox.

ahh yeah, i only posted because sometimes the attainable rates can be taken with a pinch of salt recently( download attainable has dropped by 14Mbit since the change and the usual ping times dropped also ). My SNR is fine( although upstream is low its well above 6/6.6 )
Downstream SNR (dB) 14.3
Upstream SNR (dB) 8.9

ED E

lmimmfn wrote: »

ahh yeah, i only posted because sometimes the attainable rates can be taken with a pinch of salt recently( download attainable has dropped by 14Mbit since the change and the usual ping times dropped also ). My SNR is fine( although upstream is low its well above 6/6.6 )
Downstream SNR (dB) 14.3
Upstream SNR (dB) 8.9

Thats actually quite weak. The target is 6dB for ADLS/2+, its 10 for VDSL2. And usually the upstream is pushing 15+.

lmimmfn

ED E wrote: »

Thats actually quite weak. The target is 6dB for ADLS/2+, its 10 for VDSL2. And usually the upstream is pushing 15+.

link? i read several places that for <6 for VDSL2 its disconnect time, with 7-10 being ok and 10+ being desirable. Its low yes, but it doesnt cause any issue, 0 CRC errors,FEC ~7000 being up for 16 days.

arctan

it's 6dB for VDSL too

ED E

That was word of mouth, sorry I got that wrong.