cancel
Showing results for 
Search instead for 
Did you mean: 
DiggerOfTrenches
Contributor
233 Views
Message 11 of 22

Re: PPP Dropouts during day. remote station is not answering to LCP Echo requests

Go to solution

09:36:28, 11 Mar. NTP synchronization success
09:36:15, 11 Mar. NTP synchronization start
09:36:13, 11 Mar. WAN connection ATM connected
09:36:13, 11 Mar. PPP IPCP Receive Configuration ACK
09:36:13, 11 Mar. PPP IPCP Send Configuration Request
09:36:13, 11 Mar. PPP IPCP Receive Configuration NAK
09:36:13, 11 Mar. PPP IPCP Send Configuration Request
09:36:12, 11 Mar. PPP IPCP Receive Configuration Reject
09:36:12, 11 Mar. PPP IPCP Send Configuration ACK
09:36:12, 11 Mar. PPP IPCP Receive Configuration Request
09:36:12, 11 Mar. PPP IPCP Send Configuration Request
09:36:12, 11 Mar. PPP CHAP Receive success : authentication successful
09:36:12, 11 Mar. PPP CHAP Receive Challenge
09:36:11, 11 Mar. PPP LCP Send Configuration ACK
09:36:11, 11 Mar. PPP LCP Receive Configuration Request
09:36:11, 11 Mar. PPP LCP Receive Configuration ACK
09:36:11, 11 Mar. PPP LCP Send Configuration Request
09:36:08, 11 Mar. PPP LCP Receive Configuration ACK
09:36:08, 11 Mar. PPP LCP Send Configuration Request
09:36:05, 11 Mar. DSL Link Up: Down Rate=2880Kbps, Up Rate=448Kbps; SNR Margin Down=6.6dB, Up=17.0dB
09:35:21, 11 Mar. DSL Link Down: duration was 1212 seconds
09:35:12, 11 Mar. PPP LCP Send Configuration Request
09:35:09, 11 Mar. PPP LCP Send Configuration Request
09:35:06, 11 Mar. PPP LCP Send Configuration Request
09:35:03, 11 Mar. PPP LCP Send Configuration Request
09:34:59, 11 Mar. PPP LCP Send Configuration Request
09:34:56, 11 Mar. PPP LCP Send Configuration Request
09:34:53, 11 Mar. PPP LCP Send Configuration Request
09:34:50, 11 Mar. PPP LCP Send Configuration Request
09:34:47, 11 Mar. PPP LCP Send Configuration Request
09:34:44, 11 Mar. PPP LCP Send Configuration Request
09:34:43, 11 Mar. WAN connection ATM disconnected
09:34:33, 11 Mar. PPP LCP Send Termination Request (User request)
09:34:30, 11 Mar. PPP LCP Send Termination Request (Peer not responding)
09:16:08, 11 Mar. CWMP: HDM socket closed successfully.
09:16:08, 11 Mar. CWMP: HTTP authentication success from pbthdm.x.x.x

0 Ratings
Reply
DiggerOfTrenches
Contributor
232 Views
Message 12 of 22

Re: PPP Dropouts during day. remote station is not answering to LCP Echo requests

Go to solution

05:52:27, 09 Mar. NTP synchronization success
05:52:13, 09 Mar. NTP synchronization start
05:52:12, 09 Mar. WAN connection ATM connected
05:52:12, 09 Mar. PPP IPCP Receive Configuration ACK
05:52:11, 09 Mar. PPP IPCP Send Configuration Request
05:52:11, 09 Mar. PPP IPCP Receive Configuration NAK
05:52:11, 09 Mar. PPP IPCP Send Configuration Request
05:52:11, 09 Mar. PPP IPCP Receive Configuration Reject
05:52:11, 09 Mar. PPP IPCP Send Configuration ACK
05:52:11, 09 Mar. PPP IPCP Receive Configuration Request
05:52:11, 09 Mar. PPP IPCP Send Configuration Request
05:52:10, 09 Mar. PPP CHAP Receive success : authentication successful
05:52:10, 09 Mar. PPP CHAP Receive Challenge
05:52:10, 09 Mar. PPP LCP Send Configuration ACK
05:52:10, 09 Mar. PPP LCP Receive Configuration Request
05:52:07, 09 Mar. PPP LCP Receive Configuration ACK
05:52:07, 09 Mar. PPP LCP Send Configuration Request
05:52:04, 09 Mar. DSL Link Up: Down Rate=3200Kbps, Up Rate=448Kbps; SNR Margin Down=6.5dB, Up=18.0dB
05:51:29, 09 Mar. PPP LCP Send Termination Request (User request)
05:51:25, 09 Mar. PPP LCP Send Termination Request (User request)
05:51:25, 09 Mar. DSL Link Down: duration was 66331 seconds
05:51:23, 09 Mar. PPP LCP Send Configuration Request
05:51:20, 09 Mar. PPP LCP Send Configuration Request
05:51:19, 09 Mar. WAN connection ATM disconnected
05:51:09, 09 Mar. PPP LCP Send Termination Request (User request)
05:51:06, 09 Mar. PPP LCP Send Termination Request (Peer not responding)
05:22:10, 09 Mar. admin login success from 192.168.1.190
02:32:36, 09 Mar. Receive a DHCP request

0 Ratings
Reply
DiggerOfTrenches
Contributor
230 Views
Message 13 of 22

Re: PPP Dropouts during day. remote station is not answering to LCP Echo requests

Go to solution

10:50:12, 08 Mar. NTP synchronization success
10:49:58, 08 Mar. NTP synchronization start
10:49:56, 08 Mar. WAN connection ATM connected
10:49:56, 08 Mar. PPP IPCP Receive Configuration ACK
10:49:56, 08 Mar. PPP IPCP Send Configuration Request
10:49:56, 08 Mar. PPP IPCP Receive Configuration NAK
10:49:56, 08 Mar. PPP IPCP Send Configuration Request
10:49:55, 08 Mar. PPP IPCP Receive Configuration Reject
10:49:55, 08 Mar. PPP IPCP Send Configuration ACK
10:49:55, 08 Mar. PPP IPCP Receive Configuration Request
10:49:55, 08 Mar. PPP IPCP Send Configuration Request
10:49:55, 08 Mar. PPP CHAP Receive success : authentication successful
10:49:55, 08 Mar. PPP CHAP Receive Challenge
10:49:55, 08 Mar. PPP LCP Receive Configuration ACK
10:49:54, 08 Mar. PPP LCP Send Configuration ACK
10:49:54, 08 Mar. PPP LCP Receive Configuration Request
10:49:54, 08 Mar. PPP LCP Send Configuration Request
10:49:51, 08 Mar. PPP LCP Receive Configuration ACK
10:49:51, 08 Mar. PPP LCP Send Configuration Request
10:49:48, 08 Mar. DSL Link Up: Down Rate=3296Kbps, Up Rate=448Kbps; SNR Margin Down=6.9dB, Up=15.0dB
10:49:15, 08 Mar. PPP LCP Send Termination Request (User request)
10:49:12, 08 Mar. PPP LCP Send Termination Request (User request)
10:49:11, 08 Mar. DSL Link Down: duration was 154085 seconds
10:49:10, 08 Mar. PPP LCP Send Configuration Request
10:49:09, 08 Mar. WAN connection ATM disconnected
10:49:00, 08 Mar. PPP LCP Send Termination Request (User request)
10:48:57, 08 Mar. PPP LCP Send Termination Request (Peer not responding)
09:40:58, 08 Mar. DoS(UDP Loopback): IN=ppp1 OUT= MAC=

0 Ratings
Reply
DiggerOfTrenches
Contributor
228 Views
Message 14 of 22

Re: PPP Dropouts during day. remote station is not answering to LCP Echo requests

Go to solution

06:09:01, 05 Mar. NTP synchronization success
06:08:48, 05 Mar. NTP synchronization start
06:08:46, 05 Mar. WAN connection ATM connected
06:08:46, 05 Mar. PPP IPCP Receive Configuration ACK
06:08:46, 05 Mar. PPP IPCP Send Configuration Request
06:08:46, 05 Mar. PPP IPCP Receive Configuration NAK
06:08:45, 05 Mar. PPP IPCP Send Configuration Request
06:08:45, 05 Mar. PPP IPCP Receive Configuration Reject
06:08:45, 05 Mar. PPP IPCP Send Configuration ACK
06:08:45, 05 Mar. PPP IPCP Receive Configuration Request
06:08:45, 05 Mar. PPP IPCP Send Configuration Request
06:08:45, 05 Mar. PPP CHAP Receive success : authentication successful
06:08:44, 05 Mar. PPP CHAP Receive Challenge
06:08:44, 05 Mar. PPP LCP Send Configuration ACK
06:08:44, 05 Mar. PPP LCP Receive Configuration Request
06:08:42, 05 Mar. PPP LCP Receive Configuration ACK
06:08:41, 05 Mar. PPP LCP Send Configuration Request
06:08:38, 05 Mar. DSL Link Up: Down Rate=3104Kbps, Up Rate=448Kbps; SNR Margin Down=6.6dB, Up=16.0dB
06:08:02, 05 Mar. PPP LCP Send Termination Request (User request)
06:07:59, 05 Mar. PPP LCP Send Termination Request (User request)
06:07:59, 05 Mar. DSL Link Down: duration was 20638 seconds
06:07:57, 05 Mar. PPP LCP Send Configuration Request
06:07:54, 05 Mar. PPP LCP Send Configuration Request
06:07:51, 05 Mar. PPP LCP Send Configuration Request
06:07:48, 05 Mar. PPP LCP Send Configuration Request
06:07:44, 05 Mar. PPP LCP Send Configuration Request
06:07:41, 05 Mar. PPP LCP Send Configuration Request
06:07:38, 05 Mar. PPP LCP Send Configuration Request
06:07:35, 05 Mar. PPP LCP Send Configuration Request
06:07:34, 05 Mar. WAN connection ATM disconnected
06:07:25, 05 Mar. PPP LCP Send Termination Request (User request)
06:07:22, 05 Mar. PPP LCP Send Termination Request (Peer not responding)
06:06:35, 05 Mar. admin login success from 192.168.1.190
04:24:23, 05 Mar. admin login success from 192.168.1.190
02:28:39, 05 Mar. Receive a DHCP request

0 Ratings
Reply
DiggerOfTrenches
Contributor
226 Views
Message 15 of 22

Re: PPP Dropouts during day. remote station is not answering to LCP Echo requests

Go to solution

11:00:06, 04 Mar. NTP synchronization success
10:59:53, 04 Mar. NTP synchronization start
10:59:51, 04 Mar. WAN connection ATM connected
10:59:51, 04 Mar. PPP IPCP Receive Configuration ACK
10:59:51, 04 Mar. PPP IPCP Send Configuration Request
10:59:51, 04 Mar. PPP IPCP Receive Configuration NAK
10:59:50, 04 Mar. PPP IPCP Send Configuration Request
10:59:50, 04 Mar. PPP IPCP Receive Configuration Reject
10:59:50, 04 Mar. PPP IPCP Send Configuration ACK
10:59:50, 04 Mar. PPP IPCP Receive Configuration Request
10:59:50, 04 Mar. PPP IPCP Send Configuration Request
10:59:50, 04 Mar. PPP CHAP Receive success : authentication successful
10:59:49, 04 Mar. PPP CHAP Receive Challenge
10:59:49, 04 Mar. PPP LCP Send Configuration ACK
10:59:49, 04 Mar. PPP LCP Receive Configuration Request
10:59:49, 04 Mar. PPP LCP Receive Configuration ACK
10:59:49, 04 Mar. PPP LCP Send Configuration Request
10:59:46, 04 Mar. PPP LCP Receive Configuration ACK
10:59:45, 04 Mar. PPP LCP Send Configuration Request
10:59:42, 04 Mar. DSL Link Up: Down Rate=3072Kbps, Up Rate=448Kbps; SNR Margin Down=6.6dB, Up=15.0dB
10:59:09, 04 Mar. PPP LCP Send Termination Request (User request)
10:59:06, 04 Mar. PPP LCP Send Termination Request (User request)
10:59:06, 04 Mar. DSL Link Down: duration was 53791 seconds
10:59:05, 04 Mar. PPP LCP Send Configuration Request
10:59:04, 04 Mar. WAN connection ATM disconnected
10:58:56, 04 Mar. PPP LCP Send Termination Request (User request)
10:58:53, 04 Mar. PPP LCP Send Termination Request (Peer not responding)
10:02:16, 04 Mar. admin login success from 192.168.1.190
10:01:42, 04 Mar. CWMP: HDM socket closed successfully.
10:01:42, 04 Mar. CWMP: HTTP authentication success from pbthdm.x.x.x
10:01:42, 04 Mar. CWMP: HDM socket opened successfully.
10:01:42, 04 Mar. CWMP: session completed successfully
10:01:42, 04 Mar. CWMP: HDM socket closed successfully.
10:01:42, 04 Mar. CWMP: HTTP authentication success from pbthdm.x.x.x
10:01:41, 04 Mar. CWMP: HDM socket opened successfully.
10:01:41, 04 Mar. CWMP: HDM socket opened successfully.
10:01:38, 04 Mar. CWMP: Server URL: https://pbthdm.x.x.x; Connecting as user: ACS username
10:01:38, 04 Mar. CWMP: Session start now, server: pbthdm.x.x.x, Event code:
10:01:38, 04 Mar. CWMP: Initializing transaction for event code 2 PERIODIC
08:42:42, 04 Mar. CWMP: HDM socket closed successfully.
08:42:42, 04 Mar. CWMP: HTTP authentication success from pbthdm.x.x.x
08:42:42, 04 Mar. CWMP: HDM socket opened successfully.
08:42:42, 04 Mar. CWMP: session completed successfully
08:42:41, 04 Mar. CWMP: HDM socket closed successfully.
08:42:41, 04 Mar. CWMP: HTTP authentication success from pbthdm.x.x.x
08:42:41, 04 Mar. CWMP: HDM socket opened successfully.
08:42:40, 04 Mar. CWMP: HDM socket opened successfully.
08:42:38, 04 Mar. CWMP: Server URL: https://pbthdm.x.x.x; Connecting as user: ACS username
08:42:37, 04 Mar. CWMP: Session start now, server: pbthdm.x.x.x, Event code:
08:42:37, 04 Mar. CWMP: Initializing transaction for event code 4 VALUE CHANGE
08:41:59, 04 Mar. NTP synchronization success
08:41:46, 04 Mar. NTP synchronization start
08:41:44, 04 Mar. WAN connection ATM connected
08:41:44, 04 Mar. PPP IPCP Receive Configuration ACK
08:41:44, 04 Mar. PPP IPCP Send Configuration Request
08:41:44, 04 Mar. PPP IPCP Receive Configuration NAK
08:41:44, 04 Mar. PPP IPCP Send Configuration Request
08:41:43, 04 Mar. PPP IPCP Receive Configuration Reject
08:41:43, 04 Mar. PPP IPCP Send Configuration ACK
08:41:43, 04 Mar. PPP IPCP Receive Configuration Request
08:41:43, 04 Mar. PPP IPCP Send Configuration Request
08:41:43, 04 Mar. PPP CHAP Receive success : authentication successful
08:41:43, 04 Mar. PPP CHAP Receive Challenge
08:41:42, 04 Mar. PPP LCP Send Configuration ACK
08:41:42, 04 Mar. PPP LCP Receive Configuration Request
08:41:40, 04 Mar. PPP LCP Receive Configuration ACK
08:41:39, 04 Mar. PPP LCP Send Configuration Request
08:41:38, 04 Mar. WAN connection ATM disconnected
08:41:30, 04 Mar. PPP LCP Send Termination Request (User request)
08:41:27, 04 Mar. PPP LCP Send Termination Request (Peer not responding)
08:17:00, 04 Mar. admin login success from 192.168.1.190

0 Ratings
Reply
DiggerOfTrenches
Contributor
224 Views
Message 16 of 22

Re: PPP Dropouts during day. remote station is not answering to LCP Echo requests

Go to solution

00:24:04, 18 Feb. NTP synchronization success
00:23:51, 18 Feb. NTP synchronization start
00:23:49, 18 Feb. WAN connection ATM connected
00:23:49, 18 Feb. PPP IPCP Receive Configuration ACK
00:23:49, 18 Feb. PPP IPCP Send Configuration Request
00:23:49, 18 Feb. PPP IPCP Receive Configuration NAK
00:23:49, 18 Feb. PPP IPCP Send Configuration Request
00:23:48, 18 Feb. PPP IPCP Receive Configuration Reject
00:23:48, 18 Feb. PPP IPCP Send Configuration ACK
00:23:48, 18 Feb. PPP IPCP Receive Configuration Request
00:23:48, 18 Feb. PPP IPCP Send Configuration Request
00:23:48, 18 Feb. PPP CHAP Receive success : authentication successful
00:23:48, 18 Feb. PPP CHAP Receive Challenge
00:23:47, 18 Feb. PPP LCP Send Configuration ACK
00:23:47, 18 Feb. PPP LCP Receive Configuration Request
00:23:47, 18 Feb. PPP LCP Receive Configuration ACK
00:23:47, 18 Feb. PPP LCP Send Configuration Request
00:23:44, 18 Feb. PPP LCP Receive Configuration ACK
00:23:44, 18 Feb. PPP LCP Send Configuration Request
00:23:41, 18 Feb. DSL Link Up: Down Rate=3296Kbps, Up Rate=448Kbps; SNR Margin Down=6.3dB, Up=16.0dB
00:23:03, 18 Feb. DSL Link Down: duration was 7464 seconds
00:23:00, 18 Feb. PPP LCP Send Configuration Request
00:22:57, 18 Feb. PPP LCP Send Configuration Request
00:22:53, 18 Feb. PPP LCP Send Configuration Request
00:22:50, 18 Feb. PPP LCP Send Configuration Request
00:22:47, 18 Feb. PPP LCP Send Configuration Request
00:22:44, 18 Feb. PPP LCP Send Configuration Request
00:22:41, 18 Feb. PPP LCP Send Configuration Request
00:22:38, 18 Feb. PPP LCP Send Configuration Request
00:22:35, 18 Feb. PPP LCP Send Configuration Request
00:22:32, 18 Feb. PPP LCP Send Configuration Request
00:22:31, 18 Feb. WAN connection ATM disconnected
00:22:21, 18 Feb. PPP LCP Send Termination Request (User request)
00:22:18, 18 Feb. PPP LCP Send Termination Request (Peer not responding)
22:41:35, 17 Feb. DoS(UDP Loopback): IN=ppp1 OUT= MAC= src=xxxx DST=xxxx LEN=29 TOS=0x00 PREC=0x00...
22:19:48, 17 Feb. CWMP: HDM socket closed successfully.
22:19:48, 17 Feb. CWMP: HTTP authentication success from pbthdm.x.x.x

0 Ratings
Reply
Highlighted
DiggerOfTrenches
Contributor
222 Views
Message 17 of 22

Re: PPP Dropouts during day. remote station is not answering to LCP Echo requests

Go to solution

 

Well that's a months worth. I've got plenty more.

 

Any ideas please.  @pippincp ? @NeilO  ?

0 Ratings
Reply
DiggerOfTrenches
Contributor
192 Views
Message 18 of 22

Re: PPP Dropouts during day. remote station is not answering to LCP Echo requests

Go to solution
Well I've done some research. Came up with this post on Plus Net a BT company site.

https://community.plus.net/t5/ADSL-Broadband/Can-anyone-tell-me-what-this-means/td-p/858966

So back to answering my own questions.

Seams most defiantly an ISP BT, I am a customer, problem.

As PPP is layer 2 in the OSI model. Which I already new.

And as the OSI model represents my internet connection to MY ISP.
This is the bit I have just worked out.

A problem with PPP causing loss of internet is an ISPs' problem to solve.

Moderator opinion and action please.
0 Ratings
Reply
DiggerOfTrenches
Contributor
177 Views
Message 19 of 22

Re: PPP Dropouts during day. remote station is not answering to LCP Echo requests

Go to solution

 

Easy way to spot non resync PPP dropouts in the upside down back to front topsy turvey world that is BT Hub6A.

Select 'IP' only on log page to produce this.

IPdropout.jpg

Look for the indent right the mark of non resync PPP dropout.

It is not labeled PPP/ppp1 interestingly.

As confirmed in screenshot below. IP + WAN Log.

IPWANdisconect.jpg

0 Ratings
Reply
DiggerOfTrenches
Contributor
173 Views
Message 20 of 22

Re: PPP Dropouts during day. remote station is not answering to LCP Echo requests

Go to solution

 

Is this the answer?

https://www.btplc.com/SINet/SINs/pdf/472v2p9.pdf  Interesting reading.

SIN 472Issue 2.9 British Telecommunications plc 2018Page 23of 53

5.8Real Time QoS serviceReal Time QoS is supported on all WBC end user access variants.
There aretwo elements to this service:i)From March 2018 each EP will be configured
so that up to5% of capacity can be sent as RealTime bandwidth(i.e.IP packets marked DSCP EF).
There is no extra charge for RTQoS bandwidth at the EP.ii)The CP mustorderan amount of
Real Time bandwidth for each End User line that requires the service.The RTQoS end user
allocations are symmetrical and apply in both upstream and downstream directions.
ACPs Real Time traffic, providing it is within the EP policing limit of 5%will be
passed through to the BRAS. Any excess above the policing bandwidthwill be dropped at the EP.
For End User Accesswith Real Time QoS enabled the traffic will be prioritised
with the highest priority on egress from the BRAS. Any excess traffic over the
End User AccessReal Time QoS configured bandwidth will be dropped.The Real Time bandwidth
configured for the End User will be the smaller of:Contracted Real Time bandwidth;
CVLAN rate –100 Kbit/s. This is to ensure a certain amount of BE traffic
and more importantly, control traffic, can get through.
Note:In the case of L2TP traffic, decisions on handling Real Time QoS will be based on
the outer (L2TP carrying) DSCP marking.Real Time QoS End User Access bandwidthallocations are
symmetrical and allowable rates are 350kbit/s, 1000kbit/s, 1900kbit/s, 2800kbit/s and 4900kbit/s.
Other rates were previously available but these have been withdrawn and are
no longer supported from 1 June 2018.

If the End User Accesshasnot been enabled for Real Time QoS
(i.e. if the End User RTQoS bandwidth allocation is zero)
then all trafficwill be treated as Best Efforts.

Upstream IP packets can be marked with the EF DSCP codepoint. For lines that have
non zero RTQoSbandwidth allowance EF marked packets will be prioritised and
drop protected where possible in the BT Wholesale network.Customers who use RTQoS
should be aware that when upstream prioritisation is enabled any EF marked traffic
that exceeds the end user access allocation of RTQoS traffic will be dropped.
The BT Wholesale network will not differentiate between EF marked IP packets from
different devices in an End User installation. The customer and/or end user is responsible
for ensuring that EF marked packets do not burst above the End User RTQoS allocation.
With effect from May 2018 BT Wholesale will start to introduce support for RTQoS in the
upstream direction by upgrading the existing RTQoS product. The upgrade is not service affecting
and customers donot have to take any action. Lines that have End User RTQoS bandwidth configured
will start to benefit from the new, bidirectional, configurations.
End User access lines with zero RTQoS bandwidth configured will experience no change.

 

?

 

0 Ratings
Reply