Skip to main content
shadowsfx45
shadowsfx45
New Member
February 21, 2018
Solved

FG300C to FG300E upgrade

  • February 21, 2018
  • 1 reply
  • 19676 views

Hi I am new to FortiGate firewalls.

 

We are planning to upgrade the existing FW which is FG300C 5.2.2 to FG300E latest fortios. I would like to know if there is any recommendation that i have to consider or some procedure which i can follow for the upgrade.

 

Thank you 

Best answer by Seppel

Hi,

Unfortunately, you can not update from a 300c to a 500e. usually you can save the config, change the header and read in a new fortigate. in the textfile you can also change the interfaces with search and replace. between 5.2 and 5.6, however, the hash value has changed for the encrypted passwords. Unfortunately, it is now impossible to simply transfer the config. that does not work with the forticonverter, which is more intended to convert configurations from other manufacturers. if you do not want to rewrite the complete config, you can do the detour via a 300d. Take a 300d 5.2 on it, copy 300c config on the 300d and make the update steps to 5.6.3 Maybe your reseller can help you out with a piece of her own

we have done this way from 300c to 500e.

 

Regards,

 

andy

1 reply

sw2090
SuperUser
sw2090
SuperUser
February 22, 2018

keep two things in Mind:

 

[ul]
  • different FortiGate Models may have different interface names and layout. You may due to this have to change your config before you import it on the new FGT. ALWAYS import a config backup into the same FortiOS version you exported it on. So if you have 5.2.2 on your current FG300C then downgrade the new FG300E to 5.2.2 before importing backup from the FG300C!
  • Afterwards upgrade to the latest FOLLOWING THE UPGRADE PATH as recommended by FortiNet. You find that in the relase notes for the latest FortiOS. In this Case this will mean you ned to go from 5.2.2 to 5.2.3 to 5.2.5 to 5.2.7 to 5.2.9 to 5.2.10. Then from 5.2.10 to 5.4.4. Unfortunately I don't have the rest here since we don't use v5.6 here.[/ul]

    If you do not need to preserve your config you don't need to do this of course. In this case upgrade it to the latest FortOS and then config from scratch :)

     

    hth

    Sebastian

    • ede_pfau
    SuperUser
    ede_pfau
    SuperUser
    February 22, 2018

    As it turns out the 300E is a brand-new model which is supported by FOS v5.6 only. This is often the case when you keep the hardware for, say, more than 5 years, and buy the latest HW.

     

    But, as so often, there's a light side to this:

    if you reconfigure from scratch you will wade out a lot of 'historical' objects, like addresses, services, policies. There even could be more efficient ways to achieve a protection because FOS has evolved over time.

    'from scratch' isn't meant literally, you can reuse chunks of the config (like address definitions) by cut&paste between old and new config file. Inserting into the running config will give you instant feedback of syntactical errors; OTOH the amount of 'live pasted' code is limited (finally, you'll run into a timeout).

     

    To faciliate live pasting:

    open a second console window (SSH), enter 'diag deb ena', 'diag deb cli 7'. Now, the command line interface will be quite chatty so you can spot the reason for an error more easily.

    sw2090
    SuperUser
    sw2090
    SuperUser
    February 22, 2018

    Well in this case it's worth a check if you can upgrade the 300C to 5.6. If possible you might do what I said vice versa.

    That is first upgrade the 300C to the latest 5.6 accoarding to the upgrade path and then export the config and put it into the 300E with the same 5.6 on it.

     

     

    Terms & ConditionsAccessibility statement