Cisco Cisco FirePOWER Appliance 7020

Version 5.3.0.3

Sourcefire 3D System Release Notes

3

Before You Begin: Important Update and Compatibility Notes

For more information, see the following sections:

Configuration and Event Backup Guidelines

Before you begin the update, Sourcefire strongly recommends that you back up 

current event and configuration data to an external location. This data is not 

backed up as part of the update process.
Use the Defense Center to back up event and configuration data for itself and the 

devices it manages. For more information on the backup and restore feature, see 

the Sourcefire 3D System User Guide.

The Defense Center purges locally stored backups from previous 

updates. To retain archived backups, store the backups externally.

Traffic Flow and Inspection During the Update

The update process (and any uninstallation of the update) reboots managed 

devices. Depending on how your devices are configured and deployed, the 

following capabilities are affected:

traffic inspection, including application awareness and control, URL filtering, 

Security Intelligence, intrusion detection and prevention, and connection 

logging 

traffic flow, including switching, routing, NAT, VPN, and related functionality

link state

Note that when you update clustered devices, the system performs the update 

one device at a time to avoid traffic interruption.

Traffic Inspection and Link State

In an inline deployment, your managed devices (depending on model) can affect 

traffic flow via application control, user control, URL filtering, Security 

Intelligence, and intrusion prevention, as well as switching, routing, NAT, and 

VPN. In a passive deployment, you can perform intrusion detection and collect 

discovery data without affecting network traffic flow. For more information on 

appliance capabilities, see the Sourcefire 3D System Installation Guide.
The following table provides details on how traffic flow, inspection, and link state 

are affected during the update, depending on your deployment. Note that