Firepower System Release Notes, Version 6.0.1.3

Firepower System Release Notes

Version 6.0.1.3

First Published: January 12, 2017

Last Updated: June 27, 2018

These release notes are valid for Version 6.0.1.3 of the Firepower System.

Even if you are familiar with the update process, make sure you thoroughly read and understand these release notes. They describe supported platforms, new and changed features and functionality, manager-device compatibility, and known and resolved issues. They also contain detailed information on prerequisites, warnings, and specific installation and uninstallation instructions.

Tip To access the full documentation for the Firepower System, see the documentation roadmap at http://www.cisco.com/c/en/us/td/docs/security/firepower/roadmap/firepower-roadmap.html.

For more information, see the following sections:

• Supported Platforms and Compatibility
• New Features and Functionality
• Before You Begin: Important Update and Compatibility Notes
• Installing the Update
• Uninstalling the Update
• Resolved Issues
• Known Issues
• For Assistance

Supported Platforms and Compatibility

Supported platforms, minimum originating versions, and operating systems vary by version. For more information, see:

• Supported Platforms
• Management Platform-Managed Device Compatibility

New Features and Functionality

This section of the release notes summarizes the new and updated features and functionality included in Version 6.0.1.3 of the Firepower System:

• Updated Terminology
• Updated Documentation
• Features and Changed Functionality Introduced in Previous Versions

Before You Begin: Important Update and Compatibility Notes

Before you begin the update process for Version 6.0.1.3, you should familiarize yourself with the behavior of the system during the update process, as well as with any compatibility issues or required pre- or post-update configuration changes.

Caution : Cisco strongly recommends you perform the update in a maintenance window or at a time when the interruption will have the least impact on your deployment.

For more information, see the following sections:

• Configuration and Event Backup Guidelines
• Disk Performance Management and Longevity on Firepower 4100 Devices
• Traffic Flow and Inspection During the Update
• Audit Logging During the Update
• Time and Disk Space Requirements for Updating to Version 6.0.1.3
• Web Browser and Screen Resolution Compatibility in Version 6.0.1.3
• Integrated Product Compatibility in Version 6.0.1.3

Time and Disk Space Requirements for Updating to Version 6.0.1.3

The table below provides disk space and time guidelines for the Version 6.0.1.3 update. Note that when you use the Firepower Management Center to update a managed device, the Firepower Management 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.

Note: The closer your appliance’s current version to the release version (Version 6.0.1.3), the less time the update takes.

If you encounter issues with the progress of your update, contact TAC Support.

 

Table 6 Time and Disk Space Requirements

Appliance	Space on /	Space on /Volume	Space on /Volume on Manager	Time
Firepower Management Centers (the MC750, MC1500, MC3500, MC2000, and the MC4000)	110 MB	2419 MB	n/a	58 minutes
64-bit Firepower Management Centers Virtual	101 MB	2419 MB	n/a	hardware dependent
7000 Series and 8000 Series devices (the 7010, 7020, 7030, 7050, 7110, 7115, 7120, 7125, 8120, 8130, 8140, 8250, 8260, 8270, 8290, 8350, 8360, 8370, 8390, AMP7150, AMP8050, AMP8150, AMP8350, AMP8360, AMP8370, AMP8380, and the AMP8390)	125 MB	4757 MB	926 MB	55 minutes
Cisco ASA with FirePOWER Services (the ASA 5506-X, ASA 5506H-X, ASA 5506W-X, ASA 5508-X, ASA 5516-X, ASA 5512-X, ASA 5515-X, ASA 5525-X, ASA 5545-X, ASA 5555-X, ASA 5585-X-SSP-10, ASA 5585-X-SSP-20, ASA 5585-X-SSP-40, and the ASA 5585-X-SSP-60)	58 MB	3883 MB	685 MB	184 minutes
Cisco ASA with FirePOWER Services managed via ASDM (the ASA 5506-X, ASA 5506H-X, ASA 5506W-X, ASA 5508-X, ASA 5516-X, ASA 5512-X, ASA 5515-X, ASA 5525-X, ASA 5545-X, ASA 5555-X, ASA 5585-X-SSP-10, ASA 5585-X-SSP-20, ASA 5585-X-SSP-40, and the ASA 5585-X-SSP-60)	64 MB	3906 MB	685 MB	74 minutes
NGIPSv (virtual managed devices)	107 MB	1695 MB	430 MB	hardware dependent
Cisco ASA with Firepower Threat Defense (the ASA 5506-X, ASA 5506H-X, ASA 5506W-X, ASA 5508-X, ASA 5512-X, ASA 5515-X, ASA 5516-X, ASA 5525-X, ASA 5545-X, and the ASA 5555-X)	813 MB	2651 MB	473 MB	24 minutes
Firepower 4100 Series with Threat Defense (the 4110, 4120, and the 4140)	2781 MB	2781 MB	473 MB	22 minutes
Firepower 9300 Series with Threat Defense	2781 MB	2781 MB	473 MB	22 minutes
Firepower Threat Defense Virtual: VMware and Amazon Web Services (AWS)	813 MB	2651 MB	n/a	hardware dependent

Installing the Update

Before you begin the update, you must thoroughly read and understand these release notes, especially Supported Platforms and Compatibility and Before You Begin: Important Update and Compatibility Notes.

Updates can require large data transfers from the Firepower Management Center to managed devices. Before you begin, make sure your management network has sufficient bandwidth to successfully perform the transfer. See the Troubleshooting Tech Note at https://www.cisco.com/c/en/us/support/docs/security/ firepower-management-center/212043-Guidelines-for-Downloading-Data-from-the.html.

For minimum Firepower System version requirements, see Firepower Version Requirements for Updating to Version 6.0.1.3. To update your appliances, see the guidelines and procedures outlined below:

• Updating Firepower Management Centers
• Updating 7000 Series, 8000 Series, NGIPSv, and ASA FirePOWER
• Updating Firepower Threat Defense Devices

Caution : Do not reboot or shut down your appliances during the update until you see the login prompt. The system may appear inactive during the pre-checks portion of the update; this is expected behavior and does not require you to reboot or shut down your appliances.

When to Perform the Update

Because the update process may affect traffic inspection, traffic flow, and link state, Cisco strongly recommends you perform the update in a maintenance window or at a time when the interruption will have the least impact on your deployment.

Installation Method

Use the Firepower Management Center’s web interface to perform the update. Update the Firepower Management Center first, then use it to update the devices it manages.

Order of Installation

Update your Firepower Management Centers before updating the devices they manage.

Firepower Threat Defense is new for Version 6.0 of the Firepower System. For information about installing the Firepower Threat Defense image Version 6.0.1.3 on supported ASA models, see the Cisco Firepower Threat Defense Quick Start Guide

Installing the Update on Paired Firepower Management Centers

Updating Firepower Management Center in a high availability pair is not supported in Version 6.0.X. In order to update Firepower Management Centers in a high availability environment, you must break the pair and update each Firepower Management Center individually. In order to update to Version 6.0.1.3, you must break the high availability pair.

Installing the Update on High Availability Devices

When you install an update on Firepower Threat Defense devices in a high availability pair, the system updates 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 updates the primary device, which follows the same process.

When you update a Cisco ASA with FirePOWER Services high availability pair, apply the update one device at a time, allowing the update to complete before updating the second device.

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.

When you update clustered Firepower Threat Defense devices, the primary device completes the update after all of the secondary devices. You must reboot the device cluster before you deploy configuration from the Firepower Management Center.

Caution : Prior to updating a Firepower 9300 Firepower Threat Defense device to Version 6.0.1, you must update the device to FXOS 1.1.4 or later. The device will experience a disruption in traffic during the update. This is expected behavior.

After the Installation

After you perform the update on either the Firepower Management Center or managed devices, you must redeploy your configurations. For more information, see the Firepower Management Center Configuration Guide.

Caution : When you deploy configurations, resource demands may result in a small number of packets dropping without inspection. Additionally, deploying some configurations requires the Snort process to restart, which interrupts traffic inspection. Whether traffic drops during this interruption or passes without further inspection depends on how the managed device handles traffic. For more information, see the Configurations that Restart the Snort Process section of the Firepower Management Center Configuration Guide.

There are several additional post-update steps you should take to ensure that your appliances are performing properly. These include:

• verifying that the update succeeded
• making sure that all appliances in your deployment are communicating successfully
• updating to the latest patch for Version 6.0.1.3, if available, to take advantage of the latest enhancements and security fixes
• optionally, updating your intrusion rules and vulnerability database (VDB) and redeploying your configurations
• making any required configuration changes based on the information in New Features and Functionality

The next sections include detailed instructions not only on performing the update, but also on completing any post-update steps. Make sure you complete all of the listed tasks.

Updating Firepower Management Centers

Use the procedure in this section to update your Firepower Management Centers, including Firepower Management Center Virtuals. For the Version 6.0.1.3 update, Firepower Management Centers reboot.

Caution : Before you update the Firepower Management Center, redeploy your configurations to any managed devices. Otherwise, managed device updates may fail.

Caution : Do not reboot or shut down your appliances during the update until after you see the login prompt. The system may appear inactive during the pre-checks portion of the update; this is expected behavior and does not require you to reboot or shut down your appliances.

Note: Updating a Firepower Management Center to Version 6.0.1.3 removes existing uninstallers from the appliance.

To update a Firepower Management Center:

1. Read these release notes and complete any required pre-update tasks.

2. Download the update from the Support site:

• for Firepower Management Centers and Firepower Management Centers Virtual:

Sourcefire_3D_Defense_Center_S3_Patch-6.0.1.3-1053.sh

Note: Download the update directly from the Support site. If you transfer an update file by email, it may become corrupted.

3. Upload the update to the Firepower Management Center by selecting System > Updates, then clicking Upload Update on the Product Updates tab. Browse to the update and click Upload.

The update is uploaded to the Firepower Management Center. The web interface shows the type of update you uploaded, its version number, and the date and time it was generated.

4. Make sure that the appliances in your deployment are successfully communicating with the Firepower Management Center and that there are no issues reported by the health monitor.

5. Click the System Status icon, then click the Tasks tab and make sure that there are no tasks in progress.

You must wait until any long-running tasks are complete before you begin the update. After the system update completes, to reduce clutter, remove the messages for these tasks from the Message Center.

6. Select System > Updates.

The Product Updates tab appears.

7. Click the install icon next to the update you uploaded.

The Install Update page appears.

8. Select the Firepower Management Center and click Install. Confirm that you want to install the update and reboot the Firepower Management Center.

The update process begins. To view the task status, click the System Status icon, then click on the Tasks tab. After the Firepower Management Center completes its necessary pre-update checks, you are logged out. When you log back in, the Upgrade Status page appears. The Upgrade Status page displays a progress bar and provides details about the script currently running.

If the update fails for any reason, the page displays an error message indicating the time and date of the failure, which script was running when the update failed, and instructions on how to contact TAC Support. Do not restart the update.

Caution : If you encounter any other issue with the update (for example, if a manual refresh of the Update Status page shows no progress for several minutes), do not restart the update. Instead, contact TAC Support.

When the update completes, the Firepower Management Center displays a success message and reboots.

The update process begins. You can monitor the update's progress in the Tasks tab of the Firepower Message Center.

Caution : Do not use the web interface to perform any other tasks until the update completes and the Firepower Management Center reboots. Before the update completes, the web interface may become unavailable and the Firepower Management Center may log you out. This is expected behavior; log in again to view the Tasks tab. If the update is still running, do not use the web interface until the update completes. If you encounter issues with the update (for example, if the Tasks tab indicates that the update has failed or if a manual refresh of the Tasks tab shows no progress for several minutes), do not restart the update. Instead, contact TAC Support.

9. After the update finishes, clear your browser cache and force a reload of the browser. Otherwise, the user interface may exhibit unexpected behavior.

10. Log into the Firepower Management Center.

11. Review and accept the End User License Agreement (EULA). Note that you are logged out of the appliance if you do not accept the EULA.

12. Select Help > About and confirm that the software version is listed correctly: Version 6.0.1.3. Also note the versions of the intrusion rule update and VDB on the Firepower Management Center; you will need this information later.

13. Verify that the appliances in your deployment are successfully communicating with the Firepower Management Center and that there are no issues reported by the health monitor.

14. If the rule update available on the Support site is newer than the rules on your Firepower Management Center, import the newer rules. Do not auto-apply the imported rules at this time.

For information on rule updates, see the Firepower Management Center Configuration Guide.

15. If the VDB available on the Support site is newer than the VDB on your Firepower Management Center, install the latest VDB.

Installing a VDB update causes a short pause in traffic flow and processing, and may also cause a few packets to pass uninspected. For more information, see the Firepower Management Center Configuration Guide.

16. Redeploy your configurations to all managed devices.

Deployment may cause a short pause in traffic flow and processing, and may also cause a few packets to pass uninspected. For more information, see the Firepower Management Center Configuration Guide.

17. If a patch for Version 6.0.1.3 is available on the Support site, apply the latest patch as described in the Firepower System Release Notes for that version.

Caution : When you deploy configurations, resource demands may result in a small number of packets dropping without inspection. Additionally, deploying some configurations requires the Snort process to restart, which interrupts traffic inspection. Whether traffic drops during this interruption or passes without further inspection depends on how the managed device handles traffic. For more information, see the Configurations that Restart the Snort Process section of the Firepower Management Center Configuration Guide.

You must update to the latest patch to take advantage of the latest enhancements and security fixes.

---

 

Updating 7000 Series, 8000 Series, NGIPSv, and ASA FirePOWER

After you update your Firepower Management Centers to Version 6.0.1.3, use them to update the devices they manage.

You must use a Firepower Management Center running Version 6.0 to update any managed device that does not have its own web interface. For Cisco ASA with FirePOWER Services running on the ASA 5506-X, ASA 5506H-X, ASA 5506W-X, ASA 5508-X, or ASA 5516-X, you can update the module using the Firepower Management Center or connect to the ASA device and update the ASA FirePOWER module using local management via ASDM. For more information see the Cisco ASA with FirePOWER Services Local Management Release Notes.

Updating managed devices is a two-step process. First, download the update from the Support site and upload it to the managing Firepower Management Center. Next, install the software. You can update multiple devices at once, but only if they use the same update file.

When you update clustered Cisco ASA with FirePOWER Services, apply the update one device at a time, allowing the update to complete before updating the second device.

For the Version 6.0.1.3 update, all devices reboot. 7000 Series and 8000 Series devices do not perform traffic inspection, switching, routing, NAT, VPN, or related functions during the update. Firepower Threat Defense devices do not perform VPN functions. Depending on how your devices are configured and deployed, the update process may also affect traffic flow and link state. For more information, see Traffic Flow and Inspection During the Update.

Firepower Threat Defense is new for the Version 6.0 Firepower System. You can reimage your Cisco ASA with FirePOWER Services to use Firepower Threat Defense, or you can reimage Cisco ASA devices with Firepower Threat Defense to a supported ASA version. For information about installing a Version 6.0.1.3 Firepower Threat Defense image on supported ASA models, see the Cisco Firepower Threat Defense Quick Start Guide

Caution : Before you update a managed device, use its managing Firepower Management Center to redeploy your configuration to the managed device. Otherwise, the managed device update may fail.

Caution : Installing an update and deploying configurations can interrupt traffic inspection due to Snort restarts and system restarts. How these interruptions affect traffic depends on how the managed device handles traffic. For more information, see Traffic Flow and Inspection During the Update.

Caution : Do not reboot or shut down your appliances during the update until after you see the login prompt. The system may appear inactive during the pre-checks portion of the update; this is expected behavior and does not require you to reboot or shut down your appliances.

To update 7000 Series, 8000 Series, NGIPSv, or ASA FirePOWER devices with the Firepower Management Center:

1. Read these release notes and complete any required pre-update tasks.

For more information, see Before You Begin: Important Update and Compatibility Notes.

2. Update the software on the devices’ managing Firepower Management Center; see Updating Firepower Management Centers.

3. Download the update from the Support site:

• for 7000 Series and 8000 Series managed devices:

Sourcefire_3D_Device_S3_Patch-6.0.1.3-33.sh

• for NGIPSv:

Sourcefire_3D_Device_Virtual64_VMware_Patch-6.0.1.3-33.sh

• for Cisco ASA with FirePOWER Services:

Cisco_Network_Sensor_Upgrade-6.0.1.3-1053.sh

Note: Download the update directly from the Support site. If you transfer an update file by email, it may become corrupted.

4. Upload the update to the Firepower Management Center by selecting System > Updates, then clicking Upload Update on the Product Updates tab. Browse to the update and click Upload.

The update is uploaded to the Firepower Management Center. The web interface shows the type of update you uploaded, its version number, and the date and time it was generated.

5. Make sure that the appliances in your deployment are successfully communicating with the Firepower Management Center and that there are no issues reported by the health monitor.

6. Click the install icon next to the update you are installing.

The Install Update page appears.

7. Select the devices where you want to install the update.

If you are updating a stacked pair, selecting one member of the pair automatically selects the other. You must update members of a stacked pair together.

8. Click Install. Confirm that you want to install the update and reboot the devices.

9. The update process begins. Monitor the update's progress in the Firepower Management Center by clicking the System Status icon, then clicking the Tasks tab.

Managed devices may reboot twice during the update; this is expected behavior.

Caution : If you encounter issues with the update (for example, if the Message Center indicates that the update has failed, or shows no progress on the update task for several minutes), do not restart the update. Instead, contact TAC Support.

10. Select Devices > Device Management and confirm that the devices you updated have the correct software version: Version 6.0.1.3.

11. Verify that the appliances in your deployment are successfully communicating with the Firepower Management Center and that there are no issues reported by the health monitor.

12. Redeploy your configurations to all managed devices.

Deployment may cause a short pause in traffic flow and processing, and may also cause a few packets to pass uninspected. For more information, see the Firepower Management Center Configuration Guide, Version 6.0.

13. If a patch for Version 6.0.1.3 is available on the Support site, apply the latest patch as described in the release notes for that version.

Caution : When you deploy configurations, resource demands may result in a small number of packets dropping without inspection. Additionally, deploying some configurations requires the Snort process to restart, which interrupts traffic inspection. Whether traffic drops during this interruption or passes without further inspection depends on how the managed device handles traffic. For more information, see the Configurations that Restart the Snort Process section of the Firepower Management Center Configuration Guide.

Updating Firepower Threat Defense Devices

After you update your Firepower Management Centers to Version 6.0.1.3, use them to update the devices they manage. You can update ASA devices and Firepower 9300 Security Appliances running the Firepower Threat Defense preview Version 6.0.0 to Version 6.0.1.3. This procedure documents update of Firepower Threat Defense running on at least Version 6.0.0. A Firepower Management Center must be running at least Version 6.0.1.3 to update Firepower Threat Defense devices to Version 6.0.1.3. Because they do not have a web interface, you must use the Firepower Management Center to update these devices.

Updating managed devices is a two-step process. First, download the update from the Support site and upload it to the managing Firepower Management Center. Next, install the software. You can update multiple devices at once, but only if they use the same update file.

Caution : Before you update a managed device, use its managing Firepower Management Center to redeploy policies to the managed device. Otherwise, the managed device update may fail

Caution : Do not reboot or shut down your appliances during the update until after you see the login prompt.

To update your appliances, see the guidelines and procedures outlined below:

1. Read these release notes and complete any required pre-update tasks.

For more information, see Before You Begin: Important Update and Compatibility Notes.

2. Update the software on the devices’ managing Firepower Management Center; see Updating Firepower Management Centers.

3. If you are updating a Firepower 9300 Security Appliance, update the operating system to FXOS 1.1.4 or later and restart the system; for more information see the Cisco FXOS Firepower Chassis Manager Configuration Guide.

Caution : Updating the Firepower 9300 Security Appliance to FXOS 1.1.4 or later causes a disruption in traffic. This is expected.

You must update the ROMMON image on Cisco ASA with FirePOWER Services to Version 1.1.8 prior to updating toVersion 6.0.1.3. For more information about updating the ROMMON image, see Cisco ASA Series General Operations CLI Configuration Guide.

4. Download the update from the Support site:

• for Firepower Threat Defense running on the ASA 5506-X, ASA 5506H-X, ASA 5506W-X, ASA 5508-X, ASA 5512-X, ASA 5515-X, ASA 5516-X, ASA 5525-X, ASA 5545-X, ASA 5555-X, or on VMware:

Cisco_FTD_Patch-6.0.1.3-1053.sh

• for Firepower Threat Defense running on the Firepower 4100, 4200, 4130, and 4140 Security appliance:

Cisco_FTD_SSP_Patch-6.0.1.3-1053.sh

• for Firepower Threat Defense running on the Firepower 9300 Security appliance:

Cisco_FTD_SSP_Patch-6.0.1.3-1053.sh

• for Firepower Threat Defense Virtual: VMware and Amazon Web Services (AWS):

Cisco_FTD_Upgrade-6.0.1.3-1053.

5. Upload the update to the Firepower Management Center by selecting System > Updates, then clicking Upload Update on the Product Updates tab. Browse to the update and click Upload.

The update is uploaded to the Firepower Management Center. The web interface shows the type of update you uploaded, its version number, and the date and time it was generated. The page also indicates whether a reboot is required as part of the update.

6. Make sure the appliances in your deployment are successfully communicating with the Firepower Management Center and that there are no issues reported by the health monitor.

7. Click the install icon next to the update you are installing.

8. Select the devices where you want to install the update.

9. Click Install. Confirm that you want to install the update and reboot the devices.

10. The update process begins. You can monitor the update’s progress on the Tasks tab of the Message Center.

Note: Devices may reboot twice during the update; this is expected behavior.

Caution : If you encounter issues with the update (if messages in the Tasks tab of the Message Center show no progress for several minutes or indicate that the update has failed), do not restart the update. Instead, contact TAC Support.

11. Select Devices > Device Management and confirm that the devices you updated have the correct software version: 6.0.1.3.

12. Verify that the appliances in your deployment are successfully communicating with the Firepower Management Center and that there are no issues reported by the health monitor.

13. Redeploy policies to all managed devices.

Click Deploy and select all available devices, then click Deploy.

Uninstalling the Update

The following sections help you uninstall the Version 6.0.1.3 update from your appliances:

• Planning the Uninstallation
• Uninstalling the Update from a Managed Device
• Uninstalling the Update from a Virtual Managed Device
• Uninstalling the Update from a Firepower Threat Defense device
• Uninstalling the Update from a Firepower Management Center
• Uninstalling the Update from a Cisco ASA with FirePOWER Services Managed by ASDM

Planning the Uninstallation

Before you uninstall the update, you must thoroughly read and understand the following sections.

Uninstallation Method

You must uninstall updates locally. You cannot use a Firepower Management Center to uninstall the update from a managed device.

For all physical appliances and Firepower Management Centers Virtuals, uninstall the update using the local web interface. Because virtual managed devices do not have a web interface, you must use the bash shell to uninstall the update.

Order of Uninstallation

Uninstall the update in the reverse order that you installed it. That is, first uninstall the update from managed devices, then from Firepower Management Centers.

Uninstalling the Update from Clustered or Paired Appliances

Clustered devices and Firepower Management Centers in high availability pairs must run the same version of the Firepower System. Although the uninstallation process triggers an automatic failover, appliances in mismatched pairs or clusters do not share configuration information, nor do they install or uninstall updates as part of their synchronization. If you need to uninstall an update from redundant appliances, plan to perform the uninstallations in immediate succession.

To ensure continuity of operations, uninstall the update from clustered devices and paired Firepower Management Centers one at a time. First, uninstall the update from the secondary appliance. Wait until the uninstallation process completes, then immediately uninstall the update from the primary appliance.

Caution : If the uninstallation process on a clustered device or paired Firepower Management Center fails, do not restart the uninstall or change configurations on its peer. Instead, contact TAC Support.

Uninstalling the Update from Stacked Devices

All devices in a stack must run the same version of the Firepower System. Uninstalling the update from any of the stacked devices causes the devices in that stack to enter a limited, mixed-version state.

To minimize impact on your deployment, Cisco recommends that you uninstall an update from stacked devices simultaneously. The stack resumes normal operation when the uninstallation completes on all devices in the stack.

Uninstalling the Update from Devices Deployed Inline

Managed devices do not perform traffic inspection, switching, routing, or related functions while the update is being uninstalled. Depending on how your devices are configured and deployed, the uninstallation process may also affect traffic flow and link state. For more information, see Traffic Flow and Inspection During the Update.

Uninstalling the Update and Online Help

Uninstalling the Version 6.0.1.3 update does not revert the online help to its previous version. If the version of your online help does not match that of your Firepower System software, your online help may contain documentation for unavailable features and may have problems with context sensitivity and link functionality.

After the Uninstallation

After you uninstall the update, there are several steps you should take to ensure that your deployment is performing properly. These include verifying that the uninstall succeeded and that all appliances in your deployment are communicating successfully.

The next sections include detailed instructions not only on performing the uninstallation, but also on completing any post-uninstallation steps. Make sure you complete all of the listed tasks.

Uninstalling the Update from a Managed Device

The following procedure explains how to use the local web interface to uninstall the Version 6.0.1.3 update from managed devices. You cannot use a Firepower Management Center to uninstall the update from a managed device.

Uninstalling the Version 6.0.1.3 update results in a device running Version 6.0.1.2. For information on uninstalling a previous version, refer to the Firepower System Release Notes for that version.

Uninstalling the Version 6.0.1.3 update reboots the device. Managed devices do not perform traffic inspection, switching, routing, or related functions during the update. Depending on how your devices are configured and deployed, the update process may also affect traffic flow and link state. For more information, see Traffic Flow and Inspection During the Update.

To uninstall the update from a managed device:

1. Read and understand Planning the Uninstallation.

2. On the managing Firepower Management Center, make sure that the appliances in your deployment are successfully communicating and that there are no issues reported by the health monitor.

3. On the managed device, view the Tasks tab to make sure that there are no tasks in progress.

Tasks that are running when the uninstallation begins are stopped, become failed tasks, and cannot be resumed; you must manually delete them from the Tasks tab after the uninstallation completes.

4. Select System > Updates.

The Product Updates tab appears.

5. Click the install icon next to the uninstaller that matches the update you want to remove, then confirm that you want to uninstall the update and reboot the device.

The uninstallation process begins. You can monitor the uninstallation progress in the Tasks tab.

Caution : Do not use the web interface to perform any other tasks until the uninstallation has completed and the device reboots. Before the uninstallation completes, the web interface may become unavailable and the device may log you out. This is expected behavior; log in again to view the Tasks tab. If the uninstallation is still running, do not use the web interface until the uninstallation has completed. If you encounter issues with the uninstallation (for example, if the Tasks tab indicates that the update has failed or if a manual refresh of the Tasks tab shows no progress for several minutes), do not restart the uninstallation. Instead, contact TAC Support.

6. After the uninstallation finishes, clear your browser cache and force a reload of the browser. Otherwise, the user interface may exhibit unexpected behavior.

7. Log in to the device.

8. Select Help > About and confirm that the software version is listed correctly: Version 6.0.1.2.

9. Verify that the appliances in your deployment are successfully communicating with the Firepower Management Center and that there are no issues reported by the health monitor.

---

 

Uninstalling the Update from a Virtual Managed Device

The following procedure explains how to uninstall the Version 6.0.1.3 update from virtual managed devices. You cannot use a Firepower Management Center to uninstall the update from a managed device.

Uninstalling the Version 6.0.1.3 update results in a device running Version 6.0.1.2. For information on uninstalling a previous version, refer to the Firepower System Release Notes for that version.

Uninstalling the Version 6.0.1.3 update reboots the device. Virtual managed devices do not perform traffic inspection or related functions during the update. Depending on how your devices are configured and deployed, the update process may also affect traffic flow. For more information, see Traffic Flow and Inspection During the Update.

To uninstall the update from a virtual managed device:

1. Read and understand Planning the Uninstallation.

2. Log into the device as admin via SSH or through the virtual console.

3. At the CLI prompt, type expert to access the bash shell.

4. At the bash shell prompt, type sudo su -.

5. Type the admin password to continue the process with root privileges.

6. At the prompt, enter the following on a single line:

install_update.pl --detach /var/sf/updates/Sourcefire_3D_Device_Virtual64_VMware_Patch_Uninstaller-6.0.1.3-1053.sh

The uninstallation process begins.

Caution : If you encounter issues with the uninstallation, do not restart the uninstallation. Instead, contact TAC Support.

7. After the uninstallation finishes, log into the managing Firepower Management Center and select Devices > Device Management. Confirm that the device where you uninstalled the update has the correct software version: Version 6.0.1.2.

8. Verify that the appliances in your deployment are successfully communicating with the Firepower Management Center and that there are no issues reported by the health monitor.

Uninstalling the Update from a Firepower Threat Defense device

The following procedure explains how to uninstall the Version 6.0.1.3 update from Firepower Threat Defense devices managed by the Firepower Management Center. You cannot use a Firepower Management Center to uninstall the update from a managed device.

Uninstalling the Version 6.0.1.3 update results in a device running Version 6.0.1.2. For information on uninstalling a previous version, refer to the Firepower System Release Notes for that version.

Uninstalling the Version 6.0.1.3 update reboots the device. Firepower Threat Defense devices do not perform traffic inspection or related functions during the update. Depending on how your devices are configured and deployed, the update process may also affect traffic flow. For more information, see Traffic Flow and Inspection During the Update.

To uninstall the update from a Firepower Threat Defense device:

1. Read and understand Planning the Uninstallation.

2. Log into the device as admin via SSH or through the device console.

3. For Firepower 4100 Series devices and Firepower 9300 Security Appliances, type connect module <slot number> console and then connect ftd.

4. At the CLI prompt, type expert to access the bash shell.

5. At the bash shell prompt, type sudo su -.

6. Type the admin password to continue the process with root privileges.

7. At the prompt, enter the following on a single line:

install_update.pl --detach /var/sf/updates/Cisco_FTD_Patch_Uninstaller-6.0.1.3-1053.sh

The uninstallation process begins.

Caution : If you encounter issues with the uninstallation, do not restart the uninstallation. Instead, contact TAC Support.

8. After the uninstallation finishes, the device reboots.

9. Log into the managing Firepower Management Center and select Devices > Device Management. Confirm that the device where you uninstalled the update has the correct software version: Version 6.1.0.

10. Verify that the appliances in your deployment are successfully communicating with the Firepower Management Center and that there are no issues reported by the health monitor.

Uninstalling the Update from a Cisco ASA with FirePOWER Services

The following procedure explains how to uninstall the Version 6.0.1.3 update from ASA FirePOWER modules. You cannot use a Firepower Management Center to uninstall the update from a managed device.

Uninstalling the Version 6.0.1.3 update results in a device running Version 6.0.1.2. For information on uninstalling a previous version, refer to the Firepower System Release Notes for that version.

Uninstalling the Version 6.0.1.3 update reboots the device. ASA FirePOWER modules do not perform traffic inspection or related functions during the update. Depending on how your devices are configured and deployed, the update process may also affect traffic flow. For more information, see Traffic Flow and Inspection During the Update.

To uninstall the update from an ASA FirePOWER module:

1. Read and understand Planning the Uninstallation.

2. Log into the device as admin via SSH, or through the virtual console.

3. At the CLI prompt, type session sfr console.

4. At the CLI prompt, type expert to access the bash shell.

5. At the bash shell prompt, type sudo su -.

6. Type the admin password to continue the process with root privileges.

7. At the prompt, enter the following on a single line:

install_update.pl --detach /var/sf/updates/Sourcefire_3D_Device_Virtual64_VMware_Patch_Uninstaller-6.0.1.3-1053.sh

The uninstallation process begins.

Caution : If you encounter issues with the uninstallation, do not restart the uninstallation. Instead, contact TAC Support.

8. After the uninstallation finishes, log into the managing Firepower Management Center and select Devices > Device Management. Confirm that the device where you uninstalled the update has the correct software version: Version 6.0.1.2.

9. Verify that the appliances in your deployment are successfully communicating with the Firepower Management Center and that there are no issues reported by the health monitor.

Uninstalling the Update from a Firepower Management Center

Use the following procedure to uninstall the Version 6.0.1.3 update from Firepower Management Centers and virtual Firepower Management Centers. Note that the uninstallation process reboots the Firepower Management Center.

Uninstalling the Version 6.0.1.3 update results in a Firepower Management Center running Version 6.0.1.2. For information on uninstalling a previous version, refer to the Firepower System Release Notes for that version.

To uninstall the update from a Firepower Management Center:

1. Read and understand Planning the Uninstallation.

2. Make sure that the appliances in your deployment are successfully communicating and that there are no issues reported by the health monitor.

3. Monitor the Tasks tab to make sure that there are no tasks in progress.

Tasks that are running when the uninstallation begins are stopped, become failed tasks, and cannot be resumed; you must manually delete them from the Tasks tab after the uninstallation completes.

4. Select System > Updates.

The Product Updates tab appears.

5. Click the install icon next to the uninstaller that matches the update you want to remove.

The Install Update page appears.

6. Select the Firepower Management Center and click Install, then confirm that you want to uninstall the update and reboot the device.

The uninstallation process begins. You can monitor the uninstallation progress in the Tasks tab.

Caution : Do not use the web interface to perform any other tasks until the uninstallation has completed and the Firepower Management Center reboots. Before the uninstallation completes, the web interface may become unavailable and the Firepower Management Center may log you out. This is expected behavior; log in again to view the Tasks tab. If the uninstallation is still running, do not use the web interface until the uninstallation has completed. If you encounter issues with the uninstallation (for example, if the Tasks tab indicates that the update has failed or if a manual refresh of the Tasks tab shows no progress for several minutes), do not restart the uninstallation. Instead, contact TAC Support.

7. After the uninstallation finishes, clear your browser cache and force a reload of the browser. Otherwise, the user interface may exhibit unexpected behavior.

8. Log in to the Firepower Management Center.

9. Select Help > About and confirm that the software version is listed correctly: Version 6.0.1.2.

10. Verify that the appliances in your deployment are successfully communicating with the Firepower Management Center and that there are no issues reported by the health monitor.

Resolved Issues

You can view defects resolved in this release using the Cisco Bug Search Tool ( https://tools.cisco.com/bugsearch/). A Cisco account is required.

The following issues are resolved in Version 6.0.1.3:

• Security Issue Addressed a vulnerability where arbitrary HTTP header injection allowed unauthenticated, remote attackers to bypass configured rules used by snort detection, as described in CVE-2016-1463.
• Security Issue Addressed a vulnerability in the third party product Linux, as described in CVE-2016-5696. Security Issue Addressed a cross-site scripting (XSS) vulnerability, as described in CVE-2016-6395.
• Security Issue Addressed a vulnerability where large HTTP header injections allowed unauthenticated, remote attackers to bypass malware detection rules if you deployed a file policy containing file rules with the default action set to either Block Malware or Block Malware with Reset, as described in CVE-2016-6396.
• Security Issue Addressed a vulnerability where the system detected malicious files for the first time and incorrectly allowed the file to be downloaded, allowing unauthenticated, remote attackers to bypass malware detection rules if you deployed a file policy containing file rules with the default action set to Block Malware, as described in CVE-2016-6396.
• Security Issue Resolved an issue where, if you configured the Email Notification option on the Configuration page ( System > Configuration) using Authentication, the system incorrectly stored the email account password as plain text on the system.
• Resolved an issue where the Real Time Eventing page ( Monitoring >ASA FirePOWER Monitoring > Real Time Eventing) does not load in the ASDM interface window. (CSCus11216)
• Resolved an issue where, if user IP and group mappings streamed to a managed device while the mappings updated on the Firepower Management Center, the network map on the managed device did not update correctly and did not match the network map on the Firepower Management Center. (CSCux12245)
• Resolved an issue where, if you disabled the Sensitive Data Detection option in the Advanced Settings section of the Intrusion Policy page ( Policies > Intrusion > Intrusion Policy), the system incorrectly enabled the detection option every time you downloaded a new intrusion rule update. (CSCux57338)
• Resolved an issue where, if you deployed an access control policy that generated more than 32,000 rules, then added either a network address translation (NAT) policy or a VPN policy containing a static rule and reapplied, the rules became corrupted and policy apply failed. (CSCux74877)
• The system no longer generates erroneous hardware health alert events. (CSCux82417)
• Resolved an issue where, if you deployed an SSL rule with the rule action set to Decrypt - Resign and browsed decrypted websites using Chrome Version 40 or later, the browser generated alerts for the decrypted websites. (CSCuy30988)
• Resolved an issue where, if you deployed an access control policy referencing an intrusion policy and an SSL with the action set to Decrypt - Resign, the system did not generate downloadable packet information on the packet view of the Intrusion Events page ( Analysis > Intrusion > Events). (CSCuy34078)
• Resolved an issue where, if you enabled the use of a proxy that required NTLM authentication on the Firepower Management Center and created a Security Intelligence feed on the Object Management page ( Objects > Object Management), the system experienced high CPU use and may have terminated processes when it should not have. (CSCuy45966)
• Resolved an issue where, if you created an access control policy containing a category with a comma in the category name, the system generated an Error Moving Data - An internal error has occurred error message and the access control policy was not accessible. You can no longer use commas in access control policy category names. (CSCuy68147)
• Resolved an issue here, if you added a security zone on a Firepower Management Center running Version 5.4.0 or later and updated the system to Version 6.0.0 or later and deleted the security zone, the system generated an Object deletion restricted. Remove object from the following: Access control policies error even if the security zone was not referenced within a rule. (CSCuy68648)
• Resolved an issue where, if you configure inline sets to go into bypass mode on a 7000 Series or 8000 Series device running Version 5.4.0 or later and update the device to Version 5.4.0.2 or later, Version 6.0.0 or later, or Version 6.1.0 or later, the device experienced loss of link on sensing interfaces for an extended period of time after the device rebooted during the update. (CSCuy74958)
• Resolved an issue where, if you enabled URL cloud lookups and the system submitted a lookup request for a URL starting with www., and another lookup request for the same URL but without the www. prefix, the system generated an extraneous health alert message. (CSCuy86036)
• Resolved a rare issue where the SIP preprocessor was not properly enabled even if you manually enabled the preprocessor. (CSCuy89897)
• Resolved an issue where, if you enabled adaptive profiles in the Advanced tab of the access control policy editor page and repeatedly deploy configuration, the system did not prune expired information and experienced memory issues. (CSCuz03171)
• Resolved an issue where, if you create an intrusion policy layer on a system running Version 5.4.0.X and updated the system to Version 6.0.0, then shared the intrusion policy layer, the system displayed an error. (CSCuz07954)
• Resolved an issue where the system incorrectly terminated processes suspected of high memory usage on the ASA 5585-X device. (CSCuz09158)
• Resolved a rare issue where the system experienced issues after deploying a network discovery policy with user discovery enabled and generated a The data correlator process exited (x) times error message. (CSCuz15233)
• Resolved an issue where, if you executed the system support capture-traffic CLI command, the command rejected IPv6 host addresses. (CSCuz40373)
• Resolved an issue where the system incorrectly allowed you to configure sandbox file sizes larger than 10MB on the Files and Malware Settings section on the Advanced tab of the access control editor. (CSCuz46366)
• Improved captive portal's ability to process HSTS expectations. (CSCuz46662)
• Resolved an issue where, if you deployed an access control rule referencing a file policy containing a file rule with the default action set to Block Malware, the system incorrectly enabled the Block Unresolvable TCP Header Anomalies inline normalization preprocessor option. (CSCuz50295)
• Resolved an issue where, if you activated Automated Application Bypass (AAB) and deploy failed, the system experienced issues. (CSCuz52270)
• Resolved an issue where, if you moved a Firepower Threat Defense device's interface to passive mode and deployed an SSL policy set to Decrypt Known - Key, and you downloaded a file at least 100kb, the system generated an Out of memory error. (CSCuz54616)
• Resolved an issue where, if you configured Lights-out Management (LOM) with an IP address, the system did not automatically configure the authentication type and you could not access the LOM interface via the IP address. (CSCuz66344)
• Resolved an issue where, if you updated an ASA FirePOWER module managed by ASDM connected to an Active Directory (AD) server with a User Agent from Version 6.0.0 to Version 6.0.1.1 or later and deployed an access control policy containing an Identity policy referencing a realm, the system incorrectly displayed Special Identities/Unknown in the User column of the connection event viewer instead of the correct user-to-IP map. (CSCuz74313)
• The High Availability tab on the Integration page ( System > Integration) no longer displays the High Availability button. Firepower Management Center high availability is not supported in version 6.0.1.x. (CSCuz75942)
• Resolved an issue where, if you deployed a file policy with the default action set to Block Malware and attempted to download a malware file via FTP, the system did not block the download and generated an event in the Connection Events page ( Analysis > Connections > Events) even though the file was successfully downloaded. (CSCuz80431)
• Resolved an issue where, if you deployed an SSL policy with decryption enabled and the system processed SSL traffic, the system experienced issues. (CSCuz83354)
• Resolved an issue where, if you requested metadata older than Verison 6.0.0 from a Firepower Management Center running Version 6.0.0 or later via eStreamer, the system incorrectly sent the userID field to the eStreamer client instead of the configured LDAP username (CSCuz95008)
• Resolved an issue where, if you deployed a file policy with Archive Inspection enabled for ARJ compressed files enabled during the inspection of traffic containing malformed ARJ compressed files, the system experienced issues such as geolocation database and URL database update failures. (CSCuz99094)
• Resolved an issue where, if you deployed a rule set with application or URL conditions, the system logged an incorrect access control rule for short sessions that were not identified as a known application. (CSCva07265)
• Resolved an issue where you could not view or edit NAT rules listed on any page other than page one of the NAT Configuration page ( Devices > NAT) of a registered Firepower Threat Defense device. (CSCva09395)
• Resolved an issue where generating troubleshoot on a Firepower Management Center managing more than 500 devices incorrectly processed standard output data and generated an Out of memory! error message. (CSCva12919)
• Resolved an issue where, if a link for stacked 7000 Series or 8000 Series devices dropped, the system took up to 30 seconds to acknowledge the down link. (CSCva13792)
• Resolved an issue where, in some cases, 7000 Series or 8000 Series devices configured with static routes experienced issues and used 100% of the CPU. (CSCva15195)
• Resolved an issue where, if you deployed an access control rule with the default action set to Block with reset, Interactive block, or Interactive Block with reset to a 7000 Series or 8000 Series device configured with inline tap mode enabled, the system incorrectly blocked the website and reset the webpage or generated a response page when it should not have. (CSCva17019)
• Resolved an issue where Firepower Management Center did not send events to external clients via eStreamer if some of the events contained information about SSL certificates. (CSCva27436)
• Resolved an issue where, if you applied the Microsoft updates KB3161606 or KB3172614 to a system running either Windows 8.1 and Windows Server 2012 R2 or Microsoft updates KB3161608 or KB3172605 to a system running Windows 7 SP and Windows Server 2008 R2 SP1, then used a certificate to connect to a User Agent server via TLS, the User Agent failed to complete any SSL connections to the Firepower Management Center. (CSCva32331)
• Resolved an issue where, if the eStreamer running on a Firepower Management Center experienced issues sending events to devices, managed devices did not correctly map detected users to a valid IP address and traffic did not match the appropriate access control rule. (CSCva32408)
• Resolved an issue where, if you updated the vulnerability database (VDB) on a system with host discovery enabled, network map memory usage could become excessive and cause system stability issues. (CSCva32511)
• Resolved an issue where, if you imported a system backup and checked Events, the system did not restore event tables when it should have. (CSCva40177)
• Version 6.0.13 and later now supports a maximum MTU field of 9206 bytes. (CSCva40664)
• Improved SSL inspection processes. (CSCva42950)
• Resolved an issue where, if you deployed a NAT policy to a Firepower Threat Defense Virtual device on Amazon Web Services (AWS) and then disabled the deployed NAT policy, the system did not disable the policy and generated an error message. (CSCva45597)
• Resolved an issue where, if you created a syslog alert response for intrusion or connection events, the system did not generate the required alerts and generated a health alert message reporting the events alerter process was not running. (CSCva48946)
• Resolved an issue where the system did not deploy the correct Regular Expression Limits default values within the access control policy when you deployed configuration. (CSCva54597)
• Resolved an issue where, if you added a static route to an Firepower Threat Defense device via the Device Management page ( Devices > Device Management) and added an IPv6 object with a fe80::/10 range, the system incorrectly generated a Device Configuration error message. (CSCva67810)
• Resolved an issue where, if you deployed an SSL policy containing an SSL rule with the default action set to Do Not Decrypt and the ServerHello message contained more than 14480 bytes, the system incorrectly dropped traffic that matched the rule set to Do Not Decrypt and the session failed. (CSCva78403)
• Resolved an issue where excessively generated logs triggered Automatic Application Bypass (AAB) and caused latency in both traffic detection and network performance. (CSCva81825)
• Resolved an issue where, if you deployed an access control policy containing an SSL policy with the default action set to Decrypt - Resign and a file policy with the default action set to either Block or Block with reset for PDF file types, the system did not block FTPS traffic containing PDFs when it should have. (CSCva84390)
• Resolved an issue where, if you updated a system running Version 6.0.0 or later to Version 6.0.1.2, the update stalled. (CSCva91598)
• Resolved an issue where, if you updated the system from Version 6.0.1 to Version 6.0.1.2 or later, the Firepower Management Center user interface did not load. (CSCva96344)
• Resolved an issue where, if you edited latency-based performance setting values on the Advanced tab of the access control policy editor page and deployed to a registered Firepower Threat Defense device, the system did not save the correct latency rule values. (CSCvb11320)
• Resolved an issue where, if you created a network discovery policy configured to detect hosts and a correlation policy containing a rule set to trigger if a discovery event occurs, and the OS information for a host has changed, then you added both a condition to detect an unknown OS name and a remediation Nmap scan, discovery events matching this rule did not generate corresponding Nmap scans. (CSCvb11642)
• Resolved an issue where, if you configured captive portal active authentication with SSL decryption enabled, the system experienced issues. (CSCvb14386)
• Resolved an issue where upgrading Firepower Threat Defense devices in a high availability configuration from Version 6.0.1.2 or later to Version 6.1.0 failed. (CSCvb18197)
• Resolved an issue where, if you updated the system to Version 6.1.0 or later, the Classic Licenses page ( System > Licenses > Classic Licenses) did not correctly display all the licenses. (CSCvb22481)
• Resolved an issue where Firepower devices issued extraneous health events. (CSCvb24405)
• Resolved an issue where, if you created a realm for Active Directory (AD) and Download users and groups, then added a user from the downloaded group to an access control policy and deployed to an ASA FirePOWER module, the system did not block the user when it should. (CSCvb26230)
• Resolved an issue where, if you enabled captive portal authentication on a device configured with routed subinterfaces, an external user could access the Firepower Management Center interface via the IP address of port 443 or the IP address of port 22 via SSH. (CSCvb32918)
• Resolved an issue where detecting HTTP traffic caused memory issues. (CSCvb47111)
• Improved general memory usage and reduced latency when processing high volumes of traffic against access control policies configured with URL filter conditions and user groups. (CSCvb50368)
• Improved logging performance for Firepower 4100 series devices and Firepower 9300 series devices. (CSCvb57755)
• Improved memory use when deploying configuration. (CSCvb69483)
• Resolved an issue where, if a Firepower 8350 device or AMP8350 device produced an unusually large stream of messages on the serial port console or, if you enabled it, the Lights-out Management (LOM) console, the device became unresponsive. (CSCvc26880)

Version 6.0.1.2:

• Security Issue Resolved an issue where, if you created a realm, and a User Download task completes while not viewing a realm page, the system logged the realm's domain password in plaintext.
• Security Issue Resolved an issue where, if you clicked Generate Troubleshooting Files and selected All Data or System Configuration, Policy and Logs, the generated troubleshoot files included sensitive data.
• Resolved an issue, if you deployed a network discovery policy and enabled host discovery, the system incorrectly detected hosts from networks not defined in the network discovery policy. (CSCuw51866)
• Resolved a rare issue where clustered 7000 Series and 8000 Series devices experienced memory issues during a failover. (CSCuw73767)
• Resolved an issue where, if you created a DNS policy and clicked the Copy icon, the Copying Policy pop-up did not go away once the system successfully copied the policy. (CSCuw88707)
• (CSCuw99834)
• Resolved an issue where the Intrusion Events page ( Analysis > Intrusion > Intrusion Events) did not display the correct source IP address or the correct destination IP address.(CSCux00385)
• Resolved an issue where, if you added or removed a user from a group while in an Active Directory session via an ASA FirePOWER module managed by ASDM and click Download users, the device managed by ASDM did not update the map of users and traffic did not match against users included in the group-based access. (CSCux12513)
• Resolved an issue where, if you configured the Firepower Management Center timezone to something other than UTC and generated a PDF report, the report creation time in the header or footer of the generated PDF incorrectly displayed UTC time instead of the configured timezone. (CSCux16540)
• Resolved an issue where, if you modified the Active Directory configuration and changed the name of the default NETBIOS name, user identification processes failed. (CSCux39125)
• Improved the speed of the update process if you update the system, revert the system to a previous version and then update the system again. (CSCux98291)
• Resolved an issue where, if you enabled Write changes in Intrusion Policy to the audit log on the Intrusion Policy Preferences page ( System > Configuration > Intrusion Policy Preferences) prior to updating a Firepower Management Center. (CSCuy00310)
• Resolved an issue where, if you deployed an access control policy containing a user group within a realm and the system submitted a high volume of URL lookups, network mapping dropped messages related to some users and did not match against deployed access control rules when it should. (CSCuy15844)
• Resolved an issue where, if you configured captive portal settings on the Active Authentication tab of the Identity Policy page ( Policies > Access Control > Identity) and assigned a VLAN tag as the Port type, navigating to the captive portal caused the system to drop all traffic. (CSCuy17900)
• Resolved an issue where, if you selected a host with no IP address in the Table View of Hosts page ( Analysis > Hosts > Hosts) and clicked the Delete icon, the system did not delete the host even though the web interface reported that deletion as successful. (CSCuy18649)
• Resolved an issue where, if you deployed an access control policy containing a file policy set to Block Malware and an SSL policy set to Decrypt -Known key, the system did not successfully complete the initial file transfer for incoming traffic when it should have. (CSCuy22114)
• Resolved an issue where, if you deployed a VPN on a7000 Series or 8000 Series device where the VPN monitor generated health alerts in the Health tab of the Message Center, then you deleted the VPN, the system continued to generate health alerts for the VPN even though the configuration was deleted. (CSCuy25356)
• Resolved an issue where, if you added the same SHA list to a file list in the Object Management page ( Objects > Object Management) twice from two different domains, the system generated a unable to add SHA list warning and adding the SHA list to the file list the second time failed. (CSCuy34083)
• Resolved an issue where you could not edit the HOME_NET variable in the Variable section of the Object Management page ( Objects > Object Management), then edit the EXTERNAL_NET variable to exclude the modified HOME_NET variable and save. (CSCuy34504)
• Resolved an issue where, if you attempted to log into a 7000 Series or 8000 Series device with CAC credentials, the Continue button did not work. (CSCuy39002)
• Improved the general stability of SSL processing after a policy reload. (CSCuy39348)
• Resolved an issue where, if you removed a user from all groups within a realm referenced in the access control policy and deployed configuration changes, then clicked Download users and groups from the Access Control tab, the system did not update the deployed configuration and continued to process traffic as if the group(s) still contained the user. (CSCuy39685)
• Resolved an issue where changes in how client applications were represented in iOS traffic caused issues in how eStreamer handled events for the traffic. (CSCuy40292)
• Resolved an issue where, if the system experienced a failover, the rate of transferring HTTP traffic slowed down. (CSCuy47595)
• Resolved an issue where, if you enabled the user of a proxy on the Firepower Management Center and submitted captured files to the Cisco cloud for dynamic analysis, the system generated a Dynamic Analysis Failed (Network Issue) error and did not successfully submit the files for analysis. (CSCuy49613)
• Resolved an issue where, if you deployed an intrusion rule containing an AppID web application condition and the system detected an HTTP session followed by an FTP session, the system incorrectly categorized the FTP session as an HTTP session. (CSCuy49662)
• Improved memory performance related to DNS traffic. (CSCuy61616)
• Resolved an issue where, if you configured Open Shortest Path First (OSPF) in the Dynamic Routing tab of the Virtual router page ( Devices > Devices Management > Virtual routers > Dynamic Routing) of an ASA FirePOWER module, the OSPF incorrectly reported all interfaces as available even if they were not. (CSCuy64096)
• Resolved an issue where the system did not clear disk usage health alerts on Firepower 9300 appliances and Firepower 4100 appliances. (CSCuy79810)
• The system now assigns categories for URL lookups with an unknown URL on ASA FirePOWER devices managed by ASDM when you enable both Enable URL Filtering and Query Cloud for Unknown URLs on the Cloud Services page ( Configuration > ASA FirePOWER Configuration > Local > Configuration > Cloud Service). (CSCuy79984)
• Improved Trust rule performance on Firepower Threat Defense devices. (CSCuy81530)
• Resolved an issue where, in some cases, the context explorer page ( Analysis > Context Explorer) did not load all the data. (CSCuy83009)
• Resolved an issue where, if you deployed an access control rule containing applications detected by NMAP scan, the system would not be able to find a detector for the applications, and redeploying the access control policy containing the rule with the risk application generated a Policy has rules with missing detectors. The following rules specify applications for which a detector is not defined error. (CSCuy87939)
• Resolved an issue where, if managed devices did not receive complete user or group mappings from Firepower Management Center, the system did not execute the access control rules containing the missing users or groups. (CSCuy91826)
• Resolved an issue where, if you performed an intrusion rule update on an ASA5500-X series device running at least Version 5.4.1.6 registered to a Firepower Management Center running at least Version 6.0 and then switched the ASA FirePOWER management to ASDM and deployed configuration, the ASDM web interface generated a Access Control Policy apply failed (Not a HASH reference) error. (CSCuy92630)
• Resolved an issue where, if you deployed a network analysis policy set to Maximum Detection or if you enabled the decompress_swf { lzma deflate } or decompress_pdf { deflate } keywords in the HTTP Preprocessor settings and deployed, deploying on a registered Firepower Threat Defense device failed. (CSCuy93165)
• Resolved an issue where, if you attempted to delete a deployed intrusion rule via the /usr/local/sf/bin/delete_rules.pl --prune -n local SSH command and redeployed configuration, the Firepower Management Center did not remove the deleted intrusion rule when it should have. (CSCuy94809)
• Resolved an issue where, if you updated a 7000 Series device, 8000 Series device, or ASA FirePOWER module to Version 5.4.0.5 or later, the update failed even though the Firepower Management Center displayed the update successful. (CSCuy94873)
• Resolved an issue where, if you used custom eStreamer clients to stream event data, the system experienced high CPU usage. (CSCuy95836)
• Resolved an issue where, if you deployed an access control policy containing a security intelligence object and enabled logging to system log, the system did not log events to the syslog when it should. (CSCuy97827)
• Resolved an issue where, if you configured the default time zone on the Time Zone Preference tab of the User Preferences page ( User > User Preferences) to Australia time on a Firepower Management Center with a registered Firepower Threat Defense device, deploying to the Firepower Threat Defense device failed. (CSCuz00284)
• Resolved an issue where, if you registered multiple devices to a Firepower Management Center, deploying an intrusion policy randomly failed on one of the registered devices. (CSCuz01826)
• Improved Firepower Management Center application reports. (CSCuz04049)
• Resolved an issue where, if you deployed a file rule with Archive Inspection enabled, the system stored an excessive amount of data to syslog when it should not have. (CSCuz13082)
• Resolved an issue where, if you deployed an SSL policy to a device managed by an Firepower Management Center running Version 6.0.0 and updated the Firepower Management Center to Version 6.0.1.1, then redeployed configuration and the system experienced a high volume of traffic, the system experienced a disruption in traffic. (CSCuz19469)
• Resolved an issue where, if you had a large number of intrusion policies and each policy contained more than one layer, the intrusion rule update failed. (CSCuz25692)
• Resolved an issue where the system did not block HTTPS traffic containing URLs blacklisted in Security Intelligence lists or feeds. (CSCuz50842)
• Resolved an issue where, if you deployed an SSL policy set to Decrypt-Resign and the system immediately restarted, the system experienced issues. (CSCuz79056)
• Resolved an issue where, if the system generated too many events from SNMP alerts or syslog notifications, the system experienced issues and high memory usage. (CSCva20698)
• Resolved an issue where memory issues on stacked 8000 Series devices caused processes to terminate. (CSCva39997)
• Resolved an issue where, if you created alerts configured for a specific domain and deploy, then delete the domain without deleting or modifying the alerts, the network map experienced issues. (CSCva58259)

Version 6.0.1.1:

• Security Issue Addressed a Cisco Firepower System software static credential vulnerability, as described in CVE-2016-1394.
• Improved the reliability of intrusion performance reporting. (CSCuv35007)
• Resolved an issue where a 7000 Series or 8000 Series device in high availability environment configured with a virtual switch as an endpoint dropped communication if the high availability pair experienced a failover and the secondary device became the primary device. (CSCux11121)
• Resolved an issue where, if you configured Cisco Redundancy Protocol (SFRP) via an IPv6 address on a 7000 Series or 8000 Series high availability pair with routed or hybrid interfaces, and the system experienced a fail-over, the system incorrectly handled sessions shared between the high availability pair members. (CSCux73498)
• Resolved an issue where deployment failed if you unregistered an ASA FirePOWER module from a Firepower Management Center and switched the device to an ASA FirePOWER device managed by ASDM, then attempted to save the access control policy containing web application conditions. (CSCux80311)
• Improved the general stability of deploying access control policies. (CSCux91984)
• Resolved an issue where, if you created an access control rule containing the Uncategorized URL category in the Category tab, the rule matched against any URL condition rather than the configured Uncategorized URL category. (CSCux94309)
• Resolved an issue where, if you created an access control policy on a system running Version 6.0. or earlier and updated the system to Version 6.0.1 or later, then edited the access control policy, the system did not save the modifications. (CSCuy04151)
• Improved general tunnel decoding in routed environments. (CSCuy15661)
• Resolved an issue where, if you deployed an SSL policy with the action set to Block or Block with reset to a Cisco ASA with FirePOWER Services device (ASA 5512-X, ASA 5515-X, ASA 5525-X, ASA 5545-X,ASA 5555-X, ASA 5585-X-SSP-10, ASA 5585-X-SSP-20, ASA 5585-X-SSP-40, or ASA 5585-X-SSP-60), traffic matching the SSL rule caused system issues. (CSCuy31908)
• Resolved a rare issue where, if you enabled Inspect HTTP Responses as a server-level HTTP normalization option, the system did not detect files containing 16,000 or more non-printable characters. (CSCuy43267, CSCuy43369)
• Improved the ability to add additional network interfaces to an NGIPSv device. (CSCuy45603)
• Improved general stability when deploying configuration. (CSCuy52294)
• Improved the stability of event processing while deleting a domain. (CSCuy60808)
• Resolved an issue where the system did not consistently block traffic that were SPDY-enabled. (CSCuy65157)
• Improved general performance of network mapping. (CSCuy83259)
• Resolved an issue where the configuration options for Firepower Management Center high availability appeared in the Integration page of the user interface even though high availability is not supported for Firepower Management Centers. (CSCuy96369)
• Resolved an issue where, if you deployed access control rules to a managed device configured with a security zone, the system incorrectly deployed the access control rules out of order and incoming traffic triggered rules that would not have triggered in the desired configuration. (CSCuy99274)
• Resolved a rare issue where, if you deployed configuration to a system with a registered 7000 Series or 8000 Series device, the system incorrectly ordered a rule configured to Block all traffic as the first rule and the device stopped processing all traffic. (CSCuz44843)

Version 6.0.1:

• Security Issue Addressed multiple vulnerability issues that generated denial of service in NTP, and other third parties as described in CVE-2015-7704, CVE-2015-7705, CVE-2015-7853, and CVE-2015-7855.(
• Security Issue Addressed multiple arbitrary script injection vulnerabilities allowing unauthenticated, remote attackers to exploit or overwrite functionality as described in CVE-2015-7703.
• Security Issue Addressed a vulnerability in the third party product NTP as described in CVE-2015-7852.
• Security Issue Addressed an arbitrary HTTP header injection vulnerability allowing unauthenticated, remote attackers to exploit managed devices as described in CVE-2016-134.
• Resolved an issue where, if you configured Open Shortest Path First (OSPF) in the Dynamic Routing tab of the Virtual router page ( Devices > Devices Management > Virtual routers > Dynamic Routing) and added an Area, then changed the value of the Cost column and deployed changes, the system did not update the OSPF. (CSCus31735)
• Improved the stability of Snort functionality. (CSCut75876)
• Resolved an issue where you could not manually set the time zone on an ASA FirePOWER module managed by ASDM. (CSCuu70250)
• Resolved an issue where, if you attempted to update the system with less than the required amount of free space, the update failed and the system incorrectly appeared to have a negative amount of space available. (CSCuv43019)
• Resolved an issue where, in some cases, registered devices generated extraneous logs and the system experienced issues. (CSCuw84304)
• Resolved an issue where, if you registered an ASA FirePOWER module (ASA 5512-X, ASA 5515-X, ASA 5525-X, ASA 5545-X, ASA 5555-X, ASA 5585-X-SSP-10, ASA 5585-X-SSP-20, ASA 5585-X-SSP-40, or ASA 5585-X-SSP-60) to a Firepower Management Center and enabled Clientless VPN tunnel group, then deployed an access control policy with the default action set to Allow all traffic, the system incorrectly dropped packets. (CSCuw38561)
• Improved inspection of encrypted FTP traffic using recently updated FTP standards. (CSCux02171)
• Resolved an issue where in some cases pinholes were not created for RTP connections established by calls using the SIP protocol, which prevented the VOIP channel creation for the SIP call. (CSCux03758)
• Improved HTTP traffic processing and reduced the chance of dropped packets when processing HTTP POST events that are large. (CSCux11773)
• Resolved an issue where, if you reboot a managed NGIPSv device and added multiple vmxnet3 interfaces, the system incorrectly added the interfaces causing preexisting interfaces to experience issues. (CSCux15018)
• Resolved an issue where disabling interface eth0 caused system issues. (CSCux22564)
• Improved Cisco Security Manager (CSM) troubleshooting. (CSCux30600)
• Resolved an issue where, if you created an access control policy referencing an SSL policy containing a network object with multiple entries on a managed Firepower appliance running Version 5.4 or later and you updated the system to Version 6.0, policy apply failed. (CSCux31618)
• Resolved an issue where, if an LDAP group containing the following special characters is explicitly included or excluded from the LDAP download, the system experienced issues and did not download any group or user: ( { ), ( } ), and ( #). (CSCux46525)
• Improved DCERPC2 preprocessing reliability in low memory conditions. (CSCux48253)
• Resolved an issue where, if you deployed a file policy with the default action set to Malware Block and the system detected SMB traffic, the system experienced issues. (CSCux49653)
• Resolved an issue where the system used an invalid format for the default name of a Distinguished Name object. (CSCux54184)
• Resolved an issue where Teredo traffic matching an IP any any pass intrusion rule or an alert intrusion rule caused dropped traffic or system issues. (CSCux55780)
• Resolved an issue where, if you edited and deployed an intrusion policy that was created in Version 5.4 or earlier, intrusion layers may have corrupted. (CSCux57697)
• Improved the stability of SSL traffic inspection. (CSCux59557)
• Resolved an issue where, if you deployed an intrusion policy and enabled Sensitive Data Detection, the system did not consistently mask content in traffic containing sensitive data. (CSCux61562)
• Improved packet reassembly for HTTP traffic. (CSCux61630)
• Resolved an issue where, if you deployed an SSL policy configured to Decrypt -Resign and attempted to download a large file on a high speed LAN, the system experienced issues. (CSCux66909)
• Improved the stability of using IPv6 IP with Cisco redundancy protocol (SFRP). (CSCux67113)
• If you update an ASA FirePOWER module managed by a Firepower Management Center to Version 6.0.0.1 and then switch to ASDM management, the system now automatically generates a default access control policy to be deployed. (CSCux69362)
• Resolved an issue where, if you deployed an SSL policy and enabled SSL decryption, the system experienced a disruption in traffic after a few hours of decrypting SSL traffic. (CSCux75036)
• Improved HTTP inspection of gzip compressed data when there is no Content-Length header present in the HTTP Response. (CSCux76518)
• Resolved an issue where, if you updated an ASA FirePOWER module managed by ASDM to Version 6.0.0.1 and switched the device to Firepower Management Center management, the Access Control Policy page ( Configuration > ASA FirePOWER Configuration > Policies > Access Control Policy) did not generate the default access control policy. (CSCux76581)
• Improved the fail-to-wire function on Firepower 7110, 7115, 7120, 7125, and 7150 devices. (CSCux84120)
• Resolved an issue where, if a device running Firepower Threat Defense remained registered to a Firepower Management Center for ten days or more, the Firepower Management Center generated errors if you attempted to register a new device, update the Firepower Management Center, create a backup, or edit a domain and you could not perform those actions. (CSCux89875)
• Resolved an issue where, if you deployed a file policy and added a SHA value to the global blacklist or global whitelist on an ASA FirePOWER module managed by ASDM, the system did not update the blacklist or whitelist to include the SHA value and did not mark the file policy as out-of-date. (CSCux91872)
• Resolved an issue where, if you deployed an access control policy containing an SSL rule, the system eventually dropped the majority of incoming traffic and caused a network outage. (CSCux95913)
• Resolved an issue where, if you deployed a network discovery policy with Applications disabled and a network analysis policy with the HTTP Inspect preprocessor enabled or a file policy, the system ran out of memory and stopped detecting traffic. (CSCux96457)
• Resolved an issue where, if a 7000 Series or 8000 Series in a high availability pair experienced a failover, the system did not correctly recover shared configurations, and the system experienced issues. (CSCuy20064)
• Improved stability of network mapping while applying domain configuration changes. (CSCuy30050)
• Resolved an issue where, if you created a 7000 Series or 8000 Series high availability pair in a leaf domain and broke the high availability pair in a global domain, the system erroneously generated a Load container -Invalid domain permission error even though the high availability successfully broke. (CSCuy30473)
• Resolved an issue where, if you deployed an access control policy referencing at least one intrusion rule in a leaf domain and then viewed the Packets view of the Intrusion Events page ( Analysis > Intrusion > Intrusion Events) in the global domain, the system did not display packet information from the leaf domain. (CSCuy30532)
• Resolved an issue where, if you deployed an SSL policy to registered NGFW device experiencing light traffic load, the system delayed packet delivery for ten seconds or more. (CSCuy52349)
• Resolved an issue where, if you created a variable set containing a group of multiple network objects the system incorrectly saved the variable set's default value as any. (CSCuy60748)

Version 6.0

The following issues were resolved in Version 6.0:

• Security Issue Addressed a cross-site request forgery (CSRF) vulnerability.
• Security Issue Addressed a vulnerability that allowed an authenticated user can access system files using path traversal.
• Security Issue Addressed multiple cross-site scripting (XSS) vulnerabilities, including those described in CVE-2015-0737, CVE-2015-4270, and CVE-2015-6353.
• Security Issue Addressed multiple cross-site scripting (XSS) and arbitrary HTML injection vulnerabilities including those described in CVE-2015-0707.
• Security Issue Addressed multiple vulnerability issues in MYSQL, DNS, NTP, and OpenSSL as described in CVE-2010-3614, CVE-2014-3569, CVE-2014-3570, CVE-2014-3572, CVE-2014-6568, CVE-2014-9293, CVE-2014-9294, CVE-2014-9295, CVE-2014-9296, CVE-2014-9297, CVE-2014-9298, CVE-2015-0205, CVE-2015-0287, CVE-2015-0292, CVE-2015-0374, CVE-2015-0381, CVE-2015-0382, CVE-2015-0385, CVE-2015-0391, CVE-2015-0409, CVE-2015-0411, CVE-2015-0432, CVE-2015-0498, CVE-2015-0505, CVE-2015-0506, CVE-2015-0507, CVE-2015-0511, CVE-2015-1798, CVE-2015-1799, CVE-2015-1499, CVE-2015-2566, CVE-2015-2567, CVE-2015-3405, CVE-2015-3676.
• Security Issue Addressed multiple vulnerability issues that generated denial of service in MYSQL, Linux, GNU C Library, NTP, XML, OpenSSL, and other third parties as described in CVE-2009-0696, CVE-2011-1155, CVE-2012-0876, CVE-2012-2807, CVE-2012-287, CVE-2012-3509, CVE-2012-3400, CVE-2012-3480, CVE-2012-5134, CVE-2013-0242, CVE-2013-1914, CVE-2013-4332, CVE-2013-4458, CVE-2014-3512, CVE-2014-3571, CVE-2014-3660, CVE-2014-6040, CVE-2014-8502, CVE-2015-0206, CVE-2015-0286, CVE-2015-0288, CVE-2015-0293, CVE-2015-1473, CVE-2015-1781, CVE-2015-1819.
• Security Issue Addressed multiple arbitrary script injection vulnerabilities allowing unauthenticated, remote attackers to exploit or overwrite functionality as described in CVE-2008-3075, CVE-2008-4101, CVE-2010-2252, CVE-2010-4494, CVE-2010-4651, CVE-2011-2716, CVE-2011-3102, CVE-2014-047, CVE-2014-4877, CVE-2014-5119, CVE-2014-7817, CVE-2015-1472, CVE-2015-6307.
• Security Issue Addressed multiple vulnerabilities in HTTP connection handling that allowed users to be redirected to malicious websites as described in CVE-2012-1033 and CVE-2015-0706.
• Security Issue Addressed multiple vulnerabilities that allowed unauthenticated, remote attacker to disclose sensitive information on an affected system, including those described in CVE-2011-1098 and CVE-2015-3153.
• Security Issue Addressed multiple vulnerabilities in SSLv3 that allowed external attacks on client connections, as described in CVE-2014-3556.
• Security Issue Addressed multiple parameter manipulation and misconfiguration vulnerabilities, including those described in CVE-2009-0025, CVE-2009-4022, and CVE-2015-0773.
• Security Issue Resolved multiple vulnerabilities where managed devices experienced microengine failure when processing traffic, including those described in CVE-2015-6307.
• Resolved an issue where, if the device did not process sufficient traffic, the system failed to generate complete performance graphs. (108348/CSCze87001)
• Resolved an issue where the intrusion performance graph incorrectly reported the minimum packets received instead of the actual number of packets received. (124331/CSCze87003)
• Resolved an issue where deploying a policy with a policy identification number greater than 4096 failed. (134385/CSCze89030)
• Resolved an issue which could have artificially limited the number of active dynamic NAT translations. (134561/CSCze87078)
• Resolved an issue where, in some cases, the front panel LCD informational screen of Firepower 7000 Series and 8000 Series devices incorrectly displayed some software errors as hardware errors. (140386/CSCze91939)
• Resolved an issue where the system did not display the number of failed login attempts. (140400/CSCze87152)
• Improved data pruning. (141894/ CSCze92576)
• Improved link state propagation responsiveness for Firepower 7000 Series and 8000 Series devices (143860/CSCze87386)
• Resolved an issue where, if you disabled an access control rule using an intrusion policy or variable set not used in any other rule and attempted to deploy the policy, deployment failed. (143872/CSCze87308)
• Improved URL filtering. (144198/CSCze94590, 144199/CSCze94758, 144685/CSCze94805)
• Resolved an issue where, if updating failed and you attempted to update again, some drives did not mount correctly during install. (144553/CSCze95696)
• Improved reporting. (145102/CSCze95656)
• Resolved an issue where the Discovery Statistics page did not include any events in the following rows of the statistics summary: Total Events, Total Events Last Hour, or Total Events Last Day. (145153/CSCze95751)
• Improved troubleshooting for Firepower 7000 Series and 8000 Series devices. (145187/CSCze95510)
• Resolved an issue where removing the URL Filtering license from your system caused a disruption in cloud connectivity. (144578/CSCze95183)
• Corrected the calculation used by the memory usage health monitor to prevent false alerts. (144593/CSCze94840)
• Resolved an issue where the passive interfaces on Firepower 7000 Series devices reported incorrect egress security zones and interfaces. (144624/CSCze95206)
• Resolved an issue where, if you edited the interface security zones on the Object Management page, the stacked device configuration appeared to be up-to-date when it wasn't. (144626/CSCze94847)
• Resolved an issue where, if you deployed to a cluster or device stack of Firepower 7000 Series or 8000 Series devices, the system only deployed to the primary device if the clustered or stacked devices contained out-of-date policies prior to latest policy apply. (144646/CSCze95167)
• Resolved an issue where, if you created an HTML report, the web browser incorrectly displayed the report as binary data.(144737/CSCze95180, 144738/CSCze95205)
• Resolved an issue where decrypted SSL sessions displayed URLs in connection logs as http:// instead of https://. (144785/CSCze95781)
• Resolved an issue where, if you created a custom network variable named identically to a default variable but with different capitalization, the system incorrectly assumed the custom variable and the default variable were the same and prevented you from deleting the custom variable. (44788/CSCze96160)
• Resolved an issue where the system treated DNS traffic as OpenVPN, QQ, and Viber traffic. (144789/CSCze96154)
• Resolved an issue where if you imported a policy that referenced a shared layer, importing the policy failed. (144946/CSCze96151)
• Improved disk space utilization. (145012/CSCze95309)
• Improved reliability of hardware acceleration in Firepower 7000 Series and 8000 Series devices. (145035/CSCze95433, 145509/CSCze95994, CSCus68624, CSCut53335, CSCut80043)
• Resolved an issue where, if you edited a local rule on the intrusion rule editor when viewing rule documentation, the system displayed the current local rule configuration for already-generated event data instead of the rule configuration that triggered it. (145118/CSCze95346)
• Resolved an issue where, if you generated an intrusion even performance graph with Last Hour set as the time range, the system incorrectly generated a blank graph. (145237/CSCze95774)
• Resolved an issue where, if you enabled remote storage and created a scheduled email alert response on your Firepower Management Center, the scheduled email alert disabled remote storage and remote storage backups failed. (145288/CSCze95993)
• Resolved an issue where, if you attempted to view the first or last event of an Indication of Compromise (IoC), the system did not locate the event. (145486/CSCze95786)
• Resolved an issue where the 40GB fiber NetMod traffic statistics incorrectly logged traffic on the wrong 40GB port. (145515/CSCze95830)
• Resolved an issue where access control rules containing web application conditions did not match against traffic if users on your network entered a URL into the address bar that was not all lowercase. (CSCur37364)
• Resolved an issue where the file trajectory page failed to load due to invalid subtypes. (CSCur38623)
• Resolved an issue where, in some cases, you were not able to retrieve URL category or URL reputation information. (CSCur38971)
• Resolved an issue where, if you did not deactivate a traffic profile before deleting it, the deleted profile continued to use resources when it should not. (CSCur48345)
• Resolved an issue where, if you created a custom workflow and attempted to open the packet view of an intrusion event, the system opened the incorrect intrusion event in the packet view. (CSCur48743)
• Resolved an issue where, in some cases, you could not edit your access control policy and the system generated an Unknown Error (9999): Couldn't get a lock on /var/tmp/.ac_lock error message. (CSCur55338)
• Resolved an issue where, if you created a scheduled task to install a new version of the vulnerability database (VDB) on a Firepower Management Center already running that version of the VDB, the system reinstalled the VDB and switched from active mode to standby mode every time the task was scheduled. (CSCur59252)
• Resolved an issue where, if you created a correlation rule to trigger when an intrusion event or connection event occurs and the condition matches an ingress security zone, egress security zone, ingress interfaces, or egress interface as the condition, the system did not recognize the rule and failed to generate events for traffic matching the rule. (CSCur59840)
• Resolved an issue on Firepower 7000 Series and 8000 Series managed devices where the system lost inline connectivity for up to 25 seconds on bypass-enabled inline sets during device reboot. (CSCur64678)
• You can now disable session termination logging to decrease disk space requirements. (CSCur73008)
• Resolved an issue where the system did not display the associated hosts if you expanded a vulnerability based on a client application from the vulnerabilities tab of the Network Map. (CSCur86191)
• Resolved an issue where, if you configured a routed interface on clustered Firepower 7000 Series or 8000 Series managed devices to both a private IP address and a Cisco Redundancy Protocol (SFRP) IP address, the system did not recognize which IP address was the primary address and did not establish an Open Shortest Path First (OSPF) connection. (CSCur86355)
• Resolved an issue where, if you changed the selected time zone in the Time Zone Preference tab on the User Preferences page, the system did not include daylight savings time. (CSCur92028)
• Resolved an issue where the system did not generate complete troubleshoot files if the system contained a large database. (CSCur97450)
• Resolved an issue where, in some cases, the host did not always display the block page if one of your access control rule actions was set to Block or Interactive Block. (CSCus06868)
• Resolved an issue where the system incorrectly duplicated the number of registered targets on the Intrusion Policy page. (CSCus08840)
• Resolved an issue where the system occasionally experienced latency during Snort restart. (CSCus11068)
• Resolved an issue where, an ASA 5512-X, ASA 5515-X, ASA 5525-X, ASA 5545-X, or ASA 5555-X device configured in monitor-only mode experienced a fail over if the device processed a high amount of traffic. (CSCus15229)
• Resolved an issue where the system did not support generating multiple report types when using Windows File Sharing (SMB) due to unsupported characters in the report name. (CSCus21871)
• Resolved an issue where, if you configured a domain name without a DNS entry, the web interface page did not load. (CSCus28155, CSCut89714)
• Resolved an issue where importing intrusion rules failed if you edited an intrusion policy. (CSCus29526)
• Resolved an issue where, if you created an SSL policy with the default actions set to Do Not Decrypt and attempted to establish a session, the system erroneously reported the session was blocked when it was not. (CSCus41127)
• Resolved an issue where, if you added a Cisco IOS remediation to your Cisco IOS Null Route instance and entered your password to log into the router, the device did not accept the password and remediation failed. (CSCus45769)
• Improved the optimization of certain event workflows. (CSCus52203)
• Resolved an issue where, if the intrusion policy had a sufficiently complex configuration, the system truncated the configuration and intrusion policy deployment failed. (CSCus53911)
• Improved memory utilization. (CSCus59008, CSCuu38535, CSCuu81679)
• Resolved an issue where, if you created an access control rule referencing a file policy with a Block Malware rule positioned after an access control rule containing a web application condition, the system did not identify malware files. (CSCus64393, CSCus6452)
• Resolved an issue where the system generated an Internal Server Error message if the password for your registered ASA FirePOWER module included an unsupported character. (CSCus68604)
• Resolved an issue where, if you configured both malware blocking and SSL decryption, you could not download files via HTTPS even if the files did not contain malware. (CSCus72505)
• Improved communication between Firepower Management Centers and managed devices. (CSCus79643)
• You can now deploy an access control policy containing both SSL policies and URL category conditions on a Firepower Management Center with a registered Firepower 7030 device. (CSCut02823)
• Resolved an issue where the system experienced latency when you deleted hosts from the network map. (CSCut02913)
• Improved pruning for correlation event tables. (CSCut02984)
• Resolved an issue where, if you created a file policy with Spero analysis and file capture enabled, the system did not capture files detected in incoming traffic. (CSCut06837)
• Resolved an issue where, if you restored a backup archive located on a Windows network file server (NFS), backup restoration failed. (CSCut08317)
• Resolved an issue where, if you deployed an access control policy referencing an SSL policy to a managed device with Inspect Local Router Traffic enabled, the system generated errors and experienced issues. (CSCut12631)
• Resolved an issue where deploying to a cluster of devices (in Version 6.0, known as high availability) caused the system to fail over when it should not. (CSCut12919)
• Resolved an issue where, if you created an access control rule configured to send connection events to an external syslog server and the rule matched an excessive amount of traffic, the managed device stopped sending events to the external syslog server. (CSCut14629)
• Resolved an issue where, if your intrusion policy layers shared identical names and you performed a system update, the system experienced issues. (CSCut16772)
• Improved network mapping generation when processing historical email and eStreamer events. (CSCut23688)
• Resolved an issue where, if you edited an access control rule with multiple URL category conditions and attempted to remove one of the conditions, the system removed only the first category condition listed. (CSCut25082)
• Resolved an issue where, in some cases, the Firepower Management Center experienced system issues and failed to load access control rules. (CSCut30047)
• Resolved an issue where, if you created a passive zone on a Firepower 8000 Series device and performed the show fastpath-rules CLI command, the system reported intrusion rules as inactive. (CSCut32479)
• Improved the reliability of backup and restore. (CSCut34456)
• The system generates a Having Inspect traffic during policy apply disabled may cause network disruptions until deployment completes warning if you deploy without enabling Inspect traffic during policy apply. (CSCut36078)
• Resolved an issue where, if you created a file policy configured to Inspect Archives, the system experienced issues and stopped processing traffic. (CSCut39253, CSCuu14892)
• Resolved an issue where, if you selected one or more cells of the Original Client IP column in the intrusion events table view to review or copy, the system generated an error and did not display the rows you selected. (CSCut41458)
• Resolved an issue where the system experienced latency and did not match traffic if you created an access control rule targeting users in an LDAP group that contains a large number of access-controlled users. (CSCut56233)
• Resolved an issue where, if you created and edited a search for generated events, then canceled it before the search started, the system redirected you to the events page related to the search with the incorrect search name. (CSCut63265)
• Improved disk manager functionality. (CSCut65740)
• Resolved an issue where the system experienced issues if the last entry in the map list was a duplicate. (CSCut65738)
• Resolved an issue where importing intrusion rule updates caused system issues. (CSCut65772)
• Resolved an issue where, in some cases, the system dropped database communication and experienced errors. (CSCut71816)
• Resolved an issue where, in some cases, deploying on a Firepower Management Center with registered Firepower 7000 Series and 8000 Series devices in a high-availability pair caused a fail over. (CSCut72278)
• Improved health alert notifications for Cloud Lookup failures. (CSCut77594)
• Resolved an issue where, if your system experienced two sequential failures, the system was placed into bypass mode even if you did not enable bypass mode. (CSCut80892)
• Resolved an issue where the message column of the Retrospective Malware Events table view did not include the old disposition or the new disposition values of a retrospective malware event. (CSCut83512)
• Resolved an issue where, if you restarted your ASA 5585-X device with a large number of subinterfaces configured without also restarting the SFR5585-X service card, the SFR5585-X service card appeared to fail. (CSCut89619)
• Resolved an issue where using the show managers CLI command on a device registered to a system with multiple interfaces configured caused the system displayed the incorrect IP address. (CSCut95947)
• Resolved an issue where, in some cases, update failure did not get caught in time. (CSCuu01055)
• Resolved an issue where, if you experienced system issues, the cloud continuously checked for a new update. (CSCuu04844)
• Resolved an issue where, if you created an access control policy with a URL category condition and the network map failed to load a complete database, the system experienced issues. (CSCuu06714)
• Resolved an issue where the vulnerability database (VDB) install took an unexpectedly long time. (CSCuu06786)
• Resolved an issue where, in some cases, your Firepower Management Center stopped receiving health events from a registered device. (CSCuu18450)
• Resolved an issue where, if you created an access control policy configured with a Block or Block with Reset action on Cisco ASA FirePOWER module running on a Firepower Threat Defense, the client did not always display the block page when it should. (CSCuu23884)
• Resolved an issue where the system experienced latency if you created a link aggregation group (LAG) on a Firepower 7000 Series or 8000 Series device when connected to a Cisco Nexus 7000 switch. (CSCuu31626)
• Resolved an issue where, if you changed your system's time zone to a UTC+ zone and added a correlation rule with at least one inactive period to a correlation policy, activating the correlation rule failed. (CSCuu37600)
• Resolved an issue where you experienced connectivity issues if you created a routed interface on your clustered Firepower 7000 Series or 8000 Series device (known as high availability in Version 6.0). (CSCuu37668)
• Resolved an issue where the Cisco Redundancy Protocol (SFRP) router advertisement value appeared to be configurable when you added or edited a routed IP address when it was not. (CSCuu37687)
• Resolved an issue where, if you enabled two or more management interfaces and web client lost connectivity to one of the interfaces, the system defaulted to an incorrect gateway IP address and you could not access the interface. (CSCuu44020)
• Resolved an issue where, if you created an access control policy with a geolocation condition, traffic that should have matched the condition did not. (CSCuu48800)
• Improved network map generation. (CSCuu53215, CSCuu94784, CSCuv72386, CSCuw06359)
• Improved load time for access control rules with manual URL conditions referenced in an access control policy. (CSCuu55853)
• Resolved an issue where Cisco ASA with FirePOWER Services (ASA 5506-X, ASA 5506H-X, ASA 5506W-X, ASA 5508-X, and ASA 5516-X) running the minimum ASA version 9.3.2.2 or later did not enforce the mpf-policy-map-class mode. (CSCuu68273)
• Resolved an issue where creating a search for an intrusion event with an original client IP using a negated subnet IP address caused the system to incorrectly exclude intrusion events with no original client IP. (CSCuu68438)
• Resolved an issue where, in rare cases, the system appeared unstable and did not recover from a reboot. (CSCuu93154)
• Resolved an issue where a drive failure on some DC4000 appliances caused RAID controller failure and data loss. (CSCuu93159)
• Improved eStreamer performance. (CSCuu94902)
• Resolved an issue where the system did not display the correct number of bytes in the Top Web Applications Seen and Top Client Applications Seen widgets on the Summary Dashboard if you viewed high-volume media such as video streaming on your web browser. (CSCuu97036)
• Resolved an issue where, if you deployed an SSL policy set to Decrypt-Resign on a managed device, the decrypted traffic that egressed from one interface set switched or routed so the traffic ingressed into a different interface set on the same managed device and the system experienced a disruption in SSL traffic. (CSCuu97712)
• Resolved an issue where the Send email check box on the Report Templates tab of the Reporting page did not stay selected and you stopped receiving reports via email if you generated a report, navigated away from the Report Templates tab, and then generated another report. (CSCuu97750, CSCuu41580, CSCuv43116)
• Resolved an issue where clicking Continue on interactive block web page did not always redirect you to the blocked web page. (CSCuu97934, CSCuu97946)
• Resolved an issue where, in some cases, updating failed. (CSCuu99337)
• Resolved an issue where the system did not acknowledge users as members of their primary LDAP groups. (CSCuv03821)
• Resolved an issue where, if you generated a connection event report and modified the Maximum Results value, the system did not save the new value and generated the report with the default value. (CSCuv06557)
• Resolved an issue where, if you configured the system to use a remote NTP server to synchronize time to a system with a managed device running a version older than Version 5.4 and you experienced a leap second, your system used a high amount of CPU. (CSCuv11738)
• Resolved an issue where, if you created an access control rule configured with an Interactive Block action and you viewed a blocked web page in a Chrome web browser, the Continue button to bypass the block page did not work. (CSCuv21748)
• Resolved an issue where generated internal CA certificates were valid for only 30 days instead of 10 years. (CSCuv29004)
• Resolved an issue where, if a host generated an Indication of Compromise (IoC) and you disabled the IoC for that host on the Host Profile page, the Indications of Compromise by Host dashboard widget incorrectly displayed the IoC when it should not. (CSCuv41376)
• Resolved an issue where, if you created an SSL policy default action set to Decrypt - Known Key or Decrypt - Resign on a 7000 Series or 8000 Series device and you choose to resume the SSL session with a different source IP address, SSL inspection failed and the connection log displayed an incorrect SSL policy default action. (CSCuv48689)
• You can now view server names and association classification through the show ntp CLI command on your Firepower Threat Defense devices. (CSCuv57818)
• Improved file detection and blocking. (CSCuv59181)
• To suppress IPv6 router advertisement messages on a Firepower Threat Defense device, clear the Enable RA check box in the Settings page ( Device > Device Management > Interfaces> IPv6 > Settings) under the device interface configuration on the Firepower Management Center. (CSCuv62594)
• Improved memory utilization for port ranges in access control rules. (CSCuv64114)
• Resolved an issue where, if you registered many devices or configured many interfaces on a managed device or created many VPN deployments, the system did not generate information for all of the devices or interfaces or VPN deployments on their respective pages. (CSCuv76287)
• Improved Health Monitor alerting. (CSCuv96121)
• Resolved an issue where merging intrusion policy layers generated errors. (CSCuw34380)
• Improved email notification reliability. (CSCuw36354)
• Resolved an issue where, in some cases, the system experienced errors caused by invalid username values. (CSCuw39725)
• Resolved an issue where, if you switched from Serial Over LAN (SOL) to Lights-out-Management (LOM) on a MC4000, or vice versa, the system’s console port did not work. (CSCuw67319)
• Resolved an issue where, if you enabled SSL debug logging via the s ystem support ssl-debug or system support debug-DAQ-NSE CLI command and your system experienced a high amount of traffic for an extended amount of time, the system experienced disk space issues. (CSCuw68004)
• Resolved an issue where, if you edited the global blacklist, the system incorrectly marked the access control policy as out-of-date. (CSCuy36653)

Known Issues

You can view known issues reported in this release using the Cisco Bug Search Tool ( https://tools.cisco.com/bugsearch/). A Cisco account is required.

The following known issues are reported in Version 6.0.1.3:

• In some cases, the detection_filter keyword may not count events in the expected manner (CSCvb22338)
• If you manually press the Reset button located on the back of the Firepower Threat Defense device (ASA 5506-X, ASA 5506H-X, ASA 5506W-X, ASA 5508-X, or ASA 5516-X), the device restarts, all interfaces go down, and you cannot configure or enable any of the interfaces. If you press the Reset button on the back of the device and the device becomes unresponsive after the restart, reimage the device. (CSCvb44254)
• If you Create Report Template from the Report Templates tab of the Reporting page ( Overview > Reporting) after deploying an SSL policy containing at least one SSL rule and Add Table View, then click Connection Events and edit the Search field, the search editor window does not close and the system incorrectly underlines the search keywords instead of generating an error message. (CSCvb60468)
• If you click the help icon next to the filter textbox, the system incorrectly generates an Error 404: Page not found error. (CSCvb73325)
• In rare cases, if you update an MC2000 with Lights-out Management (LOM) enabled to Version 6.0.1.3 and edit the admin user's password on the Users page ( Systems > Users), the system incorrectly generates an Invalid Password: invalid characters error even though the system saves the new password. (CSCvb82719)
• If you deploy a NAT rule containing a network object with the netTonet option disabled containing a static IPv6 or IPv4 address as the original source and destination IP to a Firepower Threat Defense high availability pair, then edit the network object's IP address to remove the IP prefix or modify the prefix to a value greater than 96 and redeploy, the system incorrectly generates an ERROR: unable to update object (Object Name) due to internal error message. As a workaround, delete the network object from the NAT rule and edit the network object's IP address, then add the network object as the NAT rule's original destination IP and redeploy. (CSCvb82803)
• If you create a new NAT rule, the system generates a timestamp bar at the bottom of the screen and you cannot click to view the next page of the NAT rules. If you cannot click the icon to view the next page, change the resolution of your monitor. (CSCvb90144)
• If you deploy a NAT rule containing a network object with the netTonet option disabled containing a static IPv6 or IPv4 address as the original source and destination IP to a Firepower Threat Defense high availability pair, then edit the network object's IP address to remove the IP prefix or modify the prefix to a value greater than 96 and redeploy, the system incorrectly generates an ERROR: unable to update object (Object Name) due to internal error message. As a workaround, delete the network object from the NAT rule and edit the network object's IP address, then add the network object as the NAT rule's original destination IP and deploy. (CSCvc11489)
• Clicking the magnifier icon on the Routes section of the Management Interface page ( System > Configuration > Management Interface) does not load route statistics for the management interface when it should. (CSCvc14746)
• If you deploy a file policy with archive inspection enabled to a managed device configured for local malware analysis and download a file via HTTP, then click Analyze file for a specific file from the file Network File Trajectory page ( Analysis > Files > Network File Trajectory), the system does not gray out the file composition report option for .ZIP files when it should. Local malware analysis correctly generates file composition reports for MACHO, PDF, NEW_OFFICE, MSOLE2, and MSEXE file types. (CSCvc36291)
• Devices deployed in passive mode or inline tap mode may experience issues decrypting traffic and generate NS_OUT_OF_MEMORY errors in connection events. As a workaround, depending on the device model, configure and deploy the interface as inline, routed, transparent, or switched. (CSCvc55195)
• Updating anASA FirePOWER module (ASA 5506-X) managed by ASDM from Version 6.0.1.2 to Version 6.0.1.3 may take up to one and a half hours to finish. If you need to update an ASA 5506-X device, review the time required to update in the Time and Disk Space Requirements for Updating to Version 6.0.1.3 and allocate maintenance time accordingly. (CSCvc79823)

The following known issues were reported in previous releases:

• The system allows you to select a custom context on the ASA FirePOWER Configuration page ( Configuration > ASA FirePOWER Configuration) of an ASA FirePOWER module managed by ASDM running Version 6.0.1 even though custom context is not supported on devices managed by ASDM. Cisco strongly recommends using admin context on the ASA FirePOWER Configuration page. (CSCus71713, CSCuy18360)
• You may experience latency if you use Firefox version 38.0.1 to view your Firepower Management Center's interface. As a workaround, use Firefox 41 or later or use a different web browser. (CSCuv11830)
• In some cases, if you create an access control policy when registering a device on a subdomain, the system creates the access control policy in the global domain instead of the subdomain when it should not. (CSCut56951)
• In some cases, if you edit a route map from Allow to Block on a Firepower Threat Defense device, the system does not deploy the edit to your managed devices. As a workaround, create a new route map on the Route Map page ( Objects > Object Management > Route Map) with the correct action and redeploy. (CSCuu27697)
• In some cases, if you edit the default network access policy in the advanced tab of the Access Control page ( Policies > Access Control), the system incorrectly displays the default network access policy as an intrusion policy on the deployment dialog window. (CSCuv48221)
• Online help does not open if you click the help icon on the Select Comparison page ( ASA FirePOWER Configuration > Policies > Files > Compare Policies) of an ASA FirePOWER module managed via ASDM. (CSCuw21863)
• In some cases, if you view All Events (Not Dropped) in the Intrusion Events table view page of a Firepower 7000 Series or 8000 Series device and sort the table by a maximum of six fields including Review By and Count and then generate a report, report generation fails. As a workaround, exclude either the Review By and Count field values or, if you include both the Review By and Count fields, only nor more than three additional field values when generating a report from the intrusion events page. (CSCuw29993)
• You cannot name a device group with a name that includes the plus ( + ) character even though the system generates a This field contains invalid characters. Only alphanumerics, hyphen ( -), underscore ( _), period (.), and plus ( +) are allowed message. (CSCuw44373)
• In some cases, if you edit the browser and shell timeout threshold values on the Shell Timeout page ( System > Configuration > Shell Timeout) and redeploy, the system logs out of inactive Firepower Management Centers up to one minute after the configured threshold values. (CSCuw48568)
• In some cases, editing a file list in a domain causes any file policy in that domain to be marked out-of-date. (CSCuw52764)
• The Device Management page ( Devices > Device Management) does not display device override values in the tooltip for device objects. (CSCuw53371)
• External certificates from Version 5.4.x are not supported in Version 6.0: the only curves supported in Version 6.0 are prime192v1, prime256v1, secp384r1 and secp521r1. You must update your system to Version 6.0 to obtain supported external certificates. (CSCuw54749)
• In some cases, if you create an access control policy referencing both a file policy containing a file rule configured to Detect Files and an SSL policy configured to Decrypt--Resign or Decrypt--known key on a system sending and receiving emails with Outlook 2013, the Connection Events page ( Analysis > Connections > Events) does not include email file attachments in generated events. (CSCuw65152)
• In some cases, if you refresh the tabs in the Device Management page ( Devices > Device Management) or the NAT page ( Devices > NAT) or the VPN page ( Devices > VPN), the system does not clear the cache on the page being refreshed and the Save button does not work. As a workaround, cancel any edits made to the page or tab and select the device you want to edit again. (CSCuw75367)
• In some cases, if you create an SSL policy containing a certificate with more than one status, such as expired or revoked, the Certificate Status column of the Connection Events page ( Analysis > Connections > Events) does not display a status. (CSCuw76040)
• In rare cases, if you create or edit a device interface on the Device Management page ( Devices > Devices Management), the system generates a No cache exists to discard and resume error and you cannot deploy. As a workaround, refresh the Device Management page and redeploy. (CSCuw77505)
• In some cases, if you incorrectly configure OSPFv3, RIP or Border Gateway Protocol on a device's virtual router page ( Devices > Devices Management > Virtual Router) and leave the configuration page without saving changes, the system generates a To revert back the configuration pop-up; click Yes to clean the virtual router configuration page of any edits or click No causes the system to generate the To revert back the configuration pop-up multiple times before saving the virtual router configuration page without any edits. (CSCuw78916)
• If you deploy a network discovery policy to a Firepower 9300 cluster or clustered or stacked Firepower 7000 Series or 8000 Series devices (in Version 6.0 known as a high availability pair), the system incorrectly counts all devices in the cluster or stack rather than indicating one device for the cluster or stack. (CSCuw79241, CSCuw79243)
• If you want to reimage your ASA 5506-X, ASA 5506H-X, ASA 5506W-X, ASA 5508-X, or ASA 5516-X device to Firepower Threat Defense, you must verify your ROMMON image meets the recommended version, Version 1.1.8, prior to reimaging. For more information on reimaging to Firepower Threat Defense, see the Cisco Firepower Threat Defense Quick Start Guide. (CSCuw79771)
• After initial setup on a Firepower Management Center, Firepower 7000 Series, or 8000 Series device, if you are connecting to the appliance from behind a network address translator (NAT) device, the system provides a redirect URL containing the IP address for the IP address you configured for the appliance rather than the NAT IP you are connecting to, and the session times out. As a workaround, correct the URL to use the NAT IP used to connect via web. (CSCuw79967)
• If you uninstall Version 5.4.1.3 or later to an earlier 5.4.x version and then update the system to Version 6.0, the update to Version 6.0 fails. Update your system to the latest version prior to updating your system to Version 6.0. (CSCuw81780)
• In some cases, if you do not select the required licenses for a device prior to device registration, the system generates an Initial policy deployment not started due to validation errors. For details, redeploy manually message. For more information on the correct licenses to select for your device, see the Firepower Management Center Configuration Guide. (CSCuw85743)
• If you edit a Firepower Threat Defense interface to use a static route IPV6 address for either a network or gateway IP address that has already been configured, the system allows you to do so even though the configuration is invalid. (CSCuw87053)
• When configuring OSPFv3 routing settings on a Firepower Threat Defense device, if you configure redistribution using a route map that is not used elsewhere in the device configuration, then delete the redistribution, deployment fails. As a workaround, either remove a route map first & deploy or configure use of the same route map elsewhere before deleting the OSPFv3 redistribution configuration. (CSCut87162)
• In some cases, if you deploy a NAT policy containing rules targeted to Firepower 7000 Series or 8000 Series managed devices' routed interfaces and then cluster the managed devices (known is Version 6.0 as a high-availability pair), some NAT rules continue to target a managed device's routed interface instead of changing to target a high availability interface when it should. As a workaround, edit the rule containing the individual interface, manually create a high availability interface, then redeploy. (CSCuw89223)
• The HTTP Listing page ( Device > Platform Settings > Firepower Threat Defense Platform Settings > HTTP) lists Authentication Certificate as a configurable field when it is not. (CSCuw89605)
• In some cases, the system generates events for large amounts of HTTP traffic processed by a port that is not specified in the HTTP preprocessor rule. As a workaround, add the port to the HTTP preprocessor rule with GID 119 and SID 15. (CSCuw90033)
• If you initiate deployment while backing up the Firepower Management Center, a message does not appear to indicate that the communication channel is blocked and the policy cannot deploy. Wait until backup process is complete and then deploy. (CSCuw90629)
• In some cases, if you create an access control policy that has an intrusion policy as the default action, the variable set icon next to the default action does not display properly. As a workaround, change the default action to use a different intrusion policy, which makes the icon show up, and then change your default action back to the previous intrusion policy. (CSCuw94067)
• In some cases, the Firepower Management Center's Deploy window displays an incorrect timestamp after you update the Firepower Management Center to Version 6.0 and deploy configuration changes. (CSCuw94083)
• In some cases, if you create an OSPFv3 router but do not configure a manual router-id in the Advanced Settings tab of the router page ( Devices > Device Management > Router), the system does not use unnamed IPv4 IP addresses and generates an OPSFv3 router process will not start as no router ID has been configured. Neither router ID in OSPFv3 nor IPv4 address configured in Interfaces error message. (CSCuw95485)
• If you create a correlation rule configured to match a MAC Vendor is condition, the system generates a Warning: no vendors match this string warning and does not execute the correlation rule. As a workaround, update your vulnerability database (VDB). If the VDB update does not resolve the issue, use the MAC Vendor contains condition instead of the MAC Vendor is condition. (CSCuw96022)
• The link to the Cisco Smart Software Manager from the Firepower Management Center Smart Licensing user interface page ( System > Local > System Policy) directs to an updated link, which also redirects. As a workaround, if the redirect does not occur quickly enough, connect to https://software.cisco.com/#module/SmartLicensing. (CSCuw96552)
• In some cases, deploy fails on a device running Version 5.4.0 that is registered to a Firepower Management Center running Version 6.0 if you deploy an access control policy that references a file policy configured for malware protection. (CSCuw97809)
• In some cases, if you enable sensitive data detection in the Advanced Settings on the Intrusion Policy page ( Policies > Intrusion > Intrusion Policy), then switch to another domain before saving, the system does not reload the Intrusion Policy page in the destination domain when it should. As a workaround, save or manually reload the Intrusion Policy page. (CSCuw97864)
• In some cases, if the time configured on a device running Version 6.0 is set ahead of the time configured on a Firepower Management Center, registering the managed device to the Firepower Management Center causes connectivity issues and the system may not be able to restore connectivity. As a workaround, execute the /etc/rc.d/init.d/pm restart CLI command. If you continue to experience connectivity issues, contact TAC Support. (CSCuw97948)
• The system shutdown CLI command causes Firepower Threat Defense devices (ASA 5506-X, ASA 5506H-X, ASA 5506W-X, ASA 5508-X, ASA 5516-X) to restart instead of shut down. (CSCuw98231)
• In some cases, if your user interface initiates a restore, the session will be disconnected and you must log in again to see the status of restore operation. (CSCuw98296)
• Version 6.0 does not support the Safari web browser on systems running the MAC OS. Use Firefox, Chrome, or Internet Explorer. (CSCuw98876)
• In some cases, the system takes several minutes or longer to save and update the base layer of an intrusion policy. (CSCux00181)
• In some cases, if the system hosting a virtual device experiences a high amount of traffic, deploying to the virtual device may cause temporary network issues. (CSCux00380)
• In some cases pinholes are not created for Real-time Transport Protocol (RTP) connections established by calls using the Session Initiation Protocol (SIP), which prevents the VOIP channel creation for the SIP call. (CSCux03758, CSCux09765)
• Although an application detector is available for the Skinny (SCCP) protocol, pinholes are not created for RTP connections established by SCCP packets. (CSCux05468)
• The system may experience dropped packets if you edit the access control policy to an intrusion preventative default action and deploy to registered devices configured with routed, transparent, or inline interfaces. (CSCux02726)
• If you enable the CPU Usage health monitor on the Health Policy page ( Health > Health Policy) for a Firepower Threat Defense device, the device generates transient erroneous 100% CPU load alarms during deployment. (CSCux07384)
• In some cases, if you create a Firepower Threat Defense device in transparent mode and register the device to a Firepower Management Center, then assign an IP address to an interface being used as the device's diagnostic interface, the Firepower Management Center does not successfully deploy the assigned IP address to the Firepower Threat Defense device. Cisco recommends restarting the Firepower Threat Defense device for the changes to take effect. (CSCux07416)
• In some cases, if you only edit the logical device's management interface of a Firepower 9300 device and deploy, the system does not warn you that the device must reboot to deploy changes when it should. (CSCux07831)
• In some cases, when deploying policies to a large number of devices, policy deployment times out and fails when Snort fails to restart. (CSCux07861)
• Rarely, during booting of the Firepower 9300, it may fail to initialize and become operational. When this happens the device will automatically reboot. No interaction is required, the device will become operational after the successful boot attempt. (CSCux07881)
• In some cases, if you deploy a clustered Firepower Threat Defense device and attempt to move the device from one subdomain to another subdomain, moving the device fails and the system generates an Updating Domain management changes failed error message. (CSCux08012)
• In some cases on Firepower 9300, if one of the nodes fails a health check during a deployment, the node is separated from the configured cluster and deployment to the cluster fails. Such a situation is recoverable on its own and when the node re-joins the cluster, retry deployment. (CSCux08115)
• In the Firepower 9300 Chassis Manager, you may not be able to edit the interface in the last row on the Interfaces screen. In addition, you may not be able to manually select some interfaces during logical device provisioning from the Chassis Manager. As a workaround, decrease the font size of your web browser. (CSCux08577)
• In some cases, if you create a cluster of Firepower 9300 devices on a Firepower Management Centerand configure interface IP addresses and a translated address pool through the Firepower Management Center user interface, the IP Pool configuration does not deploy to the device if you deploy immediately after configuring. As a workaround, edit the Interface and IP Pool again and redeploy. (CSCux09023)
• If you deploy a NAT policy which resides in a subdomain to a Firepower 7000 Series or 8000 Series device and move the device to new domain, deploy fails. As a workaround, create a new NAT policy in a new domain and target the correct device, then redeploy. (CSCux10651)
• In some cases, if you create a VPN deployment on a registered device and move the device from one domain to another domain, then deploy, deploy fails and the system generates a Pre-deploy Global Configuration Generation. Cannot find policy information error message. As a workaround, remove the VPN configuration prior to moving the device to another domain. An alternative workaround is to unregister and then register the device to the Firepower Management Center, then create a VPN deployment and deploy. (CSCux10820, CSCuz42235)
• In some cases, if a 7000 Series or 8000 Series high availability pair and the Firepower Management Center experiences a disruption in communication, you cannot break the high availability pair. If you cannot break a high availability pair, contact TAC Support. (CSCux18768)
• Use of a certificate with an RSASSA-PSS signature algorithm on a Firepower Management Centerr is not supported in Version 6.0. If you update a Firepower Management Center using such a certificate to Version 6.0 or add such a certificate in Version 6.0, the system does not allow you to log into the Firepower Management Center web interface and generates an Unable to authorize access. If you continue to have difficulty accessing this device, please contact the system administrator error. As a workaround, prior to update, generate and install an SSL certificate with either a sha1WithRSAEncryption or sha256WithRSAEncryption algorithm and restart the Firepower Management Center, or use the default Firepower Management Center certificate and restart the appliance. If you are unable to access the user interface on your Firepower Management Center, contact TAC Support. (CSCux30610)
• In some cases, if you enable a field in a network analysis (NAP) policy that is blank by default and enter a custom value, deploying the NAP policy fails. (CSCux32261)
• If the certificate used by your Firepower Management Center was generated using a public server key larger than 2048 bits, you will not be able to log into the Firepower Management Center web interface after updating to Version 6.0. As a workaround, replace certificates that were created with larger public keys by generating a server certificate request and then applying a certificate generated using that request to the Firepower Management Center. You can do the server certificate request and the certificate upload through the local configuration settings on the Firepower Management Center ( System > Local > Configuration > HTTPS Certificate). If you generate a certificate without using a CSR from the Firepower Management Center, use a public key of 2048 bits or less. If you generate a certificate that contains more than 2048 bits and lose access to the Firepower Management Center web interface, contact TAC Support. (CSCux35430)
• Version 6.0.1 does not support 2-byte characters in correlation policy names. If you use 2-byte characters in the name of a correlation policy and deploy, the system does not correctly apply the correlation rule. (CSCux35635)
• You are able to use non-numerical characters as IP addressed in the IPv4 or IPv6 Prefix List when you should not. If you use non-numerical characters for the Prefix List and include the Prefix List, deploy fails. (CSCux40496, CSCux40499)
• If you manage a Firepower Threat Defense Virtual (VMware or Amazon Web Services (AWS), or a Firepower Threat Defense Virtual in a high availability pair, the License page ( System > License) displays an incorrect number of licenses applied to virtual devices. (CSCux42926, CSCux78687)
• In some cases, if you deploy to a high availability device pair and switch peers, the system incorrectly marks the access control policy as out-of-date when it is not. As a workaround, switch the peers of a registered high availability pair and save, then edit the access control policy and deploy. (CSCux47354)
• In some cases, if you register an ASA FirePOWER module to the Firepower Management Center and add a production license on the Register page ( System > Licenses > Smart Licenses > Register), the system generates a Failed to parse the message sent from the server error and you cannot deploy the production license. As a workaround, select the evaluation mode license and deploy. If the system continues to experience errors after deploying the workaround, contact TAC Support. (CSCux48513)
• The system does not generate a warning to remove local users if you enable shell authentication with external authentication when it should. (CSCux52235)
• You cannot delete multiple devices registered to a subdomain while editing the Domains page ( System > Domains). As a workaround, click edit the domain page and save, then edit the domain again and delete the devices removed. (CSCux56021)
• In some cases, if the update fails while updating a Firepower Threat Defense device to Version 6.0.1 and you resume the update, the access control policy is not marked as-of-date when it should. As a workaround, edit the access control policy and save, then redeploy. (CSCux63806)
• Right-clicking an intrusion rule on the Intrusion Rules page ( Objects > Intrusion Rules) does not generate the context menu does when it should. As a workaround, right click an intrusion rule from the intrusion Edit Policy page ( Policies > Access control > Intrusion > Rules) to use the context menu. (CSCux64452)
• If you check Enable HTTP Server and Add an HTTP configuration to the HTTP section in the Platform Settings policy page ( Devices > Platform Settings) and save, the system generates a Please make sure HTTP server is enabled. Press 'Yes' to continue error regardless of whether Enable HTTP Server is checked or not. (CSCux67336)
• In some cases, if you edit a file policy, a DNS policy, an identity policy, or an intrusion policy that is referenced in an access control rule on a system running at least Version 6.0, the deploy notification window does not display the correct time when you modified or added the referenced policies. (CSCux74589)
• In some cases, if you deploy a file rule with the action set to Detect Files or Block Files to a device registered to a system running Version 5.4.0.4 or Version 6.0.1, the system may not correctly detect or block the file types, or decompress the archives correctly on the File Summary page ( Analysis > Files > Events) and the Connection Events page ( Analysis > Connections > Events). (CSCux81938, CSCux81952)
• In some cases, if the configured NTP server disconnects from the Firepower Management Center, the system incorrectly displays the NTP server as still connected. (CSCux90009)
• In some cases, if you edit and deploy an access control rule with logging enabled, then edit the same access control rule, the system incorrectly displays logging as disabled within the rule. View the Logging tab of the access control editor to review the correct logging configuration. (CSCux94318, CSCuy13079)
• The following system-provided network objects are not included in the drop-down list on the Object Management page ( Objects > Object Management): any, any-ipv4, and any-ipv6. (CSCux94621)
• If you add a routed IPv6 IP in the Devices tab of the Device Management page ( Devices > Device Management) of a Firepower Threat Defense device and enable an IPv6 Prefix without checking the Enable Router Advertisement option, then save and deploy, deployment fails and the system generates a Deployment failed due to configuration error. If problem persists after retrying, contact Cisco TAC. error. As a workaround, check the Enable Router Advertisement option and redeploy. (CSCux98850)
• In some cases, if you deploy an access control rule with the default action set to either Interactive Block or Interactive Block with Reset to a registered Firepower Threat Defense device in a high availability pair and then manually switch the active peer in the high availability pair, the interactive block page does not proceed after you click Continue. Click Continue a second time to bypass the interactive block page. (CSCux99397)
• Viewing files with the.JPEG extension in Version 6.0.1 generates a HTTP 403 Forbidden error page. You can correctly download and view files with the.jpg extension. (CSCux99481)
• In some cases, if you view the Identity Services Engine (ISE) section of the Identity Sources tab in the Integration page ( System > Integration), then upload a Firepower Management Center server certificate with the corresponding key and name the certificate, the save button does not operate. As a workaround, exit the Firepower Management Center certificate window and click the add ( +) icon, then save. (CSCux99516)
• In some cases, if you deploy a file policy with All types in selected Categories selected as the file type and enable the local analysis module, the file composition report of a detected file incorrectly displays the MD5 value as 00000000000000000000000000000000. (CSCuy01702)
• In some cases, if you attempt to simultaneously register two devices and deploy policy configurations on a Firepower Management Center, the system may generate a Pre-deploy Global Configuration Generation. _storePerms: Unable to store perms error in the Tasks tab of the Message Center. As a workaround, redeploy policies. (CSCuy02038)
• If you create an SSL policy containing one SSL rule with the action set to a Decrypt-Known Key and a second SSL rule with the action set to Decrypt-Resign a on a system running Version 6.0.1, the system incorrectly generates an erroneous Warning: this rule is preempted by rule <second rule listed> warning. (CSCuy03840)
• If you view a global domain access control rule of an access control policy in a subdomain and add or edit an access control rule in any other policy, the system incorrectly disables the logging options in the Logging tab of the rule editor window. As a workaround, refresh the page. (CSCuy03909)
• In some cases, if you edit security zones of a Cisco ASA with FirePOWER Services and attempt to deploy configuration from the Device Management page ( Devices > Device Management), the deploy window does not display any registered devices to deploy to when it should. As a workaround, redeploy the platform settings policy before deploying configuration from the Device Management page. (CSCuy05635)
• If you create an access control rule and select a port to Add to Destination in the port tab of the Add Rule window, the system does not let you select the same port and Add to Source. As a workaround, if you need to use the same port as both a destination port and a source port, Add to Source before you Add to Destination. (CSCuy08262)
• If you add a user to a new access control rule via the Users tab of the Add Rule window and edit the same access control rule to add another user from, then attempt to delete the first user in the Selected Users column, the system incorrectly removes the wrong user from the Selected Users list. As a workaround, delete required users before adding new user to the selected list. (CSCuy08275)
• The Firepower Management Center may experience a moderate delay in response time or system issues if you register and manage more than 100 devices at a time. (CSCuy12452)
• The system incorrectly allows you to configure Do not calculate SHA256 hash values for files larger than value to be smaller than the Maximum file size for dynamic analysis testing value in the File and Malware Settings section in the Advanced tab of the access control policy. To ensure the system is operating at maximum efficiency, please configure the Do not calculate SHA256 hash values for files larger than value to be smaller than the Maximum file size for dynamic analysis testing value. (CSCuy13054)
• The Device Management page ( Devices > Device Management) and the Appliance Status section of the Health Monitor page ( System > Health > Health Monitor) incorrectly displays the configured IP address as the name of a registered Firepower Threat Defense device. (CSCuy13451)
• In some cases, if you remove a whitelist or blacklist entry from the Global whitelist or Global blacklist ( Security Intelligence > Network Lists and Feeds > Global Whitelist or Global Blacklist) and save changes via the Chrome web browser, the system does not let you edit the Global whitelist or blacklist again. As a workaround, refresh the page. (CSCuy14441)
• If you edit an access control rule with the action set to Monitor, Trust, Block, or Interactive Block with Reset and deploy changes, the system erroneously generates a Selecting this action will reset the Intrusion Policy and File Policy to "None". Are you sure you want to continue? warning whether the access control policy contains an intrusion policy and a file policy or not. Close out the warning message to deploy changes. (CSCuy14455)
• If you query CISCO-MEMORY-POOL-MIB or CISCO-ENHANCED-MEMPOOL-MIB on a Cisco ASA with FirePOWER Services or Firepower Threat Defense, the ASA may experience high CPU utilization. (CSCuy14724)
• In some cases, the Firepower Management Center does not display all health events generated from registered Firepower Threat Defense devices. (CSCuy16548)
• In some cases, if you create an access control rule containing an web application condition or an application risk level and Store ASA FirePOWER changes on an ASA FirePOWER module managed by ASDM, the system generates a Policy has rules with missing detectors. The following rules specify applications for which a detector is not defined error and does not save changes. (CSCuy18141)
• In some cases, if the system continuously receives large amounts of Microsoft Active Directory user sessions and the network map experiences issues, and detected user sessions are not mapped to realms. If the system experiences issues mapping detected users to realms, contact TAC Support. (CSCuy18154)
• In some cases, you are unable to edit a recently modified Intrusion policy under the Inspection tab of the Editing Rule window ( Policies > Access Control > Access Control Rules). (CSCuy18430)
• If you deploy a custom network list to devices registered on a subdomain and then move the device to another leaf domain, deploy fails. As a workaround, use a system-provided network list prior to moving the device from a subdomain to a leaf domain. (CSCuy19978)
• The Syslog ID drop-down list of the Syslog Settings pop-up window does not list all the supported Syslog IDs if you edit the Syslog Settings page ( Devices > Platform Settings > Syslog > Syslog Setting). (CSCuy21648)
• If you edit an intrusion policy and click one of the categories listed in the Classifications section of the Rules window on the Edit Policy page ( Policies > Access Control > Intrusion), the system does not display all the relevant rules when it should. (CSCuy22305)
• In some cases, if you access the Firepower Management Center web interface via an IPv6 address with Internet Explorer version 11, the web interfaces experiences a slow response time. As a workaround, either use a different web browser or use an IPv4 address. (CSCuy22566)
• In some cases, accessing the online help page ( Help > ASA Firepower Online Help) on an ASA FirePOWER module managed by ASDM incorrectly generates an Error - 403 Forbidden You have tried to access a page that is forbidden error. (CSCuy27084)
• In some cases, if device registration to a Firepower Management Center fails, the Create new policy option on the Add Device page does not respond. As a workaround, Add Device again. (CSCuy28275)
• If you expand the SSL Policy to use for inspecting encrypted connections option under the SSL Policy Settings section of the Advanced tab on the Access Control Policy page ( Policies > Access Control) and click the help icon, the system incorrectly generates a Error 404:page not found page error. (CSCuy28935)
• If you click the help icon in the Compare Policy window of the Access Control policy page ( Configuration > ASA FirePOWER Configuration > Policies > Access Control Policy) on an ASA FirePOWER module managed by ASDM, the system does not redirect to the help page when it should. (CSCuy28937)
• If you Add URL on the URL tab of the Object Management page ( Configuration > ASA FirePOWER Configuration > Object Management) of an ASA FirePOWER module managed by ASDM and use unsupported characters in the name of the URL, the system does not generate an error message when it should. The following characters are currently supported: ( a...z), ( A...Z ), ( -) ( _ ) ( +) ( .). Note that the URL object name must start with a letter or an underscore ( _ ). (CSCuy28945)
• In some cases, if the active peer of a high availability pair of Firepower Threat Defense devices uses all available disk space and the system automatically switches the backup peer as the active peer, then you free up disk space on the backup peer and manually switch the backup peer with the active peer, the Tasks tab of the System Alerts page erroneously reports the high availability switch taking several minutes to complete. (CSCuy31838)
• The system does not alert you to click the Refresh icon on the User Download tab of the Realms editor page ( Configuration > ASA FirePOWER Configuration > Integration > Realms) if you modify the Group DN option in the Realm Configuration tab of the Realms page when it should. (CSCuy32051)
• If you create high availability pair with two Firepower Threat Defense devices and the active peer in the high availability pair does not have any settings configured on the Platform Settings page ( Devices > Platform Settings), then click Policy Assignments, the system does not display the high availability pair as an available device to deploy to. As a workaround, configure platform settings to both Firepower Threat Defense devices prior to creating the high availability pair. (CSCuy35753)
• In some cases, if you modify and deploy a rule from the packet view, the web page generates a HTTP Error 500 Internal server error page. (CSCuy36187)
• The system displays incorrect egress or ingress interface names for processed traffic in the Connection Events page ( Configuration > ASA FirePOWER Configuration > Eventing) and you cannot filter traffic by egress or ingress interface names on ASA FirePOWER managed by ASDM with multiple contexts. (CSCuy36674)
• In rare cases, deploying configuration fails and the system generates a Deployment failed in policy and object collection. If problem persists after retrying, contact Cisco TAC. error when it should not. As a workaround, redeploy configuration. (CSCuy36942)
• The State column of the Application Detectors page ( Policies > Application Detectors) does not sort the application detector table when it should. (CSCuy41052)
• The table view of the Connection Events page ( Analysis > Connections > Events) does not display values for the Initiator User column when it should. (CSCuy41300)
• In some cases, if you open the Add Neighbor window from the BGP IPV4 Routing tab of the Device Management page ( Devices > Device Management) of a registered device running Firepower Threat Defense and check the Configure Graceful Restart option, deploying to a Firepower Threat Defense high availability pair fails. As a workaround, do not enable the Configure Graceful Restart option. (CSCuy41385)
• If you check more than one event from the table view of the Reviewed Events page ( Analysis > Intrusions > Reviewed Events) and click View All, the generated packet view incorrectly displays one of the checked events instead of all the checked events. (CSCuy42838)
• In some cases, if you deploy an access control rule and set the rule action to Allow or Block a port object network condition of ICMPv6 Type 2 with codes 0-255, the system allows all network condition types even if the rule is configured to Block. (CSCuy43967)
• In some cases, if you use the Chrome web browser to access the Firepower Management Center and add either an object or a group from the Add VLAN Tag drop-down list two consecutive times or more on the VLAN Tag page ( Objects > VLAN Tag), the system does not generate the Add Object or Add Group window. If you attempt to delete an object or group from the VLAN Tag page, the system generates an An internal error occurred error. As a workaround, use either Internet Explorer or Firefox browsers. (CSCuy44276)
• In some cases, attempting to create or delete 1000 alerts generates a Authorization Failure: Invalid or expired session (code = 0) at /usr/local/sf/lib/perl/5.10.1/SF/EOHandler.pm line 3212 error. (CSCuy45377)
• In some cases, if you create a system policy and enable SNMP Version 3 under the Access List tab of the Platforms Settings page ( Devices > Platform Settings), then add a user to the SNMP window and click Save, the system generates a This policy includes access to pot 161 (snmp), but no SNMP users have been added. error and you cannot save the policy with SNMP settings. As a workaround, click either SNMP Version 1 or Version 2. If you must use SNMP Version 3, add SNMP users before selecting the SNMP version and save, then enable port access in the Access List tab of the Platforms Settings page and save. (CSCuy46080)
• If you add SNMP access to an ASA FirePOWER module managed by ASDM on the System Policy page ( Configuration > ASA FirePOWER configuration > Local > System Policy) and select Version 3 from the SNMP Version drop-down list, then Add User and expand the Authentication Protocol drop-down list, the system does not generate any options. (CSCuy46264)
• If you right click in the Networks tab of the Network Discovery page ( Policies > Network Discovery), the system incorrectly generates the context menu even if a rule is not selected. (CSCuy46940)
• In some cases, if you configure transparent inline mode or passive mode on a registered device and deploy an intrusion rule, the system does not generate VLAN tags for all traffic types in the expanded packet view of the Intrusion Events page ( Analysis > Intrusion > Events). (CSCuy47287)
• If you view the web interface via the Chrome web browser, the system may not allow you to Add Security Zon e or edit an existing security zone of a registered NGIPSv device from the Security Zone tab of the Object Management page ( Object > Object Management > Security Zone). As a workaround, reload the current page or use a different web browser. (CSCuy48328)
• If you import an internal certificate on the Object Management page ( Object > Object Management) and cancel the Import Internal Certificate Authority window before saving the certificate, then attempt to import the same internal certificate, the system generates the Import Internal Certificate Authority window but does not display any information in the window and you cannot import the certificate. (CSCuy49034)
• In some cases, the system does not display intrusion rules deployed at the Global domain in the expanded packet view of the Intrusion Events page ( Analysis > Intrusion > Events). (CSCuy49667)
• If you create a cluster of the following ASA FirePOWER Services devices, the system does not display the correct cluster icon on both the Deploy dialog window or the Device page: The ASA 5585-X-SSP-10, ASA 5585-X-SSP-20, ASA 5585-X-SSP-40, or the ASA 5585-X-SSP-60. (CSCuy51025)
• In some cases, if you create a syslog alert and the system experiences issues, the system generates extraneous health alerts about enabled detection engines. As a workaround, disable the syslog alert and deploy configurations. (CSCuy51339)
• In some cases, if you break a 7000 Series or 8000 Series high availability pair, the system keeps the high availability configuration in the deployments tab of the System Alerts screen when it should not. (CSCuy51614)
• If you check the Enable Auto Update s option in the Import Rules page ( Objects > intrusion Rules > Import Rules), the system incorrectly defaults to an invalid value. If you check Enable Auto Updates, you must manually set the auto update minutes value. (CSCuy51949)
• In rare cases, if you reconfigure multiple domains or traffic profiles and delete a domain while changes are saving, the system experiences issues. As a workaround, wait until configurations are saved and deployed before deleting a domain. (CSCuy54834)
• In some cases, leaving a Firepower Management Center Virtual connected to the Cisco cloud may cause system issues. (CSCuy56120)
• In some cases, the system stops added new hosts to the network map and the host view of the Discovery Event page ( Analysis > Hosts > Discovery Events) incorrectly displays the host limit has been reached. (CSCuy57044)
• In some cases, if you break a Firepower Threat Defense high availability pair, one of the devices in the pair stays in standalone mode and the system cannot recreate the high availability pair. (CSCuy57756)
• If you view the web interface in Japanese, the Save button on the VMware Tool page ( System > VMware Tool) is not translated when it should. (CSCuy58426)
• If you view the web interface in Japanese and click Deploy from the Policies page and view the deploy window, the Cancel button in the deploy window is not translated when it should. (CSCuy58661)
• In some cases, updating the Firepower Management Center to Version 6.0.1 via the Chrome web browser causes policy pages to load slowly. As a workaround, use either the Firefox or Internet Explorer web browsers. (CSCuy58664)
• In some cases, if registered ASA devices with Firepower Threat Defense or ASA FirePOWER modules experience bursts of high volume of traffic, device interfaces processing incoming traffic drops packets and the CPU does not appear to experience high usage. (CSCuy59642, CSCuy66405)
• If you deploy a network analysis policy with Maximum Detection selected as the base policy, the system only deploys the policy to registered ASA devices with Firepower Threat Defense. As a workaround, if you must deploy a network analysis policy with Maximum Detection selected as the base policy, click the Add A Layer option and disable the following options prior to deploying: Decompress SWF file (LZMA), Decompress SWF File (Deflate), and Decompress PDF File (Deflate). (CSCuy60390)
• The Identify as Special Identities/Guest if authentication cannot identify user check box in identity rule configuration is incorrectly named. It should be named Identify as Guest if authentication cannot identify user. (CSCuy65461)
• If you click Add Task on the Scheduling page ( Configuration > ASA FirePOWER Configuration > Tools > Scheduling) of an ASA FirePOWER module managed by ASDM and view the values displayed in the time drop-down list, the web interface incorrectly colors the values red and the values are not fully visible. (CSCuy69547)
• The Firepower Management Center cannot successfully deploy configuration to a Firepower Threat Defense high availability pair using an EtherChannel connection as the LAN failover link, and attempting to break the high availability pair may fail.(CSCuy73041)
• If you edit a device registered in a leaf domain from the Global domain while using Internet Explorer version 11, the system does not redirect you to the device edit page when it should. As a workaround, edit the device in the domain it is assigned to. (CSCuy73776)
• In some cases, if you create an access control rule and add a base policy in the Inheritance Settings window in the Security Intelligence tab of Initial Access Control Policy page ( Policies > Access Control > Access Control), then check the Inherit from base policy option, the system does not let you uncheck the Inherit from base policy option. As a workaround, remove the inherited base policy from the access control rule and save, then add the base policy in the Inheritance Settings window again. (CSCuy74319)
• If you update a Cisco ASA with FirePOWER Services to Version 6.0.1 and attempt to deploy policies via ASDM, policy deployment may fail. As a workaround, download and apply the latest SRU from the Support site or add the device to a Firepower Management Center and deploy the policy from the Firepower Management Center. (CSCuy84095)
• In some cases, the system incorrectly identifies Internet Control Message Protocol (ICMP) echo requests as SSL Client application protocol requests and blocks the ICMP echo request. As a workaround, create an access control rule set to Allow or Trust ICMP echo requests and order it before an access control rule set to Block incoming traffic, then deploy. (CSCuz06203)
• In some cases, if you create a cluster of 8250 devices running Version 6.0.1.1, the Firepower Management Center incorrectly displays a You have unapplied changes message even though there are no changes to deploy. (CSCuz48049)
• If you move a physical interface from admin context to a non-admin context on an ASA FirePOWER module device configured with multiple security contexts managed by an Firepower Management Center via CLI command, the Firepower Management Center does not update the interface list in the Interfaces tab of the Device Management page ( Devices > Devices Management) when it should. (CSCuz58989)
• In some cases, if you create multiple domains or realms with users and restart the system, the user session may not time out when it should. (CSCuz68841)
• In some cases, if you update a system from Version 6.0.0.1 to Version 6.0.1.1, initial deployment may fails. As a workaround, redeploy configuration. (CSCuz70743)
• If you create a TCP or UDP port objects in the Individual Objects page ( Object Management > Ports > Individual Objects) and edit an access control rule, then view the Ports tab of the edit window, you cannot add the new TCP or UDP port objects to the access control rule. (CSCuz76431)
• If you enable both Log at Beginning of Connection and Log at End of Connection options in the Logging tab of an access control rule applied to an ASA FirePOWER module managed by ASDM, the system incorrectly disables the selected server configured for SNMP and Syslog alerting even though the check box for the SNMP and Syslog server remain checked. (CSCuz80854)
• In some cases, if fragmented UDP packets with different VLAN tags go through the same inline set on a 7000 Series or 8000 Series device, the fragmented packets experience a 10 second delay and the system may drop traffic. (CSCva03312)
• If you uninstall Version 6.0.1.1 from a Firepower Threat Defense device, the device experiences a disruption in traffic. Make sure you deploy configurations after you uninstall. (CSCva10906)
• The Firepower Management Center web interface incorrectly offers Sourcefire support. Sourcefire support has been discontinued. (CSCva29671)
• Manually typing in a page number in the pagination field on the Intrusion Rules page ( Policies > Access control > Intrusion > Rules) other than the page being viewed does not redirect you to the page you typed in. (CSCva35026)
• You cannot edit the default system policy on the Device page ( Configuration > ASA FirePOWER Configuration > Device Management > Device) of an ASA 5500-X series device managed by ASDM. As a workaround, edit the local System Policy page ( Configuration > ASA FirePOWER Configuration > Local > System Policy) and redeploy. (CSCva4580)
• In some cases, if you deploy an access control policy with logging to an SNMP server enabled to a Firepower Threat Defense virtual device running AWS, SNMP traps are not generated for connection or intrusion events when they should. (CSCva46557)
• In some cases, if you configure a DHCP interface with a pool of IP addresses in the DHCP tab on the Device Management page ( Devices > Device Management) of a registered Firepower Threat Defense and deploy, then delete the DHCP configuration from the DHCP tab and add a new interface set to any interface type except None in the Interfaces tab, redeploying configuration fails. As a workaround, save and deploy after removing the DHCP configuration, then add a new interface and redeploy. (CSCva47372)
• In some cases, if you add a managed device to a third level domain and deploy an access control policy, the Domains page ( System > Domains) displays None for the access control policy even though the device was successfully added. As a workaround, navigate to the Policies page and then navigate back to the Device Management page ( Devices > Device Management). (CSCva47744)
• If you add a scheduling task from the Scheduling page ( Configuration > Tools > Scheduling) of a ASA FirePOWER module managed by ASDM and expand the Job Type drop-down menu more than once, the drop-down menu is dimmed and you cannot select a job type for the scheduled task. (CSCva49386)
• If you deploy a pair of network object groups to a Firepower Threat Defense high availability pair and the network object group IP addresses on either the primary and secondary device overlaps with the IP addresses on the other device within the pair, deployment fails and the system generates a Deployment failed due to configuration error message in the Message Center. (CSCva51022)
• In some cases, if you break a Firepower Threat Defense high availability pair and remove the secondary device from the Firepower Management Center, then re-register the same Firepower Threat Defense device to the same Firepower Management Center, the web interface incorrectly reports device discovery took 40 minutes or more when device registration may take as little as 1.5 minutes. (CSCva51271)
• If you disable the Show Notifications option in the deployment tab of the Message Center, the system continues to display notifications. (CSCva51945)
• In some cases, backup and restore functionality does not work on managed 7000 Series devices. (CSCva56596)
• On a Firepower Threat Defense Virtual with RIP and redistribution configured, even if you disable RIP and redeploy, the device continues to use RIP. (CSCva57174)
• In some cases, if you Add Manager on the Remote Management tab of the Integration page ( System > Integration) and save, then delete the manage via the delete icon for the manager, the system incorrect generates an Error: Failed to delete message when the manager is deleted successfully. (CSCva61777)
• If you enable OSPF for the primary Firepower Threat Defense in a high availability configuration with multiple router IDs and deploy, then navigate to the global domain and view the Non Stop Forwarding tab of the Advanced routing window, you are able to check all the non stop forwarding check boxes when they should be non-configurable. (CSCva73299)
• In some cases, if you change the default action of an access control policy from Trust All Traffic to Block All Traffic, the system does not block ICMP traffic that was flowing before you made the change. New ICMP connections are blocked. (CSCva80187)
• If you enable border gateway protocol and enter a value for the AS Number field on the routing tab of the Device Management page ( Devices > Device Management) and deploy to a Firepower Threat Defense registered to a Firepower Management Center, then disable the border gateway protocol and redeploy, the system incorrectly generates an Invalid Values: Errors on the page, unable to navigate. Do you want to revert back the configuration? error message. Ignore the message and continue. (CSCva83773)
• If you deploy an access control rule with the action set to Interactive Block or Interactive Block with Reset and contains a shopping URL category condition, then browse to Amazon.com and click Continue to bypass the block page, the images on the website do not load when they should. (CSCvb03678)
• Importing or exporting more than 15 intrusion policies at a time may fail and display an Error 500. As a workaround, import and export intrusion policies in smaller batches. (CSCvb18570)
• If you deploy an access control policy and with an intrusion policy added from the Intrusion Policy used before Access Control rule is determined drop-down menu in the Advanced tab of the Access Control Policy page ( Policies > Access Control), the system does not execute the action of the intrusion policy unless the access control policy also contains a file policy. (CSCvb24280)
• If you place an access control rule configured to Allow a subdomain URL (site.example.com) above an access control rule configured to Block the domain URL (example.com), the system may block request to subdomain URL. As a workaround, create an access control to Allow each subdomain URL (site.example.com, site2.example.com, etc.) you do not want blocked instead of the rule to block the domain URL, then save and redeploy. (CSCvc59811)

For Assistance

Thank you for choosing the Firepower System.

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information about the Firepower System, see What’s New in Cisco Product Documentation at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.

Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.

If you have any questions or require assistance with the Firepower System, please contact Cisco Support:

• Visit the Cisco Support site at http://support.cisco.com/.
• Email Cisco Support at tac@cisco.com.
• Call Cisco Support at 1.408.526.7209 or 1.800.553.2447.

 Printed in the USA on recycled paper containing 10% postconsumer waste.