Kitz Forum

Broadband Related => FTTC and FTTP Issues => Topic started by: tommy45 on October 31, 2019, 02:18:55 PM

Title: DLM not working as it should
Post by: tommy45 on October 31, 2019, 02:18:55 PM
Dlm seems to be taking negative action  for no known reason,  the recorded error rates are well within the threshold MTBE always under 100 errored seconds per 24 hr period no ses even the fecs are lowish  , there are no errored  many months ago  dlm  reduced the SNR (downstream) to 4db  but set re trans to hi 50, but my sync was still the max 799952 it today without any logical reason  acted again  still 4db but increased the inp to 51
, this is only a small decrease on sync but my throughput  which was around 72 mbps is now around 68 mbps!!!! what a joke dlm is
DSLAM type / SW version:   BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware:     AnnexA version - A2pv6C038m.d24j
DSL mode:                  VDSL2 Profile 17a
Status:                    Showtime
Uptime:                     0 hour 26 min 33 sec
Resyncs:                   0 (since 31 Oct 2019 13:58:14)
         
            Downstream   Upstream
Line attenuation (dB):     13.7      0.0
Signal attenuation (dB):   Not available on VDSL2      
Connection speed (kbps):   78836      19999
SNR margin (dB):           4.3      15.1
Power (dBm):               12.4      3.9
Interleave depth:          8      1
INP:                       51.00      0
G.INP:                     Enabled      Not enabled
Vectoring status:          5 (VECT_UNCONFIGURED)      

RSCorr/RS (%):             0.0003      0.0002
RSUnCorr/RS (%):           0.0000      0.0000
ES/hour:                   0      0
Title: Re: DLM not working as it should
Post by: Chrysalis on October 31, 2019, 06:37:45 PM
the ES threshold's are fast path, and will very likely be much lower with g.inp/interleave.

I dont know what they are but its probably significantly lower.

Sadly you only posted partial data, the most useful data is omitted from that telnet output.
Title: Re: DLM not working as it should
Post by: tommy45 on October 31, 2019, 07:09:30 PM
Here you go, Also i have been on  G.inp for years and it apart from in the begining has been only applied to the DS  i have had zero ds errors  only upstream  and an increased burst every time the phone rings of around 20 errored secs, this too has been ongoing for a while   but error rates since the SNR was lowered from 6 to 4db, and ret hi applied these error rates have been lower  the most they where before were around 120 per day,  they have been as low as 30 -80 per day  depending on how many incoming calls
Code: [Select]
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 26503 Kbps, Downstream rate = 78376 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 78836 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.3 15.2
Attn(dB): 13.7 0.0
Pwr(dBm): 12.4 3.9
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 243 237
M: 1 1
T: 0 42
R: 10 16
S: 0.0986 0.3781
L: 20618 5374
D: 8 1
I: 254 127
N: 254 254
Q: 8 0
V: 0 0
RxQueue: 88 0
TxQueue: 22 0
G.INP Framing: 18 0
G.INP lookback: 22 0
RRC bits: 0 24
Bearer 1
MSGc: 186 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 5.3333 0.0000
L: 48 0
D: 3 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 497350
OHFErr: 0 19
RS: 758078352 780375
RSCorr: 2878 77
RSUnCorr: 0 0
Bearer 1
OHF: 1167439 0
OHFErr: 0 0
RS: 14008529 0
RSCorr: 0 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 502694 0
rtx_c: 30 0
rtx_uc: 0 0

G.INP Counters
LEFTRS: 0 0
minEFTR: 78821 0
errFreeBits: 22548470 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 2842905297 0
Data Cells: 70674513 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 16
SES: 0 0
UAS: 23 23
AS: 18753

Bearer 0
INP: 51.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 3.98
OR: 0.01 64.22
AgR: 78916.80 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: 3066/3066 1/1

Total time = 5 hours 12 min 56 sec
FEC: 2878 77
CRC: 0 19
ES: 0 16
SES: 0 0
UAS: 23 23
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 12 min 56 sec
FEC: 137 8
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 156 1
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 = 5 hours 12 min 56 sec
FEC: 2878 77
CRC: 0 19
ES: 0 16
SES: 0 0
UAS: 23 23
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 = 5 hours 12 min 31 sec
FEC: 2878 77
CRC: 0 19
ES: 0 16
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
Title: Re: DLM not working as it should
Post by: burakkucat on October 31, 2019, 07:37:07 PM
. . .  i have had zero ds errors  only upstream  and an increased burst every time the phone rings . . .

That is strongly indicative of a joint beginning to show high resistance and/or semi-conductive tendencies. Have you performed a quiet line test recently?
Title: Re: DLM not working as it should
Post by: tommy45 on October 31, 2019, 08:10:24 PM
I did one last week and not a noise out of place, sadly that burst of errors when the voltage increases for incoming calls I'm sure was pointed out to the last OR bod, a few years ago but nothing done about it , guess i need a more conscientious engineer? But if this adverse trend continues I'll be raising a fault with my ISP, unless i start hearing audible oddities during the quiet test that are easily reproduced, been in that situation before nearly cost me a lot of money for the privilege of a RWT result
Title: Re: DLM not working as it should
Post by: ejs on October 31, 2019, 08:25:25 PM
The INP value changing from 50 to 51 does not indicate that the DLM made any changes. The exact INP level, and various other parameters often vary slightly each time it connects even when the DLM has not changed anything. Something other than the DLM may have caused the disconnection.
Title: Re: DLM not working as it should
Post by: tommy45 on October 31, 2019, 09:29:09 PM
@02.56 in the morning i can see what else it could have been, no power outages 100% sure of that My Throughput is also significantly lower too,I have no visibility to my ip profile and haven't done for ages, Zen are aware  but never fixed, it also reports an incorrect sync rate again been ongoing since March this year
Title: Re: DLM not working as it should
Post by: tommy45 on November 02, 2019, 01:38:57 PM
Further to my previous post DLM has change the parameters again, it would appear this time to have reduced the Ds target SNR to 3db from the 4db it had been on for over 200 days, It also has increased the G.inp retx From 51-52 and the RX queuing level   without issue (re sync) as far as i can tell from the stats recorded, the latest stats here:
Code: [Select]
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 26773 Kbps, Downstream rate = 82036 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): 3.6 15.1
Attn(dB): 13.8 0.0
Pwr(dBm): 12.3 4.3
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 162 237
M: 1 1
T: 0 42
R: 8 16
S: 0.0647 0.3781
L: 21128 5374
D: 8 1
I: 171 127
N: 171 254
Q: 8 0
V: 2 0
RxQueue: 136 0
TxQueue: 34 0
G.INP Framing: 18 0
G.INP lookback: 31 0
RRC bits: 0 24
Bearer 1
MSGc: 186 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 5.3333 0.0000
L: 48 0
D: 3 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 1382947
OHFErr: 0 15
RS: 2402543056 680046
RSCorr: 19067 139
RSUnCorr: 0 0
Bearer 1
OHF: 2430692 0
OHFErr: 0 0
RS: 29167564 0
RSCorr: 0 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 503153 0
rtx_c: 127 0
rtx_uc: 0 0

G.INP Counters
LEFTRS: 0 0
minEFTR: 79980 0
errFreeBits: 47632458 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 1711502681 0
Data Cells: 18721766 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 14
SES: 0 0
UAS: 24 24
AS: 39044

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: 8384/8384 2/2

Total time = 10 hours 51 min 8 sec
FEC: 19067 139
CRC: 0 15
ES: 0 14
SES: 0 0
UAS: 24 24
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 6 min 8 sec
FEC: 144 1
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 501 0
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 10 hours 51 min 8 sec
FEC: 19067 139
CRC: 0 15
ES: 0 14
SES: 0 0
UAS: 24 24
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 = 10 hours 50 min 43 sec
FEC: 19067 139
CRC: 0 15
ES: 0 14
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
I now have the max sync rate again, But only a throughput of 68mbps My IP profile on G.inp used to be 77.35  surely i should be seeing a throughput of around 72/73 mbps not 68, I still have no access to what the  IP profile is the only info i have is within zen's portal , which is giving an incorrect sync speed
Title: Re: DLM not working as it should
Post by: tommy45 on November 04, 2019, 02:15:08 PM
Been in touch with zen's tech support they ran a kbd GEA test and here's what it reported

Description GEA service test completed and no fault found.
Main Fault Location OK
Sync Status In Sync
Downstream Speed 76.6 Mbps
Upstream Speed 20.0 Mbps
Appointment Required N
Fault Target Fix Time
Fault Report Advised N
Estimated Line Length In Metres 343.8
Upstream Rate Assessment Very Good
Downstream Rate Assessment Very Good
Interference Pattern Not Detected
Service Impact No Impact Observed
Home Wiring Problem Not Detected
Downstream Policing Discard Rate 0.0
Customer Traffic Level Upstream and Downstream Traffic Detected
Technology VDSL
DP Type External
Current 15Min Bin Retrains 0
Last 15Min Bin Retrains 0
NTE Power Status PowerOn
Voice Line Test Result Not Run - Unable to run
Bridge Tap Not Detected
Radio Frequency Ingress Not Detected
Repetitive Electrical Impulse Noise Not Detected
Cross Talk Not Detected
Profile Name 0.128M-80M Downstream 4dB, Retransmission High
             0.128M-20M Upstream, Error Protection Off
------------------------------------------------------------------------------------------------------------------

Is the speed observed supposed to be sync or throughput? the target snr would appear to be incorrect

[Moderator edited to correct the mangled formatting at the end of the report.]
Title: Re: DLM not working as it should
Post by: Black Sheep on November 04, 2019, 03:07:53 PM
It is synch speed ................ if you think about it, you can never attain the full 20Mbps Upstream (that is being reported in those stats) on throughput.  :)
Title: Re: DLM not working as it should
Post by: tommy45 on November 04, 2019, 04:13:30 PM
It is synch speed ................ if you think about it, you can never attain the full 20Mbps Upstream (that is being reported in those stats) on throughput.  :)
If that is the case  then that result can't of been from my circuit or the sync has been incorrectly reported it has never been 76.6 And i don't think what the modem is saying is wrong
Code: [Select]
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 26837 Kbps, Downstream rate = 81808 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): 3.6 15.2
Attn(dB): 13.8 0.0
Pwr(dBm): 12.3 4.3
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 162 237
M: 1 1
T: 0 42
R: 8 16
S: 0.0647 0.3781
L: 21128 5374
D: 8 1
I: 171 127
N: 171 254
Q: 8 0
V: 2 0
RxQueue: 136 0
TxQueue: 34 0
G.INP Framing: 18 0
G.INP lookback: 31 0
RRC bits: 0 24
Bearer 1
MSGc: 186 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 5.3333 0.0000
L: 48 0
D: 3 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 931594
OHFErr: 0 111
RS: 763969760 1159627
RSCorr: 119257 807
RSUnCorr: 0 0
Bearer 1
OHF: 13808497 0
OHFErr: 0 0
RS: 165701230 0
RSCorr: 0 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 503664 0
rtx_c: 638 0
rtx_uc: 0 0

G.INP Counters
LEFTRS: 0 0
minEFTR: 79980 0
errFreeBits: 270594784 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 4057509605 0
Data Cells: 187072127 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 101
SES: 0 0
UAS: 24 24
AS: 221802

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: 63200/63200 7/7

Total time = 1 days 13 hours 37 min 6 sec
FEC: 119257 807
CRC: 0 111
ES: 0 101
SES: 0 0
UAS: 24 24
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 7 min 6 sec
FEC: 292 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 569 7
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 13 hours 37 min 6 sec
FEC: 28406 214
CRC: 0 38
ES: 0 35
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 48260 302
CRC: 0 31
ES: 0 28
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 2 days 13 hours 36 min 41 sec
FEC: 119257 807
CRC: 0 111
ES: 0 101
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
Title: Re: DLM not working as it should
Post by: kitz on November 04, 2019, 06:57:32 PM
It definitely is sync speed.

One thing to bear in mind is some of the data on a GEA test may be ~14 days out of date especially when it comes to the reported DLM profile.
Title: Re: DLM not working as it should
Post by: ejs on November 04, 2019, 07:43:16 PM
The GEA test reports something different from the "sync speed" (actual net data rate) on a retransmission high profile, for the same reason as for why you get a lower IP profile on a retransmission high profile. Depending on how much of the GEA test results the ISP copies and pastes, there'll be another section with something like some min / max / current speeds which will match the modem "sync speed", even on a retransmission high profile.
Title: Re: DLM not working as it should
Post by: NewtronStar on November 04, 2019, 10:00:11 PM
Its a INP/RTX High issue which lowers your thoughput from 96% to 91 or 92%
Profile Name 0.128M-80M Downstream 4dB, Retransmission High

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.5

John should be able to give you the low-downs on this subject.
Title: Re: DLM not working as it should
Post by: tommy45 on November 04, 2019, 10:37:59 PM
[One image removed at the request of originator]

Yes i had read the thread about the 88% IP profile  incorrectly set, which if i check the IP profile figure in the zen portal it is 88% not 92%  which it should be  88% of 79999kbps =70399 (70.40) When it should be (73.60) giving a throughput of approx 71mbps  not 68mbps, i have  attached a ss of the same figure that backs up it's set to 88% and one of all i get when i run further diags on the bt performance tester , which has been this way since april or may this year when zen started getting incorrect sync speed info from btw
And here is a set of modem stats  from a day before DLM messed things up 212 days uptime in total  this was 211 days
My throughput was around 72-73 mbps  then as it had been since april or may  this year  before that the circuit had  lasted over 600 days without a re sync and throughput was around 74 mbps

Code: [Select]
=~=~=~=~=~=~=~=~=~=~=~= Plink log 2019.10.30 06:00:09 =~=~=~=~=~=~=~=~=~=~=~=

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason:   1
Last initialization procedure status:   0
Max:   Upstream rate = 26598 Kbps, Downstream rate = 79288 Kbps
Bearer:   0, Upstream rate = 19999 Kbps, Downstream rate = 79952 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.3       14.6
Attn(dB):    13.7       0.0
Pwr(dBm):    12.3       3.6
         VDSL2 framing
         Bearer 0
MSGc:      -6      26
B:      243      237
M:      1      1
T:      0      42
R:      10      16
S:      0.0972      0.3781
L:      20910      5374
D:      8      1
I:      254      127
N:      254      254
Q:      8      0
V:      0      0
RxQueue:      88      0
TxQueue:      22      0
G.INP Framing:      18      0
G.INP lookback:      22      0
RRC bits:      0      24
         Bearer 1
MSGc:      186      -6
B:      0      0
M:      2      0
T:      2      0
R:      16      0
S:      5.3333      0.0000
L:      48      0
D:      3      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      4227255
OHFErr:      5      14989
RS:      1052430704      4291836
RSCorr:      5544066      98254
RSUnCorr:   0      0
         Bearer 1
OHF:      1136344466      0
OHFErr:      0      0
RS:      751230968      0
RSCorr:      14      0
RSUnCorr:   0      0

         Retransmit Counters
rtx_tx:      502212      0
rtx_c:      63982      0
rtx_uc:      46474      0

         G.INP Counters
LEFTRS:      13      0
minEFTR:   79959      0
errFreeBits:   1288426123      0

         Bearer 0
HEC:      0      0
OCD:      0      0
LCD:      0      0
Total Cells:   1797097489      0
Data Cells:   4229222725      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:      15      13711
SES:      11      0
UAS:      57      46
AS:      18252760

         Bearer 0
INP:      50.00      0.00
INPRein:   1.00      0.00
delay:      0      0
PER:      0.00      3.98
OR:      0.01      64.22
AgR:      80034.45   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:   8793205/8793205      1477/1477

Total time = 1 days 18 hours 29 min 47 sec
FEC:      5667594      99543
CRC:      560      15152
ES:      15      13711
SES:      11      0
UAS:      57      46
LOS:      1      0
LOF:      9      0
LOM:      0      0
Latest 15 minutes time = 14 min 47 sec
FEC:      231      2
CRC:      0      1
ES:      0      1
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Previous 15 minutes time = 15 min 0 sec
FEC:      202      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 = 18 hours 29 min 47 sec
FEC:      19477      564
CRC:      0      86
ES:      0      74
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Previous 1 day time = 24 hours 0 sec
FEC:      26026      470
CRC:      0      76
ES:      0      63
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Since Link time = 49 days 17 hours 2 min 47 sec
FEC:      5544066      98254
CRC:      5      14989
ES:      4      13560
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0


HELLO HG612
xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason:   1
Last initialization procedure status:   0
Max:   Upstream rate = 26598 Kbps, Downstream rate = 79288 Kbps
Bearer:   0, Upstream rate = 19999 Kbps, Downstream rate = 79952 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,3970)
Medley Phase (Final) Band Plan
US: (7,32) (871,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3970)
     VDSL Port Details        Upstream        Downstream
Attainable Net Data Rate:       26598 kbps          79288 kbps
Actual Aggregate Tx Power:          3.6 dBm           12.3 dBm
 =========================================================================================
  VDSL Band Status    U0    U1    U2    U3    U4    D1    D2    D3
  Line Attenuation(dB):    3.1    15.3    22.3     N/A     N/A    8.8    19.4    29.8   
Signal Attenuation(dB):    3.1    14.5    21.5     N/A     N/A    11.8    19.3    29.8   
   SNR Margin(dB):    14.8    14.7    14.6     N/A     N/A    4.2    4.3    4.2   
    TX Power(dBm):   -11.5   -27.8    3.5     N/A     N/A    7.9    7.8    7.0   

Good Bye HG612
Title: Re: DLM not working as it should
Post by: NewtronStar on November 04, 2019, 10:48:58 PM
Tommy the only way I know to change your INPRein from 1.00 to 0.00 is to manually cap your Download sync on the modem until it retrains with a retransmission Low then remove the cap
Title: Re: DLM not working as it should
Post by: tommy45 on November 04, 2019, 11:28:52 PM
I'm happy just getting the IP profile fixed, because it's either stuck to what it was prior to this sync i have now or set incorrectly to 88%  because although the sync has increased throughput hasn't like it should have done , Failing that a DLM reset may do the trick, but it's a long winded approach because 1st it would be interleave then wait until G.inp re enabled , and then the target margin decreasing  2 steps and there's no guarantee that it wouldn't re apply RETX hi
Title: Re: DLM not working as it should
Post by: kitz on November 05, 2019, 01:32:09 AM
The GEA test reports something different from the "sync speed" (actual net data rate) on a retransmission high profile,

Interesting, thanks.  Wasn't aware of that, not being fortunate enough to have Re-tx  and all those I've seen showed the sync.   
Title: Re: DLM not working as it should
Post by: ejs on November 05, 2019, 08:01:48 PM
How do we know that this 88% IP profile issue is incorrect rather than just something that we don't know about? Maybe Openreach have fiddled with the parameters of their retransmission profiles without informing us first.

Note that the "incorrect" IP profile tends to be about 96.8% of the "incorrect" sync speed. 70396/72727 = 96.79%

The Retransmission High profile probably includes a higher allowance for the amount of throughput expected to be lost by being used for retransmitting data.
Title: Re: DLM not working as it should
Post by: tommy45 on November 05, 2019, 10:14:34 PM
How do we know that this 88% IP profile issue is incorrect rather than just something that we don't know about? Maybe Openreach have fiddled with the parameters of their retransmission profiles without informing us first.

Note that the "incorrect" IP profile tends to be about 96.8% of the "incorrect" sync speed. 70396/72727 = 96.79%

The Retransmission High profile probably includes a higher allowance for the amount of throughput expected to be lost by being used for retransmitting data.
IP profiles aren't anything to do with openreach  they are BT Wholesale, If i was on zen's GEA there would be no Ip profile, and i would be getting 72mbpsor more instead of 67-68
Title: Re: DLM not working as it should
Post by: tommy45 on November 06, 2019, 05:32:13 PM
Zen have come back to be saying that they can see a lot of Re Transmits and suggested i plug into the test jack  to see if that changes anything, i do not have ant internal wiring  (extensions) and wouldn't be able to use the phone (no crappy adsl filter) I thought this was normal  ?

Retransmit Counters   4 days 14 hours 54 min 40 sec
rtx_tx:      504253      0
rtx_c:      1188              0
rtx_uc:      0              0
Title: Re: DLM not working as it should
Post by: tubaman on November 06, 2019, 06:12:17 PM
Zen have come back to be saying that they can see a lot of Re Transmits and suggested i plug into the test jack  to see if that changes anything, i do not have ant internal wiring  (extensions) and wouldn't be able to use the phone (no crappy adsl filter) I thought this was normal  ?

Retransmit Counters   4 days 14 hours 54 min 40 sec
rtx_tx:      504253      0
rtx_c:      1188              0
rtx_uc:      0              0

Aren't those re-transmits just G.Inp correctly doing its job?
I'm puzzled why Zen see those as a problem as the numbers don't look too bad to me.

As an example here are my re-transmit figures from 27 days of uptime:
                        Retransmit Counters                                   
rtx_tx:         66656664                0                                     
rtx_c:          30205986                0                                       
rtx_uc:         2678            0         

This equates to about 2.5M per day - rather worse that the 125K per day you are seeing!
 ???
Title: Re: DLM not working as it should
Post by: tommy45 on November 06, 2019, 06:57:58 PM
Aren't those re-transmits just G.Inp correctly doing its job?
I'm puzzled why Zen see those as a problem as the numbers don't look too bad to me.

As an example here are my re-transmit figures from 27 days of uptime:
                        Retransmit Counters                                   
rtx_tx:         66656664                0                                     
rtx_c:          30205986                0                                       
rtx_uc:         2678            0         

This equates to about 2.5M per day - rather worse that the 125K per day you are seeing!
 ???
That's what i thought the only ones i would be concerned about would be the U uncorrected , or the LEFTERS (though not sure what they are)  I have e-mailed them to re iterate that i don't see this as a (physical)line issue , but as a BT BRAS IP profile issue that hasn't been sending zen the correct snyc or IP profile for months , and it has currently  set it's self to 88% of the sync rate when it should be 91-92% , i don't see what is so hard to grasp
Title: Re: DLM not working as it should
Post by: Postal on November 06, 2019, 08:40:59 PM
I have exactly the same problem with a IDNet line and the 88.2% sync rate.  Openreach show a profile of 0.128M - 80M, 3dB, re-transmission high.  The daily rtx_tx is about 250,000 which does not seem excessive enough to cause the retransmission to be set to high.

Having looked at the downstream error figures, IDNet asked BTOR to carry out a DLM reset.  BTOR declined as the sync speed of 69.9Mbps was within spec so no action required.

This is annoying as the line is sync'd at 74951kbps but my downloads by speed test are all just over 60Mbps.  The BTW speed test shows a profile of 65.61 (which is surprisingly ~88% of the sync rate!) and would be consistent with the speed test results.

So we have BTOR reporting one profile which seems to have no relation to reported sync speeds at my router or reported error figures and BTW reporting a different profile that matches exactly the expected sync speed for a line with re-transmission high.  BTOR hold the controls so no chance of my profile being re-set to what the line will support and no lever my ISP can use to force a re-set.
Title: Re: DLM not working as it should
Post by: tommy45 on November 06, 2019, 10:21:10 PM
I can't even see the BTw IP profile on the BT speedtest site , it fails every time  with an undisclosed error or session time out but the sync and ip profile figures in the Zen portal are not correct And haven't been since earlier this year, Before RE TX was increased to High but throughput was ok The BTW Bras IP profile is the issue  and that is Wholesales problem not openreach
I don't particularly want DLM resetting  because it will take weeks to get back where i am,  1st stage is now Interleaved then Fast path , then G.inp  then lower Target SNR 2 steps from 6 to 4db , But test jack and speed tests aren't going to help , the kbd is a waste of space too  because it doesn't provide the DS sync speed just some spurious figure that seems very common 76.6mbps
Title: Re: DLM not working as it should
Post by: Postal on November 06, 2019, 11:47:55 PM
I can't even see the BTw IP profile on the BT speedtest site , it fails every time  with an undisclosed error or session time out

Long shot, but you might get through to the IP profile running the test on a different browser.  I usually use Firefox but sometimes get the error message then try on another browser and manage to see the further information page.
Title: Re: DLM not working as it should
Post by: tommy45 on November 07, 2019, 04:15:54 PM
I have tried Opera and IE11 as well as FF nothing doing
Title: Re: DLM not working as it should
Post by: tommy45 on November 07, 2019, 04:35:11 PM
Its a INP/RTX High issue which lowers your thoughput from 96% to 91 or 92%
Profile Name 0.128M-80M Downstream 4dB, Retransmission High

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.5

John should be able to give you the low-downs on this subject.
Not sure the value you highlighted in red has  that effect here is an history sync with the same value  but the ip profile was 77.35 and throughput was 74mbps then until this year the inp figure increased by 2
Title: Re: DLM not working as it should
Post by: tommy45 on November 07, 2019, 04:39:48 PM
I can't even see the BTw IP profile on the BT speedtest site , it fails every time  with an undisclosed error or session time out but the sync and ip profile figures in the Zen portal are not correct And haven't been since earlier this year, Before RE TX was increased to High but throughput was ok The BTW Bras IP profile is the issue  and that is Wholesales problem not openreach
I don't particularly want DLM resetting  because it will take weeks to get back where i am,  1st stage is now Interleaved then Fast path , then G.inp  then lower Target SNR 2 steps from 6 to 4db , But test jack and speed tests aren't going to help , the kbd is a waste of space too  because it doesn't provide the DS sync speed just some spurious figure that seems very common 76.6mbps
just had a reply back from Zen support and here is what they are saying
Quote
Here is what we're seeing:

Sync Status: In Sync
Downstream Speed: 76.6 Mbps
Upstream Speed: 20.0 Mbps

Current BRAS Profile (CVLAN Rate): 72727

'0.128M-80M Downstream 4dB, Retransmission High - 0.128M-20M Upstream, Error Protection Off'

The BRAS profile is currently at 94% of the sync rate (72Mbps/76Mbps * 100 = 94%).

Potentially, the current BRAS profile is being calculated off the sync rate of 76Mbps. However, your updates are showing the router stats of ~80Mbps.

I'm guessing the sync rates being provided by the Openreach DSLAM to BT Wholesale are out of date and inaccurate (they are in fact timestamped: 2019-10-25T14:45:00 - this could however just be the last timestamp the DLM profile was updated).

If you are in sync higher than this, then this would potentially explain the reduced CVLAN rate.

I'm not 100% if this theory is correct, so could you please force a resync when you can and I'll check if the sync rates have changed at all on this side?

If we're still seeing exactly 76.6Mbps, and you're seeing 80Mbps then it looks like the stats are stuck (this could still be a red herring, as I'm not sure if this is just a front end thing and BT Wholesale's BRAS is actually pulling the correct data from elsewhere, but it's worth investigating if we can).

I have sent zen historical stats from before anything changed earlier this year, so they can see the sync rates and date and time of re sync's including  from before and after the time stamp of that KBD test
Title: Re: DLM not working as it should
Post by: j0hn on November 08, 2019, 11:08:15 AM
Not sure the value you highlighted in red has  that effect here is an history sync with the same value  but the ip profile was 77.35 and throughput was 74mbps then until this year the inp figure increased by 2

The Bearer 0 INPRein value highlighted in red is a definite way to tell if a line is retx low/high.
0 = low
1 = high

Quote from: Zen
I'm guessing the sync rates being provided by the Openreach DSLAM to BT Wholesale are out of date and inaccurate (they are in fact timestamped: 2019-10-25T14:45:00 - this could however just be the last timestamp the DLM profile was updated).

I think they are quoting the DLM line profile timestamp which had nothing to do with the sync speed.
It's 13 days old in GEA tests.
Title: Re: DLM not working as it should
Post by: tommy45 on November 08, 2019, 06:55:02 PM
They have been back to me, saying that BT have told zen the CVLAN rate  been recalculated for an 80Mbps sync rate.
But how would this have any effect on the BRAS server that sets the IP profile? the Cvlan would already be set to 80mbps Because of the product spec 80/20? Well i did a session drop and a re sync but no change,
Sent message back to them, just had an e-mail from a manager
Quote
reviewed this connection and also spoken with Openreach.  They recalculated the BRAS but it looks like this has had no effect for you.  It's more likely that the missing few mbit/s is a result of router error more than it is a line error.  Have you checked with an alternate model router at all?

Additionally, I'm seeing from your usage that you only generally use around 5-10 mbit/s of your full service.  Is it crucial that the extra few mbit/s are reached? 
Title: Re: DLM not working as it should
Post by: tommy45 on November 29, 2019, 12:11:06 PM
Unexpected re sync this morning at 01:49am DLM has removed the Hi REXT, kept the 4db snr margin But the throughput isn't where it should be  only around 72mbps  should be 74.5 ish here are my latest stats from just after the re sync
 
Code: [Select]
=~=~=~=~=~=~=~=~=~=~=~= Plink log 2019.11.29 01:49:14 =~=~=~=~=~=~=~=~=~=~=~=

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 27473 Kbps, Downstream rate = 84188 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.0 15.2
Attn(dB): 13.7 0.0
Pwr(dBm): 12.3 3.9
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 130 237
M: 1 1
T: 0 42
R: 8 16
S: 0.0518 0.3781
L: 21468 5374
D: 16 1
I: 139 127
N: 139 254
Q: 16 0
V: 14 0
RxQueue: 60 0
TxQueue: 20 0
G.INP Framing: 18 0
G.INP lookback: 20 0
RRC bits: 0 24
Bearer 1
MSGc: 186 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 5.3333 0.0000
L: 48 0
D: 3 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 10343
OHFErr: 0 0
RS: 3076880 434226
RSCorr: 5 0
RSUnCorr: 0 0
Bearer 1
OHF: 2552 0
OHFErr: 0 0
RS: 29883 0
RSCorr: 0 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 511275 0
rtx_c: 6076 0
rtx_uc: 70514 0

G.INP Counters
LEFTRS: 10 0
minEFTR: 79982 0
errFreeBits: 36741010 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 6253821 0
Data Cells: 1333 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: 10 1020
SES: 10 0
UAS: 57 47
AS: 41

Bearer 0
INP: 48.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 3.98
OR: 0.01 64.22
AgR: 80614.82 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: 0/0 0/0

Total time = 1 days 13 hours 9 min 50 sec
FEC: 844867 6551
CRC: 537 1087
ES: 10 1020
SES: 10 0
UAS: 57 47
LOS: 1 0
LOF: 9 0
LOM: 0 0
Latest 15 minutes time = 9 min 50 sec
FEC: 4640 9
CRC: 537 2
ES: 10 2
SES: 10 0
UAS: 33 23
LOS: 1 0
LOF: 9 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 107 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 = 13 hours 9 min 50 sec
FEC: 35775 131
CRC: 537 25
ES: 10 25
SES: 10 0
UAS: 33 23
LOS: 1 0
LOF: 9 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 12921 255
CRC: 0 35
ES: 0 32
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 41 sec
FEC: 5 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0


HELLO HG612
xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 27473 Kbps, Downstream rate = 84188 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,3970)
Medley Phase (Final) Band Plan
US: (7,32) (871,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3970)
  VDSL Port Details   Upstream   Downstream
Attainable Net Data Rate:     27473 kbps     84188 kbps
Actual Aggregate Tx Power:        3.9 dBm      12.3 dBm
 =========================================================================================
  VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
  Line Attenuation(dB): 3.1 15.4 22.5   N/A   N/A 8.8 19.5 29.9
Signal Attenuation(dB): 3.1 14.6 21.6   N/A   N/A 11.9 19.3 29.9
SNR Margin(dB): 16.7 15.0 15.1   N/A   N/A 3.9 4.0 4.1
TX Power(dBm): -11.2 -27.8 3.8   N/A   N/A 7.8 7.8 7.1
Stats recorded 29 Nov 2019 12:10:37

DSLAM type / SW version:   BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware:     AnnexA version - A2pv6C038m.d24j
DSL mode:                  VDSL2 Profile 17a
Status:                    Showtime
Uptime:                     10 hours 22 min 2 sec
Resyncs:                   1 (since 23 Nov 2019 10:19:03)
         
            Downstream   Upstream
Line attenuation (dB):     13.7      0.0
Signal attenuation (dB):   Not available on VDSL2      
Connection speed (kbps):   79999      19999
SNR margin (dB):           3.9      15.1
Power (dBm):               12.3      3.9
Interleave depth:          16      1
INP:                       48.00      0
G.INP:                     Enabled      Not enabled
Vectoring status:          5 (VECT_UNCONFIGURED)      

RSCorr/RS (%):             0.0005      0.0028
RSUnCorr/RS (%):           0.0000      0.0000
ES/hour:                   0.82      1.23


So they are still seeing the wrong information on Sync and incorrectly applied IP profile, as no RETX high any more 
Title: Re: DLM not working as it should
Post by: tommy45 on December 03, 2019, 03:42:30 PM
Had another Re sync last night apparently but i also had no internet for around 15mins , usually a re sync is less than a min downtime, there isn't any obvious changes G.inp is the same, just the attainable rates have increased, maybe the Target SNR decreased to 3db?  But would that influence the attainable on the upstream?

This is immediately after the re sync
Code: [Select]
=~=~=~=~=~=~=~=~=~=~=~= Plink log 2019.12.03 01:01:13 =~=~=~=~=~=~=~=~=~=~=~=

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 29096 Kbps, Downstream rate = 88134 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): 5.1 15.4
Attn(dB): 13.6 0.0
Pwr(dBm): 12.4 3.6
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 130 237
M: 1 1
T: 0 42
R: 8 16
S: 0.0518 0.3781
L: 21468 5374
D: 16 1
I: 139 127
N: 139 254
Q: 16 0
V: 14 0
RxQueue: 60 0
TxQueue: 20 0
G.INP Framing: 18 0
G.INP lookback: 20 0
RRC bits: 0 24
Bearer 1
MSGc: 186 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 5.3333 0.0000
L: 48 0
D: 3 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 2277
OHFErr: 0 0
RS: 692304 95625
RSCorr: 2 0
RSUnCorr: 0 0
Bearer 1
OHF: 622 0
OHFErr: 0 0
RS: 6724 0
RSCorr: 0 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 0 0
rtx_c: 6824 0
rtx_uc: 117070 0

G.INP Counters
LEFTRS: 25 0
minEFTR: 79999 0
errFreeBits: 3037520420 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 1484445 0
Data Cells: 22 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: 21 1193
SES: 21 0
UAS: 663 642
AS: 10

Bearer 0
INP: 48.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 3.98
OR: 0.01 64.22
AgR: 80614.82 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: 0/0 0/0

Total time = 1 days 12 hours 21 min 53 sec
FEC: 990590 7801
CRC: 1104 1262
ES: 21 1193
SES: 21 0
UAS: 663 642
LOS: 2 0
LOF: 19 0
LOM: 0 0
Latest 15 minutes time = 6 min 53 sec
FEC: 2 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 403 403
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 2638 8
CRC: 567 2
ES: 11 2
SES: 11 0
UAS: 203 192
LOS: 1 0
LOF: 10 0
LOM: 0 0
Latest 1 day time = 12 hours 21 min 53 sec
FEC: 19614 233
CRC: 567 29
ES: 11 27
SES: 11 0
UAS: 606 595
LOS: 1 0
LOF: 10 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 36588 266
CRC: 0 47
ES: 0 45
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 9 sec
FEC: 2 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0


HELLO HG612
xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 29096 Kbps, Downstream rate = 88134 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,3970)
Medley Phase (Final) Band Plan
US: (7,32) (871,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3970)
  VDSL Port Details   Upstream   Downstream
Attainable Net Data Rate:     29096 kbps     88134 kbps
Actual Aggregate Tx Power:        3.6 dBm      12.4 dBm
 =========================================================================================
  VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
  Line Attenuation(dB): 3.2 15.4 22.4   N/A   N/A 8.7 19.3 29.8
Signal Attenuation(dB): 3.2 15.4 22.4   N/A   N/A 11.8 19.1 29.8
SNR Margin(dB): 15.4 15.4 15.4   N/A   N/A 0.0 0.0 0.0
TX Power(dBm): -11.2 -27.6 3.5   N/A   N/A 8.1 7.8 7.0

Good Bye HG612

And most recent stats  the snr has dropped  but attainable is still higher than it was prior to this latest intervention, throughput hasn't increased sadly
Code: [Select]
=~=~=~=~=~=~=~=~=~=~=~= Plink log 2019.12.03 06:00:09 =~=~=~=~=~=~=~=~=~=~=~=

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 28965 Kbps, Downstream rate = 87216 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): 3.9 14.2
Attn(dB): 13.6 0.0
Pwr(dBm): 12.4 3.6
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 130 237
M: 1 1
T: 0 42
R: 8 16
S: 0.0518 0.3781
L: 21468 5374
D: 16 1
I: 139 127
N: 139 254
Q: 16 0
V: 14 0
RxQueue: 60 0
TxQueue: 20 0
G.INP Framing: 18 0
G.INP lookback: 20 0
RRC bits: 0 24
Bearer 1
MSGc: 186 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 5.3333 0.0000
L: 48 0
D: 3 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 294247
OHFErr: 0 9
RS: 1380298096 843754
RSCorr: 3552 59
RSUnCorr: 0 0
Bearer 1
OHF: 1117198 0
OHFErr: 0 0
RS: 13405634 0
RSCorr: 0 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 12 0
rtx_c: 6836 0
rtx_uc: 117070 0

G.INP Counters
LEFTRS: 25 0
minEFTR: 79982 0
errFreeBits: 3059405155 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 2760695645 0
Data Cells: 60808892 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: 21 1202
SES: 21 0
UAS: 663 642
AS: 17946

Bearer 0
INP: 48.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 3.98
OR: 0.01 64.22
AgR: 80614.82 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: 3771/3771 1/1

Total time = 1 days 17 hours 20 min 49 sec
FEC: 994140 7860
CRC: 1104 1271
ES: 21 1202
SES: 21 0
UAS: 663 642
LOS: 2 0
LOF: 19 0
LOM: 0 0
Latest 15 minutes time = 5 min 49 sec
FEC: 54 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 194 9
CRC: 0 2
ES: 0 2
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 17 hours 20 min 49 sec
FEC: 23164 292
CRC: 567 38
ES: 11 36
SES: 11 0
UAS: 606 595
LOS: 1 0
LOF: 10 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 36588 266
CRC: 0 47
ES: 0 45
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 4 hours 59 min 5 sec
FEC: 3552 59
CRC: 0 9
ES: 0 9
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0


HELLO HG612
xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 28965 Kbps, Downstream rate = 87216 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,3970)
Medley Phase (Final) Band Plan
US: (7,32) (871,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3970)
  VDSL Port Details   Upstream   Downstream
Attainable Net Data Rate:     28965 kbps     87216 kbps
Actual Aggregate Tx Power:        3.6 dBm      12.4 dBm
 =========================================================================================
  VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
  Line Attenuation(dB): 3.2 15.4 22.4   N/A   N/A 8.7 19.3 29.8
Signal Attenuation(dB): 3.2 14.5 21.5   N/A   N/A 11.8 19.1 29.8
SNR Margin(dB): 14.6 14.5 14.1   N/A   N/A 3.9 3.9 3.9
TX Power(dBm): -11.2 -27.6 3.5   N/A   N/A 8.1 7.8 7.0

Good Bye HG612
Title: Re: DLM not working as it should
Post by: tommy45 on December 09, 2019, 12:26:31 AM
The Latest stats and why DLM is overrated bollox:
Code: [Select]
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 30167 Kbps, Downstream rate = 89244 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.5 14.9
Attn(dB): 13.6 0.0
Pwr(dBm): 12.4 3.7
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 130 237
M: 1 1
T: 0 42
R: 8 16
S: 0.0518 0.3781
L: 21468 5374
D: 16 1
I: 139 127
N: 139 254
Q: 16 0
V: 14 0
RxQueue: 60 0
TxQueue: 20 0
G.INP Framing: 18 0
G.INP lookback: 20 0
RRC bits: 0 24
Bearer 1
MSGc: 186 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 5.3333 0.0000
L: 48 0
D: 3 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 3249538
OHFErr: 0 206
RS: 1053249440 1598579
RSCorr: 122027 1591
RSUnCorr: 0 0
Bearer 1
OHF: 32137462 0
OHFErr: 0 0
RS: 385648809 0
RSCorr: 0 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 1114 0
rtx_c: 7911 0
rtx_uc: 117070 0

G.INP Counters
LEFTRS: 33 0
minEFTR: 80015 0
errFreeBits: 3667397469 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 2106560733 0
Data Cells: 1367437513 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: 21 1389
SES: 21 0
UAS: 663 642
AS: 516215

Bearer 0
INP: 48.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 3.98
OR: 0.01 64.22
AgR: 80614.82 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: 144004/144004 21/21

Total time = 1 days 11 hours 45 min 18 sec
FEC: 1112615 9392
CRC: 1104 1468
ES: 21 1389
SES: 21 0
UAS: 663 642
LOS: 2 0
LOF: 19 0
LOM: 0 0
Latest 15 minutes time = 18 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
Previous 15 minutes time = 15 min 0 sec
FEC: 7 3
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 = 11 hours 45 min 18 sec
FEC: 3321 115
CRC: 0 8
ES: 0 8
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 19637 219
CRC: 0 22
ES: 0 22
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 5 days 23 hours 23 min 33 sec
FEC: 122027 1591
CRC: 0 206
ES: 0 196
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
Title: Re: DLM not working as it should
Post by: tommy45 on February 12, 2020, 12:23:07 AM
Well after several weeks a few hrs ago my throughput is back to where i would expect it to be looks like BT wholesale fixed the bras Profile rate issue https://www.thinkbroadband.com/_assets/speedtest/button/1581466583271857755.png, though unless  it was an issue affect zen earlier tonight  i may now have a hot svlan as the single thread was really low earlier on last night