Print

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

[meritez]

interleave is enabled, add in pppoe handshake and you are at the max of your connection.
So here's your choice, leave it alone and see if it goes to fastpath on it's own, and if not then enjoy your line performing incredibly well for a SOGEA connection.

[tubaman]

interleave is enabled, add in pppoe handshake and you are at the max of your connection.
So here's your choice, leave it alone and see if it goes to fastpath on it's own, and if not then enjoy your line performing incredibly well for a SOGEA connection.

Yes, it is what it is. I suspect you have a crosstalker that has lost you a bit of speed. As @meritez says it may go back to fastpath on it's own but if not you still have a very decent connection. My own connection used to sync at about 48Mbps but as more people in the vicinity got connected it dropped to just under 44Mbps, and I can only get that by using my own modem as if I use the BT 'Smart' Hub 2 modem it only manages 37Mbps. It's irritating but there is nothing that that can be done about it so I accept it for what it is.

[adslmax]

@meritez

My SoGEA never get on fastpath. It's always staying interleaved on downstream from the Huawei cabinet (the fastpath only on upstream). I can't remember when was the last time my FTTC was on fastpath on both downstream and upstream (probably in 2018 when there is brand new Huawei fibre to the cabinet). It's been nearly 2 days now as the High Rx-tx 1.00 haven't removed yet by DLM.

Code: [Select]

Downstream Upstream
Line attenuation (dB):  11.8 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 79936 19999
SNR margin (dB):        4.4 15.2
Power (dBm):            12.4 0.1
Interleave depth:        8 1
INP:                    52.00 0
G.INP:                  Enabled Not enabled
Vectoring status:        5 (VECT_UNCONFIGURED)

RSCorr/RS (%):          0.0002 0.0159
RSUnCorr/RS (%):        0.0000 0.0000
ES/hour:                0 2.14

Code: [Select]

Downstream Upstream
General
rtx_tx          11921            0               
rtx_c            463              0               
rtx_uc          0                0               
LEFTRS          0                0               
minEFTR          79925            0               
errFreeBits      200694378        0               
Bearer 0
RxQueue          124              0               
TxQueue          31              0               
G.INP Framing    18              0               
G.INP Lookback  31              0               
RRC Bits        0                24             
Interleave depth 8                1               
INP              52.00            0.00           
INPRein          1.00            0.00           
Delay            0                0               
Bearer 1
Interleave depth 3                0               
INP              4.00            0.00           
INPRein          4.00            0.00           
Delay            3                0

Code: [Select]

Since Link time = 1 days 21 hours 47 min 17 sec
FEC:            1396            295
CRC:            0               100
ES:             0               89
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0


[tubaman]

... It's been nearly 2 days now as the High Rx-tx 1.00 haven't removed yet by DLM.
...

You just need to leave it alone and hope that DLM moves it back to ReTx Low at some point but it may not. You still have a decent fast connection so just use it and stop needlessly worrying about a few Mbps that make little or no difference to how you can use the service. I get that it is annoying when the line isn't working as perfectly as it once was but that is the nature of VDSL and at present you certainly don't have any reason to complain to your ISP about it.

[meritez]

@adslmax

If fastpath is disabled across the card you are connected to in the Huawei cabinet, which will affect between 32 to 64 SOGEA/FTTC/EoFTTC circuits on the same card, this will be an Openreach DLM decision because of cross talk across multiple ports.

I'd leave it a week and then let us know if the stats have changed.

[adslmax]

No problem at all.  Will leave it alone.  Look like FTTP has cancelled for this July moved into next April 2026 say openreach email.  Disappointed don't know why it pushed back.

[Chrysalis]

So this triggered you to order g.fast again max? As I see you made a new thread on it.

Order something like VM where this stuff doesnt happen and live happily ever after.

Regarding OR FTTP rollout, more and more hints keep coming out that their rollout seems prioritised on where they are losing the most customers.  So plans are dynamic and do change.  Because your area has g.fast it likely doesnt have as heavy customer losses as VDSL/ADSL only areas.  My area isnt due till 2026 either, and originally had no plans at all, likely because OR had barely any customers to lose.

[kitz]

I see things in this thread that make me itch each time Ive opened it as there seem to be some misconceptions.

>> fastpath on both downstream and upstream

Need reminder about use of the interleaved path does not mean the line is actually interleaved.

I cant recall the exact date, but was about 2016/17  BT/Openreach now reserve the FAST channel path for time critical data such as BT-TV and all normal data traverses using the Interleaved path.  Setting the value of Interleaving to 1 is the same as FAST.

Please, please dont think that you will go back to using the FAST path. Stop expecting your modem stats to show FAST path.
Openreach uses DLM.  All data is sent using the interleaved channel so that they can configure changes such as the depth of interleaving. If interleaving isnt required then it can easily be switched off on the interleaved path.

Using just FAST path for data transmission belongs back in the days when lines had fixed rates and no DLM.  The days when the target SNRMargin was set at 9dB.  The days when a line could either sync at the line rate - or it couldnt.  I doubt few people will remember the days when 2Mbps was brought out and how many lines could not get that speed.

I know that you hate the DLM.  That is only because you have a relatively short line that can sync at high speed. Without the DLM though there would be hundreds of thousands of lines unable to be stable and sync as fast as the available frequencies allow.  Use of the Interleaved path allows Openreach to configure changes that best suit the line and keep it in sync.  FAST path is on or off.  Interleaved path is configurable.

----------------
We very often incorrectly use the term "Interleaving".  We are all guilty of it.
We say Interleaving has been switched on, when we should in fact be using the term Error Protection.
Interleaving is used with RS encoding to send redundant data that can be used to recover corrupt data.

Interleaving - or rather error protection - is an overhead. RS encoding increases the overheads by ~8%.  These overheads are sent in out-of-band channels (OOB) that are not available to normal data.

Basically when you turn on RS encoding, it increases the amount of overheads. These overheads are assigned to OOB which reduces the amount of channels available for sync.  This is why the sync speed reduces when we see Interleaving has been switched on.

Therefore if you sync at 78,000 Interleaving and RS do not reduce the throughput of 78Mb. Typically its the more standard TCP/IP and application layer type protocols that affect throughput.

So we have the configurable interleaving path.  The path has 2 configurable bearer channels.
Without going in depth we have G.INP which use the 2nd bearer.  Retransmission is done at the physical layer by the modem on the real time data. Retransmission affects throughput overheads.

Thanks for this useful information.

Look like the SoGEA Rx High is staying on for more than 5 days now. Look like DLM is happy to leave downstream Rx High enabled but strange there is no downstream CRC , ES, SES for more than 5 days (Zero!) Clean health line.

Code: [Select]

Interleave depth 8                1               
INP              52.00            0.00           
INPRein          1.00            0.00           
Delay            0                0               
Bearer 1
Interleave depth 3                0               
INP              4.00            0.00           
INPRein          4.00            0.00           
Delay            3                0


[adslmax]

Look like tubaman was 100% right as DLM actioned to put me back on 79999Kbps on downstream after capped 60000Kbps but still refused to removed INP 1.0 High Retx. Look like have to give up then. The throughput speed was low 69Mbps (used to be 74Mbps without High Retx) Losing 11Mbps from overhead seem stupid from DLM High Retx! Evil DLM! 

Code: [Select]

adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    0
Last initialization procedure status:   0
Max:    Upstream rate = 25974 Kbps, Downstream rate = 87048 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 79999 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):        4.4             15.4
Attn(dB):        11.9            0.0
Pwr(dBm):        12.4            0.8

Bearer 0
INP:            52.00           0.00
INPRein:        1.00            0.00
delay:          0               0
PER:            0.00            3.98
OR:             0.01            64.22
AgR:            80244.76        20063.54

Bearer 1
INP:            4.00            0.00
INPRein:        4.00            0.00
delay:          3               0
PER:            16.06           0.01
OR:             95.62           0.01
AgR:            95.62   0.01

Bitswap:        1880/1880               6/6

Total time = 13 hours 21 min 10 sec
FEC:            199             159
CRC:            0               32
ES:             0               30
SES:            0               0
UAS:            30              30
LOS:            0               0
LOF:            0               0
LOM:            0               0


Code: [Select]

adsl info --pbParams
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    0
Last initialization procedure status:   0
Max:    Upstream rate = 25974 Kbps, Downstream rate = 86873 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 79999 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Discovery Phase (Initial) Band Plan
US: (7,32) (871,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3959)
Medley Phase (Final) Band Plan
US: (7,32) (871,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3959)
                  VDSL Port Details               Upstream                Downstream
Attainable Net Data Rate:           25974 kbps              86873 kbps
Actual Aggregate Tx Power:             0.8 dBm               12.4 dBm
====================================================================================
  VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
  Line Attenuation(dB): 4.1 14.4 20.9 N/A N/A 7.1 17.1 28.0
Signal Attenuation(dB): 4.1 13.9 20.2 N/A N/A 9.4 16.9 27.9
        SNR Margin(dB): 15.4 15.4 15.4 N/A N/A 4.4 4.4 4.4
         TX Power(dBm): -14.1 -29.5 0.6 N/A N/A 8.2 7.5 7.2


[tubaman]

Look like tubaman was 100% right as DLM actioned to put me back on 79999Kbps on downstream after capped 60000Kbps but still refused to removed INP 1.0 High Retx. Look like have to give up then. The throughput speed was low 69Mbps (used to be 74Mbps without High Retx) Losing 11Mbps from overhead seem stupid from DLM High Retx! Evil DLM! 

I suspected that would be the case unfortunately. It's still a great connection, better than most, so just enjoy it for what it is.

[adslmax]

I suspected that would be the case unfortunately. It's still a great connection, better than most, so just enjoy it for what it is.

Yes but never understand why DLM love to reduced the speed by 9% oh well, nothing the ISP can do it about it. As Martin say below

Hi Philip,

We have asked them 3 times now to reset the DLM, each time they are advising that they won't as everything is within their acceptable service contraints.

Kind Regards,

Martin Pitt
Managing Director

[adslmax]

Finally at last DLM has now removed high retx on Bearer 0 with INP 48 and Interleave dept 16 with INP 0.00. Throughput speed now returned to 74.8Mbps

 

[kitz]

The ISP requested DLM reset isn't the same as an engineer reset.   Only an Openreach engineer can perform a reset that returns the line to an open profile and starts the DLM again with a blank profile. 
For an ISP reset there are several conditions that must be met before OR will reset the line. They are not allowed to request a reset unless there was a fault-fix found or unless the profile was stuck and the line was now stable and not generating any errors for a considerable period of time.  None of these were the case for your line.
The ISP reset is done via NCAS and by default sets the line to interleaving/high ReTX and 6.2dB Target SNRM.   You could end up worse off by requesting an ISP DLM reset which removes any 3/4/5 dB and sets the higher rate of error protection - be that Interleaving or re-tx.   You should know this.

I had high re-tx for a year, it never bothered me because I really didnt notice a few Mbps less speed.. I doubt that you would notice either if it wasnt for the fact you probably  used more bandwidth doing speedtests than anything else.

>>  DLM actioned to put me back on 79999Kbps <<

As it does every single time.  Max think about this please.

• Every few months your line will experience some errors.
• The DLM will take action by removing any 'x'dB Target SNRM and increasing the error protection (be that interleaving or re-tx h]igh).
• Max does a speed test and his line is a couple ofMbps slower.  If it werent for the speed test or unless you are doing lots and lots of large downloads, there is no way on earth that you would 
• You panic, you call the DLM evil, you (incorrectly) think that your line is banded
• You hound your ISP for a DLM reset
• The ISP says they cant request a reset
• A couple of days later, the DLM automatically reduces your profile on its own accord.
• Every. single. time.

There must be over a dozen posts on this forum where you say your line is banded, only for the DLM to sort it itself in a few days. 
For someone who pays such attention to your line stats these are things you should know.  With all due respect you focus on the negative and get yourself in a tizz.

I tell you this, because you put yourself through so much grief.  How much time over the last week have you spent worrying about it, how much additional work have you caused your ISP - even if that is just answering tickets, that still takes time for a member of staff. :/