cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1092
Views
5
Helpful
3
Replies

Migrate FTDv to a hardware FTD appliance

Chess Norris
Level 4
Level 4

Hello,

I have customer that was planning on installing two 2130 and two 2140 FTD appliances, but due to production and delivery issues, we were  forced to install a couple of temporary FTDv. The hardware appliances have now arrived and I'm looking for some advices on how to make this migration with minimal downtime.

I am planning on re-using the ACP and use the same interface zones, but I am not sure how much I can prepare before the actual migration take place. 

 

One of the virtual FTD have a lot of L2L tunnels and I remember it's not possible to remove/delete the virtual appliances from FMC without also deleting the VPN tunnel configuration from the FMC. Could I just swap the local gateway side with the new node and then before removing the virtual appliance from FMC?

 

Can I configure the new  firewalls in FMC with overlapping data interface networks?

 

We want to use the same host name on the new FTDs, but have to use a temporary name until we remove the virtual FTD:s from FMC. Can I just rename the new ones without any issues?

 

I would appreciate some inputs on what I can configure and prepare before the migration and what I need to do after we delete the virtual FTDs from FMC.

 

Thanks

/Chess

1 Accepted Solution

Accepted Solutions

Marvin Rhoads
Hall of Fame
Hall of Fame

The steps you laid out should work fine.

Once you have registered the new appliances you can designate then as the local member of the site-to-site VPN configurations.

You can also configure them with overlapping or even the same IP addresses on the data interfaces. As long as they remain disconnected that will allow you to have everything mostly configured prior to cutover.

Changing host name after the fact is also possible. The name of the managed appliance in FMC is only locally significant (to FMC). The hostname on the device itself can likewise be changed without impacting the rest of the configuration.

View solution in original post

3 Replies 3

Marvin Rhoads
Hall of Fame
Hall of Fame

The steps you laid out should work fine.

Once you have registered the new appliances you can designate then as the local member of the site-to-site VPN configurations.

You can also configure them with overlapping or even the same IP addresses on the data interfaces. As long as they remain disconnected that will allow you to have everything mostly configured prior to cutover.

Changing host name after the fact is also possible. The name of the managed appliance in FMC is only locally significant (to FMC). The hostname on the device itself can likewise be changed without impacting the rest of the configuration.

Thank you so much, Marvin.

/Chess

Just a follow up. It all went well and no issues changing the local member of the site-to-site VPN configurations.

I think this method  also can be very useful in those case you want to re-image a FTD and you need to unregister it from the FMC. Instead of re-creating all VPN configuration, we could just deploy a FTDv and temporary move the VPN config to this FTD.

 

Thanks

/Chess

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Review Cisco Networking products for a $25 gift card