DLM recovery after faulty line is fixed

My parents have a PlusNet ADSL2 connection.

Normal sync speeds are 15 Mb/s down , 1.3 Mb/s up.

A couple of weeks ago they had a line fault, lots of noise, crackles etc etc

This of course caused the ADSL connection to go bananas, with lots of re syncs etc

BT fixed the problem a week ago, however their sync speeds are still firmly stuck
at 6.6 Mb/s down, and 1.1 Mb/s up.

Is there anything that can be done to give the DSLAM a prod, can PN do anything ? I've dared not reboot their router yet, for fear of returning to square one, though that's where they're stuck anyway !

Not the DSLAM

It probably needs the PN IP setting to be given a nudge - it will be stuck at the low level - it's mean't to mirror the BT one which is automatically set on/at sync.....but sometimes the PN one doesn't follow.

The fact the the U/S is normal further indicates it is the PN IP setting which only applies to the D/S

In reply to a post by zom22:

Not the DSLAM

It probably needs the PN IP setting to be given a nudge - it will be stuck at the low level - it's mean't to mirror the BT one which is automatically set on/at sync.....but sometimes the PN one doesn't follow.

The fact the the U/S is normal further indicates it is the PN IP setting which only applies to the D/S

Thanks, IP setting ? What does 'IP' stand for in this context ?

This is actual sync rate I'm talking about, not download/upload speeds (just to be 100% clear)

Edited by broadbandjockey (Thu 30-May-13 16:49:53)

In reply to a post by broadbandjockey:

What does 'IP' stand for in this context ?.

He really means "IPP" short for "IP Profile", see http://www.kitz.co.uk/adsl/IPprofile.htm

BTw controls this, usually at 88.2% of sync, but PN holds their own copy which on occasions can get out of step with the true BTw one. Compare the one in your PN control panel with the one reported at the Further Diagnostics of http://speedtest.btwholesale.com/

Can you do a managed reboot of the router? Rather than pulling the power or line cable, tell the router to reboot - that will ensure the DSLAM sees it in the right context and will not treat it as a loss of sync caused by noise or similar.

does it have a high margin now, implying a capped speed ?

In reply to a post by MHC:

Can you do a managed reboot of the router? Rather than pulling the power or line cable, tell the router to reboot - that will ensure the DSLAM sees it in the right context and will not treat it as a loss of sync caused by noise or similar.

I can't unfortunately, it's a ZyXEL P660, and after it's been running about 12 hours
all the options apart from the status page vanish, it it requires a power cycle re-boot
to restore them.

So although I can remote log in to it, all I can see is the up/down sync speed, and no
other options. Less than optimum isn't it ?

BTW it's a 21CN exchange, if that might help or hinder things ?

This is the direct link to the plusnet page where the PN IPP setting is shown
Its called the "current line speed" on the page
it requires a log in from the users account.
When working properly is should be the same as the BT setting rounded down so a BT setting of 11.37 becomes a plusnet setting of 11.3.
Plusnet datatransfer setting

Else you could post in the PN forums on the thread devoted to this endless problem - all 45 pages of it!
21CN IPP profile not updating
The PN staff read it during office hours and should fix it.

Sounds like the router should go in the bin anyway!

In reply to a post by zom22:

This is the direct link to the plusnet page where the PN IPP setting is shown
Its called the "current line speed" on the page
it requires a log in from the users account.
When working properly is should be the same as the BT setting rounded down so a BT setting of 11.37 becomes a plusnet setting of 11.3.
Plusnet datatransfer setting

Else you could post in the PN forums on the thread devoted to this endless problem - all 45 pages of it!
21CN IPP profile not updating
The PN staff read it during office hours and should fix it.

Sounds like the router should go in the bin anyway!

Thanks all, I'll have a read, and digest !

In reply to a post by zom22:

This is the direct link to the plusnet page where the PN IPP setting is shown
Its called the "current line speed" on the page
it requires a log in from the users account.
When working properly is should be the same as the BT setting rounded down so a BT setting of 11.37 becomes a plusnet setting of 11.3.
Plusnet datatransfer setting

Says, Current line speed: 5.8 Mb Which tallies with the actual sync of 6.6 ?

In reply to a post by zom22:

It probably needs the PN IP setting to be given a nudge - it will be stuck at the low level.

Sorry, just realised that we are on wrong track here.

Stuck IPP shows itself as low throughput, not low sync. IPP is a function of sync not t´other way round.

Ah sheeeeeeeeeeeeeeeeet
I misread the OP's first post as download still 6.6 rather than the sync speed still 6.6
My fault - I'm sorry

So despite the fault being 'mended' the router's sync speed which was 15Mbps prior to the fault is now only 6.6Mbps?
Goodness knows what it was during the fault - even worse no doubt.
That would suggest that there is still some fault present on the line.
(I'm better not make any more suggestions.......before I make a bigger mess)

Glad we got there in the end

Target noise margins are probably high and if line now stable should come over a few weeks or if in a rush might be persuaded to prod a reset

Does your parents' router display the SNR margin? Depending upon line length, this ought to be between 6dB and 12dB (probably nearer to 6dB given a previous sync rate of 15Mbps).

It sounds to me that the line may be banded by BTW, although obviously, without checking your line, I cannot be sure. If this is the case, an SNR reset should do the trick.

Suggest raising a fault at http://faults.plus.net

Just checked again now by remote logging in:-

15600 kbps Down/ 1167 kbps Up

In other words back to normal. No rebooting since the line was fixed, just seems
to have restored itself, all by itself.

Thanks to all that responded