cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
420 Views
Message 11 of 15

Re: Water ingress on external fibre junction box causing drop out?

Just for the record in case it sheds any light, log excerpts

For all of the time the fibre was down, getting constant PPP: Sending PADI messages

About ten minutes before fibre reconnected, repeated message batches like this:

02:59:51, 21 Feb. PPP: Stopped PPP daemon(0,1,5)
02:59:51, 21 Feb. PPP LCP Receive Termination ACK
02:59:51, 21 Feb. PPP LCP Send Termination Request (User request)
02:59:51, 21 Feb. PPP: LCP down
02:59:51, 21 Feb. PPP: CHAP authentication succeeded
02:59:51, 21 Feb. PPP CHAP Receive success : authentication successful
02:59:51, 21 Feb. PPP CHAP Receive Challenge
02:59:50, 21 Feb. PPP: LCP up
02:59:50, 21 Feb. PPP LCP Receive Configuration ACK
02:59:50, 21 Feb. PPP LCP Send Configuration ACK
02:59:50, 21 Feb. PPP LCP Receive Configuration Request
02:59:50, 21 Feb. PPP LCP Send Configuration Request
02:59:50, 21 Feb. PPP: Received PADS
02:59:50, 21 Feb. PPP: Sending PADR
02:59:50, 21 Feb. PPP: Received PADO
02:59:50, 21 Feb. PPP: Sending PADI
02:59:45, 21 Feb. PPP: Starting PPP daemon

Then at connection time got this

03:09:57, 21 Feb. WAN IPv6 Global unicast prefix / length: ******/56
03:09:57, 21 Feb. WAN IPv6 Global unicast address allocated: ******/64
03:09:55, 21 Feb. WAN DHCPv6 events: BOUND
03:09:53, 21 Feb. WAN DHCPv6 events: INIT
03:09:53, 21 Feb. WAN Sensing Auto sensing Running
03:09:53, 21 Feb. Success - secondary DNS servers
03:09:53, 21 Feb. Success - primary DNS servers
03:09:53, 21 Feb. WAN connection WAN1_INTERNET_ETH connected
03:09:52, 21 Feb. PPP: IPCP up
03:09:52, 21 Feb. PPP IPCP Receive Configuration ACK
03:09:52, 21 Feb. PPP IPV6CP Receive Configuration ACK
03:09:52, 21 Feb. PPP IPCP Send Configuration Request
03:09:52, 21 Feb. PPP IPCP Receive Configuration NAK
03:09:52, 21 Feb. PPP IPCP Send Configuration ACK
03:09:52, 21 Feb. PPP IPCP Receive Configuration Request
03:09:52, 21 Feb. PPP IPV6CP Send Configuration ACK
03:09:52, 21 Feb. PPP IPV6CP Receive Configuration Request
03:09:52, 21 Feb. PPP IPV6CP Send Configuration Request
03:09:52, 21 Feb. PPP IPCP Send Configuration Request
03:09:51, 21 Feb. PPP CCP Send Configuration Request
03:09:51, 21 Feb. PPP: CHAP authentication succeeded
03:09:51, 21 Feb. PPP CHAP Receive success : authentication successful
03:09:51, 21 Feb. PPP CHAP Receive Challenge
03:09:51, 21 Feb. PPP: LCP up
03:09:51, 21 Feb. PPP LCP Receive Configuration ACK
03:09:51, 21 Feb. PPP LCP Send Configuration ACK
03:09:51, 21 Feb. PPP LCP Receive Configuration Request
03:09:51, 21 Feb. PPP LCP Send Configuration Request
03:09:51, 21 Feb. PPP: Received PADS
03:09:51, 21 Feb. PPP: Sending PADR
03:09:51, 21 Feb. PPP: Received PADO
03:09:51, 21 Feb. PPP: Sending PADI

My limited understanding suggests something was "kicking in" around 10 minutes before the actual connection became properly established.

0 Ratings
Reply
307 Views
Message 12 of 15

Re: Water ingress on external fibre junction box causing drop out?

Fibre has gone down again this morning. Perhaps this is just something I need to get used to once a month — brilliant fibre 97% of the time and the down for ½ - 1 day per month...

0 Ratings
Reply
289 Views
Message 13 of 15

Re: Water ingress on external fibre junction box causing drop out?

Certainly should not be something you accept , report it, with issues that are tricky to locate,  a process of elimination should be started , starting with your  ONT , simple enough to change and should that be the end of your issues , great , culprit found , if the same issue returns the ONT has been eliminated as the problem , and time to look elsewhere, like at the headend, although it’s unlikely that a headend issue would affect only you , and if multiple users on the same PON were affected then that should have already been investigated.

As stated earlier it’s not likely to be the fibre if the LOS light never comes on , although you can never be certain, if curiosity gets the better of you (not recommended BTW ) but if you disconnect the fibre from the ONT it would be interesting to know , does the LOS light come on immediately or the PON flashes then the LOS lights up  …if the PON flashes before the ONT decides the light has been lost  , and the problem is such that the light loss is so intermittent and brief perhaps the LOS never comes on but the sync with the headend has been lost and so the PON flashes but as the light returns almost instantly the LOS light is never seen ,but it takes a few minutes to re authenticate and the cycle starts again . 

278 Views
Message 14 of 15

Re: Water ingress on external fibre junction box causing drop out?

Unfortunately hub logs won't really be if much use as all you will see are effects rather than causes. The hub is unable to monitor the status of the fibre line as that finishes at the ONT. The PPP events are either an effect of a line disconnection (that the hub won't see) or a problem with the PPP  session itself. It is impossible to know which from the hub logs.

0 Ratings
Reply
227 Views
Message 15 of 15

Re: Water ingress on external fibre junction box causing drop out?

I have included a link to new thread that the OP has posted regarding this.

https://community.bt.com/t5/BT-Fibre-broadband/BT-Network-Fault-Is-this-definitely-something-going-o...

0 Ratings
Reply