WLSE: problems with applying archived configuration

[o-ziltener]

WLSE 2.9.1a.

When I use the option "overwrite" then the wlse send the configuration into the startup-configuration and force the AP to reload.

But when I use the option "no overwrite" then the wlse do exaclty the same as with "overwrite", instead to merge the new archived configuration with the running-configuration on the ap incl. a reload!

Has anybody see the same problem too?

Any input is very welcome

Oliver

[wong34539]

This is the behaviour I see,

The two configurations are merged unless you have specified that you want to overwrite the existing configuration when you ran the job. If you choose to overwrite the configuration, two things will occur: the selected configuration template will replace the startup-config on the selected device(s) and the device(s) will be rebooted after the copy to startup-config succeeds.

May be its a bug with this verson.