Network Wizkid's Technical Knowledge Base

In this article I want to demonstrate how too add signed certificates to the Firepower Management Center (FMC) using the CLI. If you've worked with the FMC for some time, you'll know that the GUI can be quite limited when it comes to the sort of information you enter before generating a CertificateCSR. In fact a particular use case for wanting to use the CLI to generate CSR's for the FMC is when you want to issue the same certificate to more than one FMC. As it stands today there isn't a way to accommodate this use case via the GUI an although possible, this request can only be fulfilled by using the CLI. With that, in this article we will focus on how we can fulfill the mentioned requirement and have one certificate issued for more than one FMC. We will have our internal CA (Microsoft Server) issue an internal signed certificate that will be imported to both FMC's. Demonstration Hardware & Versions Microsoft Server 2019 (CA Server) Firepower Management Center v...

Recently I was tasked with upgrading some new Firepower 3D8350 sensors which would later be stacked into a 3D8360. These devices were shipped with software version 5.4.0.1 and I had a customer requirement to upgrade the sensors to version 6.2. I would normally stack these devices and upgrade them using the FMC, however, I didn’t have this luxury with these new devices so each sensor had to be upgraded one by one. I had two ways in which I could perform the software upgrades, either upgrade each device following the upgrade path (the longest way) or system restore each device to version 6.2 (the fastest way). Just to give you an idea of the upgrade path from 5.4.0.1 I have included it below; Version 5.4.0.2 > Version 6.0.0 PreInstallation Package > Version 6.0.0 > Version 6.0.1 Preinstall > Version 6.0.1 > Version 6.1.0 PreInstallation Package > Version 6.1.0 > Version 6.2.0 As you can imagine this particular upgrade path will require some time and it’s also worth m...