Print

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

[William Grimsley]

The extra stats are now available coinciding with the release of a new DSLstats version so if you are using DSLstats and want to see them you'll need to upgrade otherwise they mostly show zero!  More on the post below.:

http://forum.kitz.co.uk/index.php/topic,17106.msg314386.html#msg314386

This is a first stab at them but I suspect there will need to be some changes...

Just upgraded. Good job! How are my additional stats looking?

[William Grimsley]

On the line, 100889 Downstream FEC's occured within a minute at 06:42. On the line, the Downstream interleaver depth is 8. Should I be concerened?

[burakkucat]

No, I don't think you should be concerned. Consider those 100,889 FECs DS to be "CRCs that never occurred", as the error detection and correction is working well.

DS Interleave depth of 8 confirms that the circuit is currently operating with a moderate degree of interleaving. Again, nothing to cause any concern.

Clearly the DLM considers that a moderate degree of interleaving is the most appropriate means of stabilising your circuit.

[William Grimsley]

No, I don't think you should be concerned. Consider those 100,889 FECs DS to be "CRCs that never occurred", as the error detection and correction is working well.

DS Interleave depth of 8 confirms that the circuit is currently operating with a moderate degree of interleaving. Again, nothing to cause any concern.

Clearly the DLM considers that a moderate degree of interleaving is the most appropriate means of stabilising your circuit.

That's what I thought. So, would that mean if the Downstream interleaver depth was OFF then those 100889 FEC's would have been CRC's? So, the line would have dropped out?

[burakkucat]

If 100,889 CRCs had been recorded then I would definitely be looking for their source.

I would not like to predict how the circuit would have responded if those FECs had been CRCs!

You might be interested to take a look at a forum thread that I started back in July 2015.

[ejs]

I thought the interleaving depth of 8 was just a typical value that goes with G.INP being enabled - the retransmission ability of G.INP provides far greater error correction ability than the interleaving depth of 8 does (which is a low value, especially for VDSL2).

[William Grimsley]

Just had what I think was a DLM resync, but nothing on my line has changed except I got 1159 CRC errors. The line is clear. But, the last retrain was an RDI, what is that?

Line stats after resync:

Mode   VDSL2
Traffic Type   PTM
Status   Up
Link Power State   L0
Downstream   Upstream
Line Coding (Trellis)   On   On
SNR Margin (dB)   9.0   6.4
Attenuation (dB)   25.7   0.0
Output Power (dBm)   12.0   5.5
Attainable Rate (Kbps)   42484   8935
Rate (Kbps)   35000   8495
B (# of bytes in Mux Data Frame)   73   97
M (# of Mux Data Frames in an RS codeword)   1   1
T (# of Mux Data Frames in an OH sub-frame)   0   0
R (# of redundancy bytes in the RS codeword)   6   8
S (# of data symbols over which the RS code word spans)   0.0666   0.3658
L (# of bits transmitted in each data symbol)   9610   2318
D (interleaver depth)   8   8
I (interleaver block size in bytes)   80   106
N (RS codeword size)   80   106
Delay (msec)   0   0
INP (DMT symbol)   54.00   43.00
OH Frames   0   0
OH Frame Errors   1159   0
RS Words   370220584   3239991
RS Correctable Errors   77897   137
RS Uncorrectable Errors   0   0
HEC Errors   0   0
OCD Errors   0   0
LCD Errors   0   0
Total Cells   416565096   0
Data Cells   2584488   0
Bit Errors   0   0
Total ES   44   0
Total SES   42   0
Total UAS   77   56

[burakkucat]

RDI = Rmote Defect Indication. 

[William Grimsley]

Ooo, I've had another drop out. G.INP and interleaving removed from upstream as well as a bit of G.INP from downstream, but my downstream is still banded!

Line stats after resync:

Mode   VDSL2
Traffic Type   PTM
Status   Up
Link Power State   L0
Downstream   Upstream
Line Coding (Trellis)   On   On
SNR Margin (dB)   9.9   6.3
Attenuation (dB)   25.6   0.0
Output Power (dBm)   11.9   5.1
Attainable Rate (Kbps)   44538   8051
Rate (Kbps)   35000   8051
B (# of bytes in Mux Data Frame)   73   239
M (# of Mux Data Frames in an RS codeword)   1   1
T (# of Mux Data Frames in an OH sub-frame)   0   43
R (# of redundancy bytes in the RS codeword)   6   0
S (# of data symbols over which the RS code word spans)   0.0666   0.9472
L (# of bits transmitted in each data symbol)   9610   2027
D (interleaver depth)   8   1
I (interleaver block size in bytes)   80   120
N (RS codeword size)   80   240
Delay (msec)   0   0
INP (DMT symbol)   52.00   0.00
OH Frames   0   0
OH Frame Errors   1730   0
RS Words   229263944   3298142
RS Correctable Errors   320   0
RS Uncorrectable Errors   0   0
HEC Errors   0   0
OCD Errors   0   0
LCD Errors   0   0
Total Cells   257988759   0
Data Cells   1897917   0
Bit Errors   0   0
Total ES   55   0
Total SES   53   0
Total UAS   116   84

[William Grimsley]

Ok, so it's been 6 weeks yes 6 WEEKS since I started doing the disconnects and my line has still not returned back to normal. This seems a little long to me. #Frustrated

[William Grimsley]

My line just had 1 Upstream SES. Here comes another line fault...

[NewtronStar]

Ok, so it's been 6 weeks yes 6 WEEKS since I started doing the disconnects and my line has still not returned back to normal. This seems a little long to me. #Frustrated

The only alternative is to find away to get an Openreach broadband engineer to visit your premises under the suspicion there is a broadband fault, and they will do the normal tests and that should include a line reset/DLM and this should fix your banding issue.

of course there is a 50/50 chance you will be charged so flip a coin and I bet you don't get charged this time 

[William Grimsley]

The only alternative is to find away to get an Openreach broadband engineer to visit your premises under the suspicion there is a broadband fault, and they will do the normal tests and that should include a line reset/DLM and this should fix your banding issue.

of course there is a 50/50 chance you will be charged so flip a coin and I bet you don't get charged this time 

Oh, I wish! I have damaged some of my wires in the box which is Openreach property. I do have a friend who is an Openreach engineer. Maybe I should contact him?

Is it possible that my line banding won't be removed?

[NewtronStar]

Is it possible that my line banding won't be removed?

Well the DLM stuck me on the interleaving profile for most of my Infinity 1 life until and Openreach engineer did a DLM reset but thank god for G.INP as I was getting 2000 ES per day on fastpath.

So yes the DLM can become stuck even if the line has seen no issues for 3 -12 months

[William Grimsley]

Hmmm, I might have to think about it then.

My new MDWS ID is WilliamG.