If you are working with the trial version of FortiConverter you cannot run through any fine tuning steps of the resulting config (renaming firewall objects, syntax checks on object names, etc.), but the basic migration is done anyway. Once the migration is completed you can download the resulting config file. If you skip this step it’s possible that the resulting configuration file is using interface names that do not exist on the new Fortigate model and therefor this configuration does not work as expected. This is necessary because different Fortigate models use different interface names. Here you have to assign the old interface names to the new interface names. There is just one obstacle – in the third migration step you have to do the “Interface Mapping”: For example you will be informed that encrypted passwords are not being migrated but replaced with “123456”.
Then you’ll be guided through a few migration steps where you get some information about the migration. As source files you have to import the old config file and the empty config file of the new Fortigate model. Currently v5.6.1 is the latest FortiConverter version – please make sure that you are installing the “py”-installation file (the one with.
Fortinet support downloads software#
The installation software can be downloaded from your Fortinet support portal (download area). The tool runs as an python application on a Windows client. With the test version you can test a conversion, but the backup file of the new configuration is not available for download.
Fortinet support downloads full#
The FortiConverter requires a license for the full range of functions. So if you are going to replace an old Fortigate model with a new one and you want use the old config file (instead of configuring the new Fortigate from the scratch) you can use the FortiConverter as an alternative to the procedure we have described in one of our former blog post “How to transfer a FortiGate configuration file to a new FortiGate unit of a different model”. Also an old Fortigate config file can be used as the source file. Starting with FortiConverter 6.0, any kind of conversion requires a valid licenseįortinet has published a very nice and helpful tool for converting firewall configs from other vendors into a Fortigate configuration file.
0 kommentar(er)
