Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: 1 ... 3 4 [5]

Author Topic: DSLstats and MDWS vectoring state support  (Read 3724 times)

roseway

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 38749
  • Penguins CAN fly
    • DSLstats
Re: DSLstats and MDWS vectoring state support
« Reply #60 on: August 28, 2017, 07:29:12 AM »

Admin note: recent posts here relating to errored seconds have been removed and merged into the main MDWS topic.
Logged
  Eric

Ronski

  • Helpful
  • Kitizen
  • *
  • Posts: 2332
Re: DSLstats and MDWS vectoring state support
« Reply #61 on: August 28, 2017, 09:04:16 AM »

Tony, I'm really liking the updated vectoring display, much nicer than the old one  :thumbs:. Just as a suggestion, presuming it fits would it not be more descriptive to have "Vectoring Upload Not Supported" rather than "Vectoring Not Supported" when an uploader is using HG612 Stats?
Logged

Dray

  • Kitizen
  • ****
  • Posts: 2259
Re: DSLstats and MDWS vectoring state support
« Reply #62 on: August 28, 2017, 09:19:31 AM »

Is it possible for HG612-modem-stats to be updated? Is the source code available?
Logged

tbailey2

  • Kitizen
  • ****
  • Posts: 1215
  • it's is its when it isn't it is. No 'could of'!
    • MyDSLWebStats
Re: DSLstats and MDWS vectoring state support
« Reply #63 on: August 28, 2017, 09:24:58 AM »

Tony, I'm really liking the updated vectoring display, much nicer than the old one  :thumbs:. Just as a suggestion, presuming it fits would it not be more descriptive to have "Vectoring Upload Not Supported" rather than "Vectoring Not Supported" when an uploader is using HG612 Stats?
Tried originally and doesn't fit in various ways but you obviously understand what the short version means. The hover tells the full story. Both roseway and I have tried to contact BE1 but he's not been around for at least a year.
Logged
Tony [Admin MyDSLWebStats]
Upload & View your stats from anywhere MyDSLWebStats
My Books!
Plusnet 80/20 - DSLstats - HG612/TG582n - ECI

Ronski

  • Helpful
  • Kitizen
  • *
  • Posts: 2332
Re: DSLstats and MDWS vectoring state support
« Reply #64 on: August 28, 2017, 09:41:42 AM »

Is it possible for HG612-modem-stats to be updated? Is the source code available?

I only have very old source code, so unfortunately unless BE1 resurfaces, no I don't thinks so, and I presume Roseway has his personal email address, so I'm sure he would have tried that.
Logged

broadstairs

  • Kitizen
  • ****
  • Posts: 2755
Re: DSLstats and MDWS vectoring state support
« Reply #65 on: August 28, 2017, 09:46:26 AM »

Only just seen the new Vectoring display, I like it a lot and very easy to see compared with the traffic light. A great improvement Tony.

Stuart
Logged
ISP:TalkTalk Connection:FTTC Cab:ECI Router:ZyXEL VMG3925-B10B

Chrysalis

  • Content Team
  • Kitizen
  • *
  • Posts: 4989
Re: DSLstats and MDWS vectoring state support
« Reply #66 on: August 28, 2017, 10:25:29 AM »

Tried originally and doesn't fit in various ways but you obviously understand what the short version means. The hover tells the full story. Both roseway and I have tried to contact BE1 but he's not been around for at least a year.

How about vectoring unconfirmed?
Logged
Sky Fiber Pro - Billion 8800NL bridge & PFSense BOX running PFSense 2.4 - ECI Cab

tbailey2

  • Kitizen
  • ****
  • Posts: 1215
  • it's is its when it isn't it is. No 'could of'!
    • MyDSLWebStats
Re: DSLstats and MDWS vectoring state support
« Reply #67 on: August 28, 2017, 11:02:28 AM »

Sounds even less helpful  :'(
Logged
Tony [Admin MyDSLWebStats]
Upload & View your stats from anywhere MyDSLWebStats
My Books!
Plusnet 80/20 - DSLstats - HG612/TG582n - ECI

kwillers

  • Member
  • **
  • Posts: 68
Re: DSLstats and MDWS vectoring state support
« Reply #68 on: October 13, 2017, 12:45:19 PM »

Just to share

My line went live with Vectoring this morning, with major improvements in throughput on the Download side 18MB from 62 to 80 (not much on upload but thats a whole other thread)

I am observing the vectoring swapping between "Full Enabled" and "Partially Enabled" on a regular basis

I will monitor and see if that swapping reduces in frequency over the coming days or indeed stops
« Last Edit: October 13, 2017, 12:52:11 PM by kwillers »
Logged
Life is what happens while you're making plans

pfSense 2.4 on APU2 with Zen FTTC 80/20

tbailey2

  • Kitizen
  • ****
  • Posts: 1215
  • it's is its when it isn't it is. No 'could of'!
    • MyDSLWebStats
Re: DSLstats and MDWS vectoring state support
« Reply #69 on: October 13, 2017, 03:54:58 PM »

I will monitor and see if that swapping reduces in frequency over the coming days or indeed stops
I don't think it will stop as explained earlier in this thread by Chrysalis:

Quote
Vectoring has 2 operating modes.

One of the modes makes it so a modem can transmit vectoring compatible signals so it wont crosstalk to fully enabled vectored lines, the other mode is full vectoring where not only does it transmit compatible signals but it can also utilise other vectored signals to kill crosstalk.  I believe the 1 state is fully vectoring, the 3 state is vectoring compatible signal but no active crosstalk mitigation

Unfortunately the sampling rate at one minute intervals is probably too slow to see how long it actually stays in each state. You'd need to run a copy of DSLStats sampling as fast as possible and keep an watch  on the state but you can't do that with an upload to MDWS...
Logged
Tony [Admin MyDSLWebStats]
Upload & View your stats from anywhere MyDSLWebStats
My Books!
Plusnet 80/20 - DSLstats - HG612/TG582n - ECI

ejs

  • Kitizen
  • ****
  • Posts: 1427
Re: DSLstats and MDWS vectoring state support
« Reply #70 on: October 13, 2017, 07:01:41 PM »

tony I dont think 1 and 3 are equal to each other.

Vectoring has 2 operating modes.

One of the modes makes it so a modem can transmit vectoring compatible signals so it wont crosstalk to fully enabled vectored lines, the other mode is full vectoring where not only does it transmit compatible signals but it can also utilise other vectored signals to kill crosstalk.  I believe the 1 state is fully vectoring, the 3 state is vectoring compatible signal but no active crosstalk mitigation.

This explanation for the different states is clearly wrong. There are different levels of vectoring support, either G.993.5 "full" vectoring giving you crosstalk cancellation and a speed boost, or the vectoring friendly modes described in G.993.2 where only other lines benefit. I don't think it's even possible for your line to alternate between full vectoring and vectoring friendly while remaining connected. If it were possible, it would make little sense to be cancelling the crosstalk for your line much for the time, but then occasionally stop doing that at intervals. Therefore I don't think the vectoring state refers to full vectoring vs. vectoring friendly.

I think state 3 VECT_RUNNING probably indicates that the modem is currently doing something (perhaps sending the error samples) at the particular moment you're checking the state.
Logged

Chrysalis

  • Content Team
  • Kitizen
  • *
  • Posts: 4989
Re: DSLstats and MDWS vectoring state support
« Reply #71 on: October 14, 2017, 12:14:59 AM »

yes I was saying the same that there is 2 modes, vectoring friendly and full on vectoring, but of course I dont know if that other operating mode is in relation to vectoring friendly.
Logged
Sky Fiber Pro - Billion 8800NL bridge & PFSense BOX running PFSense 2.4 - ECI Cab

smf22

  • Member
  • **
  • Posts: 43
Re: DSLstats and MDWS vectoring state support
« Reply #72 on: October 20, 2017, 01:34:05 PM »

Not sure just how useful this be be, but I'll post anyway to show a little of what I've observed with vectoring.

What I did was collect the output of xdslctl info --vectoring at 5-second intervals over a ~four [hour] period between 19:50 and midnight, and log key output including the vectoring state, the packets sent or discarded, and the status sent or discarded.

The following is a summary count of each of the states observed during that time:

- Total samples: 2873
- State 1 samples: 2648
- State 2 samples: 5
- State 3 samples: 219

I think state 3 VECT_RUNNING probably indicates that the modem is currently doing something (perhaps sending the error samples) at the particular moment you're checking the state.

I agree with ejs based on what I saw. When in state 1 the packets sent value does not change. When in state 2 or 3 the packet and status counts increase. For example the following shows the transition from state 1 to 3 and back to 1:

Code: [Select]
2017-10-17T19:52:12: state: 1  pkts sent: 329882  disc: 0  status sent: 164941  disc: 0
2017-10-17T19:52:17: state: 1  pkts sent: 329882  disc: 0  status sent: 164941  disc: 0
2017-10-17T19:52:22: state: 3  pkts sent: 330014  disc: 0  status sent: 165007  disc: 0
2017-10-17T19:52:27: state: 3  pkts sent: 330178  disc: 0  status sent: 165089  disc: 0
2017-10-17T19:52:32: state: 1  pkts sent: 330216  disc: 0  status sent: 165108  disc: 0
2017-10-17T19:52:38: state: 1  pkts sent: 330216  disc: 0  status sent: 165108  disc: 0

In terms of state 2 I saw similar behaviour with respect to packet/status count increments for transition from state 1 to 2 and back to 1 again:

Code: [Select]
2017-10-17T20:49:06: state: 1  pkts sent: 339488  disc: 0  status sent: 169744  disc: 0
2017-10-17T20:49:11: state: 1  pkts sent: 339488  disc: 0  status sent: 169744  disc: 0
2017-10-17T20:49:17: state: 2  pkts sent: 339488  disc: 0  status sent: 169744  disc: 0
2017-10-17T20:49:22: state: 1  pkts sent: 339642  disc: 0  status sent: 169821  disc: 0
2017-10-17T20:49:27: state: 1  pkts sent: 339642  disc: 0  status sent: 169821  disc: 0

In terms of state changes from and to, the following were observed:

- 1 to 2
- 1 to 3
- 2 to 3
- 2 to 1
- 3 to 1

As the state 2 seems a little more interesting, the following is an extraction of samples either side of the five times that state 2 was observed:

Code: [Select]
2017-10-17T20:23:47: state: 1  pkts sent: 334578  disc: 0  status sent: 167289  disc: 0
2017-10-17T20:23:52: state: 2  pkts sent: 334578  disc: 0  status sent: 167289  disc: 0
2017-10-17T20:23:57: state: 3  pkts sent: 334740  disc: 0  status sent: 167370  disc: 0
2017-10-17T20:24:02: state: 3  pkts sent: 334902  disc: 0  status sent: 167451  disc: 0
2017-10-17T20:24:08: state: 1  pkts sent: 334904  disc: 0  status sent: 167452  disc: 0

2017-10-17T20:49:11: state: 1  pkts sent: 339488  disc: 0  status sent: 169744  disc: 0
2017-10-17T20:49:17: state: 2  pkts sent: 339488  disc: 0  status sent: 169744  disc: 0
2017-10-17T20:49:22: state: 1  pkts sent: 339642  disc: 0  status sent: 169821  disc: 0

2017-10-17T21:28:25: state: 1  pkts sent: 343056  disc: 0  status sent: 171528  disc: 0
2017-10-17T21:28:30: state: 3  pkts sent: 343090  disc: 0  status sent: 171545  disc: 0
2017-10-17T21:28:35: state: 3  pkts sent: 343252  disc: 0  status sent: 171626  disc: 0
2017-10-17T21:28:40: state: 2  pkts sent: 343414  disc: 0  status sent: 171707  disc: 0
2017-10-17T21:28:46: state: 1  pkts sent: 343414  disc: 0  status sent: 171707  disc: 0

2017-10-17T21:57:52: state: 1  pkts sent: 348918  disc: 0  status sent: 174459  disc: 0
2017-10-17T21:57:57: state: 3  pkts sent: 348976  disc: 0  status sent: 174488  disc: 0
2017-10-17T21:58:02: state: 3  pkts sent: 349138  disc: 0  status sent: 174569  disc: 0
2017-10-17T21:58:07: state: 2  pkts sent: 349228  disc: 0  status sent: 174614  disc: 0
2017-10-17T21:58:13: state: 1  pkts sent: 349228  disc: 0  status sent: 174614  disc: 0
2017-10-17T21:58:18: state: 3  pkts sent: 349354  disc: 0  status sent: 174677  disc: 0
2017-10-17T21:58:23: state: 1  pkts sent: 349382  disc: 0  status sent: 174691  disc: 0

2017-10-17T22:32:01: state: 1  pkts sent: 353780  disc: 0  status sent: 176890  disc: 0
2017-10-17T22:32:06: state: 2  pkts sent: 353780  disc: 0  status sent: 176890  disc: 0
2017-10-17T22:32:11: state: 1  pkts sent: 353934  disc: 0  status sent: 176967  disc: 0

I should add that during that period of collection the line did not resync and so states 1, 2 and 3 are all observed during 'normal' operation.

Nothing else to add at this stage, but hopefully the above may shed some light or raise some additional questions.

[Moderator edited to insert the missing word "hour" (as [hour], above).]
« Last Edit: October 20, 2017, 02:56:30 PM by burakkucat »
Logged
BT FTTC 80/20 Huawei Cab - Zyxel VMG8924-B10A bridge mode + Ubiquiti EdgeRouter X - smf22 on MDWS via DSLstats

roseway

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 38749
  • Penguins CAN fly
    • DSLstats
Re: DSLstats and MDWS vectoring state support
« Reply #73 on: October 20, 2017, 03:37:16 PM »

Thank you for that useful data.

I'm guessing that state 2 is a short-lived transient state, and perhaps it occurs quite frequently, but it only occasionally coincides with the 5-second sampling times.
Logged
  Eric
Pages: 1 ... 3 4 [5]