Billion UK Forum

Grimers wrote: ↑Sat Jul 21, 2018 3:26 pm Not really, bitswapping has disabled itself again.

One both the 8800NL and 880AXLR2?? (Does the DSL drop on any of the two devices??)

Grimers wrote: ↑Thu Oct 12, 2017 10:59 am Hi billion_fan,

The upstream ES and now SES counters on both downstream and upstream are broken. The upstream ES counter seems to go up even when there's nothing to cause it and sometimes (on both downstream and upstream) when there's only a few CRC's (say 2) in an ES, it reports it as a SES (AFAIK, 9 + CRC's make an SES). Also, sometimes when there are more than 9 CRC's in an ES (in this example 12) it just reports it as an ES not SES.

I hope I've explained it ok, as I've noticed I've mentioned "ES" and "SES" several times in the previous paragraph.

Here's a screenshot from the telnet interface:



Thanks!

You have been complaining about this since October 2017.
You read a couple pages on the kitz website and you think you know more than Broadcom engineers.

I'll clear a few things up for you...

SES - Severely Errored Seconds

As the name indicates this is more worse than an Errored Second (which only needs one event to trigger an ES).
A Severely Errored Second is a one second period which contains 30% or more errored blocks OR several other events such as one or more OOF.

Note: It has been observed that a LOS event may be preceeded by a SES if the LOS was not preceeded by a LPR event. ie The dying gasp message appears to prevent an additonal SES being recorded before an LOS.

9+ CRC's don't make an SES

You CAN have more ES than CRC. It isn't only CRC that cause ES

ES - Errored Seconds

A one second period of time in which either one or more coding violations occurred OR at least one Loss of Signal events occurred.

Its not unusual to see occasional ES and its best looking at the broader picture. Some routers will display the ES over 15 min periods (900 seconds), therefore a couple of errored seconds will probably go un-noticed. BT uses the ES count for its DLM.

Read that? one or more code violations. That isn't just CRC's.
You have G.INP running also.

You also complained the rtx_tx value doesn't reset.
The rtx_tx value doesn't reset on ANY Broadcom modem it is a value held by the DSLAM.

I can't see a single issue that you have posted that is actually an issue. They are all very obscure Broadcom CLI display complaints that you have misunderstood.

Even if it was showing a single ES incorrectly (it isn't) what effect is it having over the devices performance?
None.

As you've been advised on 2 other forums (kitz/thinkbroadband) you need to stop obsessing over the stats on your modem and use the internet for what it is there for.

You have had the Billion staff back and forward to their engineers and giving out test firmwares over nearly 8 pages because you misunderstand the inner workings of xDSL.

...

Anyway, downstream bitswapping seems to still be stopping randomly, and also occasionally, out of the blue, some websites cannot be accessed on all devices connected to the router. Both of these issues are fixed by initiating a resync.

We're also still experiencing the same issues I reported a while back, with the TV...

Make that Euro Truck Simulator 2, too. Sigh...

Fixed! Had to downgrade the firmware to 2.52.d5, so there's an issue with the latest firmware.

Ok, it looks like I'm joining the bandwagon with another rebooting R2! Apparently, there's a test firmware that may fix this! Please confirm?

Grimers wrote: ↑Mon Oct 01, 2018 5:55 pm Ok, it looks like I'm joining the bandwagon with another rebooting R2! Apparently, there's a test firmware that may fix this! Please confirm?

Official firmware can found below

http://www.billion.uk.com/esupport/inde ... are-252d11

Thanks.