Cisco Cisco Firepower Management Center 2000 Release Notes

Version 5.3

Sourcefire 3D System Release Notes

28

Known Issues

In rare cases, configuring an intrusion policy that contains local intrusion 

rules in a layer that is shared with another intrusion policy may cause 

intrusion policy exports to fail. As a workaround, create a backup copy of 

each shared layer and remove the shared layers from the intrusion policies 

before exporting. After the export finishes, re-add the shared layers to the 

intrusion policies. (132312)

In some cases, large system backups may fail if disk space usage exceeds 

the disk space threshold before the system begins pruning. (132501)

In rare cases, Snort may stop processing packets if any of your intrusion 

policy rules contain the sensitive data rule classification. (132600)

In some cases, using the RunQuery tool to execute 

a SHOW TABLES 

command may cause the query to fail. To avoid query failure, only run this 

query interactively using the RunQuery application. (132685)

If you reboot a Series 3 managed device after a Sourcefire 3D System 

update fails, subsequent updates may fail even after you resolve the original 

issue. (132700)

If you delete a previously-imported local intrusion rule, you cannot re-import 

the deleted rule. (132865)

In rare cases, the system may not generate events for intrusion rules 141:7 

or 142:7. (132973)

In rare cases, Snort drains system resources if you create and apply an 

access control policy with rules that specify an unusually large range of 

ports and contain other rule conditions that would cause the Defense 

Center to send them to the device in expanded form. (132998)

In some cases, remote backups of managed devices include extraneous 

unified files, generating large backup files on your Defense Center. (133040)

The Security Intelligence page of your access control policy cannot display 

more than 100 available security zones. (133418)

In some cases, configuring a proxy server to authenticate with Message 

Digest 5 (MD5) authentication causes communication issues with the 

Defense Center. As a workaround, configure basic or NLTM authentication. 

(133727, 135041, 135076)

You must edit the maximum transmission unit (MTU) on a managed device 

using the appliance’s CLI or shell. You cannot edit the MTU on a managed 

device via the user interface. (133802)

If you use the command line interface (CLI) to register a Series 3 or virtual 

managed device to a Defense Center in a high availability configuration, 

device registration fails for the second Defense Center. As a workaround, 

run the 

add_manager.pl

 script from the managed device's shell to register 

it to the Defense Center. (133825)