For those specific Configuration Failed alarms they can be cleared by successfully pushing configuration. Since PMP is template-based you can push a trivial template and that should result in a successful configuration update with no actual change made on the device.
I recommend testing against a lab device or single SM first to verify that the device doesn't reboot from this template. I would not expect this to cause a reboot but I prefer caution if attempting to do this on a large number of devices.
No, not specifically the previously pushed template. It would likely fail again anyway. Any template can be pushed, including a trivial one with no functional change. As long as the job completes successfully the alarm will clear.
For example, this template should result in a successful push every time since no configuration is actually being edited. Test on a single device first to verify the device does not reboot, before doing a select-all.
Rynet, we recently made an update to fix this in 1.6.1, the latest release, so "AXN_5.1._8174" is recognized as up-to-date. The alarm should automatically clear itself the next time the device registers to cnMaestro.
Cloud is already running 1.6.1. Are you running in cloud or on-premises?
Telemar, merging that empty template with a previous template wouldn't change anything since the template is blank. Is it correct to assume you mean automatically pushing the blank template immediately after pushing your other template in order to clear a configuration failure alarm?
If that is the case, I do not think it is the correct approach. If the template you're pushing results in configuration failure every time then I think there is something that must be corrected on that end rather than trying to clear alarms with this work around.
What is the failure error in the configuration job when you push the template you mentioned?
When I last upgraded the firmware I got indications that the updates had failed. However, when I would go to the SM to see what happened, the unit was successfully updated. Returning to CNUT and doing a refresh would clear the "failures". If I remember correctly this also happened with cnMaestro, of course there's no way to "refresh" once the job showed as failed. The cnMaestro part I'll have to confirm when I upgrade to 15.2.
"After some investigation I believe we have found the root cause of this issue. Luckily there are two solutions to resolve this for you immediately. A bug was identified and fixed in firmware version 15.1.3 where if configFileParameters.rebootIfRequired is set to true within a configuration template, the configuration job will fail in cnMaestro but the configuration changes are still applied successfully.
This gives you the following options:
Upgrade your devices to 15.1.3
Remove configFileParameters.rebootIfRequired from your configuration templates
The purpose of configFileParameters.rebootIfRequired is to allow automatic reboot when importing configuration onto the device via its web interface but it conflicts with cnMaestro configuration before version 15.1.3."
We have tried our template without that parameter and the config happens successfully on device and cnMaestro (and the reboot works fine)
Devices will still automatically reboot if required even without configFileParameters.rebootIfRequired being set. cnMaestro uses its own mechanism to tell the device to automatically reboot. configFileParameters.rebootIfRequired is only used for configuration files used outside of cnMaestro.
I've also created a Knowledge Base article detailing this for others searching for a solution.