General Discussion
  >> Fibre Broadband


Register (or login) on our website and you will not see this ad.


Pages in this thread: 1 | 2 | 3 | 4 | (show all)   Print Thread
Standard User alidaf
(newbie) Sun 19-Mar-17 08:15:09
Print Post

When is FTTC not FTTC?


[link to this post]
 
I switched to fibre since our exchange went live around 2 years ago. I've had nothing but problems; first with BT and now with Sky.
Constant disconnections! I left BT because it appeared from the router's tr069 logs that the disconnections were caused by remote management, but the Sky router logs aren't as cryptic and clearly show the VDSL2 line being dropped. I've now had 8 or 9 Openreach visits and most claim to have found and fixed a fault, but the problem persists albeit slightly better. I was somewhat alarmed though, when one of the more recent technicians told me that even though the service is advertised as FTTC, it actually isn't. Our cabinet still has a copper connection to the exchange.
How can this possibly be? Even the Openreach website lists the exchange (Manor Park) as FTTC (Cabinet No 9). The most recent technician diagnosed a difference in wire lengths between the exchange and cabinet as a potential problem (amber warning), which also suggests that we don't actually have FTTC.
Is this common practice or simply Openreach misleading customers?
Standard User WilliamGrimsley
(committed) Sun 19-Mar-17 08:41:06
Print Post

Re: When is FTTC not FTTC?


[re: alidaf] [link to this post]
 
Hmm, very strange.

Are you able to post line stats from the router? This will allow us to confirm that the line is activated for VDSL2.
Standard User alidaf
(newbie) Sun 19-Mar-17 08:44:50
Print Post

Re: When is FTTC not FTTC?


[re: WilliamGrimsley] [link to this post]
 
Here's a snippet (I have logs going back to January):

Mar 18 09:15:14 syslog: Lease renewed 3600 ip 151.227.178.3
Mar 18 09:42:50 syslog: Lease renewed 3600 ip 151.227.178.3
Mar 18 10:07:08 syslog: Lease renewed 3600 ip 151.227.178.3
Mar 18 10:12:05 syslog: [256911.764000] Line 0: VDSL2 link down
Mar 18 10:12:08 syslog: [256914.203000] Line 0: xDSL G.994 training
Mar 18 10:12:08 syslog: Clear IP addresses. IP connection DOWN.
Mar 18 10:12:22 syslog: [256928.209000] Line 0: VDSL G.993 started
Mar 18 10:14:00 syslog: [257026.997000] Line 0: VDSL2 link up, Bearer 0, us=6000, ds=22400
Mar 18 10:14:00 syslog: [257027.003000] Line 0: VDSL2 link up, Bearer 1, us=0, ds=0
Mar 18 10:14:11 syslog: Send out NTP request to ntp1.isp.sky.com
Mar 18 10:15:02 syslog: ptm0.1 - WAN link UP.
Mar 18 10:15:02 syslog: Received valid DHCP lease from server. Connection UP.
Mar 18 10:15:02 syslog: Connection Up. SNO/MAC/IP/SWVER: [AC10163E000884/902106762208/151.227.178.3/2.01.1860.R]
Mar 18 10:15:02 syslog: Send out NTP request to ntp1.isp.sky.com
Mar 18 10:15:02 syslog: Received NTP Sync Reply from ntp1.isp.sky.com
Mar 18 10:15:02 syslog: System time is up to date
Mar 18 10:15:02 syslog: Received NTP Sync Reply from ntp1.isp.sky.com
Mar 18 10:39:32 syslog: Lease renewed 3600 ip 151.227.178.3
Mar 18 11:13:24 syslog: Lease renewed 3600 ip 151.227.178.3
Mar 18 11:40:42 syslog: Lease renewed 3600 ip 151.227.178.3
Mar 18 12:11:41 syslog: [264088.116000] Line 0: VDSL2 link down
Mar 18 12:11:43 syslog: [264090.087000] Line 0: xDSL G.994 training
Mar 18 12:11:43 syslog: Clear IP addresses. IP connection DOWN.
Mar 18 12:11:56 syslog: [264103.108000] Line 0: VDSL2 link down
Mar 18 12:11:57 syslog: [264104.113000] Line 0: ADSL G.992 started
Mar 18 12:12:00 syslog: [264107.125000] Line 0: ADSL link down
Mar 18 12:12:01 syslog: [264108.130000] Line 0: ADSL G.992 started
Mar 18 12:12:02 syslog: [264109.143000] Line 0: ADSL link down
Mar 18 12:12:03 syslog: [264110.146000] Line 0: ADSL G.992 started
Mar 18 12:12:04 syslog: [264111.158000] Line 0: ADSL link down
Mar 18 12:12:05 syslog: [264112.161000] Line 0: ADSL G.992 started
Mar 18 12:12:08 syslog: [264115.174000] Line 0: ADSL link down
Mar 18 12:12:09 syslog: [264116.177000] Line 0: ADSL G.992 started
Mar 18 12:12:11 syslog: [264118.189000] Line 0: ADSL link down
Mar 18 12:12:12 syslog: [264119.193000] Line 0: ADSL G.992 started
Mar 18 12:12:13 syslog: [264120.213000] Line 0: ADSL link down
Mar 18 12:12:19 syslog: [264126.219000] Line 0: ADSL G.992 started
Mar 18 12:12:21 syslog: [264128.231000] Line 0: ADSL link down
Mar 18 12:12:23 syslog: [264130.235000] Line 0: ADSL G.992 started
Mar 18 12:12:24 syslog: [264131.246000] Line 0: ADSL link down
Mar 18 12:12:25 syslog: [264132.249000] Line 0: ADSL G.992 started
Mar 18 12:12:26 syslog: [264133.260000] Line 0: ADSL link down
Mar 18 12:12:28 syslog: [264135.263000] Line 0: ADSL G.992 started
Mar 18 12:12:30 syslog: [264137.276000] Line 0: ADSL link down
Mar 18 12:12:31 syslog: [264138.280000] Line 0: ADSL G.992 started
Mar 18 12:12:34 syslog: [264141.291000] Line 0: ADSL link down
Mar 18 12:12:35 syslog: [264142.294000] Line 0: ADSL G.992 started
Mar 18 12:12:36 syslog: [264143.306000] Line 0: ADSL link down
Mar 18 12:12:37 syslog: [264144.309000] Line 0: ADSL G.992 started
Mar 18 12:12:40 syslog: [264147.321000] Line 0: ADSL link down
Mar 18 12:12:41 syslog: [264148.324000] Line 0: ADSL G.992 started
Mar 18 12:12:44 syslog: [264151.335000] Line 0: ADSL link down
Mar 18 12:12:45 syslog: [264152.338000] Line 0: ADSL G.992 started
Mar 18 12:12:48 syslog: [264155.350000] Line 0: ADSL link down
Mar 18 12:12:52 syslog: [264159.353000] Line 0: ADSL G.992 started
Mar 18 12:12:57 syslog: [264164.365000] Line 0: ADSL link down
Mar 18 12:13:01 syslog: [264168.369000] Line 0: ADSL G.992 started
Mar 18 12:13:04 syslog: [264171.383000] Line 0: ADSL link down
Mar 18 12:13:05 syslog: [264172.386000] Line 0: ADSL G.992 started
Mar 18 12:13:06 syslog: [264173.398000] Line 0: ADSL link down
Mar 18 12:13:07 syslog: [264174.402000] Line 0: ADSL G.992 started
Mar 18 12:13:08 syslog: [264175.414000] Line 0: ADSL link down
Mar 18 12:13:10 syslog: [264177.418000] Line 0: ADSL G.992 started
Mar 18 12:13:11 syslog: [264178.431000] Line 0: ADSL link down
Mar 18 12:13:16 syslog: [264183.435000] Line 0: ADSL G.992 started
Mar 18 12:13:18 syslog: [264185.446000] Line 0: ADSL link down
Mar 18 12:13:24 syslog: [264191.451000] Line 0: ADSL G.992 started
Mar 18 12:13:25 syslog: [264192.462000] Line 0: ADSL link down
Mar 18 12:13:26 syslog: [264193.465000] Line 0: ADSL G.992 started
Mar 18 12:13:29 syslog: [264196.478000] Line 0: ADSL link down
Mar 18 12:13:34 syslog: [264201.486000] Line 0: xDSL G.994 training
Mar 18 12:13:49 syslog: [264216.491000] Line 0: VDSL G.993 started
Mar 18 12:16:13 syslog: [264360.307000] Line 0: VDSL2 link up, Bearer 0, us=4998, ds=20000
Mar 18 12:16:13 syslog: [264360.313000] Line 0: VDSL2 link up, Bearer 1, us=0, ds=0
Mar 18 12:17:23 syslog: ptm0.1 - WAN link UP.
Mar 18 12:17:23 syslog: Received valid DHCP lease from server. Connection UP.
Mar 18 12:17:23 syslog: Connection Up. SNO/MAC/IP/SWVER: [AC10163E000884/902106762208/94.195.69.68/2.01.1860.R]
Mar 18 12:17:23 syslog: Send out NTP request to ntp1.isp.sky.com
Mar 18 12:17:23 syslog: Received NTP Sync Reply from ntp1.isp.sky.com
Mar 18 12:17:23 syslog: System time is up to date


Register (or login) on our website and you will not see this ad.

Standard User witchunt
(member) Sun 19-Mar-17 08:48:36
Print Post

Re: When is FTTC not FTTC?


[re: alidaf] [link to this post]
 
You clearly have a VDSL (FTTC ) connection, one that doesn't work very well for some reason
Standard User WilliamGrimsley
(committed) Sun 19-Mar-17 08:56:59
Print Post

Re: When is FTTC not FTTC?


[re: witchunt] [link to this post]
 
This is weird, it shows ADSL and VDSL2 connections being made...
Standard User richi
(regular) Sun 19-Mar-17 09:11:26
Print Post

Re: When is FTTC not FTTC?


[re: alidaf] [link to this post]
 
In reply to a post by alidaf:
one of the more recent technicians told me that even though the service is advertised as FTTC, it actually isn't. Our cabinet still has a copper connection to the exchange.
Openreach engineers often talk utter nonsense, sadly. (For example, the chap who visited me, saying there was no such thing as LLU, swearing blind that the equipment in all exchanges is all owned and run by BT.)

But there's often a grain of truth in what they say. In this case, I bet your exchange is one of those where the fibre actually runs to a different exchange. So the only connections from the cabinets to your local exchange is the traditional "E-side" copper. It's common if your exchange is quite small but close to a larger exchange.

3 km line on THTG: 19/1.2 Mb/s with Sky
Previously: BT ISDN, Nildram, Plusnet, 186k, EFH, Be*, Plusnet (again), Pulse8
Standard User Nightglow
(member) Sun 19-Mar-17 09:13:24
Print Post

Re: When is FTTC not FTTC?


[re: WilliamGrimsley] [link to this post]
 
One extract, how is this possible,I'm very confused.

Mar 18 12:11:56 syslog: [264103.108000] Line 0: VDSL2 link down
Mar 18 12:11:57 syslog: [264104.113000] Line 0: ADSL G.992 started
Standard User alidaf
(newbie) Sun 19-Mar-17 09:17:06
Print Post

Re: When is FTTC not FTTC?


[re: witchunt] [link to this post]
 
In reply to a post by witchunt:
You clearly have a VDSL (FTTC ) connection, one that doesn't work very well for some reason

Well, Openreach claimed to have found faults and fixed them, but I still have, and a lot of people in the area also have problems. I also get a lot of periods where the DHCP lease isn't renewed for around an hour unless I soft reset the connection.
At one point, Sky claimed that a disconnected lamp near the router was the cause of the problems. It has been one long farce.
The question remains though, should FTTC mean exactly that, i.e. cabinet rather than exchange, because I certainly don't have it. A lot of the problems, from what I have discussed with the Openreach personnel, have been between the cabinet and the exchange.
Standard User alidaf
(newbie) Sun 19-Mar-17 09:19:59
Print Post

Re: When is FTTC not FTTC?


[re: Nightglow] [link to this post]
 
In reply to a post by Nightglow:
One extract, how is this possible,I'm very confused.

Mar 18 12:11:56 syslog: [264103.108000] Line 0: VDSL2 link down
Mar 18 12:11:57 syslog: [264104.113000] Line 0: ADSL G.992 started


Well, I don't have much clue regarding those specific entries but I found the logs from the BT router's tr069 logs even more confusing!
Standard User WilliamGrimsley
(committed) Sun 19-Mar-17 09:25:16
Print Post

Re: When is FTTC not FTTC?


[re: Nightglow] [link to this post]
 
I hope it's just the router's way of saying a DSL connection is being attempted.
Pages in this thread: 1 | 2 | 3 | 4 | (show all)   Print Thread

Jump to