Cisco Cisco Firepower Management Center 2000

Página de 52
Firepower System Release Notes
 
For Assistance
 
50
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 NAP policy with Max Detect 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 NAP policy 
with Max Detect 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 checkbox 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 device 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)
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: 
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:
http://support.cisco.com/
.
.
Call Cisco Support at 1.408.526.7209 or 1.800.553.2447.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To
view a list of Cisco trademarks, go to this URL:
. Third-party trademarks mentioned are the property
of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other
company. (1110R)