from time to time FortiManager 7.4.3 tries to "modify" my CLI template from "config system global" to "config 1 system global" when pushing to FortiGate Firewall 60F/100F/200F. I can force this error by "retrieve config" and pushing "policy package AND device settings" afterwards. Pushing ONLY device settings works and does not have this issue and once only device settings are pushed policy also works :)
Does anyone else have this issue or maybe a solution?
Thanks...
Solved! Go to Solution.
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.
Hey Team-IT,
that does sound strange. I've not come across this myself, but I did find indication that something similar is under investigation by the FortiManager engineering team (an issue with "config 1 router [...]" or "config 1 system interface").
This is maybe related to system templates; is one assigned to the FortiGate in question?
In addition, I would suggest you open a ticket with FortiManager technical support for further investigation. For your (and their) reference, the issue under investigation has ID 1034754.
Cheers,
Deborah
Hey Team-IT,
that does sound strange. I've not come across this myself, but I did find indication that something similar is under investigation by the FortiManager engineering team (an issue with "config 1 router [...]" or "config 1 system interface").
This is maybe related to system templates; is one assigned to the FortiGate in question?
In addition, I would suggest you open a ticket with FortiManager technical support for further investigation. For your (and their) reference, the issue under investigation has ID 1034754.
Cheers,
Deborah
Hi Debbie,
thanks for your investigation and your response here. Any yes it only affects systems where a CLI system template is assigned to. Once unassigning the system template playing the config goes smnooth. I reverted back to FMG 7.4.2 and waiting for Ticket 9525323 to be solved since it is now linked to the internal ID you provided. Thanks a lot...
We are actually facing the same identical issue... did you ever manage to find a fix for this?
i can't even force it the way you suggested it ... it still fail with the same error to me, and BTW we have 400F
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 |
---|---|
1692 | |
1087 | |
752 | |
446 | |
228 |
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.