Cisco Cisco Firepower Management Center 4000

Version 5.3.0.2

Sourcefire 3D System Release Notes

Updating Your Appliances

To ensure continuity of operations, do not update paired Defense Centers at the

same time. First, complete the update procedure for the secondary Defense

Center, then update the primary Defense Center.

Installing the Update on Clustered Devices

When you install an update on clustered devices, the system performs the

update on the devices one at a time. When the update starts, the system first

applies it to the secondary device, which goes into maintenance mode until any

necessary processes restart and the device is processing traffic again. The

system then applies the update to the primary device, which follows the same

process.

Installing the Update on Stacked Devices

When you install an update on stacked devices, the system performs the updates

simultaneously. Each device resumes normal operation when the update

completes. Note that:

•

If the primary device completes the update before all of the secondary

devices, the stack operates in a limited, mixed-version state until all devices

have completed the update.

•

If the primary device completes the update after all of the secondary

devices, the stack resumes normal operation when the update completes

on the primary device.

Installing the Update on X-Series Devices

To update to Version 5.3.0.2, Sourcefire Software for X-Series must be running at

least Version 5.3.
You cannot update Sourcefire Software for X-Series running Version 4.10.x to
Version 5.3.0.2. Instead, you must uninstall the previous version and then install

Version 5.3 before updating to Version 5.3.0.2. For detailed instructions, see the

Sourcefire Software for X-Series Installation and Configuration Guide.
Updating the Sourcefire Software for X-Series reloads the affected VAPs. If your

Sourcefire Software for X-Series is deployed inline and you are using

multi-member VAP groups, Sourcefire recommends that you update the VAPs

one at a time. This allows the other VAPs in the group to inspect network traffic

while the VAP that is being updated reloads. If you are using single-VAP VAP

groups in an inline deployment, reloading the VAP causes an interruption in

network traffic. Make sure you plan the update for a maintenance window or

other time when it will have the least impact on your deployment.

After the Installation

After you perform the update on either the Defense Center or managed devices,

you must reapply device configuration and access control policies. Applying an

access control policy may cause a short pause in traffic flow and processing, and