Has anyone heard anything about WAK_B-DSLAM-03? It still doesn't have vectoring enabled.

JOEJOEJOE:

 

Has anyone heard anything about WAK_B-DSLAM-03? It still doesn't have vectoring enabled.

 

Nope, Main man over at chorus is slightly occupied one could say right now :)

hio77:

 

JOEJOEJOE:

 

Has anyone heard anything about WAK_B-DSLAM-03? It still doesn't have vectoring enabled.

 

 

Nope, Main man over at chorus is slightly occupied one could say right now :)

 

 

 

Rollout was that rough, huh. Thanks for the heads up :)

Has SRA been enabled when Vectoring went live? My modem automatically changes its sync rate now without re-syncing. It often has a different sync rate whenever I look.

ETLN01:

Has SRA been enabled when Vectoring went live? My modem automatically changes its sync rate now without re-syncing. It often has a different sync rate whenever I look.

to follow up on the SRA comments, Here is where i see SRA play it's best role on a good line.

On a bad line, it will also do it's best to balance out and avoid a resync - preforms pretty well on the tests that i've tried to upset it...

Right after a fresh sync, often the attainable will rise up.

Here it synced at 18mbit, then very quickly climbed straight to 19mbit - There's a free 5% gain just from having a setting on!

Quick bounce of PPP session for RSP end QOS and it's going strong.

hio77:

 

Right after a fresh sync, often the attainable will rise up.

 

 

Here it synced at 18mbit, then very quickly climbed straight to 19mbit - There's a free 5% gain just from having a setting on!

 

 

 

This is actually a function of Vectoring, but SRA is required for it to work.

BMarquis:

hio77:

Right after a fresh sync, often the attainable will rise up.

Here it synced at 18mbit, then very quickly climbed straight to 19mbit - There's a free 5% gain just from having a setting on!

 

 

This is actually a function of Vectoring, but SRA is required for it to work.

@JOEJOEJOE as announced this evening, 4th September.  

Vectoring has had a few months on my line now.. biggest change i've noticed is even FEC/RTX have dropped down, with little to no change to sync (infact sync has lifted by a few mbit)

I'm keen to see what else our chorus friends can throw in to squeeze more life out of the poor old copper network. If we look to postings even 2 year ago, the idea of Vectoring or G.INP was absurd. now look at it! :)

hio77:

 

@JOEJOEJOE as announced this evening, 4th September.  

 

 

 

 

 

Vectoring has had a few months on my line now.. biggest change i've noticed is even FEC/RTX have dropped down, with little to no change to sync (infact sync has lifted by a few mbit)

 

I'm keen to see what else our chorus friends can throw in to squeeze more life out of the poor old copper network. If we look to postings even 2 year ago, the idea of Vectoring or G.INP was absurd. now look at it! :)

 

Thanks for the heads-up! 

So interesting to see the followup dates were listed today.. - I'm unsure if coincide, caused by me making a markable change to the dsl by tweaking to kick the engine into gear or something got pushed out this week.

my adsl connection finally after 12 weeks decided to move off 12dB down to 6dB...

Earlier this week i had given up on waiting for it to do it's thing (wasn't error related as far as i could see) and dropped the snr to 6dB on my end.

Got around to checking it and... been sitting at 0.1dB all day today.

error rates are a little high, seeing LOM and LOS in there is a instant nono for me (happy to see it didn't drop at all)

Suppose now i know how clean my line is though?

I had quite a weird resync the other day, actual Downstream sync now way over attainable, never had such a gap
Best ever sync and speednet test results I've ever had
Upstream sits pretty well rock steady at current sync
Been like this since Tuesday's resync and no errors to speak of since

Re actual rate > attainable, I am now seeing the same thing for the first time. 

Is this correct?

And Downstream noise safety coefficient (dB) 2.4 ?  Lower than I have ever seen.

==

Also, recently we had to revert to the Vodafone supplied modem due to landline being switched to VOIP.  Does anyone know where to find the error data, and whether we are connected on 17a (most likely) or 8b, etc.

I assume we are still on Ikanos though that info is not showing up in the list below either.

===

Line Stats 13Aug2018 (13:50)
Product type: HG659
Device ID: 00E0FC-S3G7N16225001108
Hardware version: VER.B
Software version: V100R001C206B020

Connection status Showtime
Upstream line rate (kbit/s) 2096
Downstream line rate (kbit/s) 35985
Maximum upstream rate (kbit/s) 2120
Maximum downstream rate (kbit/s) 30384
Upstream noise safety coefficient (dB) 5.4
Downstream noise safety coefficient (dB) 2.4
Upstream interleave depth 0
Downstream interleave depth 0
Line standard VDSL
Upstream line attenuation (dB) 51
Downstream line attenuation (dB) 21.7
Upstream output power (dBmV) 5.6
Downstream output power (dBmV) 13.2
Downstream interleave depth None
DSL up time 3 days 9 hours 35 minutes

Thanks for the quick reply. However, I do not understand the first sentence "... you have already picked up"?? 

Picked up?

Unlikely that we are on a vectored line card. 

We changed back to the Vodafone modem on 10 July. Prior to that we were using an ASUS DSL-AC56U modem.  On 10 July before switching modems, that was still reporting "DSL Exchange(DSLAM) : IKANOS" and "Current Profile : 17a".

I cannot find either bits of info on the HG659 but I assume it unlikely the card in our cabinet has been switched to vectoring in the intervening 5 weeks?

Presumably would have had to sway out the line card to Broadcom

Cabinet is RDB/M.