Acceptable CRC errors ?

Total time = 1 days 13 hours 56 min 46 sec
SF = 8446515
CRC = 41668
LOS = 3
LOF = 27
ES = 9099

ADSL Link Downstream Upstream
Connection Speed 18239 kbps 1399 kbps
Line Attenuation 27.0 db 12.8 db
Noise Margin 3.6 db 3.4 db


Thoughts?

Edited by epyon (Wed 14-Sep-11 11:16:47)

Total time = 1 days 13 hours 56 min 46 sec
SF = 8446515
CRC = 41668
LOS = 3
LOF = 27
ES = 9099

ADSL Link Downstream Upstream
Connection Speed 18239 kbps 1399 kbps
Line Attenuation 27.0 db 12.8 db
Noise Margin 3.6 db 3.4 db

Interleaving vs fast: not stated.

Uptime = 38 hours (ish)
Errored seconds = 2+ hours (ish)

Verdict: excessive.

BUT
do you see any user-visible effects? If not, why worry?

However, you also have 3 "loss of signal" and 27 "loss of framing" events in the same period.

At only 3db margin and 18Mbit down, perhaps without interleaving on too, there's plenty of opportunity to see if interleaving and/or increased margin helps things whilst still maintaining reasonable performance.

BTwholesale? LLU?

BE LLU

Netgear DGN2000 (BCM6338)

Fastpath

thought when gaming sometimes i get spikes/lag while hosting its sort of annoying.

i'll post full stats

# adslctl info --stats
adslctl: ADSL driver and PHY status
Status: ShowtimeRetrain Reason: 8000
Channel: FAST, Upstream rate = 1399 Kbps, Downstream rate = 18239 Kbps
Link Power State: L0
Mode: ADSL2+
Channel: Fast
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 3.6 3.2
Attn(dB): 27.0 12.8
Pwr(dBm): 18.7 12.4
Max(Kbps): 21671 1391
Rate (Kbps): 18239 1399
G.dmt framing
K: 255(0) 40
R: 0 0
S: 1 1
D: 1 1
ADSL2 framing
MSGc: 61 16
B: 254 39
M: 1 1
T: 2 3
R: 0 0
S: 0.4829 0.9815
L: 4224 326
D: 1 1
Counters
SF: 3583130 3623190
SFErr: 10012 25106
RS: 0 0
RSCorr: 0 0
RSUnCorr: 0 0

HEC: 2135 7222
OCD: 0 0
LCD: 0 0
Total Cells: 2493751985 3374272527
Data Cells: 33176812 259273759
Drop Cells: 4687
Bit Errors: 0 773214

ES: 9283 17580
SES: 520 0
UAS: 227 2181
AS: 57973

INP: 0.00 0.00
PER: 16.17 16.19
delay: 0.12 0.24
OR: 33.12 10.86

Bitswap: 10968 52

Total time = 1 days 14 hours 48 min 47 sec
SF = 8639378
CRC = 42313
LOS = 3
LOF = 27
ES = 9283
Latest 1 day time = 14 hours 48 min 47 sec
SF = 3296036
CRC = 9339
LOS = 0
LOF = 0
ES = 2541
Latest 15 minutes time = 3 min 47 sec
SF = 14072
CRC = 3
LOS = 0
LOF = 0
ES = 3
Previous 15 minutes time = 15 min 0 sec
SF = 55609
CRC = 67
LOS = 0
LOF = 0
ES = 41
Previous 1 day time = 24 hours 0 sec
SF = 5343342
CRC = 32974
LOS = 3
LOF = 27
ES = 6742
15 minutes interval [-30 min to -15 min] time = 15 min 0 sec
SF = 55609
CRC = 148
LOS = 0
LOF = 0
ES = 52
15 minutes interval [-45 min to -30 min] time = 15 min 0 sec
SF = 55608
CRC = 367
LOS = 0
LOF = 0
ES = 67
15 minutes interval [-60 min to -45 min] time = 15 min 0 sec
SF = 55671
CRC = 105
LOS = 0
LOF = 0
ES = 54
Showtime Drop Reason: 8000
Last Retrain Reason: 8000
#

Edited by epyon (Wed 14-Sep-11 12:04:50)

Possibly a touch high but certainly nothing that would make your connection appear highly degraded. It probably runs perfectly fine during general use i'd imagine?

The Loss of Signal is a concern considering you've had 3 in less than 2 days but that is likely a result of the very low SNR margin. Have you manually set your connection to use a 3dB SNR target?

Its that my f8lure graphs have been reporting packlet but i ran ping -t test overnight and there was 0%

i'm wondering who to believe.

ping -t will report 0% even if there had been massive loss - as it is only single percent resolution you could have almost have 15 minutes of downtime and still report as 0% loss.

Believe you F8Lure or ThinkBroadband monitor graphs.

In reply to a post by marcusjclifford:

ping -t will report 0% even if there had been massive loss - as it is only single percent resolution you could have almost have 15 minutes of downtime and still report as 0% loss.

Believe you F8Lure or Think Broadband monitor graphs.

or use something like this pingplotter

it will reproduce similar graphs, but show where the loss if any is occurring, sometimes for me there is loss or spikes shown on the tbb ping and also on the other f8lure chart that are network related and nothing to do with my actual connection

Consider yourself lucky.

You have just over 41,000 CRC errors. In the same time frame I get over 1million.

CRC errors 1424650
FEC errors 17252
HEC errors 492709

It's not the time frame that matters but the proportion of SFs. OP has CRCs (SFs in Error) as 0.49% of SFs, which is high. Also has 1 ES every 15 secs, which is also very high.

Hmmm i somehow think this router is junk =/

but i've swtiched to a 6db profile and run TBB ping monitor overnight to see whats what and will report back in the morning.

Edited by epyon (Wed 14-Sep-11 18:07:56)