Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: GigabitEthernet on January 19, 2015, 06:35:11 PM
-
Fibre is finally going to be coming to us within the next three months or so! ;D
I have a few questions though:
- Are the old and new cabinets linked together, if so by what, fibre?
- What's the furthest distance away a fibre cabinet could be installed from a telephone cabinet (I suppose this rests on my first question being true)?
- Have any areas had multiple fibre cabinets installed where they only had a single telephone cabinet before?
- If so, what was the reason for this, was it lack of capacity or because the location of the fibre cabinet was too far away for a lot of residents to benefit from?
-
1) They are linked by copper cables
2) 50 mtrs
3) Never personally seen this. The dial-tone still gets provided from the Exchange through the 'Telephone Cabinet', so there will only be one 'Fibre Cabinet' per one 'Telephone Cabinet'. Most new FTTC cabs are provisioned for 96 circuits initially, but expansion is easily achieved should it be needed without the need for further Cabs.
HTH ? :)
-
Thanks Black Sheep.
Wait, if the cabinets are linked by copper, does that mean that the line becomes longer?
-
Only by a maximum of 50mtrs, but in essence ..... yes. :)
-
Only by a maximum of 50mtrs, but in essence ..... yes. :)
I don't understand how it can be called fibre to the cabinet then, as it isn't fibre to the cabinet, it's copper.
-
Copper broadband (ADSL) is situated in the Telephone Exchanges ..... ergo the total distance of copper/Ali cable used is from the Exchange to the premises.
FTTC Broadband (VDSL) sees the broadband equipment sited in a new Cab within 50mtrs (but usually right next to) of the existing 'Telephone Cab'. This new Cab is fed via a fibre cable from the Exchange. Ergo, the term 'Fibre to the Cabinet' is quite correct, as the only copper/Ali cable used is from the Cab to the premises with regard to the broadband signal.
The telephone signal still travels all the way from the Exchange. Does this make sense ?? :)
-
Trying to keep it 'layman'ish' ................ the telephone signal (ie: the landline telephone number) leaves the Telephone Exchange and enters what you are calling the 'Telephone Cab'.
If FTTC is requested by the EU, the engineer will connect the telephone signal to one of the new cables going to the new FTTC Cab.
In the new FTTC Cab, the telephone number is then mixed together with the new FTTC broadband signal, and both of these signals are then sent back to the older 'Telephone cab' down yet another new cable.
Once both signals are back at the 'Telephone Cab', they are then connected through to the original D-side copper/Ali cable that feeds the EU's premises. So, hopefully you can see that the new FTTC broadband signal begins its journey from the Cab, not the Exchange, thus cutting out 'x' amount of metallic path facility which is the cause of signal losses.
it all hinges on the distance from Cab to Premises as to what speed you will achieve on the new FTTC product.
-
Ahh so the connection between the cabinets is only for the telephone. I understand now! :)
Why doesn't it all just go over fibre though? Because then you could install as many cabinets as you wanted.
-
Why doesn't it all just go over fibre though?
To maintain compatibility with other equipment and allow ADSL migration/fallback; presumably in the long run that would be the intention.
-
regarding #3 my area has 2 cabinets, the reason been the first one filled up and the voice cabinets can hold much more connections than the FTTC cabinets.
-
Ahh so the connection between the cabinets is only for the telephone. I understand now! :)
Why doesn't it all just go over fibre though? Because then you could install as many cabinets as you wanted.
Then BT could not charge you extra for the phone line use . >:D
-
Ahh so the connection between the cabinets is only for the telephone. I understand now! :)
One of the two tie pairs used by your connection is only for the voice connection. The other pair carries both voice and DSL data.
Why doesn't it all just go over fibre though? Because then you could install as many cabinets as you wanted.
I suspect that the DSLAM, in situ at the cabinet, isn't reliable or robust enough to meet the uptime requirements for access to emergency services.
Battery life, in the event of power failure, is probably the weakest aspect.
-
I don't understand how it can be called fibre to the cabinet then, as it isn't fibre to the cabinet, it's copper.
Does this help?
http://www.kitz.co.uk/adsl/fttc.htm#fttc_how_it_works
I suspect that the DSLAM, in situ at the cabinet, isn't reliable or robust enough to meet the uptime requirements for access to emergency services.
Probably correct in that they only use mini-dslams. The ECI is supposedly an MSAN, but Im also thinking about how it would integrate with the MDF. My brain is too tired to think things through, but I should imagine that would mean a massive re-organisation of the network and more investment.
21CN PTSN was a damp squid that never went anywhere and seems to have been abandoned.
-
Hi all,
Thanks to Black Sheep, I have discovered that I am about 760m from the cabinet. What's the best speed anybody has achieved at this distance and also the worst?
-
regarding #3 my area has 2 cabinets, the reason been the first one filled up and the voice cabinets can hold much more connections than the FTTC cabinets.
I wasn't aware this happens, but further investigation shows me indeed it does in some cases. The maximum a DSLAM Cab will cater for is 288 EU's ........... that's a helluva lot of cross-talk !! I'm surprised you're managing to get the synch speed you do !!
For the record .... I have never, ever witnessed a 2 DSLAM - 1 PCP scenario ....... but Chrysalis has shown it does occur.
-
This is the first dual-dslam story I heard...
https://thecomputerperson.wordpress.com/2014/11/10/diary-of-an-fttc-install/
-
will take some pics if I can later this week.
-
I believe Walter knows of sites in the Surrey Hills environs that were initially provisioned with small (fibre) cabinets and once the DSLAM had been upgraded to its maximum number of line cards, a second (fibre) cabinet was then installed. :-X
-
Another indicator of the North-South divide. Us Northerners can't afford FTTC, so 1 DSLAM will do for the whole County. ;) ;D
-
Any info on my estimated speed guys? :)
-
Thanks to Black Sheep, I have discovered that I am about 760m from the cabinet.
I'll take a quick guess at a DS throughput somewhere in the 24 - 30 Mbps range.
-
It is difficult as suggested in the PM, Alec ........ and as also pointed out, vectoring should be in full-flow by the time your village gets FTTC (6 months I think you said ?).
If so, that could also see a marked increase in speed ?? But, B*Cat has pitched it just right based on nothing more than distance. The bit we don't know is conductor size and make-up (Copper or Ali), this could see any guesstimate thrown straight out of the window ?? :)
-
It's copper to the cabinet I'm pretty sure I was told by OR. No idea on the conductor size - where could I find this out?
The line is all overhead BTW apart from about two 50m stretches where the line goes underground. The line basically follows the road which is good (some of the other lines around here go crazy routes!).
-
BS seems you got some positive news if you confident vectoring within 6 months :)
You know if this includes ECI?
-
Alas, not any official statements ...... just what I can glean from documents I have read. This is just my own thoughts, so don't hang me out to dry if it proves otherwise, but I don't think ECI is involved at this time ?? I hope I am proved wrong. ???
-
I hope you wrong also but I have to say I am not surprised.
From all the evidence thats out in the public, it looked quite clear to me that the cost of adding vectoring to ECI is significantly more than is to the huawei cabinets. Also I did observe that when it first got into the public openreach were testing vectoring, they ceased ECI rollout, that to me was a big alarm bell.
So if you are right it looks like we may be heading to a 2 tier service, which will upset alot of people on forums although maybe not so much the average user who wont even know what vectoring is.
I just find it hard to see openreach would rip out the entire dslam within 2-3 years of installing it, I dont think the shareholders would approve such a move, but I really hope we both wrong.
-
So if you are right it looks like we may be heading to a 2 tier service,
There is already a 2 tier service on FTTC (those who's premises are close to the cabinet and those who are further away).
and TBH your lucky to what you have on FTTC.
-
Well we now have our very own FTTC cabinet! There's a lot of digging going on and just today a cabinet has been spotted.
Any idea how long it will until I can order the bloody thing? :P
-
It's lonely in here :(
-
The answer to your questions is that it can be weeks or months or never. In my case the cabinet was installed on 22 March 2014, and it eventually went live on 8 September.
-
Just to add to the above, I suggest that you keep a regular eye on roadworks.org. During my long wait it was the best source of information about what BT were up to in my area, particualrly in respect of cabling work.
-
Well my exchange (TBHT) is supposedly now accepting orders. My cabinet does not appear to be however.
-
Yup confirmed: all the cabinets on my exchange that have FTTC cabinets near them are accepting orders, except mine. Just my luck :(
-
:(
-
It may just be a delay in getting the final cab complete and up to speed.
My cab did not arrive when it should of.
I managed to sign-up before its status was changed to say it was not yet ready.
Yet I got installed on the date I was promised. Dates and availability slide all over the place.
Its only gone when the status says 'NOT AVAILABLE'
Fingers Crossed :fingers: ;D
-
The "box" is sitting there, there aren't any cables lying around, all the traffic lights have gone, etc. An OR van occasionally turns up to do something so who knows.
It is the furthest cabinet from the exchange that is going live, it's a good 2.8 km away from the exchange.
-
The "box" is sitting there
They do that quite a lot ;D
My cab was 'ready' as far as I could see for months, no work being done , no Openreach vans etc
Suddenly very early one morning (approx 4:30am) I tried Plusnets 'Check your Number' page and I was told it was available.
I signed up straight away ;D
Within 2 days it was officially again 'Not available yet' ???
It was installed on the day I had been told, so was very happy.
As I said it is only gone when the Openreach site says it is 'not available' and 'never will be available'.
Things change just the timescales are often unfathomable :D
Wait for what happens next but 'Don't hold you breath !!!'
-
2) 50 mtrs
Apologies for being pedantic @BS but I've paced the distance between my FTTC cab and the old PCP cab several times and I recon the actual cable run is very near to 60m (the direct distance is over 50m anyway), does that mean mine's incorrectly installed? Worse still (in a way) the FTTC cab is further from the exchange / nearer my house than the PCP so the link from the FTTC cab goes 'back' to the PCP then 'back again' past the FTTC cab (does this increase the risk of cross-talk in any way, or is that really only within the same cable bundle?).
-
2) 50 mtrs
Apologies for being pedantic @BS but I've paced the distance between my FTTC cab and the old PCP cab several times and I recon the actual cable run is very near to 60m (the direct distance is over 50m anyway), does that mean mine's incorrectly installed? Worse still (in a way) the FTTC cab is further from the exchange / nearer my house than the PCP so the link from the FTTC cab goes 'back' to the PCP then 'back again' past the FTTC cab (does this increase the risk of cross-talk in any way, or is that really only within the same cable bundle?).
These are the full strict guidelines ...... but only by using a proper 'Time Domain Reflectometer', would you be able to adjudge the true and correct distance of the cable-ties between PCP and DSLAM ?
Copper tie circuits (to the PCP) should not exceed 50 metres
To optimise performance the RDSLAM should always be positioned so the copper tie circuits (to the PCP) do not exceed 50 metres, this is measured termination to termination.
Openreach planning may authorise copper tie circuits up to 90 metres.
Where the above conditions cannot be met dispensation can be requested from Openreach planning who may authorise copper tie circuits up to 90 metres, termination to termination.
90 to 100m requires exceptional dispensation
In exceptional circumstances tie cables exceeding 90 may be requested by email from the xxxxxxxxxxxxxxxxxxxxx
The copper tie circuits must never exceed 100 metres
The length of the copper tie cables between the PCP and RDSLAMs must not exceed 100m (this is measured termination to termination). This is a legislative restriction and must be complied with.
-
I hope you're lucky, but in my village we've had 2 new FTTC cabinets in place sitting there for coming up to 2 YEARS (it'll be the 2 year anniversary in early May), and they are STILL not ready for service. Is that some sort of record around this forum?
Like I say, I hope you're lucky... I must have been bad in a former life.... I'd rather have not known than visit the online checkers almost daily since then.
Good luck!
-
Copper tie circuits (to the PCP) should not exceed 50 metres
To optimise performance the RDSLAM should always be positioned so the copper tie circuits (to the PCP) do not exceed 50 metres, this is measured termination to termination.
Openreach planning may authorise copper tie circuits up to 90 metres.
Where the above conditions cannot be met dispensation can be requested from Openreach planning who may authorise copper tie circuits up to 90 metres, termination to termination.
Thanks for the info, can't really see why mine couldn't be installed 'to spec.' but I don't think they'll come back and fix it now :(
Hope this link works (just for info / interest): https://www.google.co.uk/maps/@52.266669,-0.806934,3a,75y,186.02h,70.23t/data=!3m4!1e1!3m2!1sa-CYP-Z6vVRNXFWl9tHvPw!2e0 PCP is the further away green box on the main road, the one at the side road is NTL/Virgin Meia)
-
I hope you're lucky, but in my village we've had 2 new FTTC cabinets in place sitting there for coming up to 2 YEARS (it'll be the 2 year anniversary in early May), and they are STILL not ready for service. Is that some sort of record around this forum?
Like I say, I hope you're lucky... I must have been bad in a former life.... I'd rather have not known than visit the online checkers almost daily since then.
Good luck!
Wait so OR came along, installed the cabinets and then left...for two years?
-
You can't rush a good job, Alec. ;)
-
You can't rush a good job, Alec. ;)
There's taking your time and there's taking your time. Utter shambles from BT. Wish the contract hadn't been given to them around here.
FTTC is going to be useless for most of the homes connected to my cabinet.
-
Wait so OR came along, installed the cabinets and then left...for two years?
Yes, exactly. I was quite disappointed after 6 month or so of waiting... not sure how to describe the feeling now.
I had a broadband issue before Christmas (2014), and the very kind engineer who visited me offered to look at the FTTC cab on his way out. He rang back 5 minutes later from the cab to say that it all looked "ready". It had power, it had fibre, it had the cable ties to the old cab, so he didn't know why it wasn't ready for service. He suggested I contact openreach, but I get the usual canned response. "Its in our plans, can't give me a definitive date... it'll be ready when its ready...". So that was already 5 months ago, and still nothing.
I'm assuming the cab has fibre, but the other end of the fibre is blocked somewhere before the exchange, but its only a couple of miles.
-
I'm assuming the cab has fibre, but the other end of the fibre is blocked somewhere before the exchange, but its only a couple of miles.
My cab is only a couple of miles from the exchange, but OR had all sorts of trouble with blocked ducts, and on a couple of occasions they had to get the road closed completely while they dug up sections of it. In some places this could be fraught with difficulty.
-
That is absolutely the biggest time-consumer of all ....... old collapsed pot ducts. Sometimes not even collapsed, they will have been smashed with some other utility service doing work, or one of their contractors. Obviously, the chances of the damage being reported so we can do an immediate duct-repair using our split-duct, is minimal.
As soon as our SSR guys come to try and 'Rod & Rope' that section, it's goodnight Vienna.
You won't need me to tell you that this will always be at a busy main road junction ...... it's hardly ever on a tiny cul-de-sac !! ;) ;D
-
I hope your area doesn't extend to Motcombe, Dorset. It's a lovely village with a great community shop and all sorts of clubs and activities. When we were looking to buy in the area it's one place we looked at.
But...
Try putting SP7 9PF in to the availability checker - that's as good as it gets anywhere in the village.
They are on the Shaftesbury exchange which has had FTTC for some time and Motcombe were told they would be getting it. But apparently the ducts are in a dreadful state so they are still waiting. If it follows the direct road from Motcombe to Shaftesbury it is going to be an absolute nightmare to dig and repair.
I was talking to an OpenReach chap working on our cabinet the other day and he said that every time an OpenReach van parks in Motcombe they get descend on by multiple people asking for news.
My guess is that once they do get it, property prices will shoot up by many, many thousands of pounds.
-
I'm still unsure of the exact speed I'll get. I think 750m to the cabinet would be about right but my line has always above average for the lines around here so would that be a good sign?
Is there going to be new technology to get me closer to 100Mbps or is that impossible?
-
I'm still unsure of the exact speed I'll get. I think 750m to the cabinet would be about right but my line has always above average for the lines around here so would that be a good sign?
As I estimated in reply #20 (above), based on that sort of length of the metallic pathway, DS will be somewhere in the 24 - 30 Mbps region.
Is there going to be new technology to get me closer to 100Mbps or is that impossible?
There are existing technologies that are currently not deployed in the Openreach network. I'll name Vectoring and G.Fast . . .
Then there are technologies that have yet to be invented, so who knows? ;)
-
Does the SNR drop on FTTC as much as it does on ADSL (for some people)?
-
It really depends upon what is behind the cause of the daily swing in the SNR and how that "disrupter's" effect is coupled into the circuit.
Once you have a FTTC product deployed, you then have a metallic pathway from the exchange to the PCP, to the FTTC, through a low-pass filter, to the PCP and finally to your home. That is the telephony "side" of the circuit.
For the Internet access, it is a fibre-optic cable from the head-end to the DSLAM in the FTTC, whence it is converted to a VDSL2 signal which joins the metallic pathway your side of the (above mentioned) low-pass filter, travels to the PCP and finally to your home.
If the disturber, which causes the daily swing in the SNR, is coupled into your metallic pathway on the D-side then we would expect to see an identical effect once the FTTC product is deployed. However if the disturber is coupled into your metallic pathway on the E-side then once the FTTC product has been deployed, we would expect to see the effect on the SNR reduced -- if not absent.
Everything about xDSL is very much "try it and see", hence it is only provided as a "best effort" product. The underlying theory of xDSL circuits is very well known. In practice there are a multitude of reasons why an xDSL circuit does not behave as the theory predicts nor as the end-user wishes. :)
-
FTTC is now live on our cabinet!
-
Utter shambles from BT. Wish the contract hadn't been given to them around here.
FTTC is going to be useless for most of the homes connected to my cabinet.
Best ring them up and tell them to decommission it, Alec. ;)
-
Utter shambles from BT. Wish the contract hadn't been given to them around here.
FTTC is going to be useless for most of the homes connected to my cabinet.
Best ring them up and tell them to decommission it, Alec. ;)
I didn't say it would be useless for my home though did I.
-
True. But is not your public duty to inform Openreach that they are unlikely to ever recoup their investment ?? Fall on your sword, if you like ?? :) :)
-
TalkTalk have now informed me that it is a self-install and unless I want to pay £65, there will be no other option.
-
TalkTalk have now informed me that it is a self-install . . .
I would expect that a self-install should not be a problem for you, Alec? :)
-
TalkTalk have now informed me that it is a self-install . . .
I would expect that a self-install should not be a problem for you, Alec? :)
I need the master socket moved though :(
-
Install an SSFP and wire up a modem extension from the A/B terminals to where you want to install the modem. Use CW1308 cable (or Cat5e if you don't mind its greater thickness).
-
Install an SSFP and wire up a modem extension from the A/B terminals to where you want to install the modem. Use CW1308 cable (or Cat5e if you don't mind its greater thickness).
I'm not prepared to do that, in fact I've been told that we will only let an engineer do it.
-
TalkTalk are going to charge for this - is that normal?
-
If it's been provisioned as a self-install, I guess so. Are you sure you can't wire up an extension yourself? It's a straightforward job, and there's plenty of good advice available here.
-
TalkTalk are going to charge for this - is that normal?
You don't get 'owt for nowt, I'm afraid.
You either opt for the self-install, or the managed install product. The latter is modular-based but 99% of the time includes HWS (Home Wiring Solutions), which ensures the modem / combined modem Hub is sited where you want it to go.
This can be done via various methods ...... it would be confirmed with the engineer on-site and the EU as to which is the preferred option.
-
It's just that when I ordered I was told that an engineer would be installing it.
An email is on its way to the CEO's office now as we're getting nowhere with this.
-
And...we're live!
49067 down, 9904 up, with the TalkTalk router. Should I connect the Huawei HG612?
-
And...we're live!
49067 down, 9904 up, with the TalkTalk router.
Are they throughput speeds or synchronisation speeds? And I presume (from your following question) that it is a combined modem/router? :-\
Should I connect the Huawei HG612?
It's up to you to choose! ;)
-
Those are synchronisation speeds. The TalkTalk router actually gives quite a lot of stats, to be fair.
Will it mess up things if I put on the HG612? Is there a training period on fibre?
-
For the first 24 hours following activation, the VDSL2 circuit operates in a "wide open" mode. The DLM will not intervene until the next day (if necessary). So if you are going to make any changes, do so now . . . before the DLM starts watching the circuit with its "evil eye". ;D
If you want to make use of either of the two line monitoring utilities then the HG612 would be a sensible choice. I presume the TalkTalk modem/router has a WAN socket into which the HG612's LAN1 port can be connected? :-\
-
I'm using a separate router anyway so the TalkTalk router is basically just a modem.
Am I likely to see an improvement with the HG612? Ping of 20ms seems a bit high although maybe that's normal?
-
Personally Alec, the TalkTalk router caused havoc for me, ES everywhere - since the HG612 has been connected all has been good!
The TalkTalk router in bridge mode always caused me tonnes of problems, if it were me hook up the HG612, leave it half hour though between disconnecting and reconnecting just in case :)
With the HG612, turn off the QoS to improve the ping and upload speeds as well.
-
I have no experience of the TalkTalk modem/router with which you have been supplied. (In parenthesis I mention that as a TalkTalk customer, the only modem/router with which I was supplied -- a Huawei SmartAX MT882 -- has long been retired to a drawer in the grotto.)
Personally I would use the Huawei HG612, as that is a well-understood device. Who knows what is contained within the firmware of the TalkTalk device, for example? Another benefit from using the HG612 is the ease of gathering circuit (line) statistics.
-
Personally I would use the Huawei HG612, as that is a well-understood device. Who knows what is contained within the firmware of the TalkTalk device, for example? Another benefit from using the HG612 is the ease of gathering circuit (line) statistics.
This is true, TalkTalk routers often get bricked by updates, i've had two die due to failed TR-069 updates. The HG635 I had, caused major issues with the DLM too, plus the Dynamic DNS never worked, neither did the port forwarding very well.
-
With Jamie on one side and the original grump-cat on the other, I wonder what Alex will now choose to do? ;)
-
I've got the HG612 connected but I can't establish a PPPoE connection via my my router. I've reset the HG612 and no luck.
-
I've got the HG612 connected but I can't establish a PPPoE connection via my my router. I've reset the HG612 and no luck.
TalkTalk isn't PPPoE it's simply DHCP - like a typical LAN connection.
-
So how do I setup my Ethernet router running Gargoyle (based on OpenWRT)?
-
Set the Gargoyle Internet/WAN to DHCP(wired) and plug your HG612 into the WAN socket I'd suppose -
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FJIVYfiv.jpg&hash=71982c2ce429e3f181cdf419ee48c6d43534ca89)
http://www.gargoyle-router.com/wiki/doku.php?id=basic
-
Set the Gargoyle Internet/WAN to DHCP(wired) and plug your HG612 into the WAN socket I'd suppose -
\snip\
This should do it :)
-
That works. Thanks a lot! :)
The only issue I have now is that I cannot access the modems stats via the router. The Gargoyle documentation recommends to enable DHCP on the modem and then it should work but that stops the Internet from working.
Sync is a couple of Mb faster on both the downstream and upstream with the HG612 so that's good. There seem to be quite a lot of errors being displayed on the web UI of the HG612 though.
-
With an unlocked HG612 you can just connect the 2nd LAN port to your network - for access to the GUI/stats. I gave mine a static IP address via the web GUI so I always knew where it was.
-
Is that the only way to do it? In the past I've been able to do it via one cable as Gargoyle has this feature built-in: maybe I just need to do some more tinkering.
-
Some more questions:
- Should I get Howlingwolf's firmware?
- How do I check if G.INP is enabled?
- How do I get those fancy graphs people are posting?
-
1. The Howlingwolf firmware is here: http://forum.kitz.co.uk/index.php/topic,14262.0.html
2. Log into the telnet interface and enter 'sh' to get to the shell. Then type 'xdslcmd info --stats' and look for any reference to Bearer 1 in the output of that command.
3. Use DSLstats or HG612_Modem_Stats
-
There seem to be quite a lot of errors being displayed on the web UI of the HG612 though.
Ignore the status as reported by the GUI. Basically it is wrong. The truth is told via a command line telnet session into the device.
-
I've been tinkering and I think the only way to access the HG612 via the Gargoyle router is to get the HG612 to do the routing itself and to then give the Gargoyle router an IP address from its DHCP server.
Something seems wrong about this setup but maybe that's just me. Is the only way to make it work?
-
Stats aren't looking great:
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 10953 Kbps, Downstream rate = 52512 Kbps
Bearer: 0, Upstream rate = 10953 Kbps, Downstream rate = 52640 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 6.1 6.6
Attn(dB): 23.1 0.0
Pwr(dBm): 12.0 5.1
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 239 241
M: 1 1
T: 64 56
R: 0 12
S: 0.1451 0.7026
L: 13232 2892
D: 1 1
I: 240 127
N: 240 254
Counters
Bearer 0
OHF: 6145328 1455580
OHFErr: 29567 21
RS: 0 4182952
RSCorr: 0 260
RSUnCorr: 0 0
Bearer 0
HEC: 14239 0
OCD: 496 0
LCD: 496 0
Total Cells: 1448999819 0
Data Cells: 130603101 0
Drop Cells: 0
Bit Errors: 0 0
ES: 1964 20
SES: 73 0
UAS: 25 25
AS: 14317
Bearer 0
INP: 0.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 2.33 9.87
OR: 82.37 25.92
AgR: 52722.05 10978.59
Bitswap: 10076/10082 303/308
Total time = 3 hours 59 min 2 sec
FEC: 0 260
CRC: 29567 21
ES: 1964 20
SES: 73 0
UAS: 25 25
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 14 min 2 sec
FEC: 0 3
CRC: 2230 1
ES: 169 1
SES: 9 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 0 2
CRC: 447 1
ES: 155 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 3 hours 59 min 2 sec
FEC: 0 260
CRC: 29567 21
ES: 1964 20
SES: 73 0
UAS: 25 25
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 0 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 3 hours 58 min 37 sec
FEC: 0 260
CRC: 29567 21
ES: 1964 20
SES: 73 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Looks like my line isn't enabled for G.INP! :(
-
the talktalk device might be fine hardware wise, but I would not use as the modem (might be ok as router) because of downtime caused by their remote updates.
-
Stats aren't looking great:
Looks like my line isn't enabled for G.INP! :(
I would say that interleaving *may* be applied by the DLM, and yes at the moment G.INP roll outs seem to have been halted.
-
In order to get the master socket moved, TalkTalk would like to send a Qube engineer. Are they a part of Openreach?
-
No .......... they are actually part of our competition.
-
But they will move the master socket?
-
Am still struggling to get my Gargoyle router to allow access to the HG612 with one cable. It was possible before when the router did the PPPoE connection whilst being given an IP via DHCP from the modem (router) but as the IP on fibre seems to be assigned by DHCP, this no longer works.
Any help with this? :)
-
In order to get the master socket moved, TalkTalk would like to send a Qube engineer. Are they a part of Openreach?
Qube Telecommunications Services (http://www.qubegb.com/)
-
But they will move the master socket?
Hmm ?? Good question and one I can't answer I'm afraid ??
I can only comment on other ISP's in-house 'engineers' ....... and fair play to them in the respect that they don't mess around with wiring up to and including the master-socket, as is how it should be.
Not sure how far Qube go though ??
-
But are they allowed to?
-
My guess is that they aren't ???
-
But are they allowed to?
Like B*Sheep, I would presume "No". :-\
However if, for example, a fellow Kitizen entered your abode (clutching her/his gubbins & tool-kit) and re-located the NTE5/A for you no one from Openreach would know. (Personally, in your situation, I would just do it myself -- as, I know, would certain other members. ;) )
-
It's not going to be an easy job to relocate the NTE5. The cable isn't long enough to go where it needs to be.
-
What I'm most disappointed with is the upload speed, it's maxing out at around 10Mb, I was hoping for nearer to 20.
I've never seen an upstream sync so slow actually.
-
Interleaving's been switched on:
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 10755 Kbps, Downstream rate = 55364 Kbps
Bearer: 0, Upstream rate = 10755 Kbps, Downstream rate = 47413 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 6.4 6.3
Attn(dB): 23.2 0.0
Pwr(dBm): 11.9 5.1
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 51 241
M: 1 1
T: 64 55
R: 12 12
S: 0.0349 0.7155
L: 14672 2840
D: 927 1
I: 64 127
N: 64 254
Counters
Bearer 0
OHF: 3270153 745349
OHFErr: 12 7
RS: 837046168 2326786
RSCorr: 48992 22
RSUnCorr: 150 0
Bearer 0
HEC: 27 0
OCD: 2 0
LCD: 2 0
Total Cells: 668403253 0
Data Cells: 9725040 0
Drop Cells: 0
Bit Errors: 0 0
ES: 730 32
SES: 10 0
UAS: 402 392
AS: 7332
Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 2.24 9.87
OR: 85.63 25.92
AgR: 47498.45 10781.19
Bitswap: 3296/3296 5/5
Total time = 6 hours 34 min 48 sec
FEC: 48992 22
CRC: 12 7
ES: 730 32
SES: 10 0
UAS: 402 392
LOS: 1 0
LOF: 9 0
LOM: 0 0
Latest 15 minutes time = 4 min 48 sec
FEC: 4480 0
CRC: 3 0
ES: 1 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 8042 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 6 hours 34 min 48 sec
FEC: 48992 22
CRC: 12 7
ES: 730 32
SES: 10 0
UAS: 402 392
LOS: 1 0
LOF: 9 0
LOM: 0 0
Previous 1 day time = 0 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 2 hours 2 min 11 sec
FEC: 48992 22
CRC: 12 7
ES: 4 7
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
-
I'm starting to have issues.
The Internet whilst fast seems quite temperamental with loading webpages, etc. They'l stop and start and sometimes I'll have to wait a good 10 seconds until they start loading.
Pinging the BBC, I can see fairly frequently, some of the pings timing out, indicating that some data is being lost in transmission.
Is there a solution to this problem?
-
There are unspecified and on-going issues right across the TalkTalk network. :'(
The only thing I can suggest you try is to drop the PPPoE session and allow it to restart.
(Don't cause a resynchronisation event between the CPE - CO equipment -- the problem is not at that level.)
-
The only thing I can suggest you try is to drop the PPPoE session and allow it to restart.
I just had a thought for you both, when you restart the PPPoE session (Dynamic IP DHCP in TalkTalks case), make sure the IP Address changes.
Whenever I manually force the session drop, my IP remains the same on resync.
Keep dropping it until the IP changes (can take a few tries/never happen). Just don't disconnect the modem as B*cat says as a few resyncs of that and you'd be in trouble!
When I had congestion on my exchange, I had to reconnect the session a good few times in an attempt to get a new IP - may solve it?
-
How come on ADSL I could make a connection with PPPoA/PPPoE (when bridging a modem and router) but on VDSL only DHCP will create a connection?
Edit: How can I force a new connection when the HG612 is doing the routing?
-
FTTC uses a different authentication method - PPPoE is used on BT infinity, TalkTalk prefer the DHCP variety - its whatever the ISP purchases from Openreach.
When you say the HG612 is doing the routing, do you mean its creating the session?
What router are you using Alec? No one has any real trouble getting a Dynamic IP session to authenticate on any router - it's easier to configure than the other types ???
My HG612 is the bridge, and then my TP Link router does the authentication side of things, so I reboot my router and that resets my session. This way I don't need to touch the modem for anything.
-
My HG612 is doing the routing and my router gets an IP from its local DHCP server. This way I can access the HG612's stats and use the Internet, all with one cable.
I don't know how to force a new IP on the HG612 when it is doing the routing. That is what I meant ;)
-
I still cant work out what you mean. :-\
What router are you using? .... and do you mean you are using the HG612 as a modem rather than routing.
If you are using the HG612 to get stats, then surely the HG612 is operating as modem only and I cant see how it is doing the routing ???
The modem is responsible for sync. The router is responsible for the PPP session. I think we need more information about what equipment you are using where. There is a way on some routers to run in bridged mode but still be able to get line stats using one cable.
-
The HG612 is set to get an IP address from TalkTalk. It will thus allow any connected device access to the Internet because it has its DHCP server enabled. It will hand out an IP address via DHCP, on its own subnet, i.e. 192.168.2.x.
What I have done is to connect my TP-LINK WDR3600 router to it via ethernet. The TP-LINK router requests an IP address from the HG612 on its local subnet, i.e. 192.168.2.x (in this case). The TP-LINK router can thus connect to the Internet and any connected device will receive an IP address on the TP-LINK router's subnet, i.e. 192.168.1.x (in this case), as it also has its DHCP server enabled.
The TP-LINK router has a static route setup so the HG612 can be accessed via the TP-LINK router, at the address 192.168.2.254. This means I can use only one cable instead of two (if the TP-LINK was getting an IP address from TalkTalk, with the HG612 just acting as the modem).
Does that make sense? :)
-
Re-post.
I think we might have a fault.
Upstream SNR has dropped from 6 to 3.8dB at the same sync speed but surely it shouldn't drop this much during the day?
# xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 10403 Kbps, Downstream rate = 54212 Kbps
Bearer: 0, Upstream rate = 10869 Kbps, Downstream rate = 47465 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 5.8 3.8
Attn(dB): 23.1 0.0
Pwr(dBm): 11.9 5.2
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 51 241
M: 1 1
T: 64 55
R: 12 12
S: 0.0349 0.7080
L: 14688 2870
D: 929 1
I: 64 127
N: 64 254
Counters
Bearer 0
OHF: 47326557 547755
OHFErr: 392 295
RS: 3525550795 1767278
RSCorr: 4412088 4391
RSUnCorr: 14761 0
Bearer 0
HEC: 3424 0
OCD: 102 0
LCD: 102 0
Total Cells: 1083764682 0
Data Cells: 143865658 0
Drop Cells: 0
Bit Errors: 0 0
ES: 118 225
SES: 0 17
UAS: 25 25
AS: 105997
Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 2.23 9.77
OR: 85.72 26.19
AgR: 47550.25 10895.07
Bitswap: 75144/75151 640/644
Total time = 1 days 5 hours 27 min 2 sec
FEC: 4412088 4391
CRC: 392 295
ES: 118 225
SES: 0 17
UAS: 25 25
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 12 min 2 sec
FEC: 117206 2
CRC: 3 1
ES: 1 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 115784 24
CRC: 0 9
ES: 0 9
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 5 hours 27 min 2 sec
FEC: 1022385 59
CRC: 40 80
ES: 14 76
SES: 0 6
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 3389703 4332
CRC: 352 215
ES: 104 149
SES: 0 11
UAS: 25 25
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 1 days 5 hours 26 min 35 sec
FEC: 4412088 4391
CRC: 392 295
ES: 118 225
SES: 0 17
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
-
The HG612 randomly disconnected from the Internet and now cannot get an IP, despite a reboot so we're back to the TalkTalk Super Router for now.
-
Attenuation has dropped to 18.4 dB on the TalkTalk router?
-
Attenuation has dropped to 18.4 dB on the TalkTalk router?
TalkTalk router does report values differently to the HG612 I found. With regard to your repost, I did reply there saying to get some kind of stats monitoring running - even if for 24 hours. This would give others here a better "view" of your line :)
As for the HG612 randomly disconnecting, reset it to the factory defaults where it's a bridge and use it as a Bridge and see where you get with it? It provides better stats than the Super Router as well :)
-
Stats monitoring it is then! :)