Transfer to 21C Network

[#1]

just had a massive spike of interference which actually disconnected my dsl  Also sent my SNRM all over the place..... just hope the BTOR engineer turns up tomorrow and starts investigating this properly.
Also just happened to check the router and getting the occasional red internet light
Uptime: 0 days, 0:19:05
FEC Errors (Up/Down): 0 / 28,561
CRC Errors (Up/Down): 0 / 148
HEC Errors (Up/Down): 0 / 1,899

[#2]

Still quiet night apart from a few massive spikes that actually disconnected me, but one thing I have noticed. My SNRM is now up about 16db, when the interference starts, usually about 17:00-18:00 hrs the SNRM drops, sometimes to as low as 13 but my FEC and CRC graphs are merely showing the occasional large spikes, nothing like the horrendous graphs I had the other week. The interference normally stops about 23:00hrs and I've just noticed while neither FEC or CRC graphs are showing anything the SNRM has risen once again to about 16db.
Is the SNRM been so high the reason my graphs are no longer showing the interference ? I'm beginning to think that what I am seeing is the actual peaks of what would be horrendous interference if it wasn't been suppressed.
DSLAM/MSAN type: IFTN
DSL mode:      G.992.5 Annex A
Status:        DSL Link Up
0 days, 5:56:39

Downstream Upstream
Attenuation (dB):      27.5 14.3
Connection speed (kbps): 10387 888
SNR margin (dB):        15.6 10.0
Power (dBm):            0.0 4.8
Interleave depth:      64 0
RSCorr/RS (%):          38729.2308 0.0001
RSUnCorr/RS (%):       
ES/hour:               
INP:                   

[#3]

Your filtered faceplate would seem to be helping perhaps. See what it's looking like without it - but make sure you use the disconnect method and sync when the interference is not there, it might be more convincing when the engineer turns up. If that cable was replaced it would likely reduce the effects somewhat more.

[#4]

08:00hrs BTOR engineer phoned to say he was on his way
08:30hrs BTOR engineer arrived
After a discussion about the cable and the REIN interference he did some tests on the broadband and a copper line test. The copper line test failed so he replaced my cables. I now have a brand new cable from the pole to my new master socket. New BT Openreach filtered faceplate fitted
Further testing and the copper line test passed.
Discussed the REIN problem and after looking at my graphs he agreed and has booked a REIN engineer to investigate. so there was no need for the co op call
SNRM has reset and now syncs at above 16Mb
11:40hrs BTOR engineer left
You are currently connected to gateway pcl-ag03.
This is located in City Lifeline House.
-----------------------------------------------
Phone exchange:
    HOLYHEAD
Estimated line speed:
    8Mb (This may vary between 6Mb and 10Mb) - Checked on 2013-04-23 02:54:03
Current line speed:
    10.5 Mb
-----------------------------------------------
Download speedachieved during the test was - 10.09 Mbps
For your connection, the acceptable range of speeds is 4 Mbps-21 Mbps.
IP Profile for your line is - 14.81 Mbps
Upload speed achieved during the test was - 0.66Mbps
Additional Information:
Upstream Rate IP profile on your line is - 0.83 Mbps
-----------------------------------------------
DSL Connection
Link Information

Uptime: 0 days, 0:31:15
DSL Type: ITU-T G.992.5
Bandwidth (Up/Down) [kbps/kbps]: 888 / 16,781
Data Transferred (Sent/Received) [MB/MB]: 6.92 / 107.93
Output Power (Up/Down) [dBm]: 12.1 / 0.0
Line Attenuation (Up/Down) [dB]: 14.2 / 27.0
SN Margin (Up/Down) [dB]: 14.9 / 5.9
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): 33 / 0
FEC Errors (Up/Down): 0 / 43,147
CRC Errors (Up/Down): 0 / 1
HEC Errors (Up/Down): 0 / 9
----------------------------------------------
So far everything is looking good, line on 10 day training and REIN engineer on the case, so many thanks to Anotherone and all at PN for their help in this matter. The BTOR Engineer was brilliant and I would be pleased if PN passed that on:)
Could someone from PN nudge my current line speed thank you

[#5]

That's brilliant, just what the doctor ordered   I've a funny feeling some nice DCT member will be along to nudge your Current Line Speed shortly.

[#6]

Many thanks Anotherone, wouldn't have got this far without your advice and help.

[#7]

Your profiles been changed for you

[#8]

Hi gtowen,
Sorry I didn't get back to you sooner. I've just updated your speed profile for you. You'll just need to drop your PPP session for that to take effect (It should do it itself automatically shortly).
That's really encouraging news regarding the engineer visit. I'll get onto your Fault Ticket this afternoon and grab those Engineer Notes and keep an eye on proceedings for you

[#9]

Thank you Chris, and thank you Chris

[#10]

Download speedachieved during the test was - 14.66 Mbps
For your connection, the acceptable range of speeds is 4 Mbps-21 Mbps.
IP Profile for your line is - 14.81 Mbps
Upload speed achieved during the test was - 0.71Mbps
Additional Information:
Upstream Rate IP profile on your line is - 0.83 Mbps
Much better 

[#11]

If your connection drops in the next few minutes...it's only me testing your line

[#12]

 Ok
[Edit]
No disconnection 

[#13]

Testing has completed

[#14]

BTW Chris, chatting with the BTOR engineer this morning he took one look at the Bitloading graphs I have (example uploaded) and said it was definitely a REIN problem   Even showed me photos he had on his work laptop of similar graphs. He also stated that the REIN engineer could tune his gadget/meter to the missing tones in the graph and could then pin point the exact cause of the problem

[#15]

Yep - that's why I wanted to make sure that a REIN Case was raised by the engineer. Thankfully there was no need for the co op call as the engineer appears to have done a spot on job