About Time Tests
Time values given here are based on in-house tests. Although we report the slowest time of all upgrades tested for a particular platform/series, your upgrade will likely take longer than the provided times for multiple reasons (provided below).
Basic Test Conditions
Deployment: Values are from tests in a Firepower Management Center deployment. This is because raw upgrade times for remotely and locally managed devices are similar, given similar conditions.
Versions: For major upgrades, we test upgrades from all eligible previous major versions. For patches, we test upgrades from the base version and from the immediately preceding patch.
Models: In most cases, we test on the lowest-end models in each series, and sometimes on multiple models in a series.
Virtual settings: We test with the default settings for memory and resources.
Push and Reboot Not Included
Values represent only the time it took for the Firepower upgrade script itself to run. Values do not include the time required to upload upgrade packages to the FMC, nor the time to copy (push) upgrade packages from the FMC to a managed device.
In FMC deployments, insufficient bandwidth between the FMC and managed devices can extend upgrade time or even cause the upgrade to time out. Make sure you have the bandwidth to perform a large data transfer from the FMC to its devices. For more information, see Guidelines for Downloading Data from the Firepower Management Center to Managed Devices (Troubleshooting TechNote).
Values also do not include reboots, readiness checks, operating system upgrades, or configuration deploys.
Time Is For Single Devices
Values are per device. In a high availability or clustered configuration, devices upgrade one at a time to preserve continuity of operations, with each device operating in maintenance mode while it upgrades. Upgrading a device pair or entire cluster, therefore, takes longer than upgrading a standalone device.
Note that stacked 8000 series devices upgrade simultaneously, with the stack operating in limited, mixed-version state until all devices complete the upgrade. This should not take significantly longer than upgrading a standalone device.
Affected Configurations and Data
We test on appliances with minimal configurations and traffic load. Upgrade time can increase with the complexity of your configurations, size of event databases, and whether/how those things are affected by the upgrade. For example, if you use a lot of access control rules and the upgrade needs to make a backend change to how those rules are stored, the upgrade can take longer.