Print

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

[roseway]

In this version I've noticed bug on Netgear DGND3700. Sometimes, CLI Commnand Prefix changes from "adslcfg" to "adsl" on its own.

I presume that you mean that it changes in DSLstats. I can't think of any explanation at present. There were no changes between v5.5 and v5.6 which could explain this. I will see if I can find any explanation, but I'm not hopeful.

Furthermore, both versions DSLStats 5.5 and DSLStats 5.6 have a bug on "Attenuation log". It shows line attenuation under "Signal attenuation".

Could you please post the output of 'adslctl info --stats' and also the contents of the DSLstats Stats page.

I suspect it would be helpful for Netgear routers if DSLStats use "adslctl info --show" instead "adslctl info --stats" - shorter output

I don't believe that the --show command returns all the needed information. There is a section at the end of the --stats command which is headed "Since Link time =...", and some items in that section are used when the section exists.

[konrado5]

Could you please post the output of 'adslctl info --stats' and also the contents of the DSLstats Stats page.

Following there are outputs. I also attach Attenuation log screenshot. If I enable both: LATN and SATN monitoring, Attenuation log shows in reverse order (only on Netgear).

Code: [Select]

adslctl info --stats
adslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    0
Last initialization procedure status:   0
Max:    Upstream rate = 1237 Kbps, Downstream rate = 19988 Kbps
Bearer: 0, Upstream rate = 1237 Kbps, Downstream rate = 18335 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):        1.3             6.7
Attn(dB):        23.5            15.6
Pwr(dBm):        18.3            12.0

                        ADSL2 framing
                        Bearer 0
MSGc:           51              16
B:              217             37
M:              1               1
T:              3               3
R:              0               0
S:              0.3799          0.9744
L:              4591            312
D:              1               1

                        Counters
                        Bearer 0
SF:             1040144         7092
SFErr:          182             0
RS:             0               619010
RSCorr:         0               0
RSUnCorr:       0               0

                        Bearer 0
HEC:            265             0
OCD:            0               0
LCD:            0               0
Total Cells:    730474772               49282321
Data Cells:     4834698         618533
Drop Cells:     0
Bit Errors:     0               0

ES:             175             0
SES:            0               0
UAS:            0               0
AS:             16891

                        Bearer 0
INP:            0.00            0.00
INPRein:        0.00            0.00
delay:          0               0
PER:            16.23           16.07
OR:             28.07           10.94
AgR:            18292.54        1243.14

Bitswap:        0/0             0/0

Total time = 4 hours 41 min 31 sec
FEC:            0               0
CRC:            182             0
ES:             175             0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Latest 15 minutes time = 11 min 31 sec
FEC:            0               0
CRC:            10              0
ES:             10              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:            0               0
CRC:            8               0
ES:             8               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Latest 1 day time = 4 hours 41 min 31 sec
FEC:            0               0
CRC:            182             0
ES:             175             0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            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
LOM:            0               0
Since Link time = 4 hours 41 min 31 sec
FEC:            0               0
CRC:            182             0
ES:             175             0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
#
#

Code: [Select]

Stats recorded 06 Aug 2015 19:27:39

DSLAM/MSAN type:        Not monitored
Modem/router firmware:  Not monitored
DSL mode:                ADSL2+
Status:                  Showtime
Uptime:                  4 hours 47 min 39 sec
Resyncs:                0 (since 06 Aug 2015 17:30:20)

Downstream Upstream
Line attenuation (dB):  23.5 15.6
Signal attenuation (dB): Not monitored
Connection speed (kbps): 18335 1237
SNR margin (dB):        1.3 6.7
Power (dBm):            18.3 12.0
Interleave depth:        1 1
INP:                    0 0
G.INP:                  Not enabled

RSCorr/RS (%):          N/A 0.0000
RSUnCorr/RS (%):        N/A 0.0000
ES/hour:                0.53 0

I don't believe that the --show command returns all the needed information. There is a section at the end of the --stats command which is headed "Since Link time =...", and some items in that section are used when the section exists.

What do you think about possibility disabling monitoring such information and using "adslctl info --show" instead "adslctl info --stats"?

[roseway]

Thank you for posting that information.

Attenuation log: I see what you mean. At the moment it's hard to understand how this can happen on Netgear only, as the values shown in the Stats tab are the correct way round. I'll investigate.

I don't believe that the --show command returns all the needed information. There is a section at the end of the --stats command which is headed "Since Link time =...", and some items in that section are used when the section exists.

What do you think about possibility disabling monitoring such information and using "adslctl info --show" instead "adslctl info --stats"?

I don't want to do this because it would impact on many other users with different modems. Making special arrangements for just one modem causes too many problems with program maintenance.

[GigabitEthernet]

Any chance you could add an option to remove SNR anomolies?

My lowest SNR is -2.1 when my modem resynced which obviously isn't too helpful when I'm trying to find my lowest SNR when the line was up.

[roseway]

You can turn off autoscaling, and set the maximum and minimum Y values to values which suit you.

(Although now I think about it, that wouldn't make any difference to the lowest SNR search.)

[GigabitEthernet]

Does that affect the right click action which shows the minimum SNR, though?

[roseway]

No, I thought of that afterwards and edited my post.

I don't really want to throw away inconvenient data on the assumption that it's an anomaly - a short-lived SNRM of -2 dB may well be valid data.

[GigabitEthernet]

Perhaps an option to delete data then?

[NewtronStar]

Perhaps an option to delete data then?

Then only way i would see a negative SNR is during a very fast forced reync for example pulling out the HG612 power cable and then back in again in 5 seconds.

These days i wait 30 minutes before plugging the power cable back in.

[kitz]

In view of the amount of occasions this is likely to happen then Im unsure if it would be an efficient use of Erics time to try to delete one specific entry out of the whole set of data.   He spends an awful lot of time on DSLstats... and knowing Eric probably more than he should be doing.

If you wish to clear the data, why dont you save what data you have, close the prog down and start a fresh window.

[roseway]

Thanks, I agree with that.

[GigabitEthernet]

I have DSLstats running in a virtual machine, running Windows XP.

If I pause DSLstats and then save the machine state and then resume the virtual machine, this will cause a violation error in DSLstats.

[roseway]

If that's an Access Violation error, this happens when a program tries to read or write to memory which it doesn't have access to. So I can only think that something has changed in the machine state between saving and resuming it.

[broadstairs]

Eric I altered the number of days to delete snapshots from 14 to 60 but suddenly at lunchtime today it decided to delete all the data from 17th to 21st August. Not what I was expecting. For now I have unticked the option in the hope it will action the change. I'm wondering if you only read this setting on program start?

Stuart

[roseway]

Stuart, it's supposed to check the configured value every time, but it looks as though there's a bug there. I'll endeavour to fix it.