A healthy line ?

[old Bill]

BT turned off the Interleaving on my line a few hours ago. Can anyone tell me if  this is a normal amount of errors to have on a line for the amount of time it has been connected ?
Line 1 (inner pair)
Protocol: G.DMT Annex A
Downstream Rate: 7232 kbps 
Upstream Rate: 448 kbps 
Channel: Fast
Current Noise Margin: 6.0 dB (Downstream), 25.0 dB (Upstream)
Current Attenuation: 41.4 dB (Downstream), 26.0 dB (Upstream)
Current Output Power: 19.7 dBm (Downstream), 11.9 dBm (Upstream)
DSLAM Vendor Information: Country: {0x0F} Vendor: {ALCB} Specific: {0x00}
PVC Info:
Since Reset Current 24-Hour Interval Current 15-Minute Interval Time Since Last Event
ATM Cell Header Errors: 1297 1297 18 0:00:07

ATM Loss of Cell Delineation: 236 236 2 0:02:01

DSL Link Retrains: 0 0 0 0:00:00

DSL Training Errors: 0 0 0 0:00:00

DSL Training Timeouts: 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: 692 692 25 0:00:07

DSL Severely Errored Seconds: 60 60 0 0:10:17

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

DSL Uncorrected Blocks: 3933 3933 28 0:00:07

ISP Connection Establishment: 

Forgot to say it has been up and running just over 3 hours.

[old Bill]

I just want to make sure the line is all OK before I come back to IDnet.

[Rik]

At best, Bill, that's around 10x my error rate, at worst nearer 20x.

[Sebby]

Hmm, those errors look pretty high to me. That in itself is not necessarily an issue; if the line is stable and it doesn't impact throughput, then there's nothing to worry about. But I've a feeling it will. You might be better to get interleaving switched back on to reduce the uncorrected errors in particular. Otherwise, in terms of SNRM and sync, it looks healthy.

Just to give you an idea, I've had 15570 uncorrected errors in about 11 days, although that is at 15dB. At 6dB, I'd expect this figure to be higher. I still think that, were we to have like for like figures, yours would be significantly greater.

[old Bill]

I am hoping things might improve once all the trees,lights ect have all been put away. Before they reset my NM I was getting about 7000 errors aday.

[ducky22]

That's not too bad. It depends how much you value the increased speed and lowered latency. That isn't a huge number of errors and shouldn't be noticable if you're just general web browsing/email.

[old Bill]

Strange thing is I reset my counter and the amont of errors for the last couple of hours has dropped my a large margin.
Collected for 1:47:58
Since Reset Current 24-Hour Interval Current 15-Minute Interval Time Since Last Event
ATM Cell Header Errors: 365 365 5 0:00:13

ATM Loss of Cell Delineation: 95 95 2 0:01:22

DSL Link Retrains: 0 0 0 0:00:00

DSL Training Errors: 0 0 0 0:00:00

DSL Training Timeouts: 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: 317 317 10 0:00:13

DSL Severely Errored Seconds: 3 3 0 0:55:30

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

DSL Uncorrected Blocks: 499 499 12 0:00:13

ISP Connection Establishment

[Rik]

They're nothing to worry about, Bill.

[Sebby]

Maybe it's "settled in" a bit, though I'm not sure that's technically possible! I still think the errors look quite high, and the errored seconds is a bit worrying. But, like I say, if it doesn't cause instability and/or poor throughput, then there is no problem.