Cisco Cisco Firepower Management Center 2000

Firepower System Release Notes

Installing the Update

The update process begins. You can monitor the update's progress in the task queue (System > Monitoring >
Task Status).

Caution:

Do not use the web interface to perform any other tasks until the update completes and the

Firepower Management Center reboots. Before the update completes, the web interface may become
unavailable and the Firepower Management Center may log you out. This is expected behavior; log in again
to view the task queue. If the update is still running, do not use the web interface until the update completes.
If you encounter issues with the update (for example, if the task queue indicates that the update has failed
or if a manual refresh of the task queue shows no progress for several minutes), do not restart the update.
Instead, contact Support.

Step 9

After the update finishes, clear your browser cache and force a reload of the browser. Otherwise, the user
interface may exhibit unexpected behavior.

Step 10

Log into the Firepower Management Center.

Step 11

Review and accept the End User License Agreement (EULA). Note that you are logged out of the
appliance if you do not accept the EULA.

Step 12

Select Help > About and confirm that the software version is listed correctly: Version 6.0.1.1. Also note
the versions of the intrusion rule update and VDB on the Firepower Management Center; you will need
this information later.

Step 13

Verify that the appliances in your deployment are successfully communicating and that there are no
issues reported by the health monitor.

Step 14

If the rule update available on the Support site is newer than the rules on your Firepower Management
Center, import the newer rules. Do not auto-apply the imported rules at this time.

For information on rule updates, see the Firepower Management Center Configuration Guide.

Step 15

If the VDB available on the Support site is newer than the VDB on your Firepower Management Center,
install the latest VDB.

Installing a VDB update causes a short pause in traffic flow and processing, and may also cause a few packets to
pass uninspected. For more information, see the Firepower Management Center Configuration Guide.

Step 16

Redeploy your configurations to all managed devices.

Deployment may cause a short pause in traffic flow and processing, and may also cause a few packets to pass
uninspected. For more information, see the Firepower Management Center Configuration Guide.

Step 17

If a patch for Version 6.0.1.1 is available on the Support site, apply the latest patch as described in the
Firepower System Release Notes for that version.

Caution:

When you deploy configurations, resource demands may result in a small number of packets

dropping without inspection. Additionally, deploying some configurations requires the Snort process to
restart, which interrupts traffic inspection. Whether traffic drops during this interruption or passes without
further inspection depends on the model of the managed device and how it handles traffic. For more
information, see the Configurations that Restart the Snort Process section of the Firepower Management
Center Configuration Guide.

You must update to the latest patch to take advantage of the latest enhancements and security fixes.

Caution:

Although the configuration options for Firepower Management Center high availability appear in the

Integration page of the user interface, high availability is not supported for Firepower Management Centers
in Version 6.0.1. Do not attempt to place Firepower Management Centers into high availability.

Updating Managed Devices and Cisco ASA with FirePOWER Servicess

After you update your Firepower Management Centers to Version 6.0.1.1, use them to update the devices they
manage.