Low Throughput.

wecpcs · Jul 26, 2009, 23:00:15

Quote from: stevethegas on Jul 26, 2009, 17:20:38
Its similar to the DG834G v4 and the GT,enable debug and then the telnet command is # adslctl info --stats

How do you enable debug and where do you enter the telnet command as I have never used either.

I have tried opening a command window and typing debug where I then get a - appear and I then enter the telnet command and all I get is an error.

Colin

Gary · Jul 26, 2009, 23:03:27

Well throughput for me tonight is appalling, and I cannot imagine at 23:01 its that busy on a Sunday night at my exchange

Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 8128 kbps(DOWN-STREAM), 448 kbps(UP-STREAM)
IP profile for your line is - 7150 kbps
Actual IP throughput achieved during the test was - 2806 kbps

4Way · Jul 26, 2009, 23:16:30

Use the following in your browser of choice,

192.168.0.1/setup.cgi?todo=debug

You can now telnet in through a cmd window

If you're using Windows: Start, run, cmd, telnet 192.168.0.1

I'm assuming you're using the default IP address

alternatively use the excellent routerstats which will give you all the info you want.

Bill · Jul 26, 2009, 23:23:30

Quote from: Lance on Jul 26, 2009, 22:51:34No matter what BT based ISP is being used, the same thing would have happened.

Or even LLU operator... they all use the same piece of copper (or aluminium if you're really unlucky).

QuoteAs it happens I've had just under 15 million FECs and 34,000 CRC errors in just of 12 hours uptime. And that's with the margin at 9db!

Sheesh, I thought mine were bad... 60,000,000 and 120,000 in about 3 weeks!

Sebby · Jul 27, 2009, 00:31:30

FEC errors are nothing to worry about as they are corrected. It's CRC and HEC errors that are the ones to (potentially) worry about as they indicate uncorrected errors, and this can impact throughput.

mist · Jul 27, 2009, 07:45:37

Think I followed the instructions some of you so kindly posted, hope they may help solve the puzzle of that dratted 1 meg loss.

BusyBox v1.00 (2008.12.10-11:52+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

# adslctl info --stats
adslctl: ADSL driver and PHY status
Status: ShowtimeRetrain Reason: 0
Channel: INTR, Upstream rate = 448 Kbps, Downstream rate = 3840 Kbps
Link Power State: L0
Mode: G.DMT
Channel: Interleave
Trellis: ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 9.3 17.0
Attn(dB): 56.0 31.5
Pwr(dBm): 19.4 12.1
Max(Kbps): 4384 972
Rate (Kbps): 3840 448
G.dmt framing
K: 121(0) 15
R: 16 16
S: 1 8
D: 32 4
ADSL2 framing
MSGc: 1 1
B: 121 15
M: 1 8
T: 1 1
R: 16 16
S: 1.1311 9.0000
L: 976 128
D: 32 4
Counters
SF: 3367129 3367147
SFErr: 34 0
RS: 228964802 28619755
RSCorr: 97650688 6
RSUnCorr: 429 0

HEC: 30 0
OCD: 0 0
LCD: 0 0
Total Cells: 518410812 0
Data Cells: 1363216 0
Drop Cells: 0
Bit Errors: 0 0

ES: 25 0
SES: 0 0
UAS: 12 0
AS: 57241

INP: 2.09 2.00
PER: 1.97 1.96
delay: 9.04 9.00
OR: 28.28 28.44

Bitswap: 0 0

Total time = 15 hours 54 min 24 sec
SF = 3367129
CRC = 34
LOS = 0
LOF = 0
ES = 25
Latest 1 day time = 15 hours 54 min 24 sec
SF = 3367129
CRC = 34
LOS = 0
LOF = 0
ES = 25
Latest 15 minutes time = 9 min 24 sec
SF = 33217
CRC = 0
LOS = 0
LOF = 0
ES = 0
Previous 15 minutes time = 15 min 0 sec
SF = 52923
CRC = 1
LOS = 0
LOF = 0
ES = 1
Previous 1 day time = 0 sec
SF = 0
CRC = 0
LOS = 0
LOF = 0
ES = 0
15 minutes interval [-30 min to -15 min] time = 15 min 0 sec
SF = 52923
CRC = 0
LOS = 0
LOF = 0
ES = 0
15 minutes interval [-45 min to -30 min] time = 15 min 0 sec
SF = 52982
CRC = 1
LOS = 0
LOF = 0
ES = 1
15 minutes interval [-60 min to -45 min] time = 15 min 0 sec
SF = 52923
CRC = 0
LOS = 0
LOF = 0
ES = 0
Showtime Drop Reason: 0
Last Retrain Reason: 0
#
#

Lance · Jul 27, 2009, 08:01:57

Quote from: Bill on Jul 26, 2009, 23:23:30
Or even LLU operator... they all use the same piece of copper (or aluminium if you're really unlucky).

Sheesh, I thought mine were bad... 60,000,000 and 120,000 in about 3 weeks!

I didn't mention LLU as they don't use profiles nor the same DLM system

As for the errors, I should have said 12 days, not hours!

Rik · Jul 27, 2009, 11:01:06

That's a relief, Lance.

Rik · Jul 27, 2009, 11:02:02

That error level doesn't look too bad, Mist.

mist · Jul 27, 2009, 11:22:34

Quote from: Rik on Jul 27, 2009, 11:02:02
That error level doesn't look too bad, Mist.

The Mystery of Mists missing meg.

Just hoping that CS get back to me soon.

I have just checked routerstats whilst posting as leave it running, now what is causing this hhhmm.

[attachment deleted by admin]

Rik · Jul 27, 2009, 11:24:48

It looks like a classic noise spike.

mist · Jul 27, 2009, 11:29:25

Yes and the interesting fact is that there is nothing electrical in use in the house at present apart from this PC.

Was busy polishing........ and that occurs

Rik · Jul 27, 2009, 11:33:19

It could be anywhere between you and the exchange, unfortunately.

mist · Jul 27, 2009, 11:35:52

oh heavens, my side of the dratted demarcation side of the socket or theirs ?

Rik · Jul 27, 2009, 11:40:03

Theirs, in all probability.

mist · Jul 27, 2009, 11:46:11

phewwwwwwwwwww, wipes sweat from brow,

Rik · Jul 27, 2009, 11:46:49

It's good and bad. If it is their side, there's a good chance it won't be resolved.

wecpcs · Jul 27, 2009, 13:36:34

Quote from: 4Way on Jul 26, 2009, 23:16:30
Use the following in your browser of choice,

192.168.0.1/setup.cgi?todo=debug

You can now telnet in through a cmd window

If you're using Windows: Start, run, cmd, telnet 192.168.0.1

I'm assuming you're using the default IP address

alternatively use the excellent routerstats which will give you all the info you want.

I have tried that and entered debug mode with no problem but when I enter the telnet command in a cmd window I get the error 'telnet command not recognised'. So it does not work on my Netgear DG834G v4 router.
Thanks anyway.

Colin

mist · Jul 27, 2009, 19:24:52

Update

No reply from CS to my emails this weekend.

Yet more of those events showed on my routerstats which Rik suggested were noise spikes this afternoon. At one time I lost connectivity, pulled all wires out of router in sheer frustration then went and slammed the iron on his shirts as router was still showing 9.3 noise margin and 3 meg profile after reconnecting.

This is now most annoying.

Rik · Jul 27, 2009, 19:27:25

I don't recommend pulling the wires, Mist, if anything it will cause the dynamic line management software to think your line is more unstable. Support have been under a lot of pressure today, due to the need to balance the network again, and one person being on holiday. I'll see if I can get someone to take a look in the morning. (Speed is not considered an emergency for out of hours...)

mist · Jul 27, 2009, 19:33:26

Thank you Rik, I shall also chase the matter up tomorrow as obviously I want this line/speed/profile issue rectified.

Rik · Jul 27, 2009, 19:39:43

I've alerted support to the thread, Mist. Please be aware that, if the BT software decides to raise margins, it's often difficult to get anything done. If IDNet successfully get the margin reduced, and the system decides to increase it again, it's almost impossible to get it reduced a second time, so do check that you've got everything filtered, that the filters are in good working order and that you don't have any flat extensions in use.

bobleslie · Jul 27, 2009, 20:48:57

Quote from: wecpcs on Jul 27, 2009, 13:36:34
I have tried that and entered debug mode with no problem but when I enter the telnet command in a cmd window I get the error 'telnet command not recognised'. So it does not work on my Netgear DG834G v4 router.
Thanks anyway.

Colin

Usually you get this message if you've not installed telnet from your windows applications list, depending on your version of windows.

IOW telnet is not usually automatically installed. You have to install it first.

wecpcs · Jul 28, 2009, 11:36:16

Quote from: bobleslie on Jul 27, 2009, 20:48:57
Usually you get this message if you've not installed telnet from your windows applications list, depending on your version of windows.

IOW telnet is not usually automatically installed. You have to install it first.

Thanks, I discovered that after downloading and installing routerstats. I then discovered that Vista has it disabled by default. Everything is fine now.
Thanks again.

Colin

bobleslie · Jul 28, 2009, 11:38:36

Good news, Colin, I like a happy ending.