Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[maverickmac]

I am on Sky Fibre Pro and I have  Interleave depth 1, INP 0 at the moment but my ES error count on downstream appears to be quite high 40+ per day hour
I have included the QLN, Hlog and Stats from DSLStats. I am using Billion 8800AXL with latest firmware 2.32e.

Are those spikes on the QLN something to be worried about? and what about the ES errors?
Is there more info I could supply for the experts here to advise
Cheers

[Black Sheep]

IMHO ...... 40+ per hour isn't high. 

[les-70]

  If Sky use the standard FTTC profile then more than 60/hour will see interleaving imposed.  If they use the fast profile 120 is the limit.  From just one hour it is hard to say just what the risks of exceeding 60/hour over the 24 period are. 

  Reducing error rates is quite hard these days as assuming a properly installed SSFP and a short dsl cable to the modem/router there is not much to fiddle with.  My line has similar speed and error rates if run with an 8800NL in the usual way.  Using a HG612 as modem reduces my errors down by about 30 percent. However close inspection of the stats shows the HG612 handles odd high CRC noise spikes better so unless you get these spikes an HG612 may not make much difference.

  If you don't mind being interleaved I would just see how it goes.  if you don't wish to be interleaved and don't mind loosing a bit of speed you could manually cap the sync speed via telnet command.  e.g. for the Billion "adsl configure --maxDataRate 64030 20000 100000" would limit your sync to 64Mb/s and and give a higher SNRM and some error reduction.

[maverickmac]

Thanks for the info. I'll keep an eye on the Stats and see how it goes.

[Chrysalis]

yeah depends on how you look at it, if none of them are SES then the error rate is probably not service affecting.

In which case the only consideration for how bad it is, if its enough to trigger DLM as les says.

[WWWombat]

Probably best to not extrapolate an ES rate from a single hour; taking 24-hour figures is better - then watch how these alter over lots of days

The QLN spikes are likely to be radio stations.

[burakkucat]

The QLN spikes are likely to be radio stations.

And, in the past, some of us have used the raw data (which is used to create the QLN plot) to geo-locate the approximate area in which a Kitizen is based! 

[N0STIE]

What about 500 ES on downstream per 24hours with fastpath enabled? Is it high amount? 4 of them are SES

[Chrysalis]

The SES ideally should be 0 but consider there is 86400 secs in a day.

I would rather have 4 SES a day with fastpath than 0 with interleaving.

[kitz]

Lets also not forget that an errored second doesnt mean that the whole second is errored.   
An errored second can be triggered by just a single coding violation within that second.   A CRC can happen so quick that you are highly likely to ever notice any performance hit by a single errored second nvm a single CRC. 

An SES is when >30% of data within a second is errored - again youre not likely to notice the odd one or two over the course of a day, it only becomes problematic when they are all bunched together and then you start to see lagginess.   

 

[Chrysalis]

indeed, my experience is that normal ES tend to not be noticeable.  Especially when they not bunched up together.