Cisco Cisco ASA 5506H-X with FirePOWER Services Notas de publicación

Descargar
Página de 6
2
ASA for FirePOWER Services Local Management Update Notes
Updating the ASA FirePOWER Module Using Local Management
For more information, see the following sections:
Configuration and Event Backup Guidelines
Before you begin the update, Cisco strongly recommends that you delete or move any backup files that reside on your 
appliance, then back up current event and configuration data to an external location.
Use the ASA FirePOWER module user interface through ASDM to back up event and configuration data for itself and the 
devices it manages. For more information on using the backup and restore feature prior to update, see the ASA 
FirePOWER Module User Guide
, Version 5.4.1.
Note: 
The module 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 reboots the ASA FirePOWER module. Depending on how your module is 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 (on the ASA device)
link state
Traffic Inspection and Link State
In an inline deployment, your ASA FirePOWER module can affect traffic flow via application control, user control, URL 
filtering, Security Intelligence, and intrusion prevention.
Version Requirements for Updating to Version 6.0
To update to Version 6.0, an ASA FirePOWER module must be running at least Version 5.4.1 of ASA for FirePOWER 
Services. If you are running an earlier version, you can obtain updates from the Support site.
Time and Disk Space Requirements for Updating to Version 6.0
The table below provides disk space and time guidelines for the Version 6.0 update. 
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. 
If you encounter issues with the progress of your update, contact Support.