Comments
-
Yes, looking for a solution to the comparison criteria rules not being able to ignore the Fortigate keys, due to NCM doing line by line comparison and Fortigate keys do not following a logical character sequence.
-
Better NCM support for FortiGate firewalls please, the connection template does not work with the 60E and comparison criteria for all FortiGates with their ever changing private keys needs a solution as well. We like the change management daily reprots on configuration changes, but ignoring all the key sections is annoying.
-
Same here... opened a case, no solution, hoping for a feature request. I might have to try to figure something out on the Fortigate side to prevent them from being shown in the config altogether without sacrificing anything of course.