Firmware updates

[Tacitus]

I'm running a 2700 with V6 firmware so the following question is probably moot.  At present I've set up various static routes in an attempt to block the BT update servers, if this is successful I'll do the same thing on a V5 to prevent any updates.  The problem is, since I'm already running V6 how do I know if the block is successful?

Part of the log shows this:

cwmd:  retried session started, server: 'https://pbthdm.bt.motive.com/cwmpWeb/CPEMgt';, event code(s): '1 BOOT,4 VALUE CHANGE'
WRN   2010-12-03T06:03:32Z   nodesd:  unable to sync data: No such file or directory
WRN   2010-12-03T06:04:32Z   nodesd:  Previous log entry repeated 7 times
WRN   2010-12-03T06:04:34Z   cwmd:  httpc_poll_dispatch - Connection timed out
WRN   2010-12-03T06:04:34Z   cwmd:  session failed...

Looking at this I deduce the 2700 was unable to connect to the update server (CPEMgt), despite several attempts.

Does anyone agree with this interpretation?

[Rik]

It looks that way to me, Tac, but Alan or MisterW will know for sure.

[MisterW]

Yep, that's failing to contact the update server. I'm not sure if the static route fiddle also works on a v5 but you can change the ACS URL on v5  ( http://bt2700hgv.tripod.com/032.htm )

[Tacitus]

Yep, that's failing to contact the update server. I'm not sure if the static route fiddle also works on a v5 but you can change the ACS URL on v5  ( http://bt2700hgv.tripod.com/032.htm )

Thanks, that's what I thought.  Problem with the static route fiddle is knowing the IP of the update servers.  The IP of this one wasn't in the static list at the time, although it is now.  Found it by trying the URL and using a packet sniffer 

[MisterW]

Problem with the static route fiddle is knowing the IP of the update servers

Doesn't an nslookup on pbthdm.bt.motive.com work ?

[Tacitus]

Doesn't an nslookup on pbthdm.bt.motive.com work ?

Yes it does    Pure brain fade - I never thought of the obvious way.....  

It's persistent though, as it's been trying to connect to bt.motive.com all morning.  Any idea what "event code(s): '1 BOOT,4 VALUE CHANGE" signify?

[MisterW]

Yep, they're pretty persistent at trying to 'phone home' 
I think it tries to contact cwmp on certain events , ie' when initially booted and when something changes hence the event codes. I've seen one other code but can't recall it at the mo.