Cisco Cisco Firepower Management Center 2000
Firepower System Release Notes
Known Issues
39
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)
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)
(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)
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)
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.1:
In rare cases, the system experiences issues after deploying a network discovery policy with user discovery
enabled such as no event processing and network discovery, and generates a
enabled such as no event processing and network discovery, and generates a
The data correlator process
exited (x) times
error message. If the system suddenly stops processing events and generates a
The data
correlator process exited (x) times
error message, contact Support. (CSCuz15233, CSCuy60302)
In some cases, if you deploy an SSL policy to a device managed by an Firepower Management Center running
Version 6.0.0 and update the Firepower Management Center to Version 6.0.1.1, then redpeloy configuration
and the system experiences a high volume of traffic, the system experiences a disruption in traffic. As a
workaround, restart the system. (CSCuz19469)
Version 6.0.0 and update the Firepower Management Center to Version 6.0.1.1, then redpeloy configuration
and the system experiences a high volume of traffic, the system experiences a disruption in traffic. As a
workaround, restart the system. (CSCuz19469)
ASA FirePOWER devices managed by ASDM do not support the Windows 10 OS. (CSCuz42216)
In some cases, if you create a cluster of 8250 devices running Version 6.0.1.1, the Firepower Management
Center incorrectly displays a
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 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)
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)
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)
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)
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 device managed by ASDM, the system incorrectly
disables the selected server configured for SNMP and Syslog alerting even though the checkbox for the SNMP
and Syslog server remain checked. (CSCuz80854)
of an access control rule applied to an ASA Firepower device managed by ASDM, the system incorrectly
disables the selected server configured for SNMP and Syslog alerting even though the checkbox for the SNMP
and Syslog server remain checked. (CSCuz80854)