Примечания к выпуску для Cisco Cisco Firepower Management Center 2000
Firepower System Release Notes
Known Issues
33
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)
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)
address, SSL inspection failed and the connection log displayed an incorrect SSL policy default action.
(CSCuv48689)
Improved file detection and blocking. (CSCuv59181)
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)
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.0.1:
In some cases, if you click Advanced in the Report Templates tab of the Reporting page (Overview >
Reporting > Report Templates) and enter a non-numeric value in the Device or Number fields, the system
does not generate an error when it should. (CSCux08842)
Reporting > Report Templates) and enter a non-numeric value in the Device or Number fields, the system
does not generate an error when it should. (CSCux08842)
In some cases, if you create an access control rule and set an HTTP response page for the rule action Block
or Block with Reset, the HTTP response page does not load a web browser on a computer running Windows
OS. (CSCux58068, CSCux76910)
or Block with Reset, the HTTP response page does not load a web browser on a computer running Windows
OS. (CSCux58068, CSCux76910)
In some cases, if you modify the device tab of the Device Management page (Devices > Device
Management), the system incorrectly displays an extraneous
Management), the system incorrectly displays an extraneous
You have unapplied changes
message.
(CSCux64275)
In some cases, if you deploy an access control policy with the default action set to Block and execute the
configure network management-interface disable-event-channel
CLI command, the system continues to
generate intrusion and connection events when it should not. (CSCux64898)
In some cases, if you attempt to log into the system with the incorrect password, the system incorrectly locks
you out of the system after two attempts instead of three attempts. (CSCux65770)
you out of the system after two attempts instead of three attempts. (CSCux65770)
If you execute the
debug pix acl
CLI command, the output data does not include whether debug mode is
enabled or not when it should. (CSCux68019)