A Few Questions About IDnet Please

Rik · Feb 08, 2008, 17:33:34

Unfortunately, it's not showing us line attenuation or noise margin.

Ideally, we also want to see what your error count is like.

DeViTTo · Feb 08, 2008, 17:34:53

Quote from: Rik on Feb 08, 2008, 17:33:34
Unfortunately, it's not showing us line attenuation or noise margin.

Ideally, we also want to see what your error count is like.

I'll reconnet my netgear tonight.

Rik · Feb 08, 2008, 17:40:03

You'll need to keep it connected for 24 hours or so, Dev, to build a picture of the error count. To access this:

Enter this in the browser address bar:

http://192.168.0.1/setup.cgi?todo=debug

which should result in a screen which just says 'Debug enable'.
(That's assuming that you haven't changed the router's IP address from the default).

Then exit from the web interface and open a command-line window. Type:

telnet 192.168.0.1

You should get a BusyBox welcome message to confirm that your telnet connection is established.

Now type:

cat proc/avalanche/avsar_modem_stats

DeViTTo · Feb 08, 2008, 18:16:21

Quote from: Rik on Feb 08, 2008, 17:40:03
You'll need to keep it connected for 24 hours or so, Dev, to build a picture of the error count. To access this:

Enter this in the browser address bar:

http://192.168.0.1/setup.cgi?todo=debug

which should result in a screen which just says 'Debug enable'.
(That's assuming that you haven't changed the router's IP address from the default).

Then exit from the web interface and open a command-line window. Type:

telnet 192.168.0.1

You should get a BusyBox welcome message to confirm that your telnet connection is established.

Now type:

cat proc/avalanche/avsar_modem_stats

Thanks RiK I will try later tonight or tommorow because of teh 24hour bit.

Rik · Feb 08, 2008, 18:23:51

The line stats we can start looking at sooner, of course, but we really want to get an idea of the error count to understand what is happening on the line.

DeViTTo · Feb 08, 2008, 20:35:36

Quote from: Rik on Feb 08, 2008, 18:23:51
The line stats we can start looking at sooner, of course, but we really want to get an idea of the error count to understand what is happening on the line.

The line stats from my netgear below the noise margin goes to 0db sometimes. Comments please, but note router only online 12mins. I like the idea of max attainable rate, but not getting near yet.

usyBox v0.61.pre (2005.11.15-07:43+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

# cat proc/avalanche/avsar_modem_stats

AR7 DSL Modem Statistics:
--------------------------------
[DSL Modem Stats]
US Connection Rate: 832 DS Connection Rate: 5696
DS Line Attenuation: 45 DS Margin: 3
US Line Attenuation: 26 US Margin: 9
US Payload : 1138080 DS Payload: 3004800
US Superframe Cnt : 39811 DS Superframe Cnt: 39812
US Transmit Power : 0 DS Transmit Power: 0
LOS errors: 0 SEF errors: 0
Errored Seconds: 0 Severely Err Secs: 0
Frame mode: 3 Max Frame mode: 0
Trained Path: 0 US Peak Cell Rate: 1962
Trained Mode: 3 Selected Mode: 1
ATUC Vendor Code: 414C4342 ATUC Revision: 1
Hybrid Selected: 3 Trellis: 1
Showtime Count: 1 DS Max Attainable Bit Rate: 6272 kbps
BitSwap: 1 US Max Attainable Bit Rate: n/a
Annex: AnxA psd_mask_qualifier: 0x0000
ATUC ghsVid: 0f 00 41 4c 43 42 00 00
T1413Vid: 00 00 T1413Rev: 00 VendorRev: 00
ATUR ghsVid: b5 00 54 53 54 43 00 00
T1413Vid: 00 00 T1413Rev: 00 VendorRev: 00

[Upstream (TX) Interleave path]
CRC: 0 FEC: 0 NCD: 1
LCD: 0 HEC: 0

[Downstream (RX) Interleave path]
CRC: 0 FEC: 0 NCD: 0
LCD: 0 HEC: 0

[Upstream (TX) Fast path]
CRC: 1 FEC: 0 NCD: 0
LCD: 0 HEC: 0

[Downstream (RX) Fast path]
CRC: 4 FEC: 0 NCD: 0
LCD: 0 HEC: 0

[ATM Stats]
[Upstream/TX]
Good Cell Cnt: 23710
Idle Cell Cnt: 1304324

[Downstream/RX)]
Good Cell Cnt: 62600
Idle Cell Cnt: 9029535
Bad Hec Cell Cnt: 11
Overflow Dropped Cell Cnt: 0

[SAR AAL5 Stats]
Tx PDU's: 2291
Rx PDU's: 3062
Tx Total Bytes: 1039645
Rx Total Bytes: 2905051
Tx Total Error Counts: 0
Rx Total Error Counts: 0

[OAM Stats]
Near End F5 Loop Back Count: 0
Near End F4 Loop Back Count: 0
Far End F5 Loop Back Count: 0
Far End F4 Loop Back Count: 0
SAR OAM Ping Response Drop Count=0
#
#

[attachment deleted by admin]

Lance · Feb 08, 2008, 21:53:04

It is the low noise margin most likely causing the reconnects. One thing you can try which may have an instant effect is removing the ring wire from all telephone sockets. It's on terminal three, and usually orange/white.

Rik · Feb 08, 2008, 23:33:44

One thing we can say immediately is that your line does not appear to be interleaved.

Sebby · Feb 09, 2008, 00:52:59

The SNRM is low, and probably the cause of the disconnects, though I note that you don't use the Netgear everyday, and I've found Netgear's to be inaccurate.

Have you considered a new router? I bet that would cure this. Something like a 2Wire 2700HG or a SpeedTouch 585v6 would be great.

DeViTTo · Feb 09, 2008, 01:07:16

Quote from: Sebby on Feb 09, 2008, 00:52:59
The SNRM is low, and probably the cause of the disconnects, though I note that you don't use the Netgear everyday, and I've found Netgear's to be inaccurate.

Have you considered a new router? I bet that would cure this. Something like a 2Wire 2700HG or a SpeedTouch 585v6 would be great.

Sorry Seb but I use a Draytek Vigor 100 ADSL2 with Dlink DIR655 normally. i discon three times in game tonight took a log after playing these are the stats I appreciate if you take a look. I'll reconnect it now.

Quote from: Lance on Feb 08, 2008, 21:53:04
It is the low noise margin most likely causing the reconnects. One thing you can try which may have an instant effect is removing the ring wire from all telephone sockets. It's on terminal three, and usually orange/white.

Allready done that Lance thanks.

AR7 DSL Modem Statistics:
--------------------------------
[DSL Modem Stats]
US Connection Rate: 832 DS Connection Rate: 5728
DS Line Attenuation: 45 DS Margin: 6
US Line Attenuation: 27 US Margin: 12
US Payload : 336 DS Payload: 240
US Superframe Cnt : 400 DS Superframe Cnt: 401
US Transmit Power : 0 DS Transmit Power: 0
LOS errors: 0 SEF errors: 0
Errored Seconds: 0 Severely Err Secs: 0
Frame mode: 3 Max Frame mode: 0
Trained Path: 0 US Peak Cell Rate: 1962
Trained Mode: 3 Selected Mode: 1
ATUC Vendor Code: 414C4342 ATUC Revision: 1
Hybrid Selected: 3 Trellis: 1
Showtime Count: 5 DS Max Attainable Bit Rate: 6304 kbps
BitSwap: 1 US Max Attainable Bit Rate: n/a
Annex: AnxA psd_mask_qualifier: 0x0000
ATUC ghsVid: 0f 00 41 4c 43 42 00 00
T1413Vid: 00 00 T1413Rev: 00 VendorRev: 00
ATUR ghsVid: b5 00 54 53 54 43 00 00
T1413Vid: 00 00 T1413Rev: 00 VendorRev: 00

[Upstream (TX) Interleave path]
CRC: 0 FEC: 0 NCD: 1
LCD: 0 HEC: 0

[Downstream (RX) Interleave path]
CRC: 0 FEC: 0 NCD: 0
LCD: 0 HEC: 0

[Upstream (TX) Fast path]
CRC: 2 FEC: 9 NCD: 0
LCD: 0 HEC: 0

[Downstream (RX) Fast path]
CRC: 0 FEC: 0 NCD: 0
LCD: 0 HEC: 0

[ATM Stats]
[Upstream/TX]
Good Cell Cnt: 7
Idle Cell Cnt: 13337

[Downstream/RX)]
Good Cell Cnt: 5
Idle Cell Cnt: 92076
Bad Hec Cell Cnt: 0
Overflow Dropped Cell Cnt: 0

[SAR AAL5 Stats]
Tx PDU's: 200666
Rx PDU's: 937185
Tx Total Bytes: 28877687
Rx Total Bytes: 373543816
Tx Total Error Counts: 0
Rx Total Error Counts: 23

[OAM Stats]
Near End F5 Loop Back Count: 0
Near End F4 Loop Back Count: 0
Far End F5 Loop Back Count: 0
Far End F4 Loop Back Count: 0
SAR OAM Ping Response Drop Count=0
#
#

Sebby · Feb 09, 2008, 01:11:20

Are these stats from the Draytek, then? How long's it been connected for? At the moment, it looks fine; a SNRM of 6dB and very low errors, but if it's only be connected 5 minutes, that's misleading.

I can't help but think that this is another case of the AR7 chipset issue.

Rik · Feb 09, 2008, 01:13:05

For that attenuation, you're probably connecting about as fast as you can, I suspect your line is not in prime condition, Dev. The thing that continues to worry me is the relatively low upstream noise margin. That is unusual.

I did find that Draytek's were not particularly good on Max myself, so moved to the Netgear and now the 2700. The latter may well offer you significant improvements.

Sebby · Feb 09, 2008, 01:15:01

You're right, Rik. I managed to miss that.

I've seen it a few times, but never has there been a definite explanation, other than noise on the upstream frequencies, for whatever reason. Often it disappears by itself.

Rik · Feb 09, 2008, 01:15:55

Though it might indicate a noise susceptibility which is causing the re-syncs.

DeViTTo · Feb 09, 2008, 02:30:11

Quote from: Sebby on Feb 09, 2008, 01:11:20
Are these stats from the Draytek, then? How long's it been connected for? At the moment, it looks fine; a SNRM of 6dB and very low errors, but if it's only be connected 5 minutes, that's misleading.

I can't help but think that this is another case of the AR7 chipset issue.

No these were taken after 5 hours with discons but monitored by telnet from the Netgear. Sorry I took a while to get back had a firewall issue couldnt access my router page after switch. I'm back on Dlink Vigor rig now.

just ran the bttest again profiles gone down a bit

Test1 comprises of Best Effort Test: -provides background information.
IP profile for your line is - 4500 kbps
DSL connection rate: 832 kbps(UP-STREAM) 5696 kbps(DOWN-STREAM)
Actual IP throughput achieved during the test was - 4236 kbps

If you wish to discuss these results please contact your ISP.

If you are experiencing problems with specific applications, servers or websites please contact your ISP for assistance.

Your test has completed please close this window to exit the performance tester.

I think someone was surfing last time thats why the lower transfer. Will I get my profile backup again? I noticed that my pings had gone up reconnected again this router and they are back as per first switch over post.

Rik · Feb 09, 2008, 10:04:43

Hi Dev

You're just synched at the bottom speed for a 5000 profile, so I'm guessing you've had a low sync when changing kit around. The profile will recover in 3-5 days, provided you don't have another low-sync event.

DeViTTo · Feb 09, 2008, 10:40:53

Quote from: Rik on Feb 09, 2008, 10:04:43
Hi Dev

You're just synched at the bottom speed for a 5000 profile, so I'm guessing you've had a low sync when changing kit around. The profile will recover in 3-5 days, provided you don't have another low-sync event.

Thanks Rik, its been up 8hours since so far and pings have recovered they went up also before.

Rik · Feb 09, 2008, 10:46:41

Good. Try and keep things stable for a few days, Dev, and it should all settle down for you.

DeViTTo · Feb 09, 2008, 10:49:05

Quote from: Rik on Feb 09, 2008, 10:46:41
Good. Try and keep things stable for a few days, Dev, and it should all settle down for you.

Have a karma for passing 30k

Rik · Feb 09, 2008, 10:49:55

Thanks, Dev. It's a sign of how the forum is growing that the first 10K took 10 months, and the next 20K took less than six!

Sebby · Feb 09, 2008, 11:53:38

Still, I can only think it's the router, as - other than the upstream SNRM - everything looks fine.

Rik · Feb 09, 2008, 11:58:15

It's certainly a candidate, Sebby, I think Dev needs to be patient with the connection for a few days and let it settle.

Sebby · Feb 09, 2008, 11:59:27

Agreed. It's a shame that both routers have the AR7 chipset, but like you said, let's see what happens over the next few days.

DeViTTo · Feb 09, 2008, 14:12:07

11.5 hours up

. I have the qnap disconnected I wonder if that could be cause of my problems.

Quote from: Sebby on Feb 09, 2008, 11:59:27
Agreed. It's a shame that both routers have the AR7 chipset, but like you said, let's see what happens over the next few days.

Does my dlink have same chipset then Seb? AR7 I have heard of probs with them I know, a lot of people go the speedtouch route.

Rik · Feb 09, 2008, 14:45:02

I'm slightly puzzled, Dev. I saw the Vigor and said "Draytek" in my mind. AFAIK, Vigor is a Draytek brand name, not D-Link.