Kitz Forum

Broadband Related => FTTC and FTTP Issues => Topic started by: ads on September 09, 2021, 06:11:25 PM

Title: FTTC dropouts
Post by: ads on September 09, 2021, 06:11:25 PM
My BT FTTC has been dropping out this week, couple of times on Monday, again on Tuesday, and now twice so far today. Always between 5-7PM, rest of the time it seems fine.

Code: [Select]
18:06:34, 09 Sep.

:HTTP UserAdmin login from 192.168.1.124 successfully

18:06:25, 09 Sep.

:HTTP UserBasic login from 192.168.1.124 successfully

18:05:55, 09 Sep.

:WAN DHCPv6 Client Prefix : 2a00:23c4:6e82:4600::/56 (valid time = 315360000 / preferred time = 315360000)

18:05:51, 09 Sep.

ppp1:TR69 connectivity to (pbthdm.bt.mo) has been closed

18:05:50, 09 Sep.

ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36

18:05:50, 09 Sep.

ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36

18:05:49, 09 Sep.

ppp1:TR69 connectivity to (pbthdm.bt.mo) has been initiated

18:05:49, 09 Sep.

ppp1:TR69 receiving InformResponse message

18:05:49, 09 Sep.

ppp1:TR69 event found : 4 VALUE CHANGE

18:05:48, 09 Sep.

ppp1:TR69 sending Inform message

18:05:48, 09 Sep.

ppp1:TR69 event found : 4 VALUE CHANGE

18:05:47, 09 Sep.

ppp1:TR69 sending Inform message

18:05:41, 09 Sep.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

18:05:41, 09 Sep.

BR_LAN: Allocated prefix = 2a00:23c4:6e82:4600::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:41, 09 Sep.

BR_LAN: Allocated address = 2a00:23c4:6e82:4600:8aa6:c6ff:fe24:dadb (valid time = 2026291200 / preferred time = 2026291200)

18:05:41, 09 Sep.

BR_LAN: Allocated prefix = 2a00:23c4:6e82:4600::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:41, 09 Sep.

ppp1: Allocated prefix = 2a00:23c4:6e82:4601::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:41, 09 Sep.

ppp1: Allocated prefix = 2a00:23c4:6e82:4600::/56 (valid time = 2026291200 / preferred time = 2026291200)

18:05:41, 09 Sep.

ppp1: Allocated address = 2a00:23c4:6e82:4601:8aa6:c6ff:fe24:dad9 (valid time = 2026291200 / preferred time = 2026291200)

18:05:41, 09 Sep.

ppp1: Allocated prefix = 2a00:23c4:6e82:4601::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:41, 09 Sep.

ppp1:TR69 creating new session with ACS

18:05:41, 09 Sep.

ppp1: Allocated prefix = 2a00:23c4:6e82:4601::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:41, 09 Sep.

ppp1: Allocated prefix = 2a00:23c4:6e82:4600::/56 (valid time = 2026291200 / preferred time = 2026291200)

18:05:41, 09 Sep.

ppp1: Allocated prefix = 2a00:23c4:6e82:4600::/56 (valid time = 2026291200 / preferred time = 2026291200)

18:05:41, 09 Sep.

:WAN DHCPv6 Client Prefix : 2a00:23c4:6e82:4600::/56 (valid time = 315360000 / preferred time = 315360000)

18:05:39, 09 Sep.

ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36

18:05:39, 09 Sep.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

18:05:39, 09 Sep.

BR_LAN: Allocated prefix = 2a00:23c4:6e82:4600::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:39, 09 Sep.

BR_LAN: Allocated address = 2a00:23c4:6e82:4600:8aa6:c6ff:fe24:dadb (valid time = 2026291200 / preferred time = 2026291200)

18:05:39, 09 Sep.

BR_LAN: Allocated prefix = 2a00:23c4:6e82:4600::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:39, 09 Sep.

ppp1: Allocated prefix = 2a00:23c4:6e82:4601::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:39, 09 Sep.

ppp1: Allocated prefix = 2a00:23c4:6e82:4600::/56 (valid time = 2026291200 / preferred time = 2026291200)

18:05:39, 09 Sep.

ppp1: Allocated address = 2a00:23c4:6e82:4601:8aa6:c6ff:fe24:dad9 (valid time = 2026291200 / preferred time = 2026291200)

18:05:39, 09 Sep.

ppp1: Allocated prefix = 2a00:23c4:6e82:4601::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:38, 09 Sep.

ppp1:WAN DHCPv6 Mode : Statefull

18:05:38, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is active

18:05:38, 09 Sep.

BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1

18:05:38, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is inactive

18:05:38, 09 Sep.

ppp1:WAN Router Discovery Setting Updated : M_flag = 1, O_flag = 0

18:05:37, 09 Sep.

ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36

18:05:37, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is active

18:05:37, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is inactive

18:05:37, 09 Sep.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

18:05:37, 09 Sep.

BR_LAN: Allocated prefix = 2a00:23c4:6e82:4600::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:37, 09 Sep.

BR_LAN: Allocated address = 2a00:23c4:6e82:4600:8aa6:c6ff:fe24:dadb (valid time = 2026291200 / preferred time = 2026291200)

18:05:37, 09 Sep.

BR_LAN: Allocated prefix = 2a00:23c4:6e82:4600::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:37, 09 Sep.

BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1

18:05:37, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is active

18:05:36, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is inactive

18:05:36, 09 Sep.

:WAN: SENSING AUTO VDSL

18:05:36, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is active

18:05:36, 09 Sep.

ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36

18:05:36, 09 Sep.

ppp1:New DYN ROUTE is added [81.139.57.100/32 gw 172.16.10.141]

18:05:35, 09 Sep.

ppp1:New DYN ROUTE is added [81.139.56.100/32 gw 172.16.10.141]

18:05:35, 09 Sep.

ppp1:PPP: PPP INFO 81.139.56.100,81.139.57.100

18:05:35, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is inactive

18:05:35, 09 Sep.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

18:05:35, 09 Sep.

BR_LAN: Allocated prefix = 2a00:23c4:6e82:4600::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:35, 09 Sep.

ppp1: Allocated prefix = 2a00:23c4:6e82:4601::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:05:35, 09 Sep.

ppp1: Allocated prefix = 2a00:23c4:6e82:4600::/56 (valid time = 2026291200 / preferred time = 2026291200)

18:05:35, 09 Sep.

ppp1:PPP: PPP INFO

18:05:35, 09 Sep.

ppp:PPP: IPCP_NAK

18:05:35, 09 Sep.

ppp:PPP: CHAP_SUCCESS

18:05:35, 09 Sep.

ppp:PPP: CHAP_RESPONSE

18:05:35, 09 Sep.

ppp:PPP: LCP_GOOD_ACK

18:05:35, 09 Sep.

ppp:PPP: LCP_REQUEST

18:05:34, 09 Sep.

:PPPoE error: timeout

18:05:26, 09 Sep.

:PPPoE error: timeout

18:05:21, 09 Sep.

:PPPoE error: timeout

18:05:16, 09 Sep.

ptm0.101:VLAN VLAN_DATA connected

18:05:16, 09 Sep.

:connection ATM_TV disconnected.[ERROR_USER_DISCONNECT]

18:05:16, 09 Sep.

:connection ATM_DATA disconnected.[ERROR_USER_DISCONNECT]

18:05:16, 09 Sep.

dsl:VDSL link Up: Down Rate=39706Kbps, Up Rate=12829Kbps, SNR Margin Down=0.00dB, SNR Margin Up=6.00dB

18:04:54, 09 Sep.

:VLAN VLAN_DATA disconnected

18:04:53, 09 Sep.

:Connection to the Internet has been terminated.(Reboot,Reconfiguration,forced termination)

18:04:53, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is active

18:04:52, 09 Sep.

:Connection to the Internet has been terminated.(Reboot,Reconfiguration,forced termination)

18:04:52, 09 Sep.

ppp1:Request for a new authenticated connection

18:04:52, 09 Sep.

ppp1:TR69 ConnectionRequest: processing request from ACS

18:04:52, 09 Sep.

ppp1:The DYN ROUTE [81.139.56.100/32 gw 172.16.10.141] is deleted

18:04:52, 09 Sep.

ppp1:The DYN ROUTE [81.139.57.100/32 gw 172.16.10.141] is deleted

18:04:52, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is inactive

18:04:51, 09 Sep.

BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1

18:04:51, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is active

18:04:51, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is inactive

18:04:51, 09 Sep.

ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36

18:04:51, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is active

18:04:51, 09 Sep.

BR_LAN:The LAN DHCPv6 Server is inactive

18:04:51, 09 Sep.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

18:04:51, 09 Sep.

BR_LAN: Revoked prefix = 2a00:23c4:6e82:4600::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:04:51, 09 Sep.

ppp1: Revoked prefix = 2a00:23c4:6e82:4601::/64 (valid time = 2026291200 / preferred time = 2026291200)

18:04:51, 09 Sep.

ppp1: Revoked prefix = 2a00:23c4:6e82:4600::/56 (valid time = 2026291200 / preferred time = 2026291200)

18:04:50, 09 Sep.

dsl:VDSL Link Down: duration was 176582 seconds

17:06:05, 09 Sep.

:WAN DHCPv6 Client Prefix : 2a00:23c4:6e82:4600::/56 (valid time = 315360000 / preferred time = 315360000)

17:03:42, 09 Sep.

ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36

17:03:42, 09 Sep.

ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36

Log I grabbed from the last dropout, anything obvious there? BT website test says they found no issues.

[Moderator edited to change [pre][/pre] tags to [code][/code] tags.]
Title: Re: FTTC dropouts
Post by: ads on September 09, 2021, 06:14:36 PM
Code: [Select]
Noise margin:
6.1 dB / 6.2 dB

Line attenuation:
37 dB

Signal attenuation:
23.1 dB / 37 dB

VPI / VCI:
0/38

Modulation:
G_993_2_ANNEX_B

Latency type:
Fast Path

if that helps ^


Oh and for some reason a tab in Firefox opens; http://www.msftconnecttest.com/00000111500/gui/?item=redirect

Never seen that before

[Moderator edited: As preceding post.]
Title: Re: FTTC dropouts
Post by: Alex Atkin UK on September 10, 2021, 01:39:25 AM
There's not really enough to go on if your router isn't even showing the number of errors.
Title: Re: FTTC dropouts
Post by: ads on September 10, 2021, 02:31:41 PM
That's all the info the stupid BT Hub 6A tells me when the event log is set to all, is there a way to gather more info?
Title: Re: FTTC dropouts
Post by: mofa2020 on September 10, 2021, 02:52:16 PM
are VPI / VCI used on FTTC lines? never seen it before when VDSL is the line modulation.
Title: Re: FTTC dropouts
Post by: burakkucat on September 10, 2021, 04:32:20 PM
are VPI / VCI used on FTTC lines?

No, never.

Quote
. . . never seen it before when VDSL is the line modulation.

It is just the result of a decision by the writer of the system code (or firmware) to display that irrelevant information.
Title: Re: FTTC dropouts
Post by: meritez on September 10, 2021, 04:35:40 PM
That's all the info the stupid BT Hub 6A tells me when the event log is set to all, is there a way to gather more info?

Anything else running at that time, boiler, microwave, etc?
Title: Re: FTTC dropouts
Post by: ads on September 11, 2021, 02:02:14 PM
Nothing new, or obvious

It did just drop out a few minutes ago, the kettle was on, but I don't think that lines up with the other dropouts
Title: Re: FTTC dropouts
Post by: ads on October 13, 2021, 03:18:40 AM
Things went back to normal for a month, then 6+ dropouts today

Is it normal for the BT Home Hub Event Log to display the wrong date every so often after dropouts?

(https://i.imgur.com/Fs014fQ.png)
Title: Re: FTTC dropouts
Post by: Alex Atkin UK on October 13, 2021, 04:02:13 AM
Darn, that's unhelpful as we can see PPP drop but does it drop sync?  (I'd assume so)
Title: Re: FTTC dropouts
Post by: gt94sss2 on October 13, 2021, 05:30:42 AM
Things went back to normal for a month, then 6+ dropouts today

Is it normal for the BT Home Hub Event Log to display the wrong date every so often after dropouts?

Your modem is rebooting - is not just a dropout.

Have you tried a hard reset?
Title: Re: FTTC dropouts
Post by: ads on October 13, 2021, 01:33:48 PM
Yep, left it unplugged for 15 minutes. It continued to drop. It's not the whole hub rebooting though, LAN continues to work (at least it seemed to while I was watching local media).

I ran another BT test thing and finally their automated system says they've detected an issue not at my property and they're going to fix it. Haven't spoken to a human so I don't really know anything else, I guess I just sit on it and hope for the best for now.
Title: Re: FTTC dropouts
Post by: Weaver on October 13, 2021, 01:58:07 PM
Is the modem itself ill? Need a replacement unit / or new PSU ?
Title: Re: FTTC dropouts
Post by: Alex Atkin UK on October 13, 2021, 02:29:43 PM
Your modem is rebooting - is not just a dropout.

Have you tried a hard reset?

Good point, I thought it was a user triggered reboot as I was looking at the time thinking "oh theres a gap", missing the obvious that the date was reset due to the reboot.
Title: Re: FTTC dropouts
Post by: gt94sss2 on October 13, 2021, 05:35:03 PM
Yep, left it unplugged for 15 minutes. It continued to drop. It's not the whole hub rebooting though, LAN continues to work (at least it seemed to while I was watching local media).

Sometimes, especially after the HH upgrades it's firmware, it needs a hard reset to take.

This is not the same as switching it off/on but pressing the reset button at the back (or in the GUI) to reset it to it's default settings.

You can backup your config before doing this and reapply it once reset
Title: Re: FTTC dropouts
Post by: ads on October 14, 2021, 12:44:45 AM
Thanks for the responses. Seeing as BT are apparently working on fixing a fault their system identified outside of my home, I'm going to do nothing and see what they say. I haven't had any more dropouts since around 5am, so maybe they've already done something at the exchange or cabinet. Might be wishful thinking though! I'll make a note of any more dropouts and if need be I'll report back and try the factory reset/restore as suggested by gt94sss2.
Title: Re: FTTC dropouts
Post by: ads on October 14, 2021, 11:39:58 AM
Thanks for the responses. Seeing as BT are apparently working on fixing a fault their system identified outside of my home, I'm going to do nothing and see what they say. I haven't had any more dropouts since around 5am, so maybe they've already done something at the exchange or cabinet. Might be wishful thinking though! I'll make a note of any more dropouts and if need be I'll report back and try the factory reset/restore as suggested by gt94sss2.

OR engineer came out a little while ago, phoned me and came into my house after doing his external tests and then ran some internal checks. Said everything is fine with the line and he reckons it's either the home hub dying or my ethernet cable or switch making it drop and is going to recommend BT replace the hub and for me to call them tomorrow/monday.
Title: Re: FTTC dropouts
Post by: ads on October 16, 2021, 02:47:54 AM
Additional query;

I've found some posts online with similar issues to mine where it was only fixed with a 'lift and shift' and I'm wondering if moving from BT to say, Plusnet, would have the same effect. My BT contract ends next month.
Title: Re: FTTC dropouts
Post by: tiffy on October 16, 2021, 09:34:37 AM
Quote
I've found some posts online with similar issues to mine where it was only fixed with a 'lift and shift' and I'm wondering if moving from BT to say, Plusnet, would have the same effect. My BT contract ends next month.

Moving to any other ISP while remaining at the same address will change nothing on the distribution infrastructure, OR will have no reason to attend, all carried out remotely.
Your line however will get a DLM reset which after a few days with the new ISP will probably leave you back exactly where you started but with an alternative modem/router which may or may not be a better performer on your line.

Any VDSL service ISP you choose to use are subject to OR's infrastructure and service, with the obvious exception of cable services, some ISP's are better than others with respect to dealing with OR but that usually comes at a cost.

If OR are "happy" with the line and not willing to investigate further why not try a replacement modem/router preferably one which can produce worthwhile line stats, there are lots available S/H at very reasonable cost especially now with the ever increasing migration rate to FTTP and most migrants using their new ISP provided devices.
Title: Re: FTTC dropouts
Post by: g3uiss on October 16, 2021, 09:35:11 AM
No. A change in ISP doesnít change the physical arrangement of your line. It will cause a DLM reset however. I donít see your problem could require a lift and shift.
Title: Re: FTTC dropouts
Post by: ads on October 18, 2021, 02:14:50 PM
I love you guys, very helpful.

BT are indeed sending out a new hub. I'll hope for the best and whine again if it doesn't help.