Lists the guidelines for migrating FDM-managed device configurations.
Guidelines for FDM-managed device migration
-
Each FDM-managed device object has a unique name and configuration—Firewall Migration Manager migrates the objects successfully without changes.
-
The name of an FDM-managed device object includes one or more special characters that are not supported by the management center—Firewall Migration Manager renames the special characters in the object name with a "_" character to meet the management center object naming criteria.
-
An FDM-managed device object has the same name and configuration as an existing object in the management Center—Firewall Migration Manager reuses the management center object for the threat defense configuration and does not migrate the FDM-managed device object.
-
Multiple FDM-managed device objects have the same name but in different cases—Firewall Migration Manager renames such objects to meet the threat defense object naming criteria.
Firewall Migration Manager analyzes both name and configuration of all objects and object groups. However, XML profiles in remote-access VPN configurations are analyzed only using the name.
Limitations for FDM-managed device configuration
Migration of your source FDM-managed device configuration has these limitations:
-
Dynamic routing protocols, like OSPF, are not automatically migrated.
-
If the source FDM-managed device configuration has access control rules that do not refer to specific tunneling protocols (like GRE, IP-in-IP and IPv6-in-IP), but these rules match unencrypted tunnel traffic on the FDM-managed device, then, on migration to the threat defense, the corresponding rules will not behave in the same way they do on the FDM-managed device. We recommend that you create specific tunnel rules for these in the Prefilter policy, on the threat defense.
-
Supported FDM-managed device crypto map will be migrated as point-to-point topology.
Limitations for RA VPN Migration
Remote Access VPN migration is supported with these limitations:
-
Custom attributes, SSL settings and VPN load balancing migration is not supported.
-
For a radius server, if dynamic authorization is enabled, the AAA server connectivity should be through an interface and not dynamic routing. If FDM-managed device configuration is found with AAA server with dynamic authorization enabled without interface, Firewall Migration Manager ignores dynamic authorization. You must enable dynamic-authorization manually after selecting an interface on the management center.
-
Bypass access control sysopt permit-vpn option is not enabled under RA VPN policy. However, if required, you can enable it from the management center.