Print

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

[underzone]

No that is plenty, just wait.

[mrk26]

Well, it looks like you getting a lot of FEC errors, which may be considered by DLM that is why may not taking positive action, especially that you run for 12 days now.

[adslmax]

Here is my FTTC stats between 2014 and 2020 (80/20 with Plusnet)

[underzone]

Yeah maybe set 40000 then. 12+ days is too long. Mine takes 4 days every time to get INPRein=0 (lots of recent ISP changes and DLM resets)

[GigabitEthernet]

Yeah maybe set 40000 then. 12+ days is too long. Mine takes 4 days every time to get INPRein=0 (lots of recent ISP changes and DLM resets)

Was this referring to me?

I'm already at 40,000.

[GigabitEthernet]

Unfortunately still no change on my line, I obviously have not capped the line enough.

[chuffer]

For any of you here who might have been following the later posts re high sync and low download speed.

It has been moved here.

https://forum.kitz.co.uk/index.php/topic,25098.15.html

[GigabitEthernet]

I've given this another go.

Capped line to 35000Kbps, before I think the issue was I was still clocking up a fairly high number of FECs which I think prevents DLM from taking positive action?

Does anyone have ideas about what level they would need to get down to, to ensure DLM takes the action and puts me on retransmission low?

[tiffy]

I've given this another go.

Capped line to 35000Kbps, before I think the issue was I was still clocking up a fairly high number of FECs which I think prevents DLM from taking positive action?

Does anyone have ideas about what level they would need to get down to, to ensure DLM takes the action and puts me on retransmission low?

You may find my experiencies as related in this recent post relevant:
https://forum.kitz.co.uk/index.php/topic,25214.msg423411.html#msg423411

I have managed to retain DS G.Inp low re-tx profile to date with an average FEC error/hr daily rate of approx 12000 as reported by DSLStats which I run 24/7, odd days are much higher/lower and my modem DS 40 Mbps clamp is still applied.

Yeah maybe set 40000 then. 12+ days is too long. Mine takes 4 days every time to get INPRein=0 (lots of recent ISP changes and DLM resets)

My line took 14 days with a fairly severe DS modem clamp applied before DLM action intervened and changed to re-tx low profile. 

[GigabitEthernet]

Thanks @tiffy, with 35000 applied I am running just under 10,000 FECs per hour (only been applied for 12 hours or so).

We will see if this has any impact.

Am I right in saying if I get re-tx low, I will not need to keep the FECs low as DLM only applies positive action, not negative in regards to FECs?

[tiffy]

Am I right in saying if I get re-tx low, I will not need to keep the FECs low as DLM only applies positive action, not negative in regards to FECs?

Have not seen a definitive forum answer to that question, lots of different opinions, my interpretation is that DLM is probably more tolerant to higher FEC rates when re-tx low profile has been achieved with respect to consequential re-application of re-tx high profile.

I still do my best to maintain the lowest possible DS FEC rates and as outlined in the previously referenced thread have kept a DS 40 Mbps modem clamp applied even though by provisioned service is only 40/10 and my line will only ever be capable of marginally over 40 Mbps DS synch. under any provision, appears to help, can't really explain why.

[GigabitEthernet]

Thanks again @tiffy, I will run the 35000 cap for as long as possible as it takes for DLM to act.

Current stats:

Code: [Select]

adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    0
Last initialization procedure status:   0
Max:    Upstream rate = 8150 Kbps, Downstream rate = 65577 Kbps
Bearer: 0, Upstream rate = 8150 Kbps, Downstream rate = 35000 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State:       L0
Mode:                   VDSL2 Annex B
VDSL2 Profile:          Profile 17a
TPS-TC:                 PTM Mode(0x0)
Trellis:                U:ON /D:ON
Line Status:            No Defect
Training Status:        Showtime
                Down            Up
SNR (dB):        18.7            6.1
Attn(dB):        23.3            0.0
Pwr(dBm):        12.1            3.9

                        VDSL2 framing
                        Bearer 0
MSGc:           -6              26
B:              73              249
M:              1               1
T:              0               40
R:              6               4
S:              0.0000          0.9746
L:              9610            2085
D:              8               1
I:              80              127
N:              80              254
Q:              8               0
V:              5               0
RxQueue:                130             0
TxQueue:                26              0
G.INP Framing:          18              0
G.INP lookback:         26              0
RRC bits:               0               24
                        Bearer 1
MSGc:           90              -6
B:              0               0
M:              2               0
T:              2               0
R:              16              0
S:              10.6667         0.0000
L:              24              0
D:              1               0
I:              32              0
N:              32              0
Q:              0               0
V:              0               0
RxQueue:                0               0
TxQueue:                0               0
G.INP Framing:          0               0
G.INP lookback:         0               0
RRC bits:               0               0

                        Counters
                        Bearer 0
OHF:            0               854979
OHFErr:         0               63
RS:             3508958752              226632
RSCorr:         153502          285
RSUnCorr:       0               0
                        Bearer 1
OHF:            3651424         0
OHFErr:         0               0
RS:             21908171                0
RSCorr:         7               0
RSUnCorr:       0               0

                        Retransmit Counters
rtx_tx:         13324416                0
rtx_c:          1568            0
rtx_uc:         0               0

                        G.INP Counters
LEFTRS:         0               0
minEFTR:        34994           0
errFreeBits:    31312492                0

                        Bearer 0
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    3947631486              0
Data Cells:     75927408                0
Drop Cells:     0
Bit Errors:     0               0

                        Bearer 1
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    0               0
Data Cells:     0               0
Drop Cells:     0
Bit Errors:     0               0

ES:             0               46
SES:            0               0
UAS:            208             208
AS:             58661

                        Bearer 0
INP:            54.00           0.00
INPRein:        1.00            0.00
delay:          0               0
PER:            0.00            9.78
OR:             0.01            26.16
AgR:            35418.64        8176.72

                        Bearer 1
INP:            2.50            0.00
INPRein:        2.50            0.00
delay:          0               0
PER:            16.06           0.01
OR:             47.81           0.01
AgR:            47.81   0.01

Bitswap:        35302/36981             67/67

Total time = 16 hours 21 min 9 sec
FEC:            153502          285
CRC:            0               63
ES:             0               46
SES:            0               0
UAS:            208             208
LOS:            0               0
LOF:            0               0
LOM:            0               0
Latest 15 minutes time = 6 min 9 sec
FEC:            123             7
CRC:            0               5
ES:             0               4
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Previous 15 minutes time = 15 min 0 sec
FEC:            245             0
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Latest 1 day time = 16 hours 21 min 9 sec
FEC:            153502          285
CRC:            0               63
ES:             0               46
SES:            0               0
UAS:            208             208
LOS:            0               0
LOF:            0               0
LOM:            0               0
Previous 1 day time = 0 sec
FEC:            0               0
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Since Link time = 16 hours 17 min 41 sec
FEC:            153502          285
CRC:            0               63
ES:             0               46
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
I have - somewhat rarely - vectoring on my line, so will be interesting to see if this makes any difference to the results.

I don't know if my line is just very noisy but without a cap I get millions and millions of FECs, never seemed to cause any harm to the usage of the connection (as they are corrected) but I wonder if this is why I have always been stuck on re-tx high. At one stage I was able to achieve 10Mb up on the upstream (when I first had the circuit provisioned, I had 55/10 and that is exactly what I got) but over time my upstream seems to have dropped. But it can't be crosstalk as I believed vectoring would stop that from having an impact.

[tiffy]

I have - somewhat rarely - vectoring on my line, so will be interesting to see if this makes any difference to the results.

Indeed, one of the very few.
My perhaps simplistic understanding of vectoring technology is that it should certainly help if not completely eliminate the effects of crosstalk on the line from FTTC cabinet to user.
Why you DS synch has dropped to 35,000 Kbps with 55/10 provision and vectoring in service, don't know.
Very round figure, could your line be banded ?

FECs, never seemed to cause any harm to the usage of the connection (as they are corrected)

This was my initial thinking also, errors that the technology has pre-corrected, however, the FEC error rate does seem to be at least one of the factors which DLM considers with respect to G.Inp re-tx profile control, as previously stated, how much this effects low to high re-tx migration via DLM is not clear.
However, quite a few forum patrons have positively established that once on DS re-tx high profile, reducing the FEC error rate by modem DS synch speed clamping will eventually produce DLM action to change re-tx profile to low.

Of course, the modem DS speed clamp will also have the effect of reducing other factors such as G.Inp LEFTRS and  rtx_uc rates which some believe are in the DLM control equasion as well ?

[GigabitEthernet]

Sorry @tiffy, I have merged two issues - and have confused you and me in the process!

What I mean is: I have purposefully capped my line to 35Mb on the downstream, in order to try and achieve Re-TX low as you have advised above. That is what you see in the stats I posted.

My other - separate - issue is that over time I have seen that my upstream sync has reduced. Initially I was able to achieve sync of over 10Mb and that has dropped to around 8 over the last year or two. This is not due to my capping of the line. When I originally went live back in 2015, I was able to achieve the full 55/10 and that was what I was provisioned on. I was later "uncapped" and I at one stage achieved 10.5Mb on the upstream.

Sorry for any confusion.

[tiffy]

What I mean is: I have purposefully capped my line to 35Mb on the downstream, in order to try and achieve Re-TX low as you have advised above. That is what you see in the stats I posted.

Of course, had read and registered that earlier, apologies, senior moment on my part !

Not sure on vectoring technology, is it aplicable to both DS and US or is that a silly question ?