Hi just recently managed to acquire a billion 8800axl nearly new to replace the awful BT home hub 6, which I'm really pleased with and BT have no control of have got some interleaving on the downstream due to reboots although the stats on the 8800axl are very good can't seem to find crc errors unless they are listed as something else?
Current stats
Status
xDSL
xDSL
Mode VDSL2
Traffic Type PTM
Status Up
Link Power State L0
Downstream Upstream
Line Coding (Trellis) On On
SNR Margin (dB) 6.5 13.1
Attenuation (dB) 17.4 0.0
Output Power (dBm) 5.5 5.5
Attainable Rate (Kbps) 65687 21223
Rate (Kbps) 53591 9995
B (# of bytes in Mux Data Frame) 51 235
M (# of Mux Data Frames in an RS codeword) 1 1
T (# of Mux Data Frames in an OH sub-frame) 64 7
R (# of redundancy bytes in the RS codeword) 12 16
S (# of data symbols over which the RS code word spans) 0.0309 0.7508
L (# of bits transmitted in each data symbol) 16584 2717
D (interleaver depth) 1049 1
I (interleaver block size in bytes) 64 255
N (RS codeword size) 64 255
Delay (msec) 8 0
INP (DMT symbol) 3.00 0.00
OH Frames 76565892 12757584
OH Frame Errors 191 17
RS Words 2420999167 1739885
RS Correctable Errors 272727 124
RS Uncorrectable Errors 22486 0
HEC Errors 5669 0
OCD Errors 0 0
LCD Errors 0 0
Total Cells 2767514283 0
Data Cells 13737942 0
Bit Errors 0 0
Total ES 21 17
Total SES 0 0
Total UAS 0 0
Billion 8800axl CRC errors
-
- Posts: 22
- Joined: Sat May 06, 2017 3:10 pm
Re: Billion 8800axl CRC errors
OH Frame Errors are the same as CRC errors
-
- Posts: 9
- Joined: Thu May 11, 2017 8:44 pm
Re: Billion 8800axl CRC errors
Hi thanks piston for the reply, have just used dslstats programme and can get full stats with this programme which is brilliant, what a fantastic router this 8800axl is never using a isp supplied router again !
-
- Posts: 124
- Joined: Mon Mar 06, 2017 11:59 am
- Location: Newton Poppleford, Devon, UK
- Contact:
Re: Billion 8800axl CRC errors
Yeah, I've no idea why the xDSL page firstly uses different terms and secondly displays less information than on the telnet interface...
William Grimsley.