Connection keeps dropping

[#1]

@James30 will wait and see then, you can see my points, with the previous engineers just marking it as resolved.
Just going to assume now "Error_no_carrier" is generic disconnect message then? 

@Dan_the_Van attached the router information as requested, do note that the cable has been changed, its now a direct connection from the test port on the mastersocket to the router using a SOGEA connector, and no microfilter. 

Also @James30, just a quick question you might be able to answer, I've been advised that OR is awaiting planning permission to take fibre to the nearest pole and they'd have it by the end of the next month, once its on the pole, how long after that do you think it'd be before PN allows FTTP, some places suggest it should be able to "preorder" 3 weeks prior to it being put onto the pole? 

[#2]

It will not be a matter of "Plusnet allowing orders" but rather it will be when BT Openreach release capacity to BT Wholesale. Both of whom run on different clock speeds to the rest of the universe.

[#3]

So we have from todays technical log,

Data rate,20.0 Mbps / 80.0 Mbps
Maximum Data rate,22.2 Mbps / 105.3 Mbps
Noise margin,6.5/12.6
Line attenuation,8.3/16.7
Signal attenuation,8.3/18.1

From 21st Oct

Data rate,                      20.0 Mbps / 80.0 Mbps
Maximum Data rate,     25.1 Mbps / 108.4 Mbps
Noise margin,               8.8/13.4
Line attenuation,          8.0/16.8
Signal attenuation,       8.0/18.2

The purpose to look at these figures is to view the noise margins.

So really little change since Openreach last visited, lets see what the CAT team has to say.

@jab1 

DSL down, this would be a break in the connection from the Hub to the green cab, the message [ERROR_NO_CARRIER] simply means the DSL signal disconnected.

It must be noted not all routers report messages in the same format

[#4]

I know what DSL Down means, @Dan_the_Van  - I've been part of the unofficial 'help team' for quite a while, and have only seen the 'error_no_carrier' message on Hub1/Hub2 logs. I know different hubs/routers have different reporting formats, some rather more useful/clearer than others.

[#5]

PN Called just there, been put on a week long monitoring period, to see if it goes down again. 

[#6]

@Townman decided to make something to automatically check if FTTP is available, using sky's site as PN's looks terrible to work with in that aspect just to make it notify me whenever FTTP is available so I don't have to keep checking 

[#7]

I've had the dredge the remnant memories of 56k dialup. Used to see in in logfiles with such.

https://en.wikipedia.org/wiki/NO_CARRIER

[#8]

Thanks for the link @greygit1 hope this will explain to others the meaning of the [ERROR_NO_CARRIER] message

01:27:14, 27 Oct. WAN connection WAN2_INTERNET_PTM disconnected.[ERROR_NO_CARRIER]

 WAN2_INTERNET_PTM - this is the DSL port of the Hub Two.

This message can be likened to someone removing a cable, in the is case the DSL cable (DSL link down), the DSL signal has gone away, therefore [ERROR_NO_CARRIER]

[#9]

It's a layer 1 (physical connection) error.

Could be within the property, could be somewhere outside the property.

I've seen it without disconnecting a local cable (I do like to test/monitor stuff).

I'm now nearly tempted to pull a plug on a Hub2 and see what errors occur (or are reported).

[#10]

Unplugging the cable from the router or the socket definitely results in the aforementioned error. Just thought I'd do an actual test to confirm my thoughts

[#11]

Thanks, @greygit1 - so, as I doubt the OP intentionally unplugs his kit, this points to something downstream of them 'unplugging' itself?

[#12]

Unfortunately I am not available (or able) to provide such testing. Therefore I'm having to asume that the modem component of the 'router' has lost a signal. Could be layer 1 (most likely cauase0, could be layer 2 (intereference causing interruption of signal). My simple understanding is that it can't be any further up the 'stack'.

I will have to reserve caveats because I cannot verify where and how the reported errors were generated. Access to the end-to-end connection and intervening devices is the only way to be sure. Not my 'arena'.

[#13]

@greygit1 

Important: - All log events are the HUB reporting what it is doing. 

WAN connection WAN2_INTERNET_PTM disconnected.[ERROR_NO_CARRIER]

From what I can determine there are two situations which can cause this message.

DSL Link Down: duration was <dsl up time> seconds {followed by}

PPP: LCP down

This would be a physical break/s in the copper cable or a DLM resync

DLM resync usually occur in a time window around 01:00 local time in an it's intention is to make the line stable. After either of these instances you will see DSL Link Up with line sync data depending on the IP Profile.

hh:mm:ss DD MON DSL Link Up: Down Rate=80000kbps, Up Rate=20000kbps; SNR Margin Down=6dB, Up=3dB

If you were to observe the Hub Two Lights during a DSL down event it will be flashing Orange

PPP: LCP down (No preceding DSL Link down)

My event log has two different events that resulted in PPP: LCP down.

00:28:58, 20 Sep. PPP LCP Receive Termination Request (NONE)

Here the Hub is reporting it is to terminate the PPP link (I expect this was due to overnight maintenance)

00:16:02, 16 Aug. PPP LCP Send Termination Request (Peer not responding)

To me it looked like the upstream device had failed, as it took 15 minutes to recover.

If you were to observe the Hub Two Lights during a PPP down event it will be solid Orange

So it is the PPP link down which results the event "WAN connection WAN2_INTERNET_PTM disconnected.[ERROR_NO_CARRIER]" either caused by DSL link down or PPP link down

The message

DSL Link Up: Down Rate=80000kbps, Up Rate=20000kbps; SNR Margin Down=6dB, Up=3dB

would only be seen with a warm or cold boot of the Hub, recovery from DSL Link down or after a DLM resync.

[#14]

@greygit1, Yes the errors are on Layer 1 of the OSI model, as the fault has to be down to the cabling/ports, engineer said that it was something to do with the broadband port at the cab, so far no other issues apart from that one disconnect. 

[#15]

I'm unable to overturn or dispute your analysis.

I predict a new series - "CSI: Network"

(only joshing)