|
|
|
looks to me that they capping upstream to 30 meg/bit as this screen shots shows
https://www.dropbox.com/s/5tdkh53hxhgr4cw/Screenshot%202018-05-25%2007.43.35.png?dl=0
anyone else notice this or has all those that having vectoring on able get 50 meg bits

freakngeek:
My thoughts on Vectoring and G.INP are
The Rich seem to have gotten richer on Downstream by the biggest margins (ie those on 100Mbp/s are now on or near 120Mbps, 20% gain
As we go down from 100Mbps pre Vectoring the downstream gain drops, I got a 4% on 75 to 78Mbps
Some results below 75Mbps seem to have very little gain at all, some even dropping
Not a single person so far has jumped with joy with a huge gain that Chorus trial Vectoring line with gains shows there should be.
Being you are pretty damn rural, It's highly likely you had very little crosstalk holding your speeds down.
The gains are where crosstalk is high, or at lower levels eg, Error rates.
freakngeek:
On the other hand the Rich Upstream sync has dropped drastically almost 20Mbps see above comment from michaelmurfy 's parents
I got not a sausage and again I doubt many have
But this is a Chorus decision nothing to do with Vectoring or G.INP
But the one redeeming thing that has happened is error rate has dropped drastically
Not a single error other than the Linecard resyncing on upstream for me, will be interesting with next Thunderstorm.
This I suppose allows most connections to go on Fast mode (no interleaving), giving a small Ping boost
Anyway I think we got more from G.INP than from Vectoring, just my thoughts on what I've seen thus far.
I could be completely wrong of course not seeing behind the scenes happenings
Would love another Chorus pre/post vectoring result for the masses
The upload drop was a well expected result, unfortunate for those who feel it.
but great for those who gained.
There has also been a trend noticed, where lower speed connections have also seen a gain in upstream; I understand this was an unexpected bonus result of the reduction in upstream speeds.
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
gorringS:
looks to me that they capping upstream to 30 meg/bit as this screen shots shows
https://www.dropbox.com/s/5tdkh53hxhgr4cw/Screenshot%202018-05-25%2007.43.35.png?dl=0
anyone else notice this or has all those that having vectoring on able get 50 meg bits
as above, intentional change.
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
hio77:DS248: ... We are .. serviced by a cabinet just within the urban area (RDB/M, which is 1.5 km cable distance from us). ...
Your linecards getting switched to vector capable ones on the 23rd may.
Thus arent on this switch flicking list.
I'm unsure of the idea here. It may be they are deployed then flicked after a week or so (the chorus folk are monitoring afterall. Think their tool also needs history)
No evidence of any change here yet so maybe it will be a week before the switch is flicked?

Oh well, at least it is (marginally) better than it has been for the last two months or so!
From what others have experienced, I do worry that our upstream may be impacted for the worse by vectoring :(
Our modem is an ASUS DSL-AC56U. Not certain where I check to see if vectoring is turned on.
Nothing obvious on the DSL Stats page.
DSL Exchange (DSLAM) is still reported as IKANOS. Not certain if this means anything?
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
DS248:hio77:DS248: ... We are .. serviced by a cabinet just within the urban area (RDB/M, which is 1.5 km cable distance from us). ...
Your linecards getting switched to vector capable ones on the 23rd may.
Thus arent on this switch flicking list.
I'm unsure of the idea here. It may be they are deployed then flicked after a week or so (the chorus folk are monitoring afterall. Think their tool also needs history)No evidence of any change here yet so maybe it will be a week before the switch is flicked?
Oh well, at least it is (marginally) better than it has been for the last two months or so!
From what others have experienced, I do worry that our upstream may be impacted for the worse by vectoring :(
Our modem is an ASUS DSL-AC56U. Not certain where I check to see if vectoring is turned on.
Nothing obvious on the DSL Stats page.
DSL Exchange (DSLAM) is still reported as IKANOS. Not certain if this means anything?

Thanks to both of you.
DS248:Thanks to both of you.
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
hio77: At 20db vectoring likely would make minor differance.
It's the underlying improvements it makes that adds up far more.
What are the "underlying improvements"?
A change from IKANOS to Broadcom likely to provide any benefit? (Assuming it will occur on our cabinet).
Also, why no longer able to access 8b?
Both DS & especially US were generally better on 8b but now if I try to force an 8b connection, it fails to connect.
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
Anyone with that sweet insider info seen what happened to WAK_B-DSLAM-03? I'm guessing we've been moved to the cleanup date as the vectoring still hasn't been enabled but weirdly G.INP is.
Thanks again,
J
JOEJOEJOE:
Anyone with that sweet insider info seen what happened to WAK_B-DSLAM-03? I'm guessing we've been moved to the cleanup date as the vectoring still hasn't been enabled but weirdly G.INP is.
Thanks again,
J
That's often the state the dslam lands in when it's not been flicked but something went wrong (eg cleanup required)
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
freakngeek:
DV130 Telnet command with a little more info is 'vdsl optn status' which reveals this:
Vigor> vdsl optn status
trellis [US] = ON, [DS] = ON.
bitswap [US] = 0, [DS] = 0. [0: default(ON), 1: ON, 2: OFF]
sra [US] = 0, [DS] = 0. [0: default(=3), 2: OFF, 3: ON , 4: DYNAMIC_SOS]
retx [US] = ON, [DS] = ON.
aelem ON
G.Vector ON
@freakngeek something a little odd here - see image. The top result is a DV130 in an area that is getting UFB, on an Ikanos cabinet. Bottom image is on a Broadcom that vectoring has been enabled on. Both modems on 3.8.2 m8.
Do you think the DV130 is reporting incorrectly?
Those look to be the modem side flags rather than current.
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
hio77:
Those look to be the modem side flags rather than current.
Ah sure, so like what it's capable of rather than what's necessarily currently enabled.
If that is the case, then I'm still to find a way in the DV130 to tell if Vectoring is actually enabled or not.
|
|
|