Deciding to Freshly Install
Use this table to identify scenarios where you need to freshly install. In all of these scenarios—including switching device management between local and remote—you will lose device configurations.
Note |
Always address licensing concerns before you reimage or switch management of a Firepower appliance. If you are using Cisco Smart Licensing, you may need to manually unregister from the Cisco Smart Software Manager to avoid accruing orphan entitlements. |
Scenario | Solution | Licensing |
---|---|---|
Upgrade FMC-managed devices from an older Firepower version (5.x, 6.0.x). |
The upgrade path from older versions includes intermediate versions. Especially in larger deployments where you must alternate FMC and device upgrade, this multi-step process can be time consuming. To save time, you can reimage older devices instead of upgrading:
|
Removing devices from the FMC unregisters them. Reassign licenses after you re-add the devices. |
Change FTD management from FDM to FMC (local to remote). |
Use the configure manager CLI command; see Command Reference for Firepower Threat Defense. |
Unregister the device before you switch management. Reassign its license after you add it to the FMC. |
Change FTD management from FMC to FDM (remote to local). |
Use the configure manager CLI command; see Command Reference for Firepower Threat Defense. Exception: The device is running or was upgraded from Version 6.0.1. In this case, fresh install. |
Remove the device from the FMC to unregister it. Reregister using FDM. |
Change ASA FirePOWER management between ASDM and FMC. |
Start using the other management method. |
Contact Sales for new Classic licenses. ASA FirePOWER licenses are associated with a specific manager. |
Replace ASA FirePOWERwith FTD on the same physical device. |
Fresh install. |
Convert Classic to Smart licenses; see the Firepower Management Center Configuration Guide. |
Replace NGIPSv with FTDv. |
Fresh install. |
Contact Sales for new Smart licenses. |