A Chronicle of My Migration and Problems
Totally brassed off with the non-response from PN 
I decided to reboot the router............
Down NM now back to 6.1 and sync speed is back up to 9726.
Noise Margin: 6.1 dB
Connection Rate: 9726 Kbps
Line Attenuation: 32.5 dB
Power: 0.0 dBm
Max Rate: 15920 Kbps
SF: 13881
SF Errors: 0
Reed Solomon: 10883154
RS Corrected: 521
RS Un-Corrected: 0
HEC: 0
Errored Seconds: 0
Severe ES: 0
Interleave Depth: 128
This also put the tones back (see image)
I decided to reboot the router............
Down NM now back to 6.1 and sync speed is back up to 9726.
Noise Margin: 6.1 dB
Connection Rate: 9726 Kbps
Line Attenuation: 32.5 dB
Power: 0.0 dBm
Max Rate: 15920 Kbps
SF: 13881
SF Errors: 0
Reed Solomon: 10883154
RS Corrected: 521
RS Un-Corrected: 0
HEC: 0
Errored Seconds: 0
Severe ES: 0
Interleave Depth: 128
This also put the tones back (see image)
Here's today's update............
Still absolutely nothing from the technical guys at PN about what (if anything) they are doing about the low performance.
I think that's appalling
Figures so far tonight - the router has been "up" only 23.75 hours since reboot:
Noise Margin: 6.2 dB
Connection Rate: 9726 Kbps
Line Attenuation: 32.5 dB
Power: 0.0 dBm
Max Rate: 15820 Kbps
SF: 5021561
SF Errors: 40
Reed Solomon: 3936904286
RS Corrected: 275827
RS Un-Corrected: 1430
HEC: 27
Errored Seconds: 36
Severe ES: 0
Interleave Depth: 128
Noise Margin: 6.1 dB
Connection Rate: 1215 Kbps
Line Attenuation: 15.0 dB
Power: 12.7 dBm
Max Rate: 1236 Kbps
SF: 4753004
SF Errors: 0
Reed Solomon: 2597109
RS Corrected: 0
RS Un-Corrected: 0
HEC: 0
Errored Seconds: 0
Severe ES: 0
Interleave Depth: 4
Total Up Time (From SF count):
0 days, 23:47:39
CRC: 40
LOS: 0
LOF: 0
ES : 36
Bytes Transferred (ppp0):
Tx: 284785 (278.1 KiB)
Rx: 368917 (360.2 KiB)
I forgot to add......... currently this is almost the best performance for quite some time:
Still absolutely nothing from the technical guys at PN about what (if anything) they are doing about the low performance.
I think that's appalling
Figures so far tonight - the router has been "up" only 23.75 hours since reboot:
Noise Margin: 6.2 dB
Connection Rate: 9726 Kbps
Line Attenuation: 32.5 dB
Power: 0.0 dBm
Max Rate: 15820 Kbps
SF: 5021561
SF Errors: 40
Reed Solomon: 3936904286
RS Corrected: 275827
RS Un-Corrected: 1430
HEC: 27
Errored Seconds: 36
Severe ES: 0
Interleave Depth: 128
Noise Margin: 6.1 dB
Connection Rate: 1215 Kbps
Line Attenuation: 15.0 dB
Power: 12.7 dBm
Max Rate: 1236 Kbps
SF: 4753004
SF Errors: 0
Reed Solomon: 2597109
RS Corrected: 0
RS Un-Corrected: 0
HEC: 0
Errored Seconds: 0
Severe ES: 0
Interleave Depth: 4
Total Up Time (From SF count):
0 days, 23:47:39
CRC: 40
LOS: 0
LOF: 0
ES : 36
Bytes Transferred (ppp0):
Tx: 284785 (278.1 KiB)
Rx: 368917 (360.2 KiB)
I forgot to add......... currently this is almost the best performance for quite some time:
Iy's been about a week now and I thought I'd let yjr FDLAM try to sort itself out.
Current status is:
Noise Margin: 4.6 dB
Connection Rate: 14251 Kbps
Line Attenuation: 32.0 dB
Power: 0.0 dBm
Max Rate: 15916 Kbps
SF: 8853090
SF Errors: 610
Reed Solomon: 1150901808
RS Corrected: 657160
RS Un-Corrected: 27932
HEC: 491
Errored Seconds: 740
Severe ES: 32
Interleave Depth: 64
Sync speed has been 14251 for a couple of days now.
Let's hope things stay this way
Graham
Current status is:
Noise Margin: 4.6 dB
Connection Rate: 14251 Kbps
Line Attenuation: 32.0 dB
Power: 0.0 dBm
Max Rate: 15916 Kbps
SF: 8853090
SF Errors: 610
Reed Solomon: 1150901808
RS Corrected: 657160
RS Un-Corrected: 27932
HEC: 491
Errored Seconds: 740
Severe ES: 32
Interleave Depth: 64
Sync speed has been 14251 for a couple of days now.
Let's hope things stay this way
Graham
Hi,spraxyt,
No, not really - only to leave things alone, which I did.
And just looking at my last post it would appear that I was drunk when I wrote it - I wasn't
It's just that I'm lousy at touch typing in the dark and I didn't bother to check my spellings.
I'm off on holiday soon, so we'll have to see how the system copes with a period of inactivity.
The error rate is still a little high for my liking:
Down
Noise Margin: 4.5 dB
Connection Rate: 14251 Kbps
Line Attenuation: 32.0 dB
Power: 0.0 dBm
Max Rate: 15980 Kbps
SF: 14101197
SF Errors: 842
Reed Solomon: 1833155668
RS Corrected: 1279386
RS Un-Corrected: 33403
HEC: 704
Errored Seconds: 909
Severe ES: 32
Interleave Depth: 64
Up
Noise Margin: 6.5 dB
Connection Rate: 1177 Kbps
Line Attenuation: 14.9 dB
Power: 12.9 dBm
Max Rate: 1196 Kbps
SF: 13470066
SF Errors: 0
Reed Solomon: 3787171
RS Corrected: 0
RS Un-Corrected: 0
HEC: 0
Errored Seconds: 0
Severe ES: 0
Interleave Depth: 4
Total Up Time (From SF count):
2 days, 18:35:44
CRC: 2912
LOS: 4
LOF: 9
ES : 909
Bytes Transferred (ppp0):
Tx: 11730196 (11.1 MiB)
Rx: 117222254 (111.7 MiB)
Graham
No, not really - only to leave things alone, which I did.
And just looking at my last post it would appear that I was drunk when I wrote it - I wasn't
It's just that I'm lousy at touch typing in the dark and I didn't bother to check my spellings.
I'm off on holiday soon, so we'll have to see how the system copes with a period of inactivity.
The error rate is still a little high for my liking:
Down
Noise Margin: 4.5 dB
Connection Rate: 14251 Kbps
Line Attenuation: 32.0 dB
Power: 0.0 dBm
Max Rate: 15980 Kbps
SF: 14101197
SF Errors: 842
Reed Solomon: 1833155668
RS Corrected: 1279386
RS Un-Corrected: 33403
HEC: 704
Errored Seconds: 909
Severe ES: 32
Interleave Depth: 64
Up
Noise Margin: 6.5 dB
Connection Rate: 1177 Kbps
Line Attenuation: 14.9 dB
Power: 12.9 dBm
Max Rate: 1196 Kbps
SF: 13470066
SF Errors: 0
Reed Solomon: 3787171
RS Corrected: 0
RS Un-Corrected: 0
HEC: 0
Errored Seconds: 0
Severe ES: 0
Interleave Depth: 4
Total Up Time (From SF count):
2 days, 18:35:44
CRC: 2912
LOS: 4
LOF: 9
ES : 909
Bytes Transferred (ppp0):
Tx: 11730196 (11.1 MiB)
Rx: 117222254 (111.7 MiB)
Graham
Good question.
Wish I had a good answer. Perhaps PN might tell us.
But just looking at the errored seconds for the up time, it would appear that I've had errors for 15 minutes over about 72 hours, whilst receiving about 110 megabytes of data.
That just has the feeling to me of being a little more than I would like to see.
However, the DSLAM does have my NM set to about 4.5 at the mo' - I would hope that if it goes a litlle higher I might hey less errors.
Having said that, I haven't noticed any breaks in connection.
Graham
Wish I had a good answer. Perhaps PN might tell us.
But just looking at the errored seconds for the up time, it would appear that I've had errors for 15 minutes over about 72 hours, whilst receiving about 110 megabytes of data.
That just has the feeling to me of being a little more than I would like to see.
However, the DSLAM does have my NM set to about 4.5 at the mo' - I would hope that if it goes a litlle higher I might hey less errors.
Having said that, I haven't noticed any breaks in connection.
Graham
Hello again,
I am now back from a very nice holiday in Egypt...........
Whilst I was away, the down rate appears to have been increased to 13000+ and when I reset the connection (as needed) it had gone up to 15000+.........................
The current stats are:
Noise Margin: 2.0 dB
Connection Rate: 15544 Kbps
Line Attenuation: 32.5 dB
Power: 0.0 dBm
Max Rate: 17564 Kbps
SF: 24876424
SF Errors: 3888
Reed Solomon: 705193994
RS Corrected: 149693470
RS Un-Corrected: 185897
HEC: 3304
Errored Seconds: 6387
Severe ES: 162
Interleave Depth: 96
Noise Margin: 6.5 dB
Connection Rate: 1208 Kbps
Line Attenuation: 15.1 dB
Power: 12.9 dBm
Max Rate: 1220 Kbps
SF: 23715780
SF Errors: 0
Reed Solomon: 2765140
RS Corrected: 0
RS Un-Corrected: 0
HEC: 0
Errored Seconds: 0
Severe ES: 0
Interleave Depth: 4
I cannot understand why the DSLAM wants to reduce the NM to about 2db (it was about 3db when I first returned home a few days ago) if it's getting this number of errors - I would have thought that it should be going in the opposite direction????? (I am ignoring the up rate as this seems irrelevant at the present time)
Admittedly, I am currently running on about 15500 kbs at 1.9db to 2.1 db (as I write this), but for how much longer?
I am pretty sure that with such a high number of errors, the DSLAM is going to punish me later down the path, and then give me a c**p rate.....
Why, oh why, would it want to to reduce the NM value further, if the errors were increasing as the NM value went down?
Does the DSLAM want to reduce the status to the point when the line won't work anymore and then start at the top again and work it's way down to a less detrimental NM figure? And then start all over again?
I still believe that not enough info is coming out of BT/PN as to how the DSLAM works (or is expected to work) for anyone to understand what is happening to their line configuration to make any sort of judgemant as to the performance of the line.
Graham
I am now back from a very nice holiday in Egypt...........
Whilst I was away, the down rate appears to have been increased to 13000+ and when I reset the connection (as needed) it had gone up to 15000+.........................
The current stats are:
Noise Margin: 2.0 dB
Connection Rate: 15544 Kbps
Line Attenuation: 32.5 dB
Power: 0.0 dBm
Max Rate: 17564 Kbps
SF: 24876424
SF Errors: 3888
Reed Solomon: 705193994
RS Corrected: 149693470
RS Un-Corrected: 185897
HEC: 3304
Errored Seconds: 6387
Severe ES: 162
Interleave Depth: 96
Noise Margin: 6.5 dB
Connection Rate: 1208 Kbps
Line Attenuation: 15.1 dB
Power: 12.9 dBm
Max Rate: 1220 Kbps
SF: 23715780
SF Errors: 0
Reed Solomon: 2765140
RS Corrected: 0
RS Un-Corrected: 0
HEC: 0
Errored Seconds: 0
Severe ES: 0
Interleave Depth: 4
I cannot understand why the DSLAM wants to reduce the NM to about 2db (it was about 3db when I first returned home a few days ago) if it's getting this number of errors - I would have thought that it should be going in the opposite direction????? (I am ignoring the up rate as this seems irrelevant at the present time)
Admittedly, I am currently running on about 15500 kbs at 1.9db to 2.1 db (as I write this), but for how much longer?
I am pretty sure that with such a high number of errors, the DSLAM is going to punish me later down the path, and then give me a c**p rate.....
Why, oh why, would it want to to reduce the NM value further, if the errors were increasing as the NM value went down?
Does the DSLAM want to reduce the status to the point when the line won't work anymore and then start at the top again and work it's way down to a less detrimental NM figure? And then start all over again?
I still believe that not enough info is coming out of BT/PN as to how the DSLAM works (or is expected to work) for anyone to understand what is happening to their line configuration to make any sort of judgemant as to the performance of the line.
Graham
Hi
Welcome back - I'm off to Egypt on Wednesday.
I'm hoping while i'm a away the DLM decides "sorry, I'll stop playing silly bees - and work".
I'm stuck in a big loop between Pn and BT - BT do a change - line speed good for few days that the DLM goes "sorry you can have the speed". PN ask to swap all but my house results in no improvement - call sent to BT - how do some change - then speed good. Repeat cycle again! :
Phil
Welcome back - I'm off to Egypt on Wednesday.
I'm hoping while i'm a away the DLM decides "sorry, I'll stop playing silly bees - and work".
I'm stuck in a big loop between Pn and BT - BT do a change - line speed good for few days that the DLM goes "sorry you can have the speed". PN ask to swap all but my house results in no improvement - call sent to BT - how do some change - then speed good. Repeat cycle again! :
Phil
Down sync has remained at 15544 for a few days now, although the throughput (profile) appears to have been increased:
The NM continues to go down slowly:
Noise Margin: 1.8 dB
Connection Rate: 15544 Kbps
Line Attenuation: 32.5 dB
Power: 0.0 dBm
Max Rate: 17424 Kbps
SF: 35243602
SF Errors: 4903
Reed Solomon: 2788996788
RS Corrected: 206520379
RS Un-Corrected: 227012
HEC: 4121
Errored Seconds: 6947
Severe ES: 164
Interleave Depth: 96
Graham
The NM continues to go down slowly:
Noise Margin: 1.8 dB
Connection Rate: 15544 Kbps
Line Attenuation: 32.5 dB
Power: 0.0 dBm
Max Rate: 17424 Kbps
SF: 35243602
SF Errors: 4903
Reed Solomon: 2788996788
RS Corrected: 206520379
RS Un-Corrected: 227012
HEC: 4121
Errored Seconds: 6947
Severe ES: 164
Interleave Depth: 96
Graham
Latest update............
Things haven't changed a great deal since the last posting:
The NM continues to fluctuate between 1.8 and 2.3 during any 24 hour period. The Sync has remained at 15544 constantly, even though I think there have been a number of "lost sync" occurrences.
I am only running RouterStats for a couple of hours in the evening now, so I only managed to see one of theses drops.
The down interleave depth remains at 96.
The current statistics are as follows:
Noise Margin: 2.3 dB
Connection Rate: 15544 Kbps
Line Attenuation: 32.5 dB
Power: 0.0 dBm
Max Rate: 17784 Kbps
SF: 92329116
SF Errors: 20940
Reed Solomon: 1378283286
RS Corrected: 682969173
RS Un-Corrected: 1124102
HEC: 17404
Errored Seconds: 13637
Severe ES: 268
Interleave Depth: 96
Noise Margin: 6.0 dB
Connection Rate: 1208 Kbps
Line Attenuation: 15.1 dB
Power: 12.9 dBm
Max Rate: 1212 Kbps
SF: 88021610
SF Errors: 0
Reed Solomon: 924801
RS Corrected: 0
RS Un-Corrected: 0
HEC: 0
Errored Seconds: 0
Severe ES: 0
Interleave Depth: 4
Total Up Time (From SF count):
18 days, 03:59:54
CRC: 34798
LOS: 120
LOF: 34
ES : 13637
