After upgrading to FortiOS 7.4, I am getting a notification to migrate the configuration when logging in with GUI. Is it necessary? What does it affect?
Solved! Go to Solution.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
I assume you are most likely referring to the new optional step in the initial "FortiGate Setup" splash screen, as shown here:
https://docs.fortinet.com/document/fortigate/7.4.0/new-features/819483/forticonverter-in-the-gui
It is intended to be used when migrating fom one model to another, so if you merely updated the firmware and have no intention of migrating, you can safely ignore it.
I assume you are most likely referring to the new optional step in the initial "FortiGate Setup" splash screen, as shown here:
https://docs.fortinet.com/document/fortigate/7.4.0/new-features/819483/forticonverter-in-the-gui
It is intended to be used when migrating fom one model to another, so if you merely updated the firmware and have no intention of migrating, you can safely ignore it.
Created on 09-19-2023 02:53 AM Edited on 09-19-2023 02:54 AM
Thanks,
Yes, it is.
I actually just did an upgrade.
I have an issue and I don't know if it is correct to do this or not.
When I try to access one FortiGate member in Cluster CLI from the other the connection is closed.
FortiGate01 # execute ha manage 1 admin
Connection closed by 169.254.0.2
When I take backups for the configuration and compare them, I always find a difference, especially in the passwords. Although they show synchronized in the HA.
What if I migrate the configuration from one of them to the other?
Created on 09-19-2023 04:41 AM Edited on 09-19-2023 04:42 AM
Password hashes can typically be ignored when comparing config backups, as their "textual representation" isn't stable, even when the real value remains unchanged.
If you can't connect to the secondary, nor is it synchronising (other config sections mismatch), that suggest a problem in HA connectivity.
You can certainly copy over the configuration to the secondary, with the necessary changes (hostname, Ha priorities, individual management intereface+IP configs), but you may need to repeat that if the root cause is not addressed.
You can try some of the steps listed here for some DIY troubleshooting: https://community.fortinet.com/t5/FortiGate/Troubleshooting-Tip-HA-synchronization-issue-cluster-out...
Alternatively, or if that fails, reach out to TAC for assistance. This KB lists some useful info you can attach in the initial report. - https://community.fortinet.com/t5/FortiGate/Troubleshooting-Tip-HA-troubleshooting-information-for-T...
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1662 | |
1077 | |
752 | |
446 | |
220 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.