FTD 4100 to 4200 migration in FMC

[ben.levin1]

Hi all. I'm trying to migrate an FMC-managed FTD 4125 HA pair to a pair of FTD 4215s.  FMC and all of the FTDs are running 7.4.2.1.

Is there any way to migrate the FTD interfaces, routing, etc over to the 4215s?  I talked to the TAC and they told me to use the migration wizard in FMC. However, this only seems to support 1100s and 2100s to 3100s, and when we run the wizard, the 4125s don't show up.  I was also going to try to use the push config option but that gives me an error that the models and interfaces don't match.

If there's no way to do this, we're going to have to do it manually, which would be time consuming.

Thanks.

[Marvin Rhoads]

Sorry to hear that TAC is struggling to support your resolution. At this point, I can only suggest that you request escalation of your case with them.

[AhmadAmro]

I wanted to update you regarding the migration. Cisco has shared several important points related to the issue we faced, and I’m sharing them here as they may help others encountering similar migration problems.

During their analysis, Cisco found a discrepancy in the HA_EXTN_DATA table on the FMC side. This inconsistency caused the static route configuration to fail during migration, which led to the model migration errors we observed. In their lab testing, Cisco identified a workaround: using “Refresh Node Status” on the HA pair before reattempting the model migration. This resolved the internal errors they previously saw.

Additionally, Cisco highlighted another issue that can cause migration validation failures. On our FTD-HA, interfaces Eth1/1 and Eth1/2 were showing an MTU value of “0”, which is invalid. MTU values must be between 64 and 9184. This will also need to be corrected to avoid migration errors.

It’s worth mentioning that I performed the same migration on other devices with the same version and platform series without any issues, which suggests the Cisco TAC findings are accurate for this specific case.

Action Plan from Cisco:

• Perform Force Refresh Node Status on the HA pair
• Correct the MTU values on Eth1/1 and Eth1/2
• Re-attempt the model migration