Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[kitz]

Now looking at your stats you dont appear to have any downstream problems but something is niggling me about your upstream.

what was niggling me about your upstream was the higher Error Counts

Upstream SNRM was an amazing 1.2 at 1am this morning

.... and the reason  why has just shown itself.

Orange appear to have you on a fixed 2Mb line...  but why would they do that?

.. and this could possibly be the reason why Orange's DLM* has put you on a capped rate line.



It would appear your upstream has a huge shift in SNRM..  if its getting down to only 1.2dB, then its going to be struggling to hold on to that 285 kbps upstream.

Upstream frequencies are lower, and normally have the least problem. 
I know you say you are plugged into the master socket.. but can you just double check your filter... and also it may be an idea to try the test socket behind the faceplate for a while - just for the sake of elimination.

I also recommend that you grab a copy of routerstats and configure it to monitor and  record your upstream SNRM.
This will hopefully show us how the decline starts and at what time.. and see if it shows a pattern that may help diagnose some sort of interference issue.

[Oranged]

I know you say you are plugged into the master socket.. but can you just double check your filter... and also it may be an idea to try the test socket behind the faceplate for a while - just for the sake of elimination.

I have on various occasions plugged into the test socket for several hours at a time with no improvement shown in sync speed or SNRM.

I have also replaced the plug-in filter, my only other move would be to replace the plug-in filter with a filtered faceplate.

Edit 1 :- I have started running Routerstats and will keep it running for 24 hours.

Edit 2 :- Unable to configure Routerstats for Belkin F5D7633UK4A

Edit 3 :- DMT is showing SNRM 24.5/9.7 at 2:55pm. So there does not appear to be any pattern when SNRM drops.

[kitz]

Edit 2 :- Unable to configure Routerstats for Belkin F5D7633UK4A

Ive been having a search around and there does appear to be some difficulty in trying to get routerstats to work with the F5D7633.  Unfortunately since I dont have one of these routers, Im unable to have a look to see what can be configured.

However, since you are using DMT ok..  then you can try using DMT tool to record your linestats.

- New tutorial Ive just done - Use DMT tool to log and record your linestats.

Hope this info helps.

[Oranged]

Many thanks for that.....glad you confirm my findings re. this Belkin model.....I thought I was doing something wrong 
I started running the logfile this morning after testing the DMT diagnosis mode config.

[Oranged]

Still running DMT Diagnosis but SNRM has been 30.4+/- 0.2 downstream and 13.8+/- 0.2 upstream all today.

Can wet weather affect the connection within BT's network ?

Because it was most erratic over the last few days when it was or had been raining but today is dry and warm.

I'll leave DMT running all night until noon tomorrow then save the logfile.

[roseway]

Wet weather can certainly affect the connection if there's a joint somewhere which isn't fully sealed and lets the rain in. This can (for example) cause a temporary partial short-circuit which clears when it all dries out again, or it can cause the joint to corrode.

[Oranged]

But would the cause produce the effect that I'm experiencing ?

Or would I experience disconnections, because even though some of the data is very erratic, I have had a consistently reliable connection since these problems started.

[Ezzer]

if your on a fixed speed then with typical snr in the teens the limitations are:

<43db attenuation then 2mb ok

<60db                             1mb ok

>60db then go for 0.5mb

if your on 2mb fixed with >43db loss, there's your problem

rate adaptive/max can become particualy tetchy >60db, the snrm really needs to be good to give a chance of giving reasonable service, some errors would probably come about from the line lenght but a large no. of errors particualy upstream would indicate an snr issue, errors are sometimes an indication of snr problems which pop up in too short a burst to register fully on the snrm count.

[Oranged]

DMT diagnosis has not revealed anything unusual happening between 30 June 09:56 and 1 July 12:05. Config. was set to update every 2 minutes.

Data rate stayed steady at 2268/285

Attenuation was steady at 43.5/20.5

Upstream SNRM was steady at 13.8

Downstream SNRM varied between minimum 27.4 (22:42:58 last night) and maximum 30.6 (11:08:58 this morning).
There was a period when it dropped to below 30 and remained there before increasing to above 30, that was between 20:38:57 last night and 04:40:58 this morning.

Re. my reference to weather, it's been dry and warm during this test.

Rain is forecast for tonight and tomorrow so I will run another logfile during that period.

[kitz]

>> 27.4 (22:42:58 last night) and maximum 30.6

Those fluctuations are within normal parameters - its usual for SNRM to take a dip in the evenings, so thats fine.

>> Re. my reference to weather, it's been dry and warm during this test.

You could be on to something there, its not unknown for some types of line fault only to materialise during wet weather. (water on the line).

[Oranged]

Update on last DMT logfile run from 6pm yesterday, overnight until around 12 noon today.

Unfortunately the rain didn't come to as much as forecasted so DMT results were very similar to previous day's

Data rate steady 2268/285

Attenuation steady 43.5/20.5

Upstream SNRM steady 13.8

Downstream SNRM between 28.1 and 30.6
From 21:08:16 last night until 04:38:16 this morning it was under 30.0

It has been raining this morning so I am running another logfile for as long it rains.

Edit @15:05 > just noticed the downstream SNRM went from 30.5 to 27.4 back 30.3 all in the space of 3 minutes.

Edit @ 18:19 > Upstream SNRM reached <1.0 at around 18:10 and for the first time in a long while I had a disconnection. Re-started eventually at around 18:15 with SNRM 20+/5+ and Attenuation 44.0/21.5, but data rate still 2268/285. DMT still running today's logfile.

[Oranged]

Here are sections of the logfile that ran from 2:25pm yesterday until 10:59am today.


              USrate     DSrate      USatt   DSatt   USsnr   DSsnr

16:40:58   285   2268   20.5   43.5   11.6   26.3
16:42:59   285   2268   20.5   43.5   11.2   26.3
16:44:58   285   2268   20.5   43.5   11.8   26.4
16:46:58   285   2268   20.5   43.5   2.2   16.7
16:48:58   285   2268   20.5   43.5   10.9   25.9
16:50:59   285   2268   20.5   43.5   1.9   19.9
16:52:59   285   2268   20.5   43.5   1.8   20.9
16:54:58   285   2268   20.5   43.5   1.8   20.8
16:56:58   285   2268   20.5   43.5   1.7   20.9
16:58:59   285   2268   20.5   43.5   1.6   20.8
17:00:58   285   2268   20.5   43.5   1.6   20.8
17:02:58   285   2268   20.5   43.5   1.7   20.8
17:04:59   285   2268   20.5   43.5   1.7   20.8
17:06:59   285   2268   20.5   43.5   1.5   20.8
17:08:58   285   2268   20.5   43.5   1.6   20.8
17:10:58   285   2268   20.5   43.5   1.6   20.7
17:12:59   285   2268   20.5   43.5   1.5   20.6
17:14:58   285   2268   20.5   43.5   1.5   20.7
17:16:58   285   2268   20.5   43.5   1.5   20.6
17:18:58   285   2268   20.5   43.5   8.8   24.9
17:20:59   285   2268   20.5   43.5   8.8   25.0
17:22:59   285   2268   20.5   43.5   8.5   24.8
17:24:58   285   2268   20.5   43.5   1.5   20.6
17:26:59   285   2268   20.5   43.5   1.4   20.7
17:28:58   285   2268   20.5   43.5   1.4   20.6
17:30:59   285   2268   20.5   43.5   1.4   20.6
17:32:58   285   2268   20.5   43.5   1.3   20.6
17:34:59   285   2268   20.5   43.5   1.4   20.6
17:36:58   285   2268   20.5   43.5   1.3   20.6
17:38:58   285   2268   20.5   43.5   1.4   20.6
17:40:58   285   2268   20.5   43.5   1.3   20.6
17:42:58   285   2268   20.5   43.5   1.3   20.6
17:44:58   285   2268   20.5   43.5   1.3   20.6
17:46:58   285   2268   20.5   43.5   1.3   20.6
17:48:59   285   2268   20.5   43.5   1.3   20.6
17:50:59   285   2268   20.5   43.5   1.2   20.5
17:52:58   285   2268   20.5   43.5   1.3   20.5
17:54:58   285   2268   20.5   43.5   1.2   20.5
17:56:59   285   2268   20.5   43.5   1.2   20.4
17:58:58   285   2268   20.5   43.5   1.2   20.5
18:00:58   285   2268   20.5   43.5   1.2   20.4
18:02:58   285   2268   20.5   43.5   1.2   20.4
18:04:59   285   2268   20.5   43.5   1.2   20.4
18:06:58   285   2268   20.5   43.5   1.2   20.4
18:08:59   285   2268   20.5   43.5   1.1   20.4
18:10:59   285   2268   20.5   43.5   1.1   20.4
18:12:59   285   2268   20.5   43.5   1.1   20.4 >>>>>>> at this point I lost connection.
18:16:59   285   2268   21.5   44.0   5.1   20.6 >>>>>>> at this point I re-connected
18:18:59   285   2268   21.5   44.0   5.1   20.5
18:20:59   285   2268   21.5   44.0   4.8   20.4
18:22:58   285   2268   21.5   44.0   4.8   20.3
18:24:58   285   2268   21.5   44.0   4.6   20.3
18:26:59   285   2268   21.5   44.0   4.6   20.1
18:28:58   285   2268   21.5   44.0   4.6   20.2
18:30:58   285   2268   21.5   44.0   4.5   20.1

Then from this point >>

18:47:02   285   2268   21.5   44.0   11.0   24.3

it started to stabilise during the evening/night and when the logfile stopped this morning the last data was >>

10:59:02   285   2268   21.5   44.0   10.5   23.9

I would appreciate any "learned" comments as the instability does not seem to be caused by weather and also seems to be unrelated to time.

[kitz]

OKay, not good, but at least now you have some evidence to show a BT engineer what is happening on your line.  You may have to keep it running longer to see if a pattern emerges.

If I were you I would contact my ISP stating that you appear to have a fault on your line, which materialises itself on occasions as very low upstream SNR.  Tell them that you have tested from the master socket which doesnt make any difference and that you have completed all the necessary diagnostics yourself that you can.

Mention that it is this fault that is keeping your upstream speed so low and therefore limiting you to the 2000 profile.  A 43dB atten line should NOT be limited to only 2000 and therefore you have a fault that needs investigating by a BT engineer.

It may be oxydisation of a joint.. but I really dont know, since that needs a BT engineer to diagnose locally/ onsite now.

Good luck

[Oranged]

Many thanks Kitz and thanks to all who contributed.

[Oranged]

Update:

Waiting on Orange to come back with plan of action ()....I sent them the DMT results.

But I've had 2 recent disconnections (that's 3 in total) which is very unusual as I said in earlier post.

Each time SNRM re-connects at 30+down / 33+up and stays more or less at that.

I've been running DMT diagnosis non-stop (except for the disconnections) since 3 July so at least I have a record.