FMG is rather useless here as switch config is part of the device config and not of the policy package.
Since the dievce config is device specific there is no way to roll that out to annother FGT.
Except if you replace that FGT in FMG by a new one and the roll out device config and policy package to it.
Thus this may still require a load of work since - if the FGTs are too different - you may have to correct a lot of interface mappings....
Anyhow I cannot imagine that a 300D and 300E are so very different. As long as they have the same INterface layout and names you should be able to copy paste most of the config (execpt from clustering).
I'd in this case try to create a backup, maybe replace the serial number in it to fit the new FGT and then apply it to the new one. Or if that don't work apply it as a script.
--
"It is a mistake to think you can solve any major problems just with potatoes." - Douglas Adams
I ended up copy+pasting sections of the old config over to the new one. I used find/replace to change the updated interface names. It worked perfectly!
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.