Erratic U/S SNRM and resulting DLM interventions

[#1]

Arrrrggggghhh - I thought things were going too well - Just had another re-sync to 7895kbps and ~ 14.5dB - what the blazes is going on?

I'm going out now for about 3 hours - can someone investigate -PLEASE?

AND another one at 1446 - back to 6.3dB d/s, 21 u/s and 12176 Kbps connection speed (as reported by RouterStats Lite)

[#2]

Sorry to hear this. I don't think there's anything more we can do from this side as it's evident there's a physical fault somewhere which needs to be investigated and fixed by an engineer. Let us know how the appointment goes tomorrow afternoon.

[#3]

@Gandalf - believe me, I will!

[#4]

---

@RandallFlagg wrote:

Hi @jab1

The upload capacity of your line is up to 1mb/s, so at around 444kb/s it's within that range - feel free to mention this to the engineer

The upload will have been capped by an order that Plusnet have made. It has nothing to do with the capability of the line or DLM and I can't imagine there's anything the engineer can do about it besides tell jab1 to tell Plusnet to uncap it. Also, strictly speaking, pretty much anything from zero to 1mb/s would be within that "up to 1mb/s" range.

[#5]

@ejs You are 100% correct - for some reason, when the interleaving was applied, my u/s has been capped at 448. My upload speed has been around the 720/750 mark ever since I have been with PN (IIRC), and I'm afraid, @RandallFlagg, you have made a slightly duff comment there.

I won't mention it to the engineer, but I will be asking PN to remove the cap - after the OR guy has been.

[#6]

I've placed an order to uncap your upstream speed which should go through tomorrow although with interleaving on you'll still see a reduced upload speed I'd imagine of around 888kbps.

[#7]

@Gandalf Thanks - I wonder why it got capped? - rhetorical question, no need to answer.

Just hope the engineer this afternoon can apply a fix to my connection problems as quickly.

[#8]

It's possible it was capped as part of adding on interleaving.

[#9]

I am waiting for a response to the ticket referenced in this thread - not a problem,I am patient.

Just to keep everything in one place, and while I remember, the SFI I had was very thorough and had carried out preliminary checks at the exchange about three hours before he turned up here, which he said hadn't revealed any obvious causes for my problems. He then spent about 45 minutes here checking everything possible, and declared everything my side of the master socket OK.

Not satisfied, he then returned to the exchange and went through my connections there with a colleague, and they did find a potential problem with jumpers, which they repaired as best as possible. Following that, they sent a high voltage down the line in an attempt to clear it, which actually succeeded - but see graphs later for the full story.

His final comment was:- 'the only other option is a 'lift & shift', but that request can only come from your ISP'

Below, and in the next post are DSL snapshots from my router and the RSL graphs from yesterday and today - less one 3 hour period when RSL crashed (~0433-~0733 today)

0759 19/02/191228 19/02/191845 19/02/191132 20/02/19

[#10]

And the rest:-

As can be seen, nothing has changed!

[#11]

Hi @jab1,

I'm sorry to see that the issue persists, after testing the line we are seeing multiple drops the day after the engineer attended.

I have raised an escalation with our suppliers to ensure all quality gates are carried out and stress that a lift and shift is next required. I'm afraid that a further visit is required as the line test has not detected an external fault, you can reply with your availability here.

Once you have replied to the ticket, please reply on here so we can pick it up as soon as possible.

Thank you.

[#12]

@Jubby I am aware that no external faults have been found to date, but as reported by the engineer, there are no apparent internal problems - so as you have correctly said, further external checks are required.

Please note, none of the drops shown on the RADIUS log in your reply were caused by any action on my part, and all equipment (router, cables & power supply) my side of the recently installed NTE are brand new.

Dates/times have been added to the ticket.

[#13]

Hi @jab1,

Thank you for updating the ticket.

Your appointment for an engineer has been booked for 26/02/2019 between 1pm-6pm. I understand the situation and have marked on the escalation review that the NTE has been replaced. Along side this, I have updated the escalation owner requesting the lift & shift and what actions have been taken previously.

When booking the appointment, I have selected for a co-op call which will result in the engineer calling us before arrival so we can discuss actions needed.

Let us know how the visit goes.

Thanks again.

[#14]

Thanks @Jubby - appreciated.

[#15]

Just in case any of the helpful PN staff are still watching this boring thread, I thought I'd post these two DSL connection reports, taken about nine hours apart - they look a bit disconcerting