If it so happens a wildcard FQDN object gets put into an address group and that group is already on a source of a policy/esss. When you are upgrading the firmware, all polices with said group will not be saved. They also will not be in the auto backup config. I say this is a bug because there is no warnings or prevention in place keeping this from happening.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
I can see how this is a nuisance. But...it's mentioned in the Release Notes, and we've already had a thread here on the forums about it.
I know how this may sound, anyway: after upgrading, always run 'diag debug conf read', and/or compare the config backup before & after. The omission is clearly printed in the debug command.
Thank You! I searched before posting this but couldn't find anything relating to it. We just upgraded to 6.0.3, I didn't see anything there, but I did just find it in the release notes of 6.0.4. Thanks Again!
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1731 | |
1099 | |
752 | |
447 | |
240 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.