01-05-2022 06:15 AM
I currently have 4 ASA 55xx w/ firepower devices in my network topology.
the devices are registered in FMC post VPN connection.
my FMC is on my internal network on site 1. (192.168.1.3)
each one of my ASAs do a site 2 site tunnel to the main office via ASDM (not FMC), then the remote devices use a local site LAN address to attach to FMC for policies, etc.
I'm moving to FTD 2130 in all locations, but my question is this.
it appears the preferred way to do all of the new configurations is via FMC
how do I register the 2130s to the FMC before they have established a VPN connection to the FMC site?
01-05-2022 07:57 AM
01-05-2022 08:41 AM
My FMC is virtual. I don't have the ability of putting it on a Public network. If I NAT tcp/8305 to it maybe that will work?
01-05-2022 09:42 AM
01-05-2022 01:15 PM
You would either need to stage the FTDs before they are sent to the remote location or you need to configure the FTD to be manageable via a public IP. So you would need to either configure the FTD management interface with an extra public IP, or if you are running 6.7 or higher configure the external / outside data interface to also be a management interface. Then, as Mohammed has mentioned, NAT the FMC IP to a public IP on port tcp/8305 and make sure there are access rules that allow the remote FTD to access the FMC on port tcp/8305.
01-05-2022 01:27 PM
I will try the NAT thing. my main Site FTD will not need it because it's on the same segment as the FMC.
I will NAT/Access Rule the Public IP to route port 8035 to the FMC.
I have one of the remote devices here so I can try it through a separate Public IP to test POC before I move them to their remote locations.
thanks for the tips guys.
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