Hi all, we have recently update FGT to FortiOS 7.2.8.
We found out a problem during the Re-Install policy.
The process returns an error and we must "Retrieve" the configuration to complete the install.
We use FortiManager 7.2.5.
Can you help us?
Regards.
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 Dado82,
the image is cut off to the right, but based on the errors, in particular 'datasrc invalid' and 'attr [srcaddr] value[...]', it looks like some references are (or were) incorrect - as if FortiManager was trying to prepare the installation package, but the source address of ID 107xxxxxxxx (a global header policy?) did not exist, or something in that vein.
I am a bit rusty with FortiManager.
Glad to hear it works after the retrieve!
Cheers,
Debbie
Hey Dado82,
if you click on the 'View Installation Log' button in that display, it basically dumps the CLI commands and responses from FortiGate, so that gives you an idea of what error FortiManager encounters when trying to push the package.
If that doesn't give you any useful information, the 'View Progress Report' button might also help in providing a bit more details.
Usually, if you get issues like that after updating FortiGate, in my experience one of three things occurred:
- you updated the FortiGate to a firmware version FortiManager is not compatible with, meaning there would be CLI syntax FortiManager cannot handle
- the FortiGate was updated to a new major branch, and either the ADOM has to be upgraded, or FortiGate has to be moved to a new ADOM (from 7.0 ADOM to 7.2 ADOM for example)
- some default values changed in FortiGate with the update, so it is no longer 100% in sync with FortiManager; a config retrieve usually fixes this and the issue does NOT reoccur
Cheers,
Debbie
Hi Deddie_FTNT thanks for the quick reply,
- The FMG version is compatible with that of the FGT, we checked directly on the Fortinet portal.
- ADOMs were correctly upgraded to 7.2 during the upgrade
- After the Retrieve, it was possible to proceed with the installation.
in View Installation Log we don't have any details, while in View Progress Report it reports the error I attach.
Hey Dado82,
the image is cut off to the right, but based on the errors, in particular 'datasrc invalid' and 'attr [srcaddr] value[...]', it looks like some references are (or were) incorrect - as if FortiManager was trying to prepare the installation package, but the source address of ID 107xxxxxxxx (a global header policy?) did not exist, or something in that vein.
I am a bit rusty with FortiManager.
Glad to hear it works after the retrieve!
Cheers,
Debbie
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 |
---|---|
1547 | |
1030 | |
749 | |
443 | |
210 |
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.