Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[les-70]

   I am not the person to know but I find the average errors since uptime are always correct but the 24 hours figures can have issues.  I can't get the "reset values" to work correctly on current versions.  The stats zero but the time interval does not seem to reset.  I am sure you can always trust the telnet-connection stats page though.


edit -- I would try the HG612 uncapped for a day as long as the errors don't look to be heading too high eg over ~1000/day.  That will give proper test against the Xyxel capped which you ran for that long. 

[roseway]

One puzzle with DSLStats is that the average ES is showing zeros for all values, the stats tab shows es/hour as 0 0, but the connection stats does show ES values for downstream. Is this a bug in the f/w or a problem with DSLStats?

The important thing is whether the ES values in the connection stats change from hour to hour, because that's what the graph, the averages, and the stats summary reflect. If the ES per hour graph shows values but they don't show in the averages or the stats summary, then that could be a bug (although it does take a bit of time after a new start or a new 24-hour period before the averages show sensible values).

[broadstairs]

The important thing is whether the ES values in the connection stats change from hour to hour, because that's what the graph, the averages, and the stats summary reflect. If the ES per hour graph shows values but they don't show in the averages or the stats summary, then that could be a bug (although it does take a bit of time after a new start or a new 24-hour period before the averages show sensible values).

Eric the ES/hour graph shows values for each hour the HG612 has been running as well as totals for the house before I switched. It is just all three average values for ES which are all zeros both down (which does happen) and up (which does not). I did try a restart of DSLStats at around 09:30 this morning but these ES averages are still all zero now at 12:12. I should have pointed out that it is the 24 hour value which is zero, if I select modem/router averages values are shown.

Seems like MDWS is seeing valid ES values when I look at the graphs.

Stuart

[roseway]

OK Stuart, I'll check it out. It works properly here, but that doesn't mean there isn't a bug of course.

[broadstairs]

OK Stuart, I'll check it out. It works properly here, but that doesn't mean there isn't a bug of course.

Eric I'm wondering if it has something to do with swapping routers without a completely new setup for DSLStats? I just stopped recording, changed routers and details for login and started it up again.

Stuart

[les-70]

  Looking at MDWS you may well wish to try the speed cap on HG612 quite soon!! it is probably safer to compare with Zyxel on a like for like speed cap. 

  Testing with any sort of noise spikes on the line is however always quite difficult as things can vary quite a bit from day to day.

[broadstairs]

Well I just issued the xdslcmd command on the HG612 to cap rates as yes the ES level was increasing. However the CRC rate is not as high on the HG612. Later tonight I'll have to at least reboot the HG612 or put the ZyXEL back as I need to alter where the power plugs are situated (part of my other move round).

Based on what I'm seeing here I might well put the ZyXEL back as capped it does not seem significantly worse. I also have to reboot the PC running DSLStats to finish an install which means a break for a few minutes in the stats gathering.

I have an HG622 plus the TT HG635 I could try however unless someone know how there would be no stats from the TT router.

Stuart

[roseway]

Eric I'm wondering if it has something to do with swapping routers without a completely new setup for DSLStats? I just stopped recording, changed routers and details for login and started it up again.

Stuart

Yes, Stuart, I guess that might be relevant. You could try the "Reset values" button on the average errors page. As it happens there will be some changes in that section of the program in the next release, but the version you have should work OK mostly.

[les-70]

I have an HG622 plus the TT HG635 I could try however unless someone know how there would be no stats from the TT router.
Stuart

   Stats are possible see http://forum.kitz.co.uk/index.php?topic=14185.msg273545#msg273545 . Do however check with shields up that all is in stealth -- that seems to be the only issue.  I would recheck with shields up after any reboot.  It will at least let you see what happening in a test.   The trouble is that I am running the actual unlocked firmware and can't properly test these config files myself.

p.s. It would be interesting to me and others if you could continue with the capped HG612 for long enough to give a proper comparison with the capped Zyxel. 

[broadstairs]

Well if my ES stay reasonable I'll leave the HG612 on for now (will have to power it off and on later to move PSU though). I'll have a play with the HG635 later on my laptop prior to testing it in a few days time.

Stuart

[burakkucat]

Hmm . . . If what I post is not that relevant to this thread, perhaps Eric or Kitz would "split it out" and re-home it . . .
On the subject of resetting parameters, the following can be performed on a Huawei HG622, a HG612 & a HG610 as a function of the Broadcom xDSL driver --

Code: [Select]

# xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 1012 Kbps, Downstream rate = 5720 Kbps
Channel: INTR, Upstream rate = 1004 Kbps, Downstream rate = 5494 Kbps

Link Power State: L0
Mode: ADSL2
TPS-TC: ATM Mode
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 4.1 5.9
Attn(dB): 46.5 27.8
Pwr(dBm): 0.0 12.8

ADSL2 framing
Bearer 0
MSGc: 39 10
B: 246 46
M: 1 4
T: 1 3
R: 8 6
S: 1.4326 5.9464
L: 1424 261
D: 32 4

Counters
Bearer 0
SF: 11100089 623755
SFErr: 59855 126
RS: 499504027 4254956
RSCorr: 2866291 1471
RSUnCorr: 305492 0

Bearer 0
HEC: 166413 69
OCD: 79 0
LCD: 79 0
Total Cells: 2318416977 423197221
Data Cells: 62050237 3833409
Drop Cells: 0
Bit Errors: 13490197 9921

ES: 3900 95
SES: 1473 0
UAS: 0 0
AS: 178881

Bearer 0
INP: 0.50 0.00
INPRein: 0 0
delay: 11 5
PER: 16.11 17.83
OR: 22.33 7.17

Bitswap: 96237/96354 704/704

Total time = 1 days 1 hours 41 min 37 sec
FEC: 2866291 1471
CRC: 59855 126
ES: 3900 95
SES: 1473 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Latest 15 minutes time = 11 min 37 sec
FEC: 110875 0
CRC: 1379 0
ES: 316 0
SES: 2 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 52680 0
CRC: 643 0
ES: 117 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Latest 1 day time = 1 hours 41 min 37 sec
FEC: 166647 40
CRC: 2072 0
ES: 456 0
SES: 2 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 2660075 797
CRC: 56473 68
ES: 3014 49
SES: 1461 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Since Link time = 2 days 1 hours 41 min 37 sec
FEC: 2866291 1471
CRC: 59855 126
ES: 3900 95
SES: 1473 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
# xdslcmd info --reset
# xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 1008 Kbps, Downstream rate = 5780 Kbps
Channel: INTR, Upstream rate = 1004 Kbps, Downstream rate = 5494 Kbps

Link Power State: L0
Mode: ADSL2
TPS-TC: ATM Mode
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 4.4 5.7
Attn(dB): 46.5 27.8
Pwr(dBm): 0.0 12.8

ADSL2 framing
Bearer 0
MSGc: 39 10
B: 246 46
M: 1 4
T: 1 3
R: 8 6
S: 1.4326 5.9464
L: 1424 261
D: 32 4

Counters
Bearer 0
SF: 499 409
SFErr: 3 0
RS: 22452 4908
RSCorr: 686 0
RSUnCorr: 6 0

Bearer 0
HEC: 1 0
OCD: 0 0
LCD: 0 0
Total Cells: 104211 19051
Data Cells: 0 0
Drop Cells: 0
Bit Errors: 330 0

ES: 2 0
SES: 0 0
UAS: 0 0
AS: 8

Bearer 0
INP: 0.50 0.00
INPRein: 0 0
delay: 11 5
PER: 16.11 17.83
OR: 22.33 7.17

Bitswap: 5/5 0/0

Total time = 8 sec
FEC: 686 0
CRC: 3 0
ES: 2 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Latest 15 minutes time = 8 sec
FEC: 686 0
CRC: 3 0
ES: 2 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Previous 15 minutes time = 0 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Latest 1 day time = 8 sec
FEC: 686 0
CRC: 3 0
ES: 2 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Previous 1 day time = 0 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Since Link time = 7 sec
FEC: 686 0
CRC: 3 0
ES: 2 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
#


[broadstairs]

So far since last night after I had to reboot the HG612 to move the PSU my errors are not nearly as high, so it will stay as it is for a while longer.

Eric - since the router reboot the ES averages are now looking fine so if there is a bug I would guess it was to do with the change of router.

Stuart

[roseway]

Thanks for that Stuart. I think (hope) that the next release should clear up the last wrinkles in this section of the program.

[les-70]

  It would be interesting to have a 24 hour report on the HG612 capped c.f. the Zyxel capped. From MDWS it looks like the ES is similar but the CRC noticeably less?   

In capped tests I did get the ES rate on the Zyxel tending to converge towards that on the HG612 with the same cap, but it took about twice the cap you have used to get them as close as yours seems to be.  No doubt every ones noise spikes and outcomes will differ though.

[broadstairs]

As of about 10:00 this morning I have put the HG635 back using the config which allows me to get stats from it. We'll see how it goes.

Stuart