Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: pintosal on March 01, 2016, 03:35:23 PM
-
I regularly use DSLSTATS to monitor my Billion 8800 NL on my Infinity 2 and would like some advice.
The attached show CRC, FEC and ES/hour.
Is there a problem with my line? Why would there appear to be CRC errors upstream, but not down?
-
You may have G.Inp enabled on the downstream. A copy of the Stats page from DSLstats will confirm it (or not).
-
Indeed, G.Inp is enabled downstream
-
That's the reason then. G.Inp is very effective at dealing with errors which would otherwise be CRCs.
-
Regarding my first post, are these number of errors indicative of problems, or is my line in good order?
-
Regarding my first post, are these number of errors indicative of problems, or is my line in good order?
I would say your line is fine, just keep monitoring the Upstream CRC errors. If they start to become more frequent, it could be a sign of a fault occuring.
-
My line had upstream error seconds like you, then I enabled PhyR on the upstream within the Billion settings:
(https://i.gyazo.com/4a35be69890333df7519084b35221876.png)
Around 11 days later the cabinet re-synced the connection and enabled G.INP on the upstream not had a single error since
(https://i.gyazo.com/a6acff6729af568015993444b742af5f.png)
(I think the spike of downstream errors is when the line disconnected for the re-sync)
So maybe the cabinet will enable G.INP for you too on the upstream?
-
Thanks for the suggestion.
PhyR was only enabled on downstream. I'll try it on upstream also.