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

FortiGate Migration from 600E(HA-A/P) To 200G(HA-A/P)

Hi Guys,

I need to migrate from 600E (HA A/P) to 200G (HA A/P). I created a FortiConverter service today and mapped only the up interfaces but did not select the HA interface (only ports 1-7). The other ports are down on the 600E.

I already configured the new 200G pair as HA A/P. I want to know what will happen when I restore the FortiConverter config file? If I don't choose to copy the HA settings there, will it destroy the current HA on the 200G??

Please advise!

Thanks,

3 REPLIES 3
ozkanaltas
Valued Contributor III

Hello @orspider ,

 

I don't have any experience with the FortiConverter service, but I used the FortiConverter standalone version. After conversion, FortiConverter will provide all configuration parts part by part. For example, policy, address, interface, ha, etc. After getting the files, you can add HA ports to the configuration. As you know, FortiGate configurationis clear text.

If you have found a solution, please like and accept it to make it easily accessible to others.
NSE 4-5-6-7 OT Sec - ENT FW
If you have found a solution, please like and accept it to make it easily accessible to others.NSE 4-5-6-7 OT Sec - ENT FW
AEK
SuperUser
SuperUser

Hi Spider

If I understand well, you converted the config without taking in consideration the HA config, right?

In that case I'd push the new config to one standalone 200G (without HA), and then I'd build the HA cluster.

AEK
AEK
Toshi_Esumi
SuperUser
SuperUser

HA config is relatively small portion under "config system ha" likely less than 20 lines. It's easy to recover even if you didn't include HA in converter conversion. It would probably skip that part. Just make sure you have backup config for that part for both units. Or if you configured in CLI originally, you probably remember what you had to configure, like priority, heartbeat interface, dedicated management gateway, monitoring interfaces, etc.
When you upload the converted standalone config to both new 200Gs with heartbeat cable disconnected, configure below in the same way the 600Es are configured:
1) hostname under "config system global"(if you set a unique hosthame for each)
2) "config system ha" part. Of course two units might have different config.
3) dedicated management interface (like mgmt) IP config

Then just connect the heartbeat cable between them. Since other parts are identical and already uploaded to both, after deciding which would be primary it should sync up leratively quickly. 

Toshi 

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