07-11-2024 12:51 PM
To use the tool, you need an FMC with the device you want to migrate to registered to. Right? Otherwise, how will it get to the device. To register it, you need an IP, which is on the management interface, or converged mode.
So, why is it when going through everything in the tool and it comes time to push to device it then fails?
07-12-2024 12:29 AM
What hardware models and software versions are you migrating from and to?
07-29-2024 11:30 AM
The FMT has a LOT of bugs to work out still and it is not ready for primetime. What I discovered is when the ASA is configured for Management VRF, and things like Radius, Tacacs, Accounting, Monitoring are using the Management interface routing table, None of it will migrate and cause errors, and the Management interface of the firewall configuration wants to overwrite the embedded M0/0, and thats where the error happened. I wound up removing all references to management from the configuration before it would fully complete.
Another Not ready for Primetime issue is it will NOT migrate outbound ACL, so all the DMZ objects do not get migrated, and I have HUNDREDS of them for a couple servers that I now have to manually add. I have 3 DMZ that only have inbound objects. Seems it would more prudent to be able to migrate the outbound ACL since anything going through to a DMZ would be going OUT the interface to the DMZ servers.
10-29-2024 08:05 AM
thanks for posting - just stumbled over the same issue while migrating ASA to FTD.
I simply removed the management interface configuration from the ASA config and it worked. No issue with that, since the mgmt interface is different on the FTD..
In general I like the migration tool, error handling could be better. I would like to be able to correct things on the fly and not start from step1 each time.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide