Cisco Cisco FirePOWER Appliance 8290

Página de 47
Version 5.3.0.8
Sourcefire 3D System Release Notes
27
Known Issues
Resolved an issue where the system misplaced the home directory files for 
user accounts after updating to a major version of the Sourcefire 3D 
System. (132503)
Resolved an issue where disabling the Quoted-Printable Decoding Depth 
advanced option in your intrusion policy did not prevent the system from 
generating events on intrusion rule 124:11. (132538)
Resolved an issue where, if you configured a custom table populated with 
data from the Correlation Events table and the Applications table, then 
selected Source IP as a common field, updates to Version 5.3 failed. 
(135735)
Resolved an issue where, in some cases, if you configured an access 
control policy with a Monitor rule (which forces end-of-connection logging) 
and a Trust rule with Log at Beginning of Connection enabled, the system did 
not generate end-of-connection events for matching SSH-encrypted traffic. 
(135952)
Known Issues
The following known issues are reported in Version 5.3.0.8:
In some cases, if you create an intrusion rule set to block Multiprotocol 
Label Switching (MPLS) traffic and specify either a source IP address or a 
destination IP address, the system does not block matching traffic. 
(CSCur46880)
In some cases, if you configure an inline pair of interfaces on a virtual 
device, the 
show traffic-statistics
 CLI command does not display 
data for the second interface of the inline pair. (CSCur59771)
In some cases, if you create an LDAP object in the Microsoft Active 
Directory and add the LDAP object to a user policy, then move the LDAP 
object, the Defense Center cannot locate the LDAP object. As a 
workaround, remove the LDAP group containing the LDAP object from the 
Users Policy page (Policies > Users) and Fetch Groups from the Defense 
Center, then add the group and recreate the LDAP object in the user policy. 
(CSCuu95350)
In some cases, if you create a health monitor email alert configured to 
generate an alert to more than one target, the system incorrectly sends 
alert emails to the configured targets intermittently. (CSCuv01314)
In some cases, executing the 
show power-supply-status
 CLI command 
on a 3D7110 or 3D7120 device incorrectly returns with Connected to power 
source even when it is not. (CSCuy01688)
In some cases, if you click the Email Status to: link on the Scheduling page 
(System > Tools > Scheduling), the web browser displays a 
500 Internal 
Server Error
 message. As a workaround, configure email notification on 
the system policy page. (CSCuv22590)