Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: V_R on November 27, 2017, 11:18:15 AM
-
Hey all,
I am in need of some advice here is possible.
I moved to Plusnet from Zen on the 1st November. I was syncing at near full speeds with Zen, then once my SNR dropped to 5.3 I maxed out the line, no interleaving and G.INP on. But I was getting disconnections due to failed echo requests (which I'm not had any with PN in the time I've been with them). That coupled with some poor single thread issues now and again and the fact Zen is a lot more a month than PN I decided to make the switch.
My speeds with Plusnet has been awful. It started at about 67Mb/s and then quickly dropped down to about 60Mb/s. Interleaving has been applied and G.INP is no where to be seen.
PN say because I'm syncing at ~65Mb I am above the MGALS which they say is 63.5Mb.
Despite the line being stable and very few errors DLM hasn't done anything. I can't get my IP profile as the site is having issues as reported on the Plusnet forums by adslmax.
I am using the HG612 (unlocked) with an Asus RT-N66U with the Merlin FW.
Can anyone give me some insight or advice?
I'm on MDSLWS, username is .Sam.
Here are the stats from the modem:
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 26590 Kbps, Downstream rate = 75436 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 65871 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 15.3
Attn(dB): 10.4 0.0
Pwr(dBm): 13.4 -5.0
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 51 237
M: 1 1
T: 64 42
R: 12 16
S: 0.0251 0.3781
L: 20384 5374
D: 1289 1
I: 64 127
N: 64 254
Counters
Bearer 0
OHF: 96660407 1259365
OHFErr: 61 301
RS: 3270070457 827041
RSCorr: 408505 1734
RSUnCorr: 7456 0
Bearer 0
HEC: 2339 0
OCD: 41 0
LCD: 41 0
Total Cells: 2577908770 0
Data Cells: 620956794 0
Drop Cells: 0
Bit Errors: 0 0
ES: 11 594
SES: 10 0
UAS: 1415 1405
AS: 155994
Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 1.61 3.98
OR: 118.97 64.22
AgR: 65990.22 20063.54
Bitswap: 70174/70174 640/641
Total time = 1 days 17 hours 11 min 17 sec
FEC: 1127391 5132
CRC: 5696 843
ES: 11 594
SES: 10 0
UAS: 1415 1405
LOS: 1 0
LOF: 9 0
LOM: 0 0
Latest 15 minutes time = 11 min 17 sec
FEC: 40 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 2
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 = 17 hours 11 min 17 sec
FEC: 177867 557
CRC: 0 112
ES: 0 99
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 163298 1034
CRC: 0 168
ES: 0 120
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 1 days 19 hours 19 min 53 sec
FEC: 408505 1734
CRC: 61 301
ES: 1 236
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
-
Forgot, Plusnet GEA test results.
Test Outcome Pass
Test Outcome Code GTC_FTTC_SERVICE_0000
Description GEA service test completed and no fault found .
Main Fault Location OK
Sync Status In Sync
Downstream Speed 65.8 Mbps
Upstream Speed 20.0 Mbps
Appointment Required N
Fault Report Advised N
NTE Power Status PowerOn
Voice Line Test Result Pass
Bridge Tap Not Detected
Radio Frequency Ingress Not Detected
Repetitive Electrical Impulse Noise Not Detected
Cross Talk Not Detected
Estimated Line Length In Metres 200.6
Upstream Rate Assessment Very Good
Downstream Rate Assessment Low
Interference Pattern Regular Interference Observed Daily
Service Impact No Impact Observed
Interference Duration Longest Occurrence From 07:00 to 20:45
Interference Location Customer Premise
Home Wiring Problem Not Detected
Downstream Policing Discard Rate 0.0
Customer Traffic Level Upstream and Downstream Traffic Detected
Technology VDSL
Current 15Min Bin Retrains 0
Last 15Min Bin Retrains 0
Profile Name 0.128M-80M Downstream, Interleaving Low - 0.128M-20M Upstream, Error Protection Off
Time Stamp 2017-11-12T11:45:00
Parameters MIN MAX AVG
Down Stream Line Rate 65.7 Mbps 66.5 Mbps 66.0 Mbps
Up Stream Line Rate 19.9 Mbps 19.9 Mbps 19.9 Mbps
Up Time 0.0 Sec 900.0 Sec 897.4 Sec
Retrains 0.0 1.0 0.0
Current and Last 15 Minute Bin Performance
Parameters Last Traffic Count(Upto 15 mins) Current Traffic Count(Upto 15 mins)
Start Time Stamp 2017-11-25T11:09:57Z 2017-11-25T11:24:57Z
Ingress Code Violation 1 1
Egress Code Violation 0 0
Errored Seconds 0 0
Severely Errored Seconds 0 0
Unavailable Seconds 0 0
-
Sync should be identical no matter the ISP.
However, it can take quite a bit of time for a line to get back to its full potential sync.
Your line isn't banded.
You have interleaving applied which knocks off roughly 10% of the sync speed.
In time G.INP will be applied, increasing sync.
If the line remains stable the snrm target will be lowered increasing the sync further.
Nothing between you and the cabinet (or at the cabinet either) has changed. If you're still using the same modem then eventually you'll get the same sync.
-
That's what I'm hoping for but it seems like its taken a long time for nothing to change.
The line is stable but DLM doesn't seem to have done anything apart from adding interleaving, which I've never had on this line in the 6 years I've had VDSL.
Are 'stuck' IP profiles still a thing?
-
No. Dropping the PPP session for 10 mins fixes a stuck IP profile, but yours isn't stuck. Your speed tests are right for the current sync.
Your speed test results show perfectly what has happened.
Old ISP
with G.INP and 5dB margin = 74Mb
line is reset
New ISP
fastpath day 1, no G.INP and 6dB margin = 67Mb
interleaving added, 10% sync taken = 60Mb
Interleaving is the default on Huawei cabinets. When a line is 1st activated it runs on an open profile (fastpath) for the 1st day then usually reverts to interleaving.
It's been less than 4 weeks. My line took 11 weeks to apply G.INP.
No ISP has any control of DLM. Nothing you can do but wait unfortunately.
-
Fair enough, that makes sense. But why am I not closer to the Max attainable then?
"Max: Upstream rate = 26590 Kbps, Downstream rate = 75436 Kbps"
Edit:
Looks like the BTW performance tester is working again...
Download speed achieved during the test was - 59.55 Mbps
For your connection, the acceptable range of speedsis 40 Mbps-63.76 Mbps .
Additional Information:
IP Profile for your line is - 63.76 Mbps
:(
-
The max attainable rate is overestimated by default when you have interleaving applied.
If you wait DLM will give you g.inp again.. and when that happens your attainable speed estimates will be more accurate again
-
If your line is interleaved, the attainable rate is grossly overestimated by the modem, it is a calculated value which in this case can never be achieved in practice. My line has G.inp applied and the attainable is less than my actual sync speed however since my sync is 79999/20000 I'm not complaining. :)
-
Well, Plusnet insisted on sending an engineer out, he came on Wednesday.
They wanted him to do a DLM reset. He refused saying it would 'upset the ports' whatever that means.
He did change the socket for a newer one because it was obsolete apparently, it was an older pre filtered BT faceplate. An ADSL v1.0, now I have a Master Socket 5C.
Also the second socket was backwired apparently, (the line is split into two where the drop wire hits the side of the house, this was done a long time ago by BT/OR apparently) - which I had no idea was the case tbh, I just assumed it split and went to the two sockets - which isn't anymore, and doesn't work anymore either. So I need to get that re wired as I'd like it working again.
All this has made little to no noticeable difference in my line stats or anything else. I am still stuck with 60Mbps download speeds.
In hindsight I wish I'd never bother moving from Zen, looking back now the extra £13 a month and the occasional max echo request failure (which I haven't had with PN incidentally so I assume that must have been an issue with Zen somehow) thing it was doing seems like a small inconvenience...
Guess I just have to wait it out. I just wish it would hurry up! :blush:
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 27111 Kbps, Downstream rate = 75196 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 66440 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.8 15.0
Attn(dB): 10.2 0.0
Pwr(dBm): 13.5 -4.6
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 51 237
M: 1 1
T: 64 42
R: 12 16
S: 0.0249 0.3781
L: 20560 5374
D: 1301 1
I: 64 127
N: 64 254
Counters
Bearer 0
OHF: 103921244 3850138
OHFErr: 0 318
RS: 833876208 2217229
RSCorr: 18007793 3219
RSUnCorr: 0 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 4062071116 0
Data Cells: 397514568 0
Drop Cells: 0
Bit Errors: 0 0
ES: 10 251
SES: 10 0
UAS: 117 107
AS: 166276
Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 1.60 3.98
OR: 120.00 64.22
AgR: 66560.00 20063.54
Bitswap: 82881/82881 1299/1299
Total time = 1 days 22 hours 13 min 35 sec
FEC: 18008854 3219
CRC: 5746 318
ES: 10 251
SES: 10 0
UAS: 117 107
LOS: 1 0
LOF: 9 0
LOM: 0 0
Latest 15 minutes time = 13 min 35 sec
FEC: 1 4
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 6
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 = 22 hours 13 min 35 sec
FEC: 14921438 2221
CRC: 0 162
ES: 0 130
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 3087416 998
CRC: 5746 156
ES: 10 121
SES: 10 0
UAS: 117 107
LOS: 1 0
LOF: 9 0
LOM: 0 0
Since Link time = 1 days 22 hours 11 min 15 sec
FEC: 18007793 3219
CRC: 0 318
ES: 0 251
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
-
PN staff say on the forum a year ago was
If your fibre is banded, the line can only be reset by an engineer calling DCoE (diagnostics centre of excellence). And the only way to progress this would be to arrange an engineer appointment I'm afraid.
-
V_R
Mine was the same too. My line is banded for nearly 20 days now.
1st resync: 11th Nov 2017
Downstream Upstream
Line attenuation (dB): 11.5 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 79999 20000
SNR margin (dB): 8.3 13.9
Power (dBm): 12.4 -0.6
Interleave depth: 8 8
INP: 46.00 47.00
G.INP: Enabled Enabled
2nd resync: 12th Nov 2017
Downstream Upstream
Line attenuation (dB): 11.5 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 73998 20000
SNR margin (dB): 10.1 14.0
Power (dBm): 12.5 -0.6
Interleave depth: 8 4
INP: 52.00 55.00
G.INP: Enabled Enabled
3rd resync: 22nd Nov 2017
Downstream Upstream
Line attenuation (dB): 11.5 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 74000 20000
SNR margin (dB): 10.0 14.4
Power (dBm): 12.4 -0.6
Interleave depth: 16 8
INP: 49.00 47.00
G.INP: Enabled Enabled
4th resync: 26th Nov 2017
Downstream Upstream
Line attenuation (dB): 11.4 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 74000 19999
SNR margin (dB): 9.9 15.1
Power (dBm): 12.5 -0.9
Interleave depth: 16 1
INP: 49.00 0
G.INP: Enabled Not enabled
and this my stats right now as of now:
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 30214 Kbps, Downstream rate = 88705 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 74000 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): 9.8 15.0
Attn(dB): 11.4 0.0
Pwr(dBm): 12.5 -0.9
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 174 237
M: 1 1
T: 0 42
R: 8 16
S: 0.0752 0.3781
L: 19456 5374
D: 16 1
I: 183 127
N: 183 254
Q: 16 0
V: 3 0
RxQueue: 42 0
TxQueue: 14 0
G.INP Framing: 18 0
G.INP lookback: 14 0
RRC bits: 0 24
Bearer 1
MSGc: 154 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 6.4000 0.0000
L: 40 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 776210
OHFErr: 0 214
RS: 1040293664 843924
RSCorr: 2196 1483
RSUnCorr: 0 0
Bearer 1
OHF: 31521493 0
OHFErr: 0 0
RS: 315214319 0
RSCorr: 6 0
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 105935 203
rtx_c: 122 1573
rtx_uc: 32181 79134
G.INP Counters
LEFTRS: 10 24
minEFTR: 73983 19991
errFreeBits: 1135218782 390973694
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 3332794463 0
Data Cells: 1089838088 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: 11 163
SES: 11 0
UAS: 64 53
AS: 506397
Bearer 0
INP: 49.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 3.98
OR: 0.01 64.22
AgR: 74132.27 20063.54
Bearer 1
INP: 4.50 0.00
INPRein: 4.50 0.00
delay: 3 0
PER: 16.06 0.01
OR: 79.68 0.01
AgR: 79.68 0.01
Bitswap: 174/174 63/63
Total time = 8 days 18 hours 5 min 31 sec
FEC: 8631 3059
CRC: 569 214
ES: 11 163
SES: 11 0
UAS: 64 53
LOS: 1 0
LOF: 7 0
LOM: 0 0
-
V_R's line does not appear to be banded. It has interleaving, not retransmission, which is resulting in less bandwidth than what otherwise might be achievable.
-
@adslmax, your stats are fine man. Just chill and wait. That line is a lot better than a lot of other people's. Hell I'd swap with you any time to have stats like that.
V_R's line does not appear to be banded. It has interleaving, not retransmission, which is resulting in less bandwidth than what otherwise might be achievable.
Indeed, that seems to be the case. I'm no expert on all this and I've have several different conversations with Plusnet support members over the last week or so, and they've all told me something different, of which my line is banded. I didn't know otherwise and took their word for it.
However it would seem I'm not banded as the latest GEA test shows this:
"Profile Name 0.128M-80M Downstream, Interleaving Low - 0.128M-20M Upstream, Error Protection Off" - which sows my max as 80M, which tells me its not banded, is that correct?
I can only get a maximum of 60.19 Mb/s out of my line at the moment, does that seem right for my stats show below?
Download speed achieved during the test was - 60.34 Mbps
For your connection, the acceptable range of speedsis 40 Mbps-64.31 Mbps .
Additional Information:
IP Profile for your line is - 64.31 Mbps
If anyone would like to just look over my stats on https://www.mydslwebstats.co.uk/Container.htm I would be grateful, just to see if anything looks out of place. I'm .Sam. - should be right at the top. Thanks.
I feel my stats are pretty poor considering my line is only about 200m with an attenuation of 10.2.... :(
Stats:
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 27040 Kbps, Downstream rate = 75424 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 66440 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.9 14.9
Attn(dB): 10.2 0.0
Pwr(dBm): 13.5 -4.5
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 51 237
M: 1 1
T: 64 42
R: 12 16
S: 0.0249 0.3781
L: 20560 5374
D: 1301 1
I: 64 127
N: 64 254
Counters
Bearer 0
OHF: 159791869 1010585
OHFErr: 0 464
RS: 2251854350 2932252
RSCorr: 21599989 4124
RSUnCorr: 0 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 2597377632 0
Data Cells: 810969085 0
Drop Cells: 0
Bit Errors: 0 0
ES: 10 352
SES: 10 0
UAS: 117 107
AS: 255671
Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 1.60 3.98
OR: 120.00 64.22
AgR: 66560.00 20063.54
Bitswap: 137200/137200 1632/1632
Total time = 1 days 23 hours 3 min 30 sec
FEC: 21601050 4124
CRC: 5746 464
ES: 10 352
SES: 10 0
UAS: 117 107
LOS: 1 0
LOF: 9 0
LOM: 0 0
Latest 15 minutes time = 3 min 30 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: 1256 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 = 23 hours 3 min 30 sec
FEC: 3590934 870
CRC: 0 141
ES: 0 96
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 14922700 2256
CRC: 0 167
ES: 0 135
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 2 days 23 hours 1 min 9 sec
FEC: 21599989 4124
CRC: 0 464
ES: 0 352
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
Full GEA results below.
Test Outcome Pass
Test Outcome Code GTC_FTTC_SERVICE_0000
Description GEA service test completed and no fault found .
Main Fault Location OK
Sync Status In Sync
Downstream Speed 66.4 Mbps
Upstream Speed 20.0 Mbps
Appointment Required N
Fault Report Advised N
NTE Power Status PowerOn
Voice Line Test Result Pass
Bridge Tap Not Detected
Radio Frequency Ingress Not Detected
Repetitive Electrical Impulse Noise Not Detected
Cross Talk Not Detected
Estimated Line Length In Metres 191.0
Upstream Rate Assessment Very Good
Downstream Rate Assessment Low
Interference Pattern Regular Interference Observed on Week Days
Service Impact No Impact Observed
Interference Duration Longest Occurrence From 11:15 to 12:15
Interference Location Customer Premise
Interference Observed In Days 2
Home Wiring Problem Not Detected
Downstream Policing Discard Rate 0.0
Customer Traffic Level Upstream and Downstream Traffic Detected
Technology VDSL
Current 15Min Bin Retrains 0
Last 15Min Bin Retrains 0
Profile Name 0.128M-80M Downstream, Interleaving Low - 0.128M-20M Upstream, Error Protection Off
Time Stamp 2017-11-29T10:45:00
Parameters MIN MAX AVG
Down Stream Line Rate 66.4 Mbps 66.4 Mbps 66.4 Mbps
Up Stream Line Rate 19.9 Mbps 19.9 Mbps 19.9 Mbps
Up Time 574.0 Sec 900.0 Sec 896.7 Sec
Retrains 0.0 4.0 0.0
Current and Last 15 Minute Bin Performance
Parameters Last Traffic Count(Upto 15 mins) Current Traffic Count(Upto 15 mins)
Start Time Stamp 2017-11-30T14:55:26Z 2017-11-30T15:10:26Z
Ingress Code Violation 2 0
Egress Code Violation 0 0
Errored Seconds 0 0
Severely Errored Seconds 0 0
Unavailable Seconds 0 0
-
V_R very odd as your Estimated Line Length In Metres 191.0 as mine is Estimated Line Length In Metres 248.3 as I expecting your stats are lots better than mine. But do remember this, the current GEA TEST under Profile Name 0.128M-80M Downstream, Interleaving Low - 0.128M-20M Upstream, Error Protection Off can be outdated with old time stamp on it, not updated correct by BT system.
Mine is:
Line attenuation (dB) U0 U1 U2 U3 U4 D1 D2 D3
01 Dec 2017 11:05:09 2.6 13.1 19.8 N/A N/A 6.8 15.4 25.5
-
Another question if I may...
Plusnet say
"Minimum guaranteed access line speed: 63.5Mbps
This is the minimum speed you should expect to achieve on your line."
I'm connected at:
Max: Upstream rate = 27036 Kbps, Downstream rate = 75424 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 66440 Kbps
But I only ever see at most 61Mbps.
Download speed achieved during the test was - 60.34 Mbps
For your connection, the acceptable range of speeds is 40 Mbps-64.31 Mbps .
Additional Information:
IP Profile for your line is - 64.31 Mbps
So despite the connection speed, am I below the MGALS?
-
@ V_R Plusnet say
"Minimum guaranteed access line speed: 63.5Mbps
This is the minimum speed you should expect to achieve on your line."
I'm connected at:
Downstream rate = 75424 Kbps that higher than BT estimated at 63.5Mbps.
-
So despite the connection speed, am I below the MGALS?
No. I think all speed estimates, and the MGALS, are in terms of what's commonly referred to as the "sync speed", not speedtest results or IP profiles.
-
I think PN only interesting look at BT Estimated Sync Rate under Downstream Handback Threshold(Mbps)
-
They wanted him to do a DLM reset. He refused saying it would 'upset the ports' whatever that means.
No idea what he meant about upsetting the ports as its nothing to do with that. However resetting the DLM wouldn't really achieve anything anyhow.
It would remove INP=3 (interleaving) and take you back to the open profile. Then within 48hrs DLM will take you back to 6dB and INP=3 which is the default profile.
From default profile DLM will monitor your line and if your are on a Huawei cab apply G.INP. This stage can take a couple of weeks or so.
So really its a good job the engineer didn't do a DLM reset because all it would have done is pushed you back to where you were at the beginning of Nov.
-
I got message from Galdalf as he say to me
Hi there.
Whilst we can arrange a visit, leaving notes for the engineer to not contact you but to perform a task, the engineer would generally only be able to reset the line (by calling their support team, Diagnostic Centre of Excellence) after a fault has been rectified.
If they find no fault with the service regardless of whether they visit your property or reset the line, the £65 charge will likely be applicable.
It's worth noting that banding isn't always considered a fault with the service. Speeds can be banded for a range of issues, in some cases to help stabilise a connection.
As your speeds are towards the top end of the estimates/the most a FTTC service can be provisioned on, it's likely that they'll find no fault.
On the other hand, you may get lucky and they may find a fault.
But I just reply to him saying below
Thanks for getting back to me. I can wait until after xmas see what happen to DLM control it. It's might restored the line back to 80Meg from 74Meg, if that didn't happen after xmas, I will get back to you to get an engineer out.
So, hopefully DLM will removed banded on my line sooner or later as long I keep the modem ON at all times and leave it alone. So, if that does restored it back to 80Meg, great it would save me £65 call out charge if no fault is found.
Thanks for getting back to me. Will let u know soon after xmas.
And finally Galdalf reply
No problems at all. Hopefully you'll get a nice little x-mas present from DLM, that the banding is removed.
Keep us posted. -Anoush
But as of now I give up. And will accepted 74Meg because I getting throughput speed of 70Meg (before was 75Meg) so losing 5Meg is hardly any difference which I am now accepting it and move on. Let DLM do it own things itself.
-
No. I think all speed estimates, and the MGALS, are in terms of what's commonly referred to as the "sync speed", not speedtest results or IP profiles.
That's what I was afraid of! Would have been nice to have at least something to go back to them with....
Max, please don't turn this into another 'Ermahgerd my connection' thread. You have several as it is!
No idea what he meant about upsetting the ports as its nothing to do with that. However resetting the DLM wouldn't really achieve anything anyhow.
It would remove INP=3 (interleaving) and take you back to the open profile. Then within 48hrs DLM will take you back to 6dB and INP=3 which is the default profile.
From default profile DLM will monitor your line and if your are on a Huawei cab apply G.INP. This stage can take a couple of weeks or so.
So really its a good job the engineer didn't do a DLM reset because all it would have done is pushed you back to where you were at the beginning of Nov.
Yes I am on a Huawei cabinet. Looking back it looks like interleaving was applied on the 7/11, I guess it could take a month or more?
I'm .Sam. on https://www.mydslwebstats.co.uk/Container.htm
Thanks for all the info folks. :)
-
Max, please don't turn this into another 'Ermahgerd my connection' thread. You have several as it is!
About an hour ago or so.. I was about to start and split this topic because I was beginning to find it confusing when the topic changed back to banding on Max's line.
I actually had the panel open to do so - but because some of posts referenced others - and it would just have ended up making 2 disjointed threads :(
-
Yes I am on a Huawei cabinet. Looking back it looks like interleaving was applied on the 7/11, I guess it could take a month or more?
I wish I could give you more info about time scale. I've seen it come back on some lines within days.. yet there are other lines which have taken many weeks.
-
Fair do's. I'll just sit tight and see what happens, we have Xmas coming up anyway, far more important stuff to deal with for the time being!
Thank you all for your help and replies.
-
access line speed means sync speed, so no.
-
So an interesting turn of events.
I've just got a reply from Plusnet about this issue. (after a week!) Here is their response...
"I have tested the connection and the downstream sync speed is currently 66.4mbps. The workplace profile we have at Plusnet had been set at 63.6mbps due to the last Delta Report from the Exchange which was received on 26/11/2017, reporting a speed of 63.6mbps, so in that respect it was "banded". I have manually increased the speed profile to the maximum, if you now drop the sync on the router for 20 seconds it will update with the new speed profile, and all things being equal you should then see the correct sync speed."
However I've just done that and its not made any difference.
If you want to see my line stats look for .Sam. on https://www.mydslwebstats.co.uk/Container.htm
Any ideas?
-
I think PN is just increase your PN ip profile to maximum 63.5 Mb to match BT delta report but they won't increase it to match your sync rate as your line still banded, and probably never removed off for a long while.
-
I think PN is just increase your PN ip profile to maximum 63.5 Mb to match BT delta report but they won't increase it to match your sync rate as your line still banded, and probably never removed off for a long while.
Come again?
-
I think you just got the same CS rep as what Bestgear did here (http://forum.kitz.co.uk/index.php/topic,20631.msg359982.html#msg359982).
Someone is getting confused between the IPprofile and the DLM profile. :'(
DLM controls the sync speed banding. The workplace profile (otherwise known as the PN Stable rate) is based on the IPprofile and affects throughput speed.
Them adjusting the 'workplace' profile will have no absolutely no impact on your sync speed. Only an Openreach Engineer can remove DLM banding. :/
-
I've had a similar issue with my Zen account.
I returned onshore to find my sync rate had dropped from 74Mb down to 17Mb and my Netgear D7000 had frozen. I rebooted that and logged an issue with Zen and we agreed to leave it a week to see if it would come back up. It did but got stuck at bang on 49Mb. I called Zen again (As per their request after the week) and they said they would send an engineer out. At this point I was quite busy with things in life so declined.
Fast forward 9 weeks and still no joy so Zen sent out an engineer. Line checked and tested all OK so a profile reset was done. It looks like I'll be playing the waiting game again for G.inp to be re-applied and my interleaving depth lowered from 1021.
If I remember correctly, It took my line about a year to get up to its maximum level from when it first went live and ran happily there for 2.5 years. It seems happy where it is now at 52.2Mb. Don't really notice much difference to be fair.
-
Well, they've contacted me again to discuss the matter.
Essentially there is no fault, I am within MGALS, only just mind you, by about 1.5Mbps.
The cocky little sod on the end of the phone basically told me "tough p00, you don't need 75Mbps anyway". I know he's technically right, but his attitude was **** poor.
I've got a good mind to complain as his attitude stank. I did as a matter of course ask what it would cost to get out of my contract, he said it would be £130. Not actually as bad as I thought, but still a lot.
There is a part of me that wants out as they've been pretty poor during the whole situation, from telling me there is a fault, isn't a fault, I am banded, I'm not banded. etc. their general CS is very poor and their knowledge almost non existent. One of them didn't even know what interleaving was.
So there we are. In hindsight I wish I'd stuck with Zen, they may cost more, but at least you can get thought to someone within a minute and they are actually knowledgeable and more than just a semi trained ape who will just read from a script..
Edit: lol that swear filter.
-
In Plusnet's defence, you would have experienced the exact same issue no matter what ISP you switched to.
The migration comes with a line reset. As you're on a Huawei cabinet g.inp has been removed and INP/interleaving applied, knocking the sync down. This is entirely automated and no ISP can control any part of it.
Ideally Plusnet staff should have been able to tell you that though. Sending the OpenReach engineer to do a DLM reset would have made the clock start again on waiting for g.inp to return.
-
Yeah indeed, and I now know this, so will be prepared for it next time/in the future.
But my point about the exceptional levels of retardation from their CS still stands.
-
But my point about the exceptional levels of retardation from their CS still stands.
Ideally Plusnet staff should have been able to tell you that though.
Indeed, that wasn't very clever, nor was the attitude.
For that I do feel V_R has valid grounds for complaint if he has the time to chase it.
Sending the OpenReach engineer to do a DLM reset would have made the clock start again on waiting for g.inp to return.
From what I can gather, he didn't do.. so hopefully thats a plus. I just wish we knew what the time scale is.. and why on some lines it only takes a few days yet on others it takes many weeks.
-
Yeah he didn't do the reset, he just sorted the back wiring and changed the old filtered socket socket for a newer pre filtered one..
I'd also be a little happier if what the engineer did actually improved anything, but it didn't, my stats are exactly the same as they were and now I have to get an extension fitted to replace the socket he disconnected! :mad:
So I hope you can understand my frustration! :wall:
-
I can :(
-
Cheap broadband == cheap support staff. Even if they come from Yorkshire.
That makes for a turnover in staff, and light training regimes.
But there's a downside to having a complicated DLM system involved... that complication makes it difficult for new & lightly-trained staff to understand themselves, let alone explain it to customers. When we (somewhat knowledgeable people) use a term like "banding", we tend to accept that there are other phrases, but they all come down to capping the speed ... and we've had *years* to come to terms with the process. It would help CS staff if BT used the same term in their explanations, and in the result of the FTTC tests. But the tests certainly don't - they just show a lower profile.
Is some of this a matter of inconsistent terminology in places?
What term does BT use to describe the process we call "banding"? And do they use the same term for FTTC and ADSL2+?
-
I think band, banded is the term BT use in technical documents. I don't think there's any inconsistent terminology, although no, the FTTC test doesn't print a big BANDED warning if the connection is. But even if a connection were banded, I don't think that in itself is a reason to send out Openreach to do a reset.
More and more people seem to be running into difficultly trying to solve something that isn't a problem. If the ISP does something, whatever they do will be wrong as there is no problem, and if they tell the end user that there is no problem, then the end user probably won't like that either.
-
The problem is, no matter how many times you tell people that the speed they will actually get is dependent on their line and others on the same cabinet, they feel aggrieved if they are not getting the same speeds as others on the same product and paying the same amount.
Perhaps ISPs should automatically discount their prices by 1p per month for every 1Mbps they are syncing below the top speed for their product. That way everybody would get the speed they are paying for! >:D
-
Is some of this a matter of inconsistent terminology in places?
What term does BT use to describe the process we call "banding"? And do they use the same term for FTTC and ADSL2+?
Good question!
With 20CN/21CN, BT Wholesale definitely use the term 'capped' for their DLM. eg "capped rate xkbps". All the BTw docs from where I mostly learnt about DLM use 'capping' or 'capped'. SINET uses capped in several of their documents eg Capped Rate Profiles.
I always previously used the term capped, but somewhere along the lines I admit, I too have started to used the term banding for NGA.
I can't find any official Openreach document that uses the term banding, other than for price banding. The first time I can see 'banding' being used is from the Plusnet explanations written by Chris Pettit.
Even the ASSIA court case mentions 'speed capping'. eg
The 20CN, 21CN and NGA profiles contain values for levels of interleaving, cap and/or margin (depending on the network). and
BT's NGA system subsequently held to be essential to BT's infringement at trial (the "cap level table").
Somewhere along the lines we have shifted towards using the term banding. If this is an implication of the ASSIA dispute over 'capping' I have no idea.
-
Perhaps ISPs should automatically discount their prices by 1p per month for every 1Mbps they are syncing below the top speed for their product. That way everybody would get the speed they are paying for! >:D
I think that argument has been covered several times before. Primarily on the grounds of cost.
Longer lines are those which cost most to install and maintain as far as Openreach are concerned.
Its also longer lines which are more problematic when it comes to DSL requiring more support from both OR and the ISP :(
If you start going down that route it could get messy. We've already been down the bandwidth charging route.
Openreach already have the various speed bands and there's also the lower cost option for very slow vdsl lines.
-
I can't find any official Openreach document that uses the term banding, other than for price banding. The first time I can see 'banding' being used is from the Plusnet explanations written by Chris Pettit.
I seem to recall that it was during the marathon, long drawn out, process to the resolution of Bald Eagle1's circuit problem that certain Plusnet operatives insisted that there was no "capping" just "banding". ::)
-
The reason I suggested 1p per 1Mbps was to make it a nominal discount (far less than the value if the introductory offers ISP's throw around left,right and centre!) - the maximum discount would be 79p for an 80/20 line delivering 1Mbps. In practice must peoples discount would be around 20p tops because ISP's would do as Plusnet do and only sell people higher spec. products if the line would actually benefit.
-
I've looked at the WBC DLM FAQ Issue 1.0 from 2009 and it certainly talks about banded profiles:
What are banded profiles?
Initially, each line is configured to run in a fully rate adaptive mode (i.e. very low
minimum rate and maximum rate set as high as possible). One of the options that DLM
uses to improve a line’s performance is the application of a banded line profile. Rather
than being fully rate adaptive these banded profiles are more restricted and specify a
minimum and maximum rate that the line has to run between. For example, one
banded profile specifies a minimum rate of 3.3Mbps and a maximum rate of 6.6Mbps
and therefore any line with this profile would be restricted to run within this range.
There are various levels of banded profiles available to DLM and they are carefully
applied based on the historical line speed performance of the line. The banded profiles
are detailed in the table below:
WBC banded line profile (rate kbps)
7168 - 14336
4864 - 9728
3328 - 6656
2272 - 4544
1472 - 3072
1152 - 2272
576 - 1152
288 - 576
160 - 288
I think the current FTTC DLM only bothers about capping the maximum rate, I think it no longer also sets a higher minimum rate.
The solution is to use neither the term banding nor capping, and just say that the DLM always ensures that you receive the optimum broadband experience.
-
Openreach already have the various speed bands and there's also the lower cost option for very slow vdsl lines.
Do you mean the 18/2 product? My line on the BTW checker used to show provide availability and Sim availability. When I enquired to BT retail earlier this year they said it was not available.
Having just checked again, my line shows only Sim availability.
I shall be looking check the market and possibly again next year and I will be interested if any ISP offers 18/2.
I currently sync at about 17mbs.
-
18/2 is only available on certain cabinets.
It's sold as BT Faster Broadband.
If you call and ask for the 18/2 package they likely won't know what you're talking about.
-
I have no issue with variable pricing on sync rate. The problem is as kitz reply shows, there is now an expectation for some strange reason that isps should be charging based on their costs to openreach and nothing else.
e.g. the cost of backhaul is often not considered, a line syncing at a higher rate does have inherent higher backhaul costs because there needs to be capacity free to service that line "just in case" the end user utilises the connection, and 40mbps of capacity is cheaper than 80mbps of capacity on a percentile based burst billing model which is what the isp's pay for.
I also have no issue of really paying for what you get and the only way costs would be relevant is that they low enough that its a profitable service. But the UK market at least in xDSL is not really run like this, certainly a factor is the ofcom regulation. The original pricing model before ofcom got stuck in had 2mbps ADSL cost circa £80 month for the consumer vs about £40 a month for 0,5mbit ADSL. The model before ofcom intervention had different openreach ports cost differently based on the burst speed, and also BTw backhaul was much more in line with industry standard pricing. However ofcom wanted to push dirt cheap broadband to homes regardless of sync speed, so ADSL MAX came about with its fixed pricing for all, and BTw backhaul shot up in price to compensate BT for the lost revenue on the new access port prices. This horrible imbalanced model of course led to the dark days of UK broadband where isps were having significant capacity problems due to the cheap deployment of high speed ports alongside expensive backhaul to service those connections. This model is what made LLU so attractive, as there was significant gains to be had on backhaul costs when using LLU. Why the likes of ukonline, BE and sky could offer unlimited usage without throttling.
-
It would appear my line has recovered a lot quicker than when it was initially installed. Going back to my comment on page 2, The BT engineer carried out a full line check and reset everything. Bang on a week later, G.INP was applied to my line, Then over the past few days my SNR has slowly started coming down. I think I'm within a few Mb to what my line was originally before it wobbly fit.
I understand every line is different, But thought I would give you my timescales for my line to go back to 'optimum' speed.
-
I understand every line is different, But thought I would give you my timescales for my line to go back to 'optimum' speed.
I think the main problem is qualifying for a line reset. If you do not qualify your line never gets fixed especially if it is banded.
Thankfully Plusnet have been decent for me but I only suspect it was because each time when they ran diagnostics the line failed so it qualified for an engineer to come out.
I am a firm believer that you should be able to request a line reset even if there is no fault detected on the line. There needs to be safeguards but if a customer can give a reasonable reason (>6db margin db, banded, faulty modem, local event eg weather etc) the ISP should be able to click a button and it just happens.
-
>6db margin db, banded
I don't think those would be reasonable reasons for doing a reset. There's not really any point in having the DLM do banding if it's just going to lead to someone doing a reset because it's banded.
-
Well this took a bit of a turn didn't it. :D
Just thought I'd update this thread a bit and mention that my line is exactly the same, no DLM changes at all. Best I can get out of a speedtest is now about 59Mb/s. :(
On the 16th Dec I had a message in my Plusnet Member Centre saying that the cease on my line has been actioned. I didn't action any cease. They say it was done at about 4 in the morning, sounds like an automated thing to me. No one could tell me what happened despite being transferred to the ones who would apparently know. ::)
They are awful and I want nothing more to do with them. So rightly or wrongly, I'm sacking off PN. I've lost all hope for them and their CS. I'm going back to Zen. In hindsight I wish to God I never bothered moving, hindsight's a bitch right!?
It'll cost me a bit, but worth it IMO. You live and learn.
Anyway Line stat for those who are interested and I'm .Sam. on https://www.mydslwebstats.co.uk/Container.htm if you're interested...
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 27247 Kbps, Downstream rate = 75468 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 66285 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.0 15.7
Attn(dB): 10.2 0.0
Pwr(dBm): 13.5 -4.6
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 51 237
M: 1 1
T: 64 42
R: 12 16
S: 0.0250 0.3781
L: 20512 5374
D: 1297 1
I: 64 127
N: 64 254
Counters
Bearer 0
OHF: 557217303 1121912
OHFErr: 0 1666
RS: 913550789 4049181
RSCorr: 15569649 20249
RSUnCorr: 0 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 2227963820 0
Data Cells: 1541471236 0
Drop Cells: 0
Bit Errors: 0 0
ES: 0 1152
SES: 0 0
UAS: 23 23
AS: 893646
Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 1.60 3.98
OR: 119.71 64.22
AgR: 66404.60 20063.54
Bitswap: 323658/323658 2349/2350
Total time = 1 days 8 hours 14 min 29 sec
FEC: 15569649 20249
CRC: 0 1666
ES: 0 1152
SES: 0 0
UAS: 23 23
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 14 min 29 sec
FEC: 16951 7
CRC: 0 2
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: 13881 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 = 8 hours 14 min 29 sec
FEC: 445443 726
CRC: 0 113
ES: 0 45
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 2291015 1170
CRC: 0 167
ES: 0 116
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 10 days 8 hours 14 min 5 sec
FEC: 15569649 20249
CRC: 0 1666
ES: 0 1152
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
-
V_R,
I'm having a similar experience to yours, not as bad I admit, but not the greatest when I came from a solid 80/20 service from BT and over to PN I've had the worst stats ever on my line and I'm going 60 days plus with no real recovery in sight (same hardware on my side so hardware and line are not the issue.) Still on a 6db SNR, still no sync at 80 and loads of errors on my upstream though it's not impacting the line as far as I can tell.
I wonder if on day 14 your line will have another reset and kick in G.INP and adjust your Interleaving downward as looking at your errors and SNR you should have a better line than I do and mine isn't terrible.
Fingers crossed, but totally get your frustration, I'm less than happy myself with PN and thought I was moving onto a winner from all the feedback I had from friends and colleagues, so far not in my case either.
-
Hey guys,
Can someone take a look at my stats and tell me what might be going on? It started today, this afternoon. 18.08 was a manual re sync to try and take advantage of the extra SNR.
I'm .Sam. (at the top)
https://www.mydslwebstats.co.uk/Container.htm
I'm still not seeing a jot of difference in actual download speeds. Its still almost exactly the same as its always been.
(https://i.imgur.com/LXyvvhj.png)
Stats recorded 04 Jan 2018 18:26:09
DSLAM/MSAN type: BDCM:0xa48c / v0xa48c
Modem/router firmware: AnnexA version - A2pv6C038m.d24j
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 0 hour 17 min 11 sec
Resyncs: 2 (since 04 Jan 2018 17:45:06)
Downstream Upstream
Line attenuation (dB): 10.2 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 69930 19999
SNR margin (dB): 6.2 15.3
Power (dBm): 13.4 -4.6
Interleave depth: 1369 1
INP: 3.00 0
G.INP: Not enabled Not enabled
Vectoring status: 5 (VECT_UNCONFIGURED)
RSCorr/RS (%): 0.0341 0.0010
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 0 4.87
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 25989 Kbps, Downstream rate = 80732 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 69930 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.2 15.3
Attn(dB): 10.2 0.0
Pwr(dBm): 13.4 -4.6
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 51 237
M: 1 1
T: 64 42
R: 12 16
S: 0.0237 0.3781
L: 21640 5374
D: 1369 1
I: 64 127
N: 64 254
Counters
Bearer 0
OHF: 677559 259290
OHFErr: 0 2
RS: 173288386 2295462
RSCorr: 59053 22
RSUnCorr: 0 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 138467626 0
Data Cells: 7766255 0
Drop Cells: 0
Bit Errors: 0 0
ES: 0 2
SES: 0 0
UAS: 23 23
AS: 1031
Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 1.52 3.98
OR: 126.30 64.22
AgR: 70056.34 20063.54
Bitswap: 452/453 1/1
Total time = 17 min 34 sec
FEC: 59053 22
CRC: 0 2
ES: 0 2
SES: 0 0
UAS: 23 23
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 2 min 34 sec
FEC: 8211 18
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: 50842 4
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 23 23
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 17 min 34 sec
FEC: 59053 22
CRC: 0 2
ES: 0 2
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 = 17 min 9 sec
FEC: 59053 22
CRC: 0 2
ES: 0 2
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
-
It may be worth turning off the modem before you go to bed for that port on the DSLAM to relax it may need 6 or so hours and switch the modem back on in the morning and observe the DS SNRM.
EDIT: what ever it was it's fixed itself ::)