Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
rumikal74
New Contributor

restore from USB 80 c

i have FG 500 A  and i try to restore the conf file to 80C   from USB 

but it give me 

Copy config 1.conf from USB disk ... Get config file from USB disk OK. Invalid config file Command fail. Return code -39

 can any one help 

thanks 

1 Solution
ede_pfau
SuperUser
SuperUser

You simply cannot restore configurations between different hardware models. Depending on the complexity of your config, either rebuild from scratch (which has many advantages), or re-format config file manually (port names, model-specific lines etc.) which is not a trivial task. More or less it's the same amount of work.

 

Third alternative: the FortiConverter converts between FG models. But...it's not for free. Maybe your Fortinet partner owns one and can offer you the conversion.

Ede Kernel panic: Aiee, killing interrupt handler!

View solution in original post

Ede Kernel panic: Aiee, killing interrupt handler!
2 REPLIES 2
ede_pfau
SuperUser
SuperUser

You simply cannot restore configurations between different hardware models. Depending on the complexity of your config, either rebuild from scratch (which has many advantages), or re-format config file manually (port names, model-specific lines etc.) which is not a trivial task. More or less it's the same amount of work.

 

Third alternative: the FortiConverter converts between FG models. But...it's not for free. Maybe your Fortinet partner owns one and can offer you the conversion.

Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
Toshi_Esumi

Another key issue you need to be aware of is the difference of the OS version. If possible you should bring up the version on the existing machine to match the new one. Sometimes it might not be possible.

We needed to take similar steps in the past when Fortinet discontinued one hardware model we were using and when we decided to upgrade the hardware.

How we did was:

1) configured & tested the key features we deploy such as IPSec and SSL VPNs, FW policies, routing protocols including interface config with the new hardware to see the config difference in CLI.

2) come up with formulas how we need to adjust the config.

3) then start copying&pasting config with the modifications section by section

4) then our case we repeated it for all VDOMs.

How to cut it over to the new one needed a different type of planing and preparation.

Announcements
Check out our Community Chatter Blog! Click here to get involved
Labels
Top Kudoed Authors