Skip to main content
supportchris
New Member
April 30, 2020
Question

FortiGate 50e Config File to new (same model) FortiGate 50e

  • April 30, 2020
  • 1 reply
  • 5611 views

Hello all --

 

I currently have a FortiGate 50e (#1) up and running. I will be installing a second 50e (#2) in another location. I wanted to copy (restore) the config form #1 to device #2. Since most of the settings will be the same, I wanted to cut time down on having to do a full configuration on #2 and just change the settings that need to be changed. However, once I restore the config file to #2, it no longer allows me to access the device. Any suggestions?

    1 reply

    Toshi_Esumi
    SuperUser
    SuperUser
    April 30, 2020

    I'm not sure what you meant by "access the device". But assume you're realizing it (#2) has #1's config including interface IPs and admin username/password. Then to figure out what's going on or change something to allow your access from an interface, you need to get in via Console port and use CLI to do it.

    You could have pre-modified the config file to adjust it for #2's needs before uploading. But since it's already uploaded, modifying it via Console would be the fastest option.

    supportchris
    New Member
    April 30, 2020

    Thanks for the input Toshi.

     

    Just for clarity, what I meant by cant access is that I cant get to it by GUI or CLI. Unfortunately I am not a network person (more of the sys admin type) and am not too experienced with configuring network equipment. We had a service provider configure the original one so I just took that config file, modified it with a new IP and uploaded it. However, with the new IP (or even old IP) I was unable to get into the device. It was connected to a stand alone laptop so that it wouldnt interfere with the current network. I was able to get it going through the cloud and changed\updated configurations that way.

    Toshi_Esumi
    SuperUser
    SuperUser
    May 1, 2020

    Then, probably you couldn't even ping the IP you are trying to get in with. Could be a typo for the address when you change or DHCP if your laptop is relying to. Anyway, you need to console into it then correct.