Guys check these Fastpath stats for me please

Dont mention Talk Talk !! · Feb 15, 2008, 09:59:10

I ditched my DLink DSL504T router as it was causing way too many stale sessions to occur, Ive now got a 2wire HG1800 router. I was syncing at the max for an interleave line 7616k , I asked idnet to switch interleaving off and now I am syncing at 8128k and will have to give my profile 3 days to catch back up.

Here are my Fastpath stats , do you think they look stable enough to allow to continue stable usage ?

Transmit and Receive Data

IP Bytes Packets Errors

Receive 31412053 22955 0

Transmit 750117 12242 0

Data Errors

Statistics

Collected for 1:11:21

Since Reset Current 24-Hour Interval Current 15-Minute Interval Time Since Last Event

ATM Cell Header Errors: 7 7 0 0:12:40

ATM Loss of Cell Delineation: 0 0 0 0:00:00

DSL Link Retrains: 1 1 0 1:11:17

DSL Initialization Errors: 0 0 0 0:00:00

DSL Initialization Timeouts: 0 0 0 0:00:00

DSL Line Search Initializations: 0 0 0 0:00:00

DSL Loss of Framing Failures: 0 0 0 0:00:00

DSL Loss of Signal Failures: 0 0 0 0:00:00

DSL Loss of Power Failures: 0 0 0 0:00:00

DSL Loss of Margin Failures: 0 0 0 0:00:00

DSL Cumulative Errored Seconds: 10 10 1 0:04:25

DSL Severely Errored Seconds: 0 0 0 0:00:00

DSL Corrected Blocks: 0 0 0 0:00:00

DSL Uncorrected Blocks: 10 10 1 0:04:25

ISP Connection Establishment: 1 1 0 1:10:50

Details

DSL Connection Details

DSL Line (Wire Pair): Line 1 (inner pair)

Protocol: G.DMT

Downstream Rate: 8128 kbps

Upstream Rate: 448 kbps

Channel: Fast

Current Noise Margin: 9.0 dB (Downstream), 21.0 dB (Upstream)

Current Attenuation: 5.0 dB (Downstream), 10.5 dB (Upstream)

Current Output Power: 19.5 dB (Downstream), 12.0 dB (Upstream)

DSLAM Vendor Information: Country: {B5} Vendor: {TSTC} Specific: {400}

PVC Info: 0/38

Internet Connection Details

Connection Type: PPPoA

Username:

Internet Address:

Subnet Mask:

Default Gateway:

Primary Domain Name Server:

Secondary Domain Name Server:

Domain:

Maximum Transmission Unit (MTU): 1500

Gateway Ping: Successful

DNS Communication: Successful

Configuration Server Post: Successful

What do you think ?

James

Dont mention Talk Talk !! · Feb 15, 2008, 11:16:17

and here is a second set of stats taken a bit later, no drop outs so far.

Transmit and Receive Data

IP Bytes Packets Errors

Receive 53722134 39591 0

Transmit 1462760 21376 0

Data Errors

Statistics

Collected for 2:33:45

Since Reset Current 24-Hour Interval Current 15-Minute Interval Time Since Last Event

ATM Cell Header Errors: 14 14 0 0:05:48

ATM Loss of Cell Delineation: 0 0 0 0:00:00

DSL Link Retrains: 1 1 0 2:33:41

DSL Initialization Errors: 0 0 0 0:00:00

DSL Initialization Timeouts: 0 0 0 0:00:00

DSL Line Search Initializations: 0 0 0 0:00:00

DSL Loss of Framing Failures: 0 0 0 0:00:00

DSL Loss of Signal Failures: 0 0 0 0:00:00

DSL Loss of Power Failures: 0 0 0 0:00:00

DSL Loss of Margin Failures: 0 0 0 0:00:00

DSL Cumulative Errored Seconds: 16 16 0 0:05:48

DSL Severely Errored Seconds: 0 0 0 0:00:00

DSL Corrected Blocks: 0 0 0 0:00:00

DSL Uncorrected Blocks: 18 18 0 0:05:48

ISP Connection Establishment: 1 1 0 2:33:14

what do you think ?

james

Rik · Feb 15, 2008, 11:19:25

Roughly one error every 10 minutes, you should be fine - I just wonder why the router re-trained. It may take 5 days for your profile to catch up, btw.

Dont mention Talk Talk !! · Feb 15, 2008, 11:28:16

the thing about the re-training of the router is a pain in the @rse rik, that last router I had , the dlink dsl 504T just gave so many stale sessions, aparently it is known for compiling stale data, even though i use idnet dns servers. Each time I had to reboot the dsl , the IP profile dropped and 3 days in, hadnt reclimbed back to 7150k and I had to ring support to get it nudged back up, Im expecting to have to do this again in a couple of days time, im syncing at 8128 but profile is only at 6500 instead of 7150.

See the new router , 2wire hg1800 are they considered to be stable and decent equipment ?

James

Rik · Feb 15, 2008, 11:47:34

The 2700 is better known to use, James, and they are certainly popular with most people who have one. The 1800 seems to have similar characteristics from what I have seen.

Your profile will take up to 5 days to adjust btw, as it's only a small step.

Dont mention Talk Talk !! · Feb 15, 2008, 14:51:04

here is more update of the stats

DSL Connection Details

DSL Line (Wire Pair): Line 1 (inner pair)

Protocol: G.DMT

Downstream Rate: 8128 kbps

Upstream Rate: 448 kbps

Channel: Fast

Current Noise Margin: 9.0 dB (Downstream), 21.0 dB (Upstream)

Current Attenuation: 5.0 dB (Downstream), 10.5 dB (Upstream)

Current Output Power: 19.5 dB (Downstream), 12.0 dB (Upstream)

DSLAM Vendor Information: Country: {B5} Vendor: {TSTC} Specific: {400}

PVC Info: 0/38

IP Bytes Packets Errors

Receive 244115304 175589 0

Transmit 5980205 96432 0

Data Errors

Statistics

Collected for 6:09:36

Since Reset Current 24-Hour Interval Current 15-Minute Interval Time Since Last Event

ATM Cell Header Errors: 81 81 0 0:12:11

ATM Loss of Cell Delineation: 0 0 0 0:00:00

DSL Link Retrains: 1 1 0 6:09:32

DSL Initialization Errors: 0 0 0 0:00:00

DSL Initialization Timeouts: 0 0 0 0:00:00

DSL Line Search Initializations: 0 0 0 0:00:00

DSL Loss of Framing Failures: 0 0 0 0:00:00

DSL Loss of Signal Failures: 0 0 0 0:00:00

DSL Loss of Power Failures: 0 0 0 0:00:00

DSL Loss of Margin Failures: 0 0 0 0:00:00

DSL Cumulative Errored Seconds: 68 68 0 0:12:11

DSL Severely Errored Seconds: 0 0 0 0:00:00

DSL Corrected Blocks: 0 0 0 0:00:00

DSL Uncorrected Blocks: 98 98 0 0:12:11

ISP Connection Establishment: 1 1 0 6:09:05

No drop outs, how do you think the stats are holding up, does there appear to be stability in there ?

James

Rik · Feb 15, 2008, 14:52:49

I error every 3 minutes. No problem.

Dont mention Talk Talk !! · Feb 15, 2008, 18:49:13

thanks for taking a look rik , I appreciate it. heres the last set of stats, it now 6.45 pm , what is the error rate now and still no dropped line.

DSL Connection Details

DSL Line (Wire Pair): Line 1 (inner pair)

Protocol: G.DMT

Downstream Rate: 8128 kbps

Upstream Rate: 448 kbps

Channel: Fast

Current Noise Margin: 7.0 dB (Downstream), 21.0 dB (Upstream)

Current Attenuation: 5.0 dB (Downstream), 10.5 dB (Upstream)

Current Output Power: 19.5 dB (Downstream), 12.0 dB (Upstream)

DSLAM Vendor Information: Country: {B5} Vendor: {TSTC} Specific: {400}

PVC Info: 0/38

IP Bytes Packets Errors

Receive 244589814 177864 0

Transmit 6167329 97270 0

Data Errors

Statistics

Collected for 10:07:17

Since Reset Current 24-Hour Interval Current 15-Minute Interval Time Since Last Event

ATM Cell Header Errors: 101 101 1 0:01:01

ATM Loss of Cell Delineation: 0 0 0 0:00:00

DSL Link Retrains: 1 1 0 10:07:13

DSL Initialization Errors: 0 0 0 0:00:00

DSL Initialization Timeouts: 0 0 0 0:00:00

DSL Line Search Initializations: 0 0 0 0:00:00

DSL Loss of Framing Failures: 0 0 0 0:00:00

DSL Loss of Signal Failures: 0 0 0 0:00:00

DSL Loss of Power Failures: 0 0 0 0:00:00

DSL Loss of Margin Failures: 0 0 0 0:00:00

DSL Cumulative Errored Seconds: 100 100 1 0:01:01

DSL Severely Errored Seconds: 0 0 0 0:00:00

DSL Corrected Blocks: 0 0 0 0:00:00

DSL Uncorrected Blocks: 134 134 1 0:01:01

ISP Connection Establishment: 1 1 0 10:06:46

The downstream attenuation has fluctuated through the day from 5db (morning) to 7.5db - 9db (afternoon) back down to 5db at teatime, is this a normal occurrence and again, what do you calculate the error rate at now ?

James

Rik · Feb 15, 2008, 18:54:17

1 error in 5+ minutes. No problems there.

I take it you mean noise margin, not attenuation is fluctuating? The latter is normal, it drops as darkness descends due to the increased propagation of radio waves plus things like street lights. If the attenuation is fluctuating, it would suggest a line or router fault.

Dont mention Talk Talk !! · Feb 15, 2008, 18:58:20

whoops

my mistake
here is the line that caught my eye

Current Noise Margin: 6.5 dB (Downstream), 21.0 dB (Upstream)

Thats the one that had different values, the attenuation never altered at all , is this all ok rik ?

James

Rik · Feb 15, 2008, 19:05:10

Yeah, that's normal, James - ADSL works in the MW radio band, so all those nice telephone lines act as a giant aerial and pull all sorts of noise into the line, so you'll see the d/s margin moving about, some routers fluctuate more than others. If you haven't already, removing the ring wire from terminal three of every telephone socket can show a big improvement. You don't need it, and because it's unbalanced, it really picks up the noise badly.

Sebby · Feb 15, 2008, 19:29:41

Quote from: Dont mention Talk Talk !! on Feb 15, 2008, 18:58:20
whoops

my mistake
here is the line that caught my eye

Current Noise Margin: 6.5 dB (Downstream), 21.0 dB (Upstream)

Thats the one that had different values, the attenuation never altered at all , is this all ok rik ?

Just to put your mind at rest, I'll tell you as well that those figures are fine. The target is 6dB, and you don't really want to be dropping too much below that (although if you've sync'd during the day when conditions are better, you'll find that this is inevitable at night). Ultimately, if your line is stable and you have no problems with throughput, don't worry too much about the stats.

Dont mention Talk Talk !! · Feb 15, 2008, 22:31:47

rik

those estimates you made 1 error in every x minutes, what figures did you use to be able to give me the error rate ?

James

Sebby · Feb 15, 2008, 22:43:22

What you want to do is take the number of uncorrected errors and divide it by the time your router has been sync'd.

Lance · Feb 15, 2008, 23:29:57

They look good to me, too!

Dont mention Talk Talk !! · Feb 16, 2008, 20:56:46

how can you get a minus db noise reading

Current Noise Margin: -1.0 dB (Downstream), 21.0 dB (Upstream)

what does a figure like that mean, line has not dropped at all.

James

Rik · Feb 17, 2008, 10:27:00

A number of routers will hold a line with a negative noise margin, though not usually for very long (the error count has probably shot up at this point). Bear in mind that the margin is headroom, not actual SNR, it just means the router is better at picking the signal out from the background noise than anyone expected to be possible.

Sebby · Feb 17, 2008, 14:20:28

I've always considered routers that display a negative SNRM to have inaccurate reporting. Theoretically, there's no way a router could hold sync with a true negative SNRM!

That said, such routers don't necessarily have a problem holding sync, despite these apparent figures, e.g. Netgears.

Personally, I prefer a router that doesn't suffer from this; I believe the ones that tend to show a negative SNRM are AR7-based.

Rik · Feb 17, 2008, 14:36:40

IAC, it's annoying that the firmware writers couldn't be bothered to handled signed integers correctly.

Sebby · Feb 17, 2008, 14:40:39

I absolutely agree, Rik. It's just I don't think there is such thing as a negative SNRM (the line would have dropped). I just think these routers are poor reporters.

Dont mention Talk Talk !! · Feb 17, 2008, 14:41:43

The connection is still going unfalteringly strong . Monday will be day 3 since connecting the new modem and ip profile still hasnt given itself a kick up the @rse to 7150k yet, its sitting at 6500k, guess it will be contact IDNet support Monday morning to get that task carried out.

James

Rik · Feb 17, 2008, 14:43:41

Quote from: Sebby on Feb 17, 2008, 14:40:39
I absolutely agree, Rik. It's just I don't think there is such thing as a negative SNRM (the line would have dropped). I just think these routers are poor reporters.

Netgear's noise margin reporting has always been flaky. It will be interesting to see how Gary makes out with the v4 in that respect.

Rik · Feb 17, 2008, 14:44:18

Quote from: Dont mention Talk Talk !! on Feb 17, 2008, 14:41:43
The connection is still going unfalteringly strong . Monday will be day 3 since connecting the new modem and ip profile still hasnt given itself a kick up the @rse to 7150k yet, its sitting at 6500k, guess it will be contact IDNet support Monday morning to get that task carried out.

You need to wait 5 days for that profile change.

Sebby · Feb 17, 2008, 14:47:17

Quote from: Rik on Feb 17, 2008, 14:43:41
Netgear's noise margin reporting has always been flaky. It will be interesting to see how Gary makes out with the v4 in that respect.

Indeed, Rik. I'm sure it's that AR7 chipset, I'm just sure. Gary's stats on his v4 seem to be much improved so far.

Rik · Feb 17, 2008, 14:49:44

It's time we had another update. Gary, where are you??