08-27-2020 03:17 PM
Solved! Go to Solution.
08-28-2020 04:52 AM
As @Rob Ingram noted the sftunnel is encrypted (TLS 1.2 over tcp/8305). Some people are reluctant to expose any management interface to the internet, even encrypted - perhaps with good reason because ...bugs. In that case your option 1 is preferable.
08-27-2020 11:31 PM
Hi,
You could NAT the FMC behind the local FTD and manage the other FTD's over the internet, communication between FTD and FMC is secured and encrypted using the sftunnel.
HTH
08-28-2020 04:52 AM
As @Rob Ingram noted the sftunnel is encrypted (TLS 1.2 over tcp/8305). Some people are reluctant to expose any management interface to the internet, even encrypted - perhaps with good reason because ...bugs. In that case your option 1 is preferable.
08-28-2020 06:28 AM
Hi Marvin
Thanks for the reply. So, from your response, option #1 is preferred.
I would keep FMC and FTD in each city on a local IP Address (Boston, Chicago, New York, Atlanta, Pittsburgh, Birmingham). Then, I would simply continue to use my Headquarters FMC at Hilton Head Island and add these 6 FMC devices in each city to it with their local IP's for one management web dashboard. ( I have purchased the licensing for this already). The S2S tunnels would be the way that configs are deployed from Hilton Head FMC to the individual Cities like Birmingham.
I am just typing this out to make sure I understand. There are no Public IP's for any FMC or FTD, correct?
Much appreciated,
Jen
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