Guidelines and Limitations for Readiness Checks
These guidelines and limitations apply to Firepower readiness checks.
Evaluates Firepower Software Readiness Only
The readiness check is for Firepower software readiness only. It does not assess preparedness for intrusion rule, VDB, or GeoDB updates. Readiness checks are not supported for hotfixes or patch uninstallers.
Version and Platform Requirements
Current FMC Version |
Readiness Check Support |
---|---|
5.4 – 6.0 |
Not supported. |
6.0.1 |
Supported, with a preinstallation package. If you want to run readiness checks on a Version 6.0.1 → 6.1 upgrade, first install the Version 6.1 preinstallation package. You must do this for the FMC and its managed devices. See the Firepower System Release Notes Version 6.1.0 Pre-Installation Package. |
6.1 – 6.6.x |
You can use a Version 6.1–6.6.x Firepower Management Center to perform the readiness check on itself and its standalone managed devices. For clustered devices, stacked devices,
and devices in high availability pairs, you can run the readiness check from the
Linux shell, also called expert mode. To run the check, you must first push
or copy the upgrade package to the correct location on each device, then use this
command: |
6.7.0+ |
You can use a Version 6.7.0+ Firepower Management Center to perform the readiness check on itself and the devices it manages, including FTD devices configured for high availabilty and scalability. |
Time Requirements
The time required to run the readiness check varies depending on appliance model and database size. You may find it expedient to forgo readiness checks if your deployment is large.
![]() Tip |
For all device upgrades to 6.2.3–6.6.x, you can reduce the amount of time it takes to run readiness checks by copying (pushing) upgrade packages to devices before you begin. Readiness checks for FTD device upgrades to Version 6.7.0+ no longer require the upgrade package to reside on the device. Although we still recommend you copy the upgrade package to the device before you begin the upgrade itself, you no longer have to do so before you run the readiness check. |
During The Check/Failed Checks
Do not manually reboot, or shut down an appliance running readiness checks. If your appliance fails the readiness check, correct the issues and run the readiness check again. If the readiness check exposes issues that you cannot resolve, do not begin the upgrade. Instead, contact Cisco TAC.