Kitz Forum

Broadband Related => FTTC and FTTP Issues => Topic started by: g3uiss on December 28, 2019, 10:48:51 PM

Title: Caught out
Post by: g3uiss on December 28, 2019, 10:48:51 PM
Why does it always happen when your not looking. My VDSL line started with severe errors at about 6:15 this evening from a normal ES of 50/hr it jumped to over 500 with CRC in the region of 3000. It’s still at that rate, but by the time I noticed,  it was welnpassed the Fast Path rate so saw little reason to shut down the line. So tomorrow I’m expecting to be interleaved and being on an ECI. Cab it might be moths before, if ever I go back to fast path. With a sync rate of only 20mbs the reduction is noticeable. I did do a quite line test when I noticed, but it was silent. I guess someone in the area has some poor electrical equipment running.

Not a new occurrence but usually I get the DSL stats warning and turn of the modem for a couple of hours. Holiday season and out with family without phone.

Just a moan about our outdated provision of broadband. I have a ADSL2 line as well but little errors on that.

Tony
Title: Re: Caught out
Post by: g3uiss on December 29, 2019, 07:34:29 AM
Apart from dropping back to normal around 0300 for a couple of hours, now  CRC's are back around 100/min and ES 26/min. I guess nothing can be done. Looks like the DLM hasn't action so far, could this be a wider event ?

Line is still quite and still syncing at normal speed . Thru put seems normal also

Tony
Title: Re: Caught out
Post by: g3uiss on December 29, 2019, 09:56:06 AM
Actually appreciate some advice. I did restart DSL stats about 7:30 just in case something was stuck. I’ve turned on uploading for a few minutes so the stats can be seen at www.west-Lodge.com/vdsl/index.htm.

Should I just let it run until DLM apples interleaving ? Or unplug for some time ?

Advise appreciated.
Title: Re: Caught out
Post by: tubaman on December 29, 2019, 10:04:32 AM
Have you tried a different modem to ensure it's not that at fault? Last time I had those sorts of errors it was when my Netgear D6220 decided to go bad.
 :)
Title: Re: Caught out
Post by: g3uiss on December 29, 2019, 10:19:01 AM
Thanks @tubaman. Just swapped it out with an identical HG612 and no change at all.

Tony
Title: Re: Caught out
Post by: g3uiss on December 29, 2019, 02:51:44 PM
Now running at 1 ES per second which I guess Is the max DSL stats or telnet can show. Surprised no dip in SNRM or sync rate. Perplexing  >:(
Title: Re: Caught out
Post by: nfxcr3w on December 29, 2019, 04:03:02 PM
Have you tried a different VDSL cable either a cat 5e twisted pair or the one I'm using High Speed RJ11 DSL Cable 0.5m from Tandy. Using high grade ADSL Nation Pro+ Just to rule out any issues with the cabling.
Title: Re: Caught out
Post by: roseway on December 29, 2019, 04:10:13 PM
Now running at 1 ES per second which I guess Is the max DSL stats or telnet can show.

It's the highest value which can possibly exist. A higher value would mean that there were more seconds containing errors than there were total seconds.
Title: Re: Caught out
Post by: g3uiss on December 29, 2019, 04:14:47 PM
Yes just tried an alternate cable. @roseway thanks that’s what I thought / meant. Looking over the last 12 hours it’s steady climbed up to as you say the maximum. Nothing in this house, and the fact it returned to normal for a few hours in the middle of the night I guess it must be external. No doubt the DLM will do something tonight. As I’m on ECI it can only apply interleave or cap ?

Tony
Title: Re: Caught out
Post by: Alex Atkin UK on December 29, 2019, 07:47:37 PM
Thanks @tubaman. Just swapped it out with an identical HG612 and no change at all.

Tony

Did you swap out the PSU too? I know it can be tempting to use the same one if its the same device but you want to eliminate that as a potential fault too.
Title: Re: Caught out
Post by: g3uiss on December 29, 2019, 07:54:17 PM
No I didn’t ! But I will and report back. Thanks.
Title: Re: Caught out
Post by: sevenlayermuddle on December 29, 2019, 09:36:00 PM
Seems to me like if you are getting 1 ES every second, yet not enough errors in total to reduce SNRM enough to disconnect the line, a possibility is that you might be getting repeated very short bursts of interference at about 1 second intervals.

Taking a wild guess, one thing that I think might fit that pattern would be farmers’ electric fences.   Is that a possible cause, where you live?

Even if not electric fences, maybe still worth wandering around with an AM radio.  A pattern of ‘clicks’ at about one second intervals might prove my theory, then it’d be a case of figuring out what’s causing them.

Just a thought. :)
Title: Re: Caught out
Post by: g3uiss on December 29, 2019, 10:30:12 PM
7lm thanks for the suggestion. I’m not in a rural area so unlikely, and when I returned home this evening ES are back to their normal level. So whatever has now gone, but I will get penalised by the DLM tomorrow. Such is the nature of our service I think.

Happy new year to all Tony
Title: Re: Caught out
Post by: j0hn on December 30, 2019, 12:35:36 AM
My advise would be to power down the modem overnight and let the DSLAM port rest.

Reconnect in the morning and see if the ES are still there.

At 1 ES every second I would expect considerable packet loss and for it to be very much affecting your service.

Contact your ISP if nothing changes as that should be a clear cut fault. Could simply be a faulty line card port.
Title: Re: Caught out
Post by: g3uiss on December 30, 2019, 09:51:09 AM
@J0hon   Thanks but the DLM put me on interleave at 0300. Lost 10% sync but zero errors now. Yes I was getting packet loss and reported to ISP.  They couldn’t see anything and line test was clear. I guess I should wait and sete if fastpath ever returns, or would you still rest the port ?

Tony
Title: Re: Caught out
Post by: g3uiss on December 30, 2019, 10:14:37 PM
I’m beginning to think interleaving isn’t so bad. !!

No errors CRC or ES and a good thru put. Yes 10% drop in sync and increased latency. Might upset gamers but my VPN’s are responsive.

It gives one less issue to worry about( if you are inclined to). While I’m interleaved I might stop DSL stats little point I think.

Happy new year to all

Tony
Title: Re: Caught out
Post by: Alex Atkin UK on December 30, 2019, 10:55:48 PM
Interleaving being good and considering NOT monitoring your stats any more?  Blasphemy! :p

To be fair you're probably right, I get packet loss sometimes on my VPNs and I do wonder if that is due to being fastpath.  Although I'd expect if it was high enough to impact the VPN then it would probably have caused DLM to kick in by now.  It did once on my poorer line but recovered back to fastpath later.
Title: Re: Caught out
Post by: g3uiss on December 30, 2019, 11:30:12 PM
 :D That’s my comment. ! Thanks @AA
Title: Re: Caught out
Post by: mrk26 on December 31, 2019, 11:59:31 AM
I think is worth to try eci modem or any modem with lantiq chipset if you are on eci cabinet. My line is stable now and I'm on eci cabinet as well. I tried few different modems with different chipset. And what I realised with eci modem on eci cab you still get fec errors on fastpatch (not many on my line) but when I plugged zyxel VMG1312-B10A I got more crc errors(not many but more than with eci modem ) because on broadcom chipset there is no fec errors correction on fastpatch. So basically if you got issues with high amount of errors, with lantiq chipset modem on fast patch most of these crc errors will be corrected. I may be wrong but this is what I observed on my line.
Title: Re: Caught out
Post by: g3uiss on December 31, 2019, 12:38:10 PM
How did you monitor your line using a Lantique chipset modem ?

I was under the impression even on Fastpath US has some system that generates FEC’s. Not many but some.

Also Zen have offered to request a DLM reset but I’m delaying that until after the festive season as my REIN ( suspected) might have gone !

Title: Re: Caught out
Post by: mrk26 on December 31, 2019, 01:52:14 PM
I use eci modem with chaos calmer, so there is a kind of stats to view.
Title: Re: Caught out
Post by: g3uiss on December 31, 2019, 02:27:04 PM
Not aware of that but thanks. I haven’t any suitable modem so I’m just going to wait and get a DLM reset mid January hopefully by which time the noise will have gone.

Thanks. Tony
Title: Re: Caught out
Post by: mrk26 on December 31, 2019, 02:44:25 PM
All info in this thread https://forum.kitz.co.uk/index.php/topic,15918.0.html (https://forum.kitz.co.uk/index.php/topic,15918.0.html)
Also eci modems should be fairly cheap on ebay if you want to try.
Title: Re: Caught out
Post by: kitz on January 01, 2020, 10:33:05 PM
Wow!  Thats a very high rate of errors on the 29th - well above the known ILQ red limits.  :(

I was looking at your line stats and was just about to say its amazing the line isnt interleaved - then I noticed the date on the summary page....  and your further post above saying that DLM did take action. :'(

All you can do now really is leave it a few weeks and hope that DLM reverses the action.   I doubt the ISP would be too willing to do anything within a couple of weeks..  from memory the instructions to the ISPs was that resets should only be requested if it appeared stuck.   I waited 6 weeks and mine didn't shift..  I probably could have contacted them sooner but I was a bit busy and I was hoping it would correct itself.    However since you have already contacted Zen and they are aware that it's a one off thing, you could probably try getting them to request a reset after about 2 wks if it hasn't already moved itself by that time.
Title: Re: Caught out
Post by: g3uiss on January 02, 2020, 08:11:51 PM
Thanks @kitz. Zen have already offered a reset. Can one estimate from the FEC ( CRCs that didn’t happen) what the CRC / ES might be if interleave removed ?

No point in asking for a reset if the noise source is still there.

Tony
Title: Re: Caught out
Post by: kitz on January 03, 2020, 01:46:22 PM
Not really .    If you are seeing hundreds/ thousands of FEC's it doesnt necessarily mean they will all convert to CRCs once error correction is removed.    Any spike patterns should still show up though on the graph.