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.
Hey FortiDave,
it would be pretty convoluted, true.
Regarding the VPN Manager on FortiManager, yes, it provides roughly the same benefit.
-> it automatically creates the VPN tunnels, routing, interfaces, etc
-> you would have to manually create the policies though
-> if you go for a full-mesh between multiple FortiGates, you only have to add the FortiGates a single time and tunnels will be created automatically between each node
-> https://docs.fortinet.com/document/fortimanager/6.4.0/examples/556949/configuring-a-full-mesh-vpn-to... for example
-> https://docs.fortinet.com/document/fortimanager/6.4.8/administration-guide/770750/overview
Regarding importing the FortiGate again post-upgrade:
- FortiManager should ignore the VPN and only have an interface and policy for it
-> the VPN will NOT show in VPN manager
- if the VPN is not properly mapped to interfaces/policies FortiManager might try to delete it, so check the installation preview carefully
In principle, if you are going to use FortiManager extensively, and are planning to do centralized VPN management with FortiManager, I would suggest recreating the tunnels in FortiManager VPN manager and replacing the configuration existing on FortiGate to get the VPN better integrated into policy packages and central management, but if you just have the few VPNs and don't plan any major changes or additions, you can also just leave it as is.
Hey FortiDave,
It's not possible to copy the FGT config via CLI to FortiManager.
You could maybe get away with some scripting to ADOM database, but that would be a bit tricky.
You can also manually rebuild the policies in FortiManager to line up with current FortiGate configuration.
The main points would be:
- you need some interface objects in ADOM database that map to the FortiGate VPN interfaces
-> these almost certainly need to be created manually
-> as long as FortiGate updated its own config to FortiManager device manager, you should be able to map the ADOM interface object to the VPN tunnel
-> do you see the tunnel interfaces in Device Manager? If not, you could retrieve the configuration (import to just Device Manager level, no ADOM DB shenanigans)
Once you have the interfaces mapped, everything else should be fairly straightforward
-> ensure you have the policy-relevant objects in place (addresses/users/groups/etc); these should be simple to script by copy&pasting from FGT config
-> either script (not sure if this will work) or manually recreate the VPN policies with the appropriate ADOM interface object (that maps to the FGT VPN interface)
After this, start an installation and check in the Preview what FMG is trying to do; I believe it should NOT try to remove the VPN anymore (given that it's attached to an in-use interface), though it might try to delete and recreate the policies around it
Thanks Debbie, appreciate the detailed response.
Seems a bit confaluted for the time I have. Ill probably just rebuild the VPN from FGM and push / overwrite current config.
Two questions, if you can help..
I like to use the FGT VPN wizard directly on the firewall as it builds the routes, interfaces, policy automatically. Does the VPN Manager on FGM provide the same benefits, or is it a more manual process?
Also, if I was to upgrade the FGT inline with ADOM, and re-import configuration, does all the VPN config / settings migrate nicely, or is there still a manual process involved?
Im trying to gage if it was just a bad idea doing direct on FW, regardess of the ADOM mismatch.
Thanks again.
Hey FortiDave,
it would be pretty convoluted, true.
Regarding the VPN Manager on FortiManager, yes, it provides roughly the same benefit.
-> it automatically creates the VPN tunnels, routing, interfaces, etc
-> you would have to manually create the policies though
-> if you go for a full-mesh between multiple FortiGates, you only have to add the FortiGates a single time and tunnels will be created automatically between each node
-> https://docs.fortinet.com/document/fortimanager/6.4.0/examples/556949/configuring-a-full-mesh-vpn-to... for example
-> https://docs.fortinet.com/document/fortimanager/6.4.8/administration-guide/770750/overview
Regarding importing the FortiGate again post-upgrade:
- FortiManager should ignore the VPN and only have an interface and policy for it
-> the VPN will NOT show in VPN manager
- if the VPN is not properly mapped to interfaces/policies FortiManager might try to delete it, so check the installation preview carefully
In principle, if you are going to use FortiManager extensively, and are planning to do centralized VPN management with FortiManager, I would suggest recreating the tunnels in FortiManager VPN manager and replacing the configuration existing on FortiGate to get the VPN better integrated into policy packages and central management, but if you just have the few VPNs and don't plan any major changes or additions, you can also just leave it as is.
Thanks again Debbie. That really clears a lot up.
if you change anything in the config on the FGT and not via FMG you have to da a retrieve config in FMG device manager afterwards to have FMG take over the changes. Otherwise they might indeed be overwritten since deploying a policy package will always also deploy the device config.
--
"It is a mistake to think you can solve any major problems just with potatoes." - Douglas Adams
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 |
---|---|
1713 | |
1093 | |
752 | |
447 | |
231 |
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.