Cisco Cisco Firepower Management Center 2000

Seite von 30
 
7
FireSIGHT System Release Notes
Version 5.3.1.6
  Before You Begin: Important Update and Compatibility Notes
link state
Traffic Inspection and Link State
In an inline deployment, your ASA FirePOWER devices (depending on model) can affect traffic flow 
via application control, user control, URL filtering, Security Intelligence, and intrusion prevention. 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 FireSIGHT 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.
Audit Logging During the Update
When updating appliances that have a web interface, after the system completes its pre-update tasks and 
the streamlined update interface page appears, login attempts to the appliance are not reflected in the 
audit log until the update process is complete and the appliance reboots.
Version Requirements for Updating to Version 5.3.1.6
To update your appliances to Version 5.3.1.6, a Defense Center must be running at least Version 5.3.0.1. 
If you are running an earlier version, you can obtain updates from the Support site.
Note
This update is not supported on managed devices or Sourcefire Software for X-Series. 
The closer your appliance’s current version to the release version (Version 5.3.1.6), the less time the 
update takes.
Time and Disk Space Requirements for Updating to Version 5.3.1.6
The table below provides disk space and time guidelines for the Version 5.3.1.6 update. Note that when 
you use the Defense Center to update an ASA FirePOWER device, the Defense Center requires 
additional disk space on its 
/Volume
 partition.
Caution
Do not restart the update or reboot your appliance at any time during the update process. Cisco provides 
time estimates as a guide, but actual update times vary depending on the appliance model, deployment, 
and configuration. Note that the system may appear inactive during the pre-checks portion of the update 
and after rebooting; this is expected behavior. 
Table 1-2
Network Traffic Interruptions
Deployment
Network Traffic Interrupted?
Inline
Network traffic is blocked throughout the update.
Passive
Network traffic is not interrupted, but also is not inspected during the update.