Radius Log Request

[#1]

Another Rx drop then - might that coincide with you switching off one of the laptops?

[#2]

That is certainly weird, especially as those are being done on the ethernet connected desktop. Apart from that, and the line problem, looking quite good.

[#3]

More graphs -

[#4]

A few comments might be helpful ie are you aware of anything from  17.27 til 20-55  watching i-player playing a game
something switched on for that period?
Again nothing for 14.25 on 25 july - almost identical graph to 20.45pm on 22July.
Maybe just try to leave it without  a manual resync to see when/if the Rx drops back on its own.

[#5]

Hi cedlor  - no i-player, and don't play games.
Nothing switched on here during that period - I was laid in bed shivering/sweating.
I will leave it alone -going back to bed.

[#6]

Sounds like you've caught a bug there John, hope it's not too bad and you recover quickly.
Looks like you had a loss of sync at about 1425/6 ish on the 25th (sync speed graph to match such incidents is always useful), probably the line going intermittent and the resync occurring whilst it was still bad (at slow speed) then the noise reducing so the SNRM then rises. Can you turn the Average SNRM plotting back on again as well, that's sometimes handy.
A "graceful disconnect & resync" might be the best thing (as mentioned in reply #70) when the noise is absent.

[#7]

Yup - It's nasty one, still feel a weak as a kitten.
Router log:

DSL Connection
Link Information

Uptime: 1 day, 20:48:33
DSL Type: ITU-T G.992.5
Bandwidth (Up/Down) [kbps/kbps]: 780 / 7,948
Data Transferred (Sent/Received) [MB/GB]: 120.25 / 0.97
Output Power (Up/Down) [dBm]: 11.8 / 20.2
Line Attenuation (Up/Down) [dB]: 16.7 / 33.5
SN Margin (Up/Down) [dB]: 6.2 / 12.4
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / TSTC
Loss of Framing (Local/Remote): 0 / 0
Loss of Signal (Local/Remote): 1 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): -
Error Seconds (Local/Remote): 852 / 1
FEC Errors (Up/Down): 15,229 / 23,471
CRC Errors (Up/Down): 24 / 96
HEC Errors (Up/Down): 73 / 3,779
BT speedtest::
1. Best Effort Test: -provides background information.
Download  Speed
6.85 Mbps

0 Mbps 7.15 Mbps
Max Achievable Speed
Download speedachieved during the test was - 6.85 Mbps
For your connection, the acceptable range of speeds is 2 Mbps-7.15 Mbps.
IP Profile for your line is - 7.01 Mbps
2. Upstream Test: -provides background information.
Upload Speed
0.52 Mbps

0 Mbps 0.83 Mbps
Max Achievable Speed
Upload speed achieved during the test was - 0.52Mbps
Additional Information:
Upstream Rate IP profile on your line is - 0.83 Mbps
RSL plots to follow.

[#8]

Plots (2 lots of five)

[#9]

Second half

[#10]

My guess is that the phone was in use at ~0925.
I really think it would be good to do a CLT asap, see if they can catch the line problem - what do you think?

[#11]

NFF when testing the copper line:
No fault was found after automated testing.

[#12]

Oh well, not surprising with an intermittent fault.
Hopoefully your sync speed will have returned to near normal John, as the CLT is an intrusive test as you know, and gives a break in sync of just under 3 minutes (usually).

[#13]

SNRM logs to date. Note I had a a resync - as you can see, PN didn't apply the new speed until 0816 this morning - so much for TR069 making things quicker!
I will have post the speed logs from the laptop - hadn't noticed that somehow they had been deactivated on the desktop.

[#14]

Connection speed log for the change yesterday PM - sorry there isn't one for the misbehaviour in the middle of the night.

[#15]

Don't worry about  that. Just handy sometimes to see the matching sync graph when there's a sudden step in SNRM and sync loss.