TR069 events

[#1]

So why does the PN Hub1 keep trying to record TR069 events against bad URLS:

05:46:23, 23 Apr.	(3408473.290000) CWMP: session closed due to error: Could not resolve host
05:46:23, 23 Apr.	(3408473.240000) CWMP: Server URL: https://ceased.tr69.p; Connecting as user: ACS username
05:46:23, 23 Apr.	(3408473.240000) CWMP: Session start now. Event code(s): '0 BOOTSTRAP,2 PERIODIC,4 VALUE CHANGE'
05:45:52, 23 Apr.	(3408442.970000) CWMP: session closed due to error: Could not resolve host
05:45:48, 23 Apr.	(3408438.610000) CWMP: Server URL: https://ceased.tr69.p; Connecting as user: ACS username
05:45:48, 23 Apr.	(3408438.600000) CWMP: Session start now. Event code(s): '0 BOOTSTRAP,2 PERIODIC,4 VALUE CHANGE'
05:43:40, 23 Apr.	(3408310.770000) CWMP: Initializing transaction for event code 4 VALUE CHANGE

Surely if TR069 is needed it should be working?

Edited to add : This was a new router from PN - I did a factory reset on it (under advise from a CS Rep) and then reloaded my backed up configuration.

[#2]

Anyone?

[#3]

I have the same issue.  mid june time the router stopped working. i was unable to logon to the device and it reported there were too many sessions logged onto it (or something like that).  checking the event log it recorded may failed tr069 events.  the url had changed from trying https://pbthdm.bt.mo to https://ceased.tr69.p;  the username had changed to setup@plusdsl.net (or .com can't quite remember.  i changed everything back to my username and password and everything works as it should though don't really understand what and why this happened.

[#4]

The rest of my setup is fine - its just the TR069 stuff that seems to be broken... it still tries a few times a day to send data but of course it fails.

[#5]

When a device is removed/deleted from the management platform the TR069 URL in the Hub One is munged to prevent communication with the ACS server. This is by design.

As to why it was ceased to begin with, that's something I'd need to look into.

[#6]

I may have figured it out.  The PN router isn't new.  it was from ebay to replace a really old PN one with wireless ac.  I had to enter my username and password to get it working rather than rely on TR069.  I bet the original owners account my have "ceased" hence the reports in the TR069 event logs.  hadn't realised that PN tie the router serial to the account to get tr069 to work

[#7]

But mine came from Plusnet.... so.......

[#8]

Yep, you've likely hit the nail on the head. When an account is cancelled, any Hub Ones formerly associated with it will be ceased. We can probably re-associate it with your account if you're concerned about future firmware updates etc. but you'd likely need to factory reset?

Edit: that was a response to @rliver73. Steve, your situation is undoubtedly different. We did have a problem a while back where a small number of units were being ceased inadvertently.

[#9]

@bobpullen - mine only went wrong after I did a factory reset as part of the investigations into the packet loss on my line. So I guess that's when it would have pulled the configuration from you and got set to ceased.

[#10]

Would getting TR069 re-enabled on my router help with the diagnosis of the problems I've been having since the start of January and which PN and BTOR seem to be unable to resolve?

[#11]

Unlikely Steve, we'd only be able to see what you already can by logging into the router interface really.