Hi
I have noticed that when I upload a line/s of config to a device if there is a syntax error within the lines and the response is 'invalid or unrecognised command etc' Cirrus doesn't react in anyway to this and then proceeds to save the config and mark the Upload job as completed despite the fact that the line was never entered in to the config.
We are not in the habbit of uploading unchecked lines of config but mistakes will happen. But the main reason for this is we still have a number of Catos devices on our network and the commands for these devices compared to the IOS are slightly different.
I have tested this on both IOS and Catos, typing the line 'this is not a valid command' into a snippet setting it to save the config after the change and uploading it.
What happens when I review the log is that the command is rejected yet Cirrus goes ahead with saving the config and then marking the job as completed. It is easy to check the command script log after making changes to a small number of devices but on a database our size with our 2000 devices checking every command script log after making a change is impossible.
Is there anyway of switching on an active reporting mechanism that will recognise the response to invalid commands. Or at the very least is the a report or policy that will show the lines of config that weren't added.
Thanks
Ciaran
