Kitz Forum

Broadband Related => FTTC and FTTP Issues => Topic started by: nivek1612 on June 19, 2017, 11:12:52 AM

Title: FTTC Down and Up speed mismatch
Post by: nivek1612 on June 19, 2017, 11:12:52 AM
So the BT checker for my line suggest speeds of approx
Down 44-60
Up 11-17

Now I'm actually seeing Down of 62 and Up of 10

Is that usual to see the two at separate ends of the estimates or does it suggest a line issue somewhere ?

Title: Re: FTTC Down and Up speed mismatch
Post by: Dray on June 19, 2017, 11:28:19 AM
Can you post a lot more line stats?
Title: Re: FTTC Down and Up speed mismatch
Post by: skyeci on June 19, 2017, 11:37:57 AM
Kev uploads as kwillers on mydslwebstats if that helps.
Title: Re: FTTC Down and Up speed mismatch
Post by: Chrysalis on June 19, 2017, 12:03:47 PM
may have the issue that ronski has, one other guy had it also, ill check mdws later
Title: Re: FTTC Down and Up speed mismatch
Post by: Dray on June 19, 2017, 12:12:39 PM
No upload tones after 2396 on the Bits/tone graph
Title: Re: FTTC Down and Up speed mismatch
Post by: WWWombat on June 19, 2017, 12:56:55 PM
So the BT checker for my line suggest speeds of approx
Down 44-60
Up 11-17

Now I'm actually seeing Down of 62 and Up of 10

Is that usual to see the two at separate ends of the estimates or does it suggest a line issue somewhere ?

That's a good question, but the answer might be being overtaken by circumstances.

Six months ago+, your speeds looked like 60/15 and 55/13. They look like they were in proportion.

Recently, before SNRM changes, you were getting 52/11. Slightly favouring the downstream at this stage, but not hugely out of balance.

Now you are around 62/11, where the balance has shifted a lot. However ... that balance only shifted because XdB has come into operation, and given you an extra 10Mbps in one direction only.

I would suggest that the estimator hasn't been changed to take account of XdB, and may never be. In those circumstances, most lines will look to favour the downstream much more than the upstream.

As for why your line, at 52/11, was slightly out of balance? It looks to be noise in the upstream direction. If you look at the "Quiet Line", "SNR per tone" and "bits per tone" graphs, you can see that U2 has relatively few bits, seemingly because it is noisier - especially in the upper part of U2. Compare the noise with other similar lines, like "happyhorse". It also looks like power is playing a part too, as you have slightly lower upstream power than similar lines; this may be restricted as part of the "upstream power backoff" mechanism, trying to mediate upstream capability between lines.
Title: Re: FTTC Down and Up speed mismatch
Post by: nivek1612 on June 19, 2017, 01:11:41 PM
No upload tones after 2396 on the Bits/tone graph

hmmm hadn't spotted that

I've actually got a new drop cable being installed tomorrow, so will be interesting to see if that has any effect. Long story as to why its being moved.

Title: Re: FTTC Down and Up speed mismatch
Post by: nivek1612 on June 19, 2017, 01:13:14 PM
As for why your line, at 52/11, was slightly out of balance? It looks to be noise in the upstream direction. If you look at the "Quiet Line", "SNR per tone" and "bits per tone" graphs, you can see that U2 has relatively few bits, seemingly because it is noisier - especially in the upper part of U2. Compare the noise with other similar lines, like "happyhorse". It also looks like power is playing a part too, as you have slightly lower upstream power than similar lines; this may be restricted as part of the "upstream power backoff" mechanism, trying to mediate upstream capability between lines.

Not sure I fully follow that but I'm trying to :-)
Title: Re: FTTC Down and Up speed mismatch
Post by: Chrysalis on June 19, 2017, 01:15:43 PM
That's a good question, but the answer might be being overtaken by circumstances.

Six months ago+, your speeds looked like 60/15 and 55/13. They look like they were in proportion.

Recently, before SNRM changes, you were getting 52/11. Slightly favouring the downstream at this stage, but not hugely out of balance.

Now you are around 62/11, where the balance has shifted a lot. However ... that balance only shifted because XdB has come into operation, and given you an extra 10Mbps in one direction only.

I would suggest that the estimator hasn't been changed to take account of XdB, and may never be. In those circumstances, most lines will look to favour the downstream much more than the upstream.

As for why your line, at 52/11, was slightly out of balance? It looks to be noise in the upstream direction. If you look at the "Quiet Line", "SNR per tone" and "bits per tone" graphs, you can see that U2 has relatively few bits, seemingly because it is noisier - especially in the upper part of U2. Compare the noise with other similar lines, like "happyhorse". It also looks like power is playing a part too, as you have slightly lower upstream power than similar lines; this may be restricted as part of the "upstream power backoff" mechanism, trying to mediate upstream capability between lines.

wombat check my line, I upgraded the billion dsl firmware again last week, and observed the UPBO is more aggressive, a circa 3db loss on the upstream margin.  I did multiple resyncs to see if it was the UPBO lottery, which I think its not.  I will downgrade the firmware again sometime this week to see if the upstream SNRM recovers, so dsl firmware could be playing a part here.
Title: Re: FTTC Down and Up speed mismatch
Post by: nivek1612 on June 20, 2017, 02:39:13 PM
Well I had the new drop cable installed today

Here is the outcome for the Upload speeds

OLD CABLE
UP 10,531 with 5.3 of SNR

NEW CABLE
UP 10,646 but with 6.4 SNR

So a good 1 dB of improvement in the SNR but negligible speed and I'm still missing tones (right expression ??) in upper U2

So now time to raise with my ISP
Can anyone help me out how here explain how I frame the problem to the ISP will "missing tone in upper U2 make sense to them  ?"

Title: Re: FTTC Down and Up speed mismatch
Post by: Chrysalis on June 20, 2017, 04:17:53 PM
kevin having now looked at your bits/tone data I think your issue is a UPBO problem.

Looks like you are on a long line profile where the power is focused on U1, but looking at your DS tones I expect if you had a short line power mask profile then the U2 tones would give you more bits than U1.  So its a dslam configuration issue.

Your signal in the DS areas surrounding the U2 range is actually stronger than my line, the difference is that I have a different power mask profile and as a result can comfortably max out the US at 20000kbits.
Title: Re: FTTC Down and Up speed mismatch
Post by: nivek1612 on June 20, 2017, 05:04:25 PM
I may have a first in computer science but you lost me there :-)

Sounds like if its a DSLAM issue I'm screwed right ?
Title: Re: FTTC Down and Up speed mismatch
Post by: Chrysalis on June 20, 2017, 09:00:41 PM
Well your line on the DS seems to be performing well given the attenuation.  So I make the assumption lines at comparable distance might usually have less useable bits in the U2 range but your line looks like without any UPBO would populate the U2 bits comparable to what you get in D2.

Openreach configure UPBO so either U1 or U2 has power back off applied, for long lines its U2 and for short lines its U1.  But when you have lines hovering in between they can be stuck on configurations that are not optimal.
Title: Re: FTTC Down and Up speed mismatch
Post by: WWWombat on June 20, 2017, 10:00:54 PM
Not sure I fully follow that but I'm trying to :-)

I'll try to explain better... A bit long, though.

If you look at the "Quiet Line", "SNR per tone" and "bits per tone" graphs, you can see that U2 has relatively few bits, seemingly because it is noisier - especially in the upper part of U2.

First, check the "bits per tone" graph for your line, and for "happyhorse". You'll note that your U2 spectrum is carrying fewer bits, and none in the higher region. Around 3 bits per tone, perhaps.

In DSL, the reason that the modem synchronises with fewer bits on any one frequency is because it has a lower SNR. That means the spectrum is receiving lower signal levels or higher noise levels; the lower number of bits is the modem's way to cope with that situation. Comparing the two "SNR per tone" graphs confirms this.

Are you getting more noise from other lines? Yes. This can be seen in the "quiet line" graph (although that only measures the noise at the time of the last sync; it isn't "live").

In U2, "happy horse" is seeing noise from other subscribers of between -122 and -124dB; your line is between -116dB and -120dB - which is perhaps 4-6dB noisier; for comparison, -140dB is very, very quiet.

In DSL, there needs to be an extra 3dB of SNR in order for a tone to carry one extra bit. Your extra 4-6dB of noise means (roughly) that each tone in U2 can carry 1-2 bits less than "happyhorse"'s.

Onto the "power" graph... Unfortunately, this only shows the aggregate transmission power, rather than the power used on each tone. So we have to guess a little.

Your aggregate upstream power is running at 1.5dB lower than "happyhorse"'s. If this means the power of individual tones is lower by that amount, then your line also has a slightly lower signal level too. A lower signal that could be worth another bit here and there.

In total, we can see reasons why your U2 tones can be carrying 2-3 bits less. When aggregated over time, that could be worth 10Mbps on your sync speed.

The question is ... is any of this speed recoverable through a fault. The answer is that it is unlikely.

a) Crosstalk noise varies, and depends on the number of your neighbours that have subscribed.

Complaining to your ISP, or calling out an Openreach engineer, isn't going to get rid of those subscribers.

b) Upstream power varies too; it is forced to reduce by the DSLAM to allow distant subscribers to get reasonable upstream speeds.

Again, complaining to your ISP, or calling out an Openreach engineer, isn't going to get rid of those subscribers.

That is, I should say, all just my opinion. There could be some form of fault on your line that happens to be augmenting the noise or suppressing the signal ... which an engineer visit could fix. But there's little that stands out as obvious.

Onto the positive news...

Going by the attenuation values, "hungryhorse" has a shorter line, and ought to get higher speeds anyway. Yet the downstream speed is actually comparable.

Go back to that "quiet line" graph, and look at the noise in the downstream spectrum. You'll see that your line is quieter by 3-4dB. That helps your line carry more downstream speed, relatively.

DSL is a matter of swings and roundabouts. You can see how much your speed depends on the noise/interference you are receiving from other lines. And that interference behaves differently for upstream and downstream.

So now time to raise with my ISP
Can anyone help me out how here explain how I frame the problem to the ISP will "missing tone in upper U2 make sense to them  ?"

"missing tones in upper U2" is, in the end, a consequence of DSL trying to make best use of your line's capabilities, in your line's environment, while also trying to make best use of other lines. It is "designed-for", not a fault.

ISPs won't care about details like this. In the end, all they care about is whether the total throughput speed is within spec.
Title: Re: FTTC Down and Up speed mismatch
Post by: WWWombat on June 20, 2017, 10:12:30 PM
observed the UPBO is more aggressive, a circa 3db loss on the upstream margin.  I did multiple resyncs to see if it was the UPBO lottery, which I think its not.

I note you saw power changes in those resyncs, by almost 3dB too.

Strange that upstream and downstream power changes seem to match each other at almost all times. I wonder if the stats programme is misreading one of them. I wonder too what happens to the power level in the different bands.

Title: Re: FTTC Down and Up speed mismatch
Post by: Chrysalis on June 20, 2017, 10:44:53 PM
dont know but thought worth raising it to you, I will flash the older firmware back within the next hour.
Title: Re: FTTC Down and Up speed mismatch
Post by: nivek1612 on June 20, 2017, 11:59:09 PM
WWWombat wow that was an amazingly clear explanation thank you

As someone who remembers 1200 baud modems, I guess 10MB up isn't so bad ;-)
Title: Re: FTTC Down and Up speed mismatch
Post by: WWWombat on June 21, 2017, 01:09:07 PM
dont know but thought worth raising it to you, I will flash the older firmware back within the next hour.

Can you do a full "--stats" and "--pbParams" output before & after too? Partly to check that MDWS is logging the right things, and partly to see the power values in the sub-bands.
Title: Re: FTTC Down and Up speed mismatch
Post by: Chrysalis on June 21, 2017, 02:02:53 PM
I already did the switch, maybe MDWS has got before and after logged?

Code: [Select]
# adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    0
Last initialization procedure status:   0
Max:    Upstream rate = 28323 Kbps, Downstream rate = 68165 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 67596 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.1             11.8
Attn(dB):        15.0            0.0
Pwr(dBm):        6.6             6.6

                        VDSL2 framing
                        Bearer 0
MSGc:           18              150
B:              239             236
M:              1               1
T:              21              5
R:              0               16
S:              0.1130          0.3771
L:              16992           5410
D:              1               1
I:              240             255
N:              240             255

                        Counters
                        Bearer 0
OHF:            28897698                212466
OHFErr:         72              9
RS:             0               2210458
RSCorr:         0               44
RSUnCorr:       0               0

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

ES:             63              9
SES:            0               0
UAS:            24              24
AS:             51633

                        Bearer 0
INP:            0.00            0.00
INPRein:        0.00            0.00
delay:          0               0
PER:            1.78            6.15
OR:             107.46          202.87
AgR:            67703.53        20203.27

Bitswap:        18616/18616             5/5

Total time = 14 hours 20 min 57 sec
FEC:            0               44
CRC:            72              9
ES:             63              9
SES:            0               0
UAS:            24              24
LOS:            0               0
LOF:            0               0
LOM:            0               0
Latest 15 minutes time = 5 min 57 sec
FEC:            0               0
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               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 = 14 hours 20 min 57 sec
FEC:            0               44
CRC:            72              9
ES:             63              9
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 = 14 hours 20 min 33 sec
FEC:            0               44
CRC:            72              9
ES:             63              9
SES:            0               0
UAS:            0               0
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 = 28365 Kbps, Downstream rate = 68185 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 67596 Kbps

Discovery Phase (Initial) Band Plan
US: (6,31) (882,1193) (1984,2770)
DS: (33,857) (1218,1959) (2795,4083)
Medley Phase (Final) Band Plan
US: (6,31) (882,1193) (1984,2770)
DS: (41,857) (1218,1959) (2795,4083)
                  VDSL Port Details               Upstream                Downstream
Attainable Net Data Rate:           28365 kbps              68185 kbps
Actual Aggregate Tx Power:             6.6 dBm                6.6 dBm
====================================================================================
        VDSL Band Status                U0              U1              U2              U3              U4              D1              D2              D3
  Line Attenuation(dB):  1.0     12.1    26.4     N/A     N/A    9.8     22.6    36.6   
Signal Attenuation(dB):  1.2     12.1    26.4     N/A     N/A    12.2    22.4    36.6   
                SNR Margin(dB):  11.6    11.9    11.8     N/A     N/A    6.1     6.1     6.2   
                 TX Power(dBm): -4.7    -26.2    6.2      N/A     N/A    10.6    7.3     7.4   

I am looking to see if I can find historical output of these logged as dslstats runs these commands itself.
Title: Re: FTTC Down and Up speed mismatch
Post by: Chrysalis on July 15, 2017, 09:14:03 AM
Can you do a full "--stats" and "--pbParams" output before & after too? Partly to check that MDWS is logging the right things, and partly to see the power values in the sub-bands.

looks like I have the data, I found loads of files that dslstats has saved, will attach.
Title: Re: FTTC Down and Up speed mismatch
Post by: tbailey2 on July 15, 2017, 09:24:03 AM
If you look back to June 21st on MDWS (30 day view) the overall power levels changed from 4.1/4.1 to 6.6/6.5dB. On Jun 26th dropped to 4.8/4.8dB..

Title: Re: FTTC Down and Up speed mismatch
Post by: Chrysalis on July 15, 2017, 09:41:24 AM
yep thanks tony, I posted these 2 files tho as wombat specifically requested them.