Questions on presets / Firmware upgrade

[Dan Morphis]

On Wed, May 2, 2018 at 8:36 AM, George Chelidze <george.chelidze at magticom.ge
> wrote:

> Dan, please find my answer below.
>
> On 05/02/2018 08:06 PM, Dan Morphis wrote:
> > Was the event your only precondition? Was the channel in a faulted
> > state for that CPE? Presets without a channel get put on the "default"
> > channel.
> >
> > -dan
>
> 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.

>
> 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.


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.

-dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.genieacs.com/pipermail/users/attachments/20180502/76e1d171/attachment.html>