Cisco Cisco Firepower Management Center 2000

Página de 18
 
5
FireSIGHT System Release Notes
Version 5.3.1
  Before You Begin: Important Update and Compatibility Notes
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 Defense Center to back up event and configuration data. For more information on the backup 
and restore feature, see the FireSIGHT System User Guide.
Note
The Defense Center purges locally stored backups from previous updates. To retain archived backups, 
store the backups externally.
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
To update to Version 5.3.1, 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 appliances’ current version to the release version (Version 5.3.1), the less time the 
update takes.
Time and Disk Space Requirements for Updating to Version 5.3.1
The table below provides disk space and time guidelines for the Version 5.3.1 update. Note that when 
you use the Defense Center to update a managed 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. 
The reboot portion of the update includes a database check. If errors are found during the database check, 
the update requires additional time to complete. System daemons that interact with the database do not 
run during the database check and repair.