That worries me a bit as I suspect the first thing our branch offices do if there's an internet outage is start rebooting stuff.įwiw, I know these things get a lot of stick, but tbh I'm loving them (once I got over the pppoe thing!). The docs are also pretty specific about not pulling the power on it as well. I have branches all over Europe, so outages are not always easy to deal with. it's just if you have the console cable and you power it off and on it & watch it, it complains about having been powered off and starts checking databases and saying 'this could take hours'. Maybe I'm overworrying about the power thing. When it gets there, cross your fingers that it registers ok & then drop a basic config on it and go from there setting up lots of Vpns in my case. So you do your very basic config.essentially an IP on the outside interface and set that as Mgmt, give it the IP/key of your FMC and send it out. which many of our sites were doing with the Asa. It's been a bit of a pain in that you can't use pppoe when using an outside interface for Mgmt.

Yuh if you Google 'ftd deployment with remote fmc' you'll find the Cisco article I'm using, it does just that.

Cisco firepower 1010