Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: facboy on September 20, 2019, 10:12:17 AM
-
Is it still possible to get a stuck BT wholesale IP Profile on FTTC? The short version is that my BT wholesale IP Profile seems to be stuck on 70.69Mbps, even though the sync rate has always been 79999kbps. Assuming both figures are megabits/kilobits ps (is that right?), I calculate the ratio as 70.69/79.99 = 88.2%, which according to https://kitz.co.uk/adsl/IPprofile.htm is a 21CN profile? Plusnet say the IP Profile can't get stuck, it's just a determined by the sync speed.
Longer version:
Since I switched to PlusNet in June, I have never been able to get more than about 68Mbps on any speed test, even though the line has consistently synced at 79999kbps. Previously on Sky it synced at 79999kbps and i got more or less the speeds expected (about 73-74Mbps iirc). The wiring internally was not in the greatest shape, but it had never been a problem with Sky. The max attainable before and after the switch was around 81-82Mbps. That said I could see quite a lot of errors in the stats, and when I plugged into the master the max attainable went up to around 90Mbps, and SNR etc went up a bit too. About 2 months ago I bit the bullet and rewired the lines and now the max attainable is up to 90Mbps at the usual modem location and the error rates are way down on what they were before.
None of this has had any effect on the IP profile or any of the speed tests. Obviously it's not the end of the world but it bugs me. These are the stats pulled off the web UI (Zyxel VMG8924-B10A) this morning - I left the modem off overnight to see if it made any difference after an extended downtime, no difference.
====================================================================================
VDSL Training Status: Showtime
Mode: VDSL2 Annex B
VDSL Profile: Profile 17a
G.Vector: Disable
Traffic Type: PTM Mode
Link Uptime: 0 day: 2 hours: 0 minute
====================================================================================
VDSL Port Details Upstream Downstream
Line Rate: 20.063 Mbps 79.998 Mbps
Actual Net Data Rate: 19.999 Mbps 79.999 Mbps
Trellis Coding: ON ON
SNR Margin: 15.3 dB 6.3 dB
Actual Delay: 0 ms 0 ms
Transmit Power: - 6.5 dBm 12.9 dBm
Receive Power: -18.4 dBm 3.8 dBm
Actual INP: 0.0 symbols 52.0 symbols
Total Attenuation: 0.0 dB 9.4 dB
Attainable Net Data Rate: 30.031 Mbps 90.462 Mbps
====================================================================================
VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
Line Attenuation(dB): 4.8 9.5 13.3 N/A N/A 5.5 11.0 18.0
Signal Attenuation(dB): 4.8 8.8 12.7 N/A N/A 6.6 10.9 18.0
SNR Margin(dB): 17.2 15.1 15.4 N/A N/A 6.3 6.3 6.2
TX Power(dBm): -21.2 -34.2 -6.6 N/A N/A 9.3 7.9 7.0
====================================================================================
VDSL Counters
Downstream Upstream
Since Link time = 13 sec
FEC: 4 13
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 44 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 = 2 hours 44 sec
FEC: 4 13
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 30 30
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
Total time = 2 hours 44 sec
FEC: 4 13
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 30 30
LOS: 0 0
LOF: 0 0
LOM: 0 0
====================================================================================
-
It isn't stuck as such, it's incorrectly configured too low.
I've seen 88% about half a dozen times and only seen it being fixed once.
BTWholesale had to rebuild the line, or some other technical term similar to that.
Not sure any of the other examples managed to get it corrected.
It won't be easy to get them to concede there's a problem.
-
It isn't stuck as such, it's incorrectly configured too low.
I've seen 88% about half a dozen times and only seen it being fixed once.
BTWholesale had to rebuild the line, or some other technical term similar to that.
Not sure any of the other examples managed to get it corrected.
It won't be easy to get them to concede there's a problem.
I have the same problem with an IDNet line. I've just raised the matter with their support so we'll see what happens.
-
Just to add the times I've seen an 88% IP profile they were on a retransmission high profile which is usually 91-92%.
-
Just to add the times I've seen an 88% IP profile they were on a retransmission high profile which is usually 91-92%.
Looking at the numbers, that may be the case with my line. Is there any way that the retransmission high profile can be changed?
-
had a DLM reset done today (like 1 hour ago), already a cursory speedtest has got as high as 73 when it previously would hit 68 absolute max. so it's a victory of sorts.
-
had a DLM reset done today (like 1 hour ago), already a cursory speedtest has got as high as 73 when it previously would hit 68 absolute max. so it's a victory of sorts.
good result. your line stats are similar to mine and I can get 74mbps easily on a single thread so there's no reason for you to get stuck at 68. ;D
-
had a DLM reset done today (like 1 hour ago), already a cursory speedtest has got as high as 73 when it previously would hit 68 absolute max. so it's a victory of sorts.
Did DLM re activate G.inp and RETX high profile again ?