Cisco Cisco FirePOWER Appliance 7115
Version 5.3.0.6
Sourcefire 3D System Release Notes
36
Known Issues
•
In some cases, Lights Out Management (LOM) appears to be disabled on
the LOM page (System > Local > Configuration > Console Configuration >
Lights Out Management) even if it is not. If you are unsure what the LOM
status is, use the
ipmitool
command in expert shell mode to enable or
disable LOM. (CSCus10996)
•
In some cases, managed devices stop processing traffic when the Defense
Center updates a large security intelligence feed referenced in an access
control policy during a policy apply. As a workaround, reapply the policies
containing security intelligence feeds. (CSCus19921)
•
Running troubleshooting on your system may cause latency. (CSCus19876)
•
In some cases, licenses that expired prior to registering a device to your
Defense Center are not available on the registered device and the device is
unable to generate intrusion events. As a workaround, re-register the
device. (CSCus22402)
•
In some cases, the system does not clear all intrusion policy locks when you
upload intrusion rules or install SRUs. (CSCus29526)
•
In some cases, if you attempt to edit the cost setting in the Interfaces page
(Device Manager > Virtual Routers > Edit > Dynamic Routing > OSPF Areas > Edit
> Interfaces) on a device with a virtual router, the system does not configure
the value correctly. (CSCus31735)
•
The User Agent will submit the error
Unable to determine user
@[address]. Check network and firewall settings
when it should be
a warning. (CSCus47368)
•
In some cases, if you include special characters in the password for your
registered ASA FirePOWER device, the system generates an
Internal
Server Error
message. (CSCus68604)
•
In some cases, if your system includes an SSL Visibility Appliance (SSLVA)
device and you create a file policy containing a Web Application category
and a Block Malware rule, your first attempt to download a file identified as
and a Block Malware rule, your first attempt to download a file identified as
malware over HTTPS may fail. As a workaround, disable the file policy.
(CSCus72505)
•
In some cases, if you create a custom user role, the system may not enable
some checkboxes but the options available under the disabled checkboxes
are enabled. (CSCus87248)
•
If you create an intrusion policy containing more than one shared layer, the
system automatically creates an Event View Override Layer for each shared
layer, names the Event View Override Layers with duplicate names, and
may experience system issues. As a workaround, edit the intrusion policies
with multiple shared layers and manually change the name of the
automatically generated override layers. (CSCut16772)