02-15-2019 12:41 AM - edited 02-21-2020 08:49 AM
Hello Cisco
02-16-2019 07:41 PM
1. As of release 6.3 you can now do High Availability with either FMC or the local firepower Device Manager (FDM).
2. You can configure either way - start with migrating to standalone and then make it HA or migrate direct to HA.
3. If you use the migration tool (vs. manual migration) then you have to use FMC.
4. No. Note that when in HA, each FTD device requires the relevant feature licenses such as Base, URL Filtering or Malware.
02-22-2019 01:23 AM
Thanks Marvin for your return, it is helpful.
Let's say i go for the manual migration from ASA-X to FTD 4100. Do i need to collect VPN Pre-shared keys or other keys or can I just copy and paste from the old config file?
02-22-2019 02:25 AM - edited 02-22-2019 02:25 AM
For VPN pre-shared keys you need to have them in plain text. You can retrieve them from the ASA if you get the running-config using the command:
more system:running-config
If your ASA is using a CA-signed certificate that will have to be rehosted on the new appliances. Unless you have the original private key used (e.g. if you used OpenSSL to create the original CSR) or made it exportable when you first created it, you will have to regenerate a CSR and get the CA to issue the certificate.
02-25-2019 07:45 AM
Thank you so much.
One last question, can the FMCv can do the same job the FMC do(in regard to the migration tool)??
02-25-2019 08:11 AM
FMCv vs. FMC physical appliance are equivalent with respect to migration tool functionality.
The physical appliances can themselves be configured as HA and have increased scalability (for managing more sensors and ingesting and storing more events). Other than that, they are functionally equivalent.
02-25-2019 10:21 PM
Thanks.
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