Questions on presets / Firmware upgrade
George Chelidze
george.chelidze at magticom.ge
Thu May 3 03:35:02 EDT 2018
Hi Dan,
Please find my answers below.
On 05/03/2018 12:05 AM, Dan Morphis wrote:
>
>
> This is how the preset looked before:
>
> {
> "_id" : "firmware-upgrade",
> "channel" : "",
> "weight" : 0,
> "precondition" : "{\"_tags\":\"upgrade\"}",
> "configurations" : [
> {
> "type" : "provision",
> "name" : "firmware-upgrade"
> }
> ],
> "schedule" : "",
> "events" : {
> "1 BOOT" : true
> }
> }
>
>
> So this creates a preset in the default channel with a precondition of
> 1 BOOT and a tag of upgrade. For this to execute, the CPE must have
> the upgrade tag, the channel default must not be in a faulted state
> for the CPE and had to have just booted.
All of these were true except maybe channel faulted state which I didn't
check. Will give it a try.
>
> Then I replaced "1 BOOT" with "2 PERIODIC" and now it works like a
> charm
> but with periodic event. I am not sure regarding the channel's faulted
> state, but I'll give it a try once again. In general, is it a good
> practice to put firmware-upgrade/firmware-upgrade-complete presets
> in a
> separate channel?
>
> What provision do you want to upgrade after a firmware upgrade?
> Setting the config? If the CPE needs its config, it (should) will send
> a 0 BOOTSTRAP event. In all the CPEs I've tested, that will happen if
> you update the config on the CPE.
a very simple provision - untag a CPE and reboot:
const tag = "Tags.upgrade";
declare(tag, null, {value: false});
declare("Reboot", null, {value: Date.now()});
>
> I forgot to ask one question regarding log() in provisions: while my
> provision contains log() statements, I don't see output in logs.
> Should
> I enable debugging to see the output and which file logs are
> written to?
>
> Yes, it should be in the cwmp log file.
Thanks for your support.
Best regards,
George Chelidze
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.genieacs.com/pipermail/users/attachments/20180503/6a2c737f/attachment.html>
More information about the Users
mailing list