So yesterday I had Openreach at last install FTTC however I do not think the engineer did it correctly. I explained that my computer and router etc. is nowhere near the master socket and that I am currently using an extension socket for my ADSL connection. Looking at where he'd run a cable he decided that he'd try using the current extension as the VDSL socket, replacing the extension faceplate with the VDSL faceplate. He seemed to get decent speeds however from it, I think I remember his JDSU recording 40,000 and 8,000 for download and upload attainable rate respectively. Since then I have had some odd issues. I found that installing microfilters on the cordless handset I use increased the speed on speedtest from 32Mbps to around 38Mbps. My upload also seems to fall short of what it should be, attaining only 6Mbps. Should I be phoning Openreach or is this actually ok?
For exact figures, this my speedtest currently.
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fwww.speedtest.net%2Fresult%2F1872820056.png&hash=24d7fad4dcfcc3bf919c1a48c7935695cbf379c2) (http://www.speedtest.net)
If it matters BT's speedtest keeps giving me the error "The Performance Tester is currently unable to run a speed test for your broadband connection. Please try again shortly, however if this problem persists, raise the issue with your service provider."
Thanks for your help. My only concern is when I saw the JDSU the attainable rate vs max attainable was 99% on the upload and I think the max was 8100ish. And also the way he installed it, the VDSL faceplate is not on the master socket, is that ok?
No it isn't, the drop wire goes to the master socket. This then goes to the 2 extension sockets, one of which has had the VDSL faceplate fitted.
seems pretty clear to me by the description that it aint been done right. There is no such thing as unorthodox its either done right or done wrong and that is done wrong. Filters on a VDSL circuit, dont think so! The SSFP should be doing all the filtering as it should be at the first (master) socket, if you've got an SSFP where an extension should be then it defeats the purpose.
curiosity killed the cat
C:\Users\Ben>tracert bbc.co.uk
Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.lan [192.168.1.1]
2 7 ms 6 ms 6 ms 217.32.141.4
3 7 ms 7 ms 7 ms 217.32.140.206
4 12 ms 12 ms 12 ms 217.41.216.130
5 12 ms * * 217.41.222.82
6 11 ms 11 ms 11 ms 217.41.222.178
7 12 ms 11 ms 11 ms acc1-10GigE-0-2-0-6.bm.21cn-ipp.bt.net [109.159.
248.108]
8 24 ms 20 ms 23 ms core1-te0-15-0-0.ealing.ukcore.bt.net [109.159.2
48.12]
9 19 ms 18 ms 82 ms peer2-xe1-0-0.telehouse.ukcore.bt.net [109.159.2
54.104]
10 21 ms 21 ms 21 ms 194.74.65.42
11 * * * Request timed out.
12 21 ms 21 ms 20 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
13 19 ms 19 ms 20 ms 132.185.255.134
14 22 ms 21 ms 21 ms 212.58.241.131
Trace complete.
This is now more worrying. Since the uplift I think this could be impacting my speeds. I have removed the ring wire at the MAIN master socket to try and reduce interference and I have plugged the DECT station into the faceplate's filter, thus eliminating ALL external filters. Another point to note, I'm using the HomeHub v2 in the filtered socket as I require it's DECT station functionality. This results it a strange situation. When my connection dies and reconnects, the modem and it fight, and eventually the modem wins. Once the modem has a connection it holds on and the homehub has no issue. I find this odd since it is running through a filter...
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fspeedtest.net%2Fresult%2F1897538044.png&hash=7ce195e773a17e892ed5f461014f7d101fcaee88)
Just now
(Note Speedtest thought I was nearer Aberdeen than Gloucester, I'm in Cornwall so this obviously isn't true.)
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fspeedtest.net%2Fresult%2F1892349127.png&hash=30fb1049750e3bd09bf76aaad36e1fa4ab034985)
FridayCode: [Select]C:\Users\Ben>tracert bbc.co.uk
Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.lan [192.168.1.1]
2 7 ms 6 ms 6 ms 217.32.141.4
3 7 ms 7 ms 7 ms 217.32.140.206
4 12 ms 12 ms 12 ms 217.41.216.130
5 12 ms * * 217.41.222.82
6 11 ms 11 ms 11 ms 217.41.222.178
7 12 ms 11 ms 11 ms acc1-10GigE-0-2-0-6.bm.21cn-ipp.bt.net [109.159.
248.108]
8 24 ms 20 ms 23 ms core1-te0-15-0-0.ealing.ukcore.bt.net [109.159.2
48.12]
9 19 ms 18 ms 82 ms peer2-xe1-0-0.telehouse.ukcore.bt.net [109.159.2
54.104]
10 21 ms 21 ms 21 ms 194.74.65.42
11 * * * Request timed out.
12 21 ms 21 ms 20 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
13 19 ms 19 ms 20 ms 132.185.255.134
14 22 ms 21 ms 21 ms 212.58.241.131
Trace complete.
I've also done a BT speedtest though I forgot to save the profile (doh). From what I remember I had the full 20 up but only 55 down.
24 hours Near End Far End
CRC 4294967287 0
FEC 4294965975 0
ES 0 0
SES 0 0
UAS 77 0
Current 15 mins Near End Far End
CRC 4294967256 0
FEC 4294947535 1
ES 4294967256 4294967264
SES 0 4294967291
UAS 0 0
24 hours Near End Far End
CRC 47 0
FEC 24707 1
ES 42 0
SES 4294967295 0
UAS 30 0
Alpha # echo "bbsg 0" > /tmp/pipe/dsl_cpe0_cmd
Alpha # cat /tmp/pipe/dsl_cpe0_ack
nReturn=0 nDirection=0 nNumData=3
nFormat=(nBandIndex, (nLimit_firstToneIndex, nLimit_lastToneIndex), (nBorder_fir
stToneIndex, nBorder_lastToneIndex)) nData="
(00,(0010,0031),(0010,0031))
(01,(0882,1193),(0882,1193))
(02,(1984,2324),(2073,2315))
"
Alpha # echo "bbsg 1" > /tmp/pipe/dsl_cpe0_cmd
Alpha # cat /tmp/pipe/dsl_cpe0_ack
nReturn=0 nDirection=1 nNumData=3
nFormat=(nBandIndex, (nLimit_firstToneIndex, nLimit_lastToneIndex), (nBorder_fir
stToneIndex, nBorder_lastToneIndex)) nData="
(00,(0033,0857),(0033,0857))
(01,(1218,1959),(1218,1849))
(02,(2795,3391),(2795,3373))
Current 15 mins Near End Far End
CRC 4294967292 0
FEC 4294967137 0
ES 114 0
SES 29 0
UAS 66 0
24 hours Near End Far End
CRC 4294967292 0
FEC 4294967137 0
ES 114 0
SES 29 0
UAS 66 0
Also, not sure if it's just the ECI modem being dumb or there is actually an issue butCRC is definitely not identified correctly. You wouldn't have a connection at all with that error rate.Code: [Select]24 hours Near End Far End
CRC 4294967287 0
FEC 4294965975 0
ES 0 0
SES 0 0
UAS 77 0
EDIT2: I'm hoping this data is bogus:Code: [Select]Current 15 mins Near End Far End
CRC 4294967256 0
FEC 4294947535 1
ES 4294967256 4294967264
SES 0 4294967291
UAS 0 0
24 hours Near End Far End
CRC 47 0
FEC 24707 1
ES 42 0
SES 4294967295 0
UAS 30 0
EDIT3:
Found the band plan command, first is upstream, second is downstream.Code: [Select]Alpha # echo "bbsg 0" > /tmp/pipe/dsl_cpe0_cmd
Alpha # cat /tmp/pipe/dsl_cpe0_ack
nReturn=0 nDirection=0 nNumData=3 nFormat=(nBandIndex, (nLimit_firstToneIndex, nLimit_lastToneIndex), (nBorder_firstToneIndex, nBorder_lastToneIndex)) nData="
(00,(0010,0031),(0010,0031))
(01,(0882,1193),(0882,1193))
(02,(1984,2324),(2073,2315))
"
Alpha # echo "bbsg 1" > /tmp/pipe/dsl_cpe0_cmd
Alpha # cat /tmp/pipe/dsl_cpe0_ack
nReturn=0 nDirection=1 nNumData=3 nFormat=(nBandIndex, (nLimit_firstToneIndex, nLimit_lastToneIndex), (nBorder_firstToneIndex, nBorder_lastToneIndex)) nData="
(00,(0033,0857),(0033,0857))
(01,(1218,1959),(1218,1849))
(02,(2795,3391),(2795,3373))
Those error counts are pulled directly from the web interface, aka ECI's not mine.
I'll add band plans to eDMT shortly.
Still with my connection, could it just be that the DSLAM needs to retrain? That's what I'm hoping for, an uplift really shouldn't be detrimental :P
My upstream has significantly decreased, as has the maximum attainable and my latency has increased. I have since then reset my router due to causing the pipe to hang (got a command wrong, causes pipe to hang sometimes). I have had the modem on for just over an hour, and the 24 hour count resets on every reboot so that's one hours worth. That doesn't look so bad. Also, 42/5 is significantly less than the 55/20 I'm estimated.
How weird!
Still, what should I do about my upstream going down?
Could it be the fact that the internal extension has cross-talk on that upstream band?
Still, what should I do about my upstream going down?
The master socket is an NTE5 type, I have since removed the ring wire. All extensions are on a "bus" from this as far as I can tell. The engineer said that the internal line quality was okay since this house was new as of last summer and at that point he was getting more or less full attainable rate for the 40/10 package.
I ordered the so called 'uplift' from 40/10 to 80/20 as I was quoted 55/20 over the 40/10, I obviously took the opportunity. For a few days I had the stable readings you have seen although now my upload has began to drop even lower. Its now only 5000000kb/s attainable (the sync rate is actually HIGHER).
I am actually not sure which cabinet I am connected too. There is one cabinet however it doesn't appear to have it's FTTC counterpart. The engineer mentioned the cabinet being "just down the road" so I assume it's quite close.
I have removed the HH2 to remove all possibility of conflict, this has made no change.
Overall that is an accurate account.
Alpha # echo "g997lsg 0 1" > /tmp/pipe/dsl_cpe0_cmd
Alpha # cat /tmp/pipe/dsl_cpe0_ack
nReturn=0 nDirection=0 nDeltDataType=1 LATN=0 SATN=0 SNR=62 ATTNDR=8650125 ACTPS=-901 ACTATP=109
Alpha # echo "g997lsg 1 1" > /tmp/pipe/dsl_cpe0_cmd
Alpha # cat /tmp/pipe/dsl_cpe0_ack
nReturn=0 nDirection=1 nDeltDataType=1 LATN=231 SATN=178 SNR=64 ATTNDR=42533120 ACTPS=-901 ACTATP=55
The master socket is an NTE5 type, I have since removed the ring wire. All extensions are on a "bus" from this as far as I can tell. The engineer said that the internal line quality was okay since this house was new as of last summer and at that point he was getting more or less full attainable rate for the 40/10 package.
I ordered the so called 'uplift' from 40/10 to 80/20 as I was quoted 55/20 over the 40/10, I obviously took the opportunity. For a few days I had the stable readings you have seen although now my upload has began to drop even lower. Its now only 5000000kb/s attainable (the sync rate is actually HIGHER).
I am actually not sure which cabinet I am connected too. There is one cabinet however it doesn't appear to have it's FTTC counterpart. The engineer mentioned the cabinet being "just down the road" so I assume it's quite close.
I have removed the HH2 to remove all possibility of conflict, this has made no change.
Overall that is an accurate account.
Am not getting involved in the 'speed issues', just wanted to point out that the 'Fibre Cab' can be anywhere within 100mtrs of the existing 'Copper/Ali cab'. It doesn't neccesarily have to be sited right next to it. Just FYI. :)
Since the 80/20 uplift the actual upstream rate has dropped to 5000000.
Channel Status Upstream Downstream
Actual Net Data Rate 4908000 kbps 38276000 kbps
Actual Interleave Delay 0 ms 975 ms
Actual INP 0 Symbols 30 Symbols
Attainable Net Data Rate 5228652 kbps 44221344 kbps
Transmit Power 115 dBm 26 dBm
Actual Net Data Rate 4908000 kbps 38276000 kbps
. . .
Attainable Net Data Rate 5228652 kbps 44221344 kbps
I feel a peculiar sensation when looking at two of those lines and the claimed units --QuoteActual Net Data Rate 4908000 kbps 38276000 kbps
. . .
Attainable Net Data Rate 5228652 kbps 44221344 kbps
:-\ :help:
seems pretty clear to me by the description that it aint been done right. There is no such thing as unorthodox its either done right or done wrong and that is done wrong. Filters on a VDSL circuit, dont think so! The SSFP should be doing all the filtering as it should be at the first (master) socket, if you've got an SSFP where an extension should be then it defeats the purpose.
Welcome to the Kitz fora, Openreach Dude.
You will have seen from that minor interaction with BBB that we are a cat and Openreach Engineer friendly site.
Unfortunately the OP never provided the requested pictures and so, to this day, no opinion has been formed (by the regular members here) regarding that installation . . . :no:
Is there anything that you could possibly tell us -- in the Introductions (http://forum.kitz.co.uk/index.php/board,11.0.html) forum, please -- about yourself and your area of expertise within Openreach?
Seems to be quite a bit of expertise on this forum as it is :)
You'll also find that we are willing to learn new techniques or tips. :)