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 haven't tried it myself but this could possibly convert the config file between fortigate models. If this doesn't work, only way is manual conversion section by section. By the way, most likely you need to match FortiOS version between two units to use this tool. Good luck.
You cannot load a config file from one model into another model. The update procedure will check the header lines in the config file to prevent this - as it doesn't make sense. Most notably port names/numbering is different between models, and if an unknown port name (for example, "lan" instead of "internal") is referenced in a policy, the policy won't load and an error is created.
If at all both units must run the same firmware version and patch level. Then, as @Toshi posted, you can cut&paste sections from the original config file via CLI to the new model. Note that a "new", factory-reset model already has a configuration which may contradict the config commands you enter.
In short, especially on these small models, it would be easier and preferable to recreate the config in the GUI. Single data items, like IPsec VPN PSKs, can then be inserted manually if absolutely necessary.
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 |
---|---|
1669 | |
1082 | |
752 | |
446 | |
225 |
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.