That's terrible!
That's the PN equivalent of 'please reinstall Windows' then?
Each time it suggests switching the BT modem off for 30 seconds
Please don't do that from now on.
I know, but Im not the type that wanted to phone up PN just for the hell of it... and perhaps then be referred back by asking if Id done all the troubleshooting in their booklet. I wanted to be able to fix it myself without spending time hanging on the phone.
I didnt realise that they had my profile down as adsl2+ in their systems rather than fttc, which is why I couldnt authenticate properly.
DLM monitors that number of resyncs by examining the recorded up time in each 15 mins time slot. If there was 15 mins up-time in one time slot, and less than 15 mins in the next then it would record that a 'forced (i.e. unsolicited) resync' had occurred. If at least two time slots back-to-back have no up time, it will (should ) determine that this was a solicited resync e.g. following the EU powering down the line, and ignore it for the purposes of determining instability.
and that is exactly the reason why earlier in this thread, that once Id done all the suggested 'trouble shooting' that I wanted to let my line settle for a while before putting the Huawei on and I didnt want to push my luck.
What I wasnt aware of is the 'first day' period of grace. Ive been away from the BT DLM now for about 5+ years and although once upon a time I did know a fair bit about it.. its one of those things that when youre not effected by it yourself then you perhaps dont always follow closely whats going on because you dont see it first hand.
I loved Be*s DLM. It worked and gave the EU so much control over their line. None of this hidden mystery stuff and IP profiles.
However I suppose I can grudgingly admit I know why BT do it.. and I can imagine ' Old Aunt Edith' could muck up her line to become unstable because she didnt know what she was doing with being presented the opportunity of setting your own line profiles
I know that Asbo has proved on another thread that (becuase of 'last gasp' communications between the modem and the DSLAM - at least the Huawei ones!) that powering it down prevents line-errors being recorded, which you would otherwise get if you just unplugged it from the line (either at the modem or NTE), which DLM would frown on.
Ahhhhhhhh the joys of dying gasp and its effects on the DLM. Something else LLU freed me from... and something else Ive had more than one rants about going back to the early days of maxdsl... lol coming back to a BTw based ISP brings memories flooding back. If you search history back far enough theres possibly several posts by me on this topic across various forums, and how either some routers werent sending the dying gasp signal.. or the BTw DLM was ignoring it. iirc all dsl modems are supposed to hold on to a small amount of energy in reserve sufficient to send the dying gasp message to the DSLAM in the event of power failures etc.
Its a long time ago now, but the Voyager routers didnt seem to do this very well - or back then BTs DLMs didnt care.
At the other end of the spectrum from that which you are currently experiencing with your PN PPPoE, quite often (becuase the TG firmware has the wrong PPP timeouts set by PN) a modem resync will not be detected by PN's RADIUS servers, as it happens too quickly within the PPP timeout - But DLM has seen it (rather like the garden shed in Bill & Ben)!!!!!
Oh gawd... this really is like a stroll down memory lane today. Im experiencing deja vu... and now recalling why I rejoiced when Be came here and I was suddenly free from stuck bRAS profiles and the BTw DLM.. and stale sessions. I guess I need to bring myself back up to date again.