Disconnections Low SNR at Evening

[#1]

This is great, blood annoyed with plusnet and BT both are trying to fob me off, wished I stayed with O2/Sky  
Had a normal BT engineer out not a REIN one that was requested, he did agree with me and that it is a REIN issue and my line is good, he did not know why he had to come when a REIN engineer should of come instead.
He tryed to book a REIN engineer to come out for me but was told by BT that they would have to fix my SNR at 9 first to see if it cures it but now I have a [Censored] sync rate and with multi people trying to use it, it's getting annoying  
Even got told by plusnet support on phone to basically if what BT does fixes it then to lump what you have got, but he did not understand or care about the REIN issue/interference, gets worse when the BT engineer ran out of MK2 face plates  
I wonder how much it would cost me to leave  

 Uptime: 0 days, 1:02:02 
 
DSL Type: ITU-T G.992.5 
 
Bandwidth (Up/Down) [kbps/kbps]: 864 / 3,680 
 
Data Transferred (Sent/Received) [MB/GB]: 38.09 / 1.12 
 
Output Power (Up/Down) [dBm]: 12.6 / 0.0 
 
Line Attenuation (Up/Down) [dB]: 32.7 / 53.0 
 
SN Margin (Up/Down) [dB]: 8.8 / 11.9 
 
System Vendor ID (Local/Remote): TMMB / ---- 
 
Chipset Vendor ID (Local/Remote): BDCM / IFTN 
 
Loss of Framing (Local/Remote): 17 / 0 
 
Loss of Signal (Local/Remote): 2 / 0 
 
Loss of Power (Local/Remote): 0 / 0 
 
Loss of Link (Remote): - 
 
Error Seconds (Local/Remote): 138 / 2 
 
FEC Errors (Up/Down): 3,167 / 528 
 
CRC Errors (Up/Down): 31 / 9 
 
HEC Errors (Up/Down): 102 / 45 
          

[#2]

Hi ONeill,
I can see that your Fault Ticket is still with our Faults Team ready for retested and for further review. A Faults Advisor will give you a call within the next few days to discuss this further with you. Unfortunately we cannot guarantee that a REIN Engineer will attend as there are so few of them around. It's important to note too that REIN investigation isn't something BT Openreach *have* to do, it's something they will investigate if they feel there is a REIN Issue.
I can't see any reason for further investigation to be carried out to get this looked at further. As I say, the Faults Team will be back in touch.

[#3]

What do you mean by  "I can't see any reason for further investigation to be carried out to get this looked at further", leave it as it is and lump it then  ?

[#4]

Sorry, that was a typo.
I can't see any reason why we wouldn't investigate this further.
I appreciate your frustrated, I'll do what I can to help.

[#5]

No problem Chris 
It is frustrating 
In the middle of typing and it resyncs me even lower 

Uptime: 0 days, 0:00:27 
 
DSL Type: ITU-T G.992.5 
 
Bandwidth (Up/Down) [kbps/kbps]: 864 / 3,513 
 
Data Transferred (Sent/Received) [MB/GB]: 45.46 / 1.35 
 
Output Power (Up/Down) [dBm]: 12.6 / 0.0 
 
Line Attenuation (Up/Down) [dB]: 32.7 / 52.5 
 
SN Margin (Up/Down) [dB]: 9.0 / 12.2 
 
System Vendor ID (Local/Remote): TMMB / ---- 
 
Chipset Vendor ID (Local/Remote): BDCM / IFTN 
 
Loss of Framing (Local/Remote): 26 / 0 
 
Loss of Signal (Local/Remote): 3 / 0 
 
Loss of Power (Local/Remote): 0 / 0 
 
Loss of Link (Remote): - 
 
Error Seconds (Local/Remote): 150 / 2 
 
FEC Errors (Up/Down): 3 / 22 
 
CRC Errors (Up/Down): 0 / 0 
 
HEC Errors (Up/Down): 0 / 0 

[#6]

Just had another resync, what the hell is going on  

Uptime: 0 days, 0:01:07 
 
DSL Type: ITU-T G.992.5 
 
Bandwidth (Up/Down) [kbps/kbps]: 866 / 4,731 
 
Data Transferred (Sent/Received) [MB/GB]: 46.15 / 1.36 
 
Output Power (Up/Down) [dBm]: 12.6 / 0.0 
 
Line Attenuation (Up/Down) [dB]: 32.7 / 52.5 
 
SN Margin (Up/Down) [dB]: 6.1 / 6.0 
 
System Vendor ID (Local/Remote): TMMB / ---- 
 
Chipset Vendor ID (Local/Remote): BDCM / IFTN 
 
Loss of Framing (Local/Remote): 35 / 0 
 
Loss of Signal (Local/Remote): 4 / 0 
 
Loss of Power (Local/Remote): 0 / 0 
 
Loss of Link (Remote): - 
 
Error Seconds (Local/Remote): 160 / 2 
 
FEC Errors (Up/Down): 7 / 20 
 
CRC Errors (Up/Down): 0 / 0 
 
HEC Errors (Up/Down): 0 / 0 

Now waiting for the REIN interference so it can kick my SNR down to 0 and force me to restart again  
On a side not that is similar to when I was on O2 

[#7]

Hi ONeill,
What is happening here is you have a hard to locate source of noise which blasts your broadband to hell when it hits.  It will impact broadband regardless of who your ISP is.  BT will try to mask the problem by raising the target SNRM which is not ideal.  Chris has a lot of experience dealing with this BT strategy - work with him, but be prepared for this to take time.  My REIN issue took 6 months to resolve.
Kevin

[#8]

Will do Townman and I am not waiting 6 months of this hell just to fix it   and I know what BT are playing at I just wish they would listen  
Just done it again at 19:19 stats and graph of before and after added.
Got this when trying to ping again

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 192.168.1.254: Destination host unreachable.
Reply from 192.168.1.254: Destination host unreachable.
Reply from 192.168.1.254: Destination host unreachable.
Reply from 192.168.1.254: Destination host unreachable.
Ping statistics for 8.8.8.8:
Connection could not be established: Could not bring up link

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)

Stats before restart

Uptime: 0 days, 2:59:43 
 
DSL Type: ITU-T G.992.5 
 
Bandwidth (Up/Down) [kbps/kbps]: 866 / 4,731 
 
Data Transferred (Sent/Received) [MB/GB]: 93.45 / 2.14 
 
Output Power (Up/Down) [dBm]: 12.6 / 0.0 
 
Line Attenuation (Up/Down) [dB]: 32.7 / 52.5 
 
SN Margin (Up/Down) [dB]: 6.0 / 429496729.3 
 
System Vendor ID (Local/Remote): TMMB / ---- 
 
Chipset Vendor ID (Local/Remote): BDCM / IFTN 
 
Loss of Framing (Local/Remote): 35 / 0 
 
Loss of Signal (Local/Remote): 4 / 0 
 
Loss of Power (Local/Remote): 0 / 0 
 
Loss of Link (Remote): - 
 
Error Seconds (Local/Remote): 589 / 2 
 
FEC Errors (Up/Down): 6,993,630 / 12,362,087 
 
CRC Errors (Up/Down): 5 / 20,843 
 
HEC Errors (Up/Down): 5 / 1,012,181

Stats After Restart

Uptime: 0 days, 0:08:43 
 
DSL Type: ITU-T G.992.5 
 
Bandwidth (Up/Down) [kbps/kbps]: 864 / 3,520 
 
Data Transferred (Sent/Received) [kB/MB]: 326.18 / 1.96 
 
Output Power (Up/Down) [dBm]: 12.6 / 0.0 
 
Line Attenuation (Up/Down) [dB]: 32.7 / 52.5 
 
SN Margin (Up/Down) [dB]: 9.2 / 6.0 
 
System Vendor ID (Local/Remote): TMMB / ---- 
 
Chipset Vendor ID (Local/Remote): BDCM / IFTN 
 
Loss of Framing (Local/Remote): 0 / 0 
 
Loss of Signal (Local/Remote): 0 / 0 
 
Loss of Power (Local/Remote): 0 / 0 
 
Loss of Link (Remote): - 
 
Error Seconds (Local/Remote): 1 / 0 
 
FEC Errors (Up/Down): 252 / 9,559 
 
CRC Errors (Up/Down): 0 / 1 
 
HEC Errors (Up/Down): 0 / 0 

First bit of graph is BT and the exchange resyncing, will try and post another updated graph when I can.

[#9]

Some one managed to get a graph of it going back up, as you can see it goes up from about 6.5db to about 12.0db and checking just now it's sitting at 13.2db, so good for this fix at 9.0db 
Sync is still 3520 and as you know won't go back up until exchange boots me back up

[#10]

Just another graph to add, this time it's gone from 13.0 dB to 6.6 db.
Update
Change the graph to a later one that shows it  going back up to 12.6 dB
Update
Just another graph to show it's fallen again, back to 6.3 dB

[#11]

Quote from: ONeill

so good for this fix at 9.0db

Slight confusion here - the SNRM is not fixed at 9dB, it will always be dynamic depending on the background noise.
Your TARGET SNRM has been fixed to 9dB - this means that on a resynch, you will get a synch speed which delivers a SNRM of 9dB over the then present noise and the DLM will not seek to ever adjust the TARGET.
The actual SNRM will then vary from that point due to the noise ceasing (SNRM rises) or commencing (SNRM falls) - actual SNRM is never static.
@DCT - from the graphs, there looks like a definite noise problem - is there any chance of actually getting a rein engineer on site?
Kevin

[#12]

The Faults Team are due to pick this fault back up within the next 24 hours.
We'll try our best to get a REIN Engineer out, but as I say, it might take a while as there aren't as many REIN trained engineers as we would all like unfortunately.

[#13]

Thanks for getting back to me Chris  ;), I know there are not alot of REIN engineers out there, but I wish that BT would pull there fingers out  
I just wish we can hurry and sort this problem out as being on this speed I'm getting my ear chewed off  
Oh on a side note SNR is 7.0 dB and interference seems louder today, might just be the rain 

[#14]

Got a reply from support the other day and going to send a REIN engineer, I did send them a reply but not sure if they got it, so can some one from DCT tell them I am available, This Friday, Saturday, Monday from 11:00AM - 18:00, but would like it saturday if possible.

[#15]

We've got your response, our Faults Team will pick this up and book the engineer for you.