Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: jaydub on February 18, 2021, 11:02:29 PM
-
I have an IP Profile of 73.77 on an 80 Mbps sync and pull ~71Mbps on the TBB speed test. I have no idea why the IP profile is set as low as it is. Using a Broadcom modem on and ECI cabinet connected to a BTw backhaul with IDNet. Any ideas?
Number: 0xxxxxxxxxx
The current Downstream IP profile rate is: 73.77
The current Upstream IP profile rate is: 20
-
I have just done a TBB speed check and now getting speeds of 74Mbps, so realised my IP profile must have changed.
Just checked the profile out using the Mouselike checker and am pleased to report that my IP profile appears to have been reset to what I think might be expected on an 80/20 line:
Number: 0xxxxxxxxxx
The current Downstream IP profile rate is: 77.42
The current Upstream IP profile rate is: 20
That works out at about 96.8% of the sync speed.
The only thing that I know has changed is that we had a momentary power cut yesterday. Would that have been enough to reset the lP profile?
It's been stuck on 73.77 since early April 2019, so am slightly intrigued about what has precipitated the change. Does anybody have any ideas?
-
Any line re-synch or even a PPP session re-connect for whatever reason has the potential to change BRAS IP profile.
It would appear that DLM has now deemed your line to be currently capable of sustaining G.Inp Re-Tx low profile, hence the approx 97% DS data/synch ratio.
There does not seem to be a definitive opinion as to what criteria DLM applies with respect to DS Re-Tx profile selection but DS FEC error rate appears to be one of the main contenders.
-
I'm an irregular stats gatherer and speed tester so it appears that my pervious speed test was on 10th February, so quite possibly nothing to do with yesterday's power cut.
Looking back at old stats it looks as though I have been on an INPRein of 0 the whole time I have been on IDNet's BTw backhaul. I also don't appear to have had any downstream FECs, although I have logged up to ~250 per day on the upstream.
I guess we will have to put this down to the vagaries of DLM.
-
From the limited stat's you report your line seems almost too good to be true.
80 Mbps DS synch on 80/20 service, very short line to cabinet, zero cross talk?
Zero DS FEC error rate, have never experienced this on the 3 VDSL-2 lines I monitor 24/7.
I try to limit my DS FEC error rate to approx. 10,000 errors/hour (avg. error rate/day) as reported by DSLStats by modem DS speed clamping in order to retain DS G.Inp Re-Tx low profile, found that this was necessary on my 40/10 service.
Assuming a DS synch of 80 Mbps on your line as you are reporting, I can see no other logical reason why your data/synch ratio changed from 92.2% to 96.8% as a result of the last re-synch other than a change of DS G.Inp Re-Tx profile from high to low.
-
Are you really getting zero DS FECs as I didn't think that was possible in the real world. On a good day mine runs at circa 250k FECS per hour!
-
Not sure it hasn't suffered from cross talk as the line used to have a max sync rate of about 104 Mbps downstream, which is now down to about 83 Mbps.
By way of comparison, my stats from January:
dsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 24119 Kbps, Downstream rate = 84004 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79987 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): 6.9 9.1
Attn(dB): 6.5 0.0
Pwr(dBm): -11.7 -11.7
VDSL2 framing
Bearer 0
MSGc: 18 150
B: 239 236
M: 1 1
T: 23 5
R: 0 16
S: 0.0955 0.3771
L: 20104 5410
D: 1 1
I: 240 255
N: 240 255
Counters
Bearer 0
OHF: 999266789 1429544
OHFErr: 698 835
RS: 0 499127
RSCorr: 0 4635
RSUnCorr: 0 0
Bearer 0
HEC: 2254 0
OCD: 1 0
LCD: 1 0
Total Cells: 810395526 0
Data Cells: 1876953224 0
Drop Cells: 0
Bit Errors: 0 0
ES: 530 547
SES: 0 0
UAS: 29 29
AS: 1652923
Bearer 0
INP: 0.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 1.65 6.15
OR: 116.09 202.87
AgR: 80103.09 20203.27
Bitswap: 1969/1969 162/162
Total time = 19 days 3 hours 9 min 12 sec
FEC: 0 4635
CRC: 698 835
ES: 530 547
SES: 0 0
UAS: 29 29
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 9 min 12 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: 0 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 = 3 hours 9 min 12 sec
FEC: 0 40
CRC: 4 9
ES: 3 6
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 0 242
CRC: 33 37
ES: 28 25
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 19 days 3 hours 8 min 43 sec
FEC: 0 4635
CRC: 698 835
ES: 530 547
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
and from yesterday:
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 24078 Kbps, Downstream rate = 82607 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79987 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): 6.8 9.0
Attn(dB): 6.6 0.0
Pwr(dBm): -11.7 -11.7
VDSL2 framing
Bearer 0
MSGc: 18 150
B: 239 236
M: 1 1
T: 23 5
R: 0 16
S: 0.0955 0.3771
L: 20104 5410
D: 1 1
I: 240 255
N: 240 255
Counters
Bearer 0
OHF: 75886921 1320617
OHFErr: 49 54
RS: 0 49349
RSCorr: 0 350
RSUnCorr: 0 0
Bearer 0
HEC: 157 0
OCD: 0 0
LCD: 0 0
Total Cells: 2125762709 0
Data Cells: 113103767 0
Drop Cells: 0
Bit Errors: 0 0
ES: 41 36
SES: 0 0
UAS: 28 28
AS: 125530
Bearer 0
INP: 0.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 1.65 6.15
OR: 116.09 202.87
AgR: 80103.09 20203.27
Bitswap: 119/119 37/37
Total time = 1 days 10 hours 52 min 38 sec
FEC: 0 350
CRC: 49 54
ES: 41 36
SES: 0 0
UAS: 28 28
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 7 min 38 sec
FEC: 0 3
CRC: 1 0
ES: 1 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: 0 15
CRC: 1 2
ES: 1 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 10 hours 52 min 38 sec
FEC: 0 127
CRC: 19 23
ES: 17 16
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 0 223
CRC: 30 31
ES: 24 20
SES: 0 0
UAS: 28 28
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 1 days 10 hours 52 min 9 sec
FEC: 0 350
CRC: 49 54
ES: 41 36
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
-
Are you really getting zero DS FECs as I didn't think that was possible in the real world. On a good day mine runs at circa 250k FECS per hour!
I have either got 0 downstream FECs or my VMG1312-B10A is misreporting.
I went through a lot of historical DSLStats data yesterday evening and couldn't see any downstream FECs being reported on any of the stats I looked at.
-
I have either got 0 downstream FECs or my VMG1312-B10A is misreporting.
I went through a lot of historical DSLStats data yesterday evening and couldn't see any downstream FECs being reported on any of the stats I looked at.
I doubt it's misreporting as they aren't known for that. Clearly a very good line indeed.
:)
-
I doubt it's misreporting as they aren't known for that. Clearly a very good line indeed.
:)
It's a fastpath line.
FEC isn't enabled on the Downstream*
*Unless using a Lantiq chipset modem.
-
It's a fastpath line.
FEC isn't enabled on the Downstream.
That would explain it.
I am lucky to live so close to the cabinet, not so lucky in that it is an ECI cabinet and my QLN graph might be considered leas than ideal
-
It's a fastpath line.
FEC isn't enabled on the Downstream.
Ahh, didn't know that, never been in a position to monitor a fastpath line.
From your stats, note your DS attenuation is 6.5 dB, the ECI cabinet must be practically beside your residence?
-
. . . my QLN graph might be considered leas than ideal
It's not perfect but nor is it bad. I'd call it quite reasonable.
How does the corresponding Hlog plot look for your circuit?
-
It's a fastpath line.
FEC isn't enabled on the Downstream.
That can't be right:
Profile: 17a
Trellis: D: ON / U: ON
Bitswap: D: ON / U: ON
G.INP: D: Not Enabled / U: Not Enabled
Virtual Noise Support: D: Not Supported / U: Not Supported
Attain Data Rate: 77.608 Mb/s / 24.456 Mb/s
Actual Data Rate: 67.000 Mb/s / 20.000 Mb/s
Impulse Noise Prot: 0.0 sym / 0.0 sym
Interleave Delay: 0.0 ms / 0.0 ms
NFEC: 255 / 255
RFEC: 16 / 16
LSYMB: 17979 / 5410
Interleave Depth: 1 / 1
Interleave Block: 255 / 255
LPATH: 0 / 0
Line Attenuation: 11.7dB / 13.3dB
Signal Attenuation: 11.8dB / 13.1dB
Noise Margin: 5.5dB / 7.3dB
Transmit power: 13.8dBm / 1.3dBm
FECS: 1248 / 184938
ES: 50 / 20752
SES: 0 / 1
LOSS: 0 / 0
UAS: 57 / 57
HEC: 0 / 0
CRC_P: 0 / 0
CRCP_P: 0 / 0
15m Code Violations: 0 / 0
15m FEC Errors: 0 / 0
1d Code Violations: 3 / 116
1d FEC Errors: 36 / 422
-
That can't be right:
His stats clearly show it is.
VDSL2 framing
Bearer 0
MSGc: 18 150
B: 239 236
M: 1 1
T: 23 5
R: 0 16
A small amount of FEC on the upstream, none on the downstream.
Only Lantiq chipsets devices add FEC on the downstream on fastpath.
Broadcom and others (Mediatek for 1) do not.
Revised my post above to avoid confusion.
-
His stats clearly show it is.
A small amount of FEC on the upstream, none on the downstream.
Only Lantiq chipsets devices add FEC on the downstream on fastpath.
Broadcom and others (Mediatek for 1) do not.
Revised my post above to avoid confusion.
Darn it, why they have to make the statistics so cryptic rather than using words.
Also, very interesting, I did not know that.
-
It's not perfect but nor is it bad. I'd call it quite reasonable.
How does the corresponding Hlog plot look for your circuit?
The tail off varies from sync to sync.
The big tail off is from January this year. The much flatter profile is from the current sync.
These are pretty much the worst case and best case graphs
-
The "tail off" is what I call the "high-frequency tail-end droop" and is a characteristic of circuits that terminate on an ECI Hi-FOCuS M41 Mini-Shelf, configured as a DSLAM. As you have observed, the "tail off" / "tail-end droop" varies with each circuit re-train.
However the Hlog plots clearly show that you are located very close to the DSLAM. The "flying gulls" (tm. Kitz) are indicative of some degree of cross-talk . . . but, overall, the circuit is quite good.
-
The "tail off" is what I call the "high-frequency tail-end droop" and is a characteristic of circuits that terminate on an ECI Hi-FOCuS M41 Mini-Shelf, configured as a DSLAM. As you have observed, the "tail off" / "tail-end droop" varies with each circuit re-train.
However the Hlog plots clearly show that you are located very close to the DSLAM. The "flying gulls" (tm. Kitz) are indicative of some degree of cross-talk . . . but, overall, the circuit is quite good.
Thanks B*cat. I've not come across the 'flying gulls' before and TBH I'm not quite sure which area of the graph I should be looking at. Please feel free to assist the uneducated (me) here.
The cabinet is probably 20m at ground level away from the master socket. It does go up to a pole and back down again, but we really couldn't be any better located for the cabinet.
I assume the drop in sync from its original ~104 Mbps must be down to crosstalk, so not surprised you can see some evidence of it.
-
Thanks B*cat. I've not come across the 'flying gulls' before and TBH I'm not quite sure which area of the graph I should be looking at. Please feel free to assist the uneducated (me) here.
Look at the DS3 band, the far right-hand, red, one. Consider it as a gull flying away from you (having just snatched your sandwich).
-
Look at the DS3 band, the far right-hand, red, one. Consider it as a gull flying away from you (having just snatched your sandwich).
Thanks, B*cat. Obvious when you know what you are looking for.
-
I assume the drop in sync from its original ~104 Mbps must be down to crosstalk, so not surprised you can see some evidence of it.
I assume you mean attainable rather than sync? Such as my connection:
2013: (Digital Region)
Max: Upstream rate = 34360 Kbps, Downstream rate = 114828 Kbps
Path: 0, Upstream rate = 34077 Kbps, Downstream rate = 99999 Kbps2014: (Openreach)
Max: Upstream rate = 32657 Kbps, Downstream rate = 93908 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79987 Kbps2015: (Openreach)
Max: Upstream rate = 30698 Kbps, Downstream rate = 93112 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79987 Kbps2016:
Max: Upstream rate = 32321 Kbps, Downstream rate = 91712 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79987 Kbps2017:
Max: Upstream rate = 29454 Kbps, Downstream rate = 69656 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 69892 Kbps2018:
Max: Upstream rate = 26585 Kbps, Downstream rate = 68416 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 69129 Kbps2019:
Max: Upstream rate = 24780 Kbps, Downstream rate = 62277 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 62249 Kbps
-
I assume you mean attainable rather than sync?
I did indeed. Good spot, Alex. Shouldn't post when I'm supposed to be working. I was never very good at multi-tasking and it always ends badly!
Some of my stats for comparison:
November 2016:
Max: Upstream rate = 30773 Kbps, Downstream rate = 103792 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79987 Kbps
January 2019
Max: Upstream rate = 23149 Kbps, Downstream rate = 86840 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79987 Kbps
Now:
Max: Upstream rate = 24029 Kbps, Downstream rate = 82770 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79987 Kbps