Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
I've scheduled a weekly backup on my FMC to run every Sunday at 8 PM and for some reason, it always fails with the message, "Failure: Remote storage is enabled but not mounted." If I run the backup manually, it will backup the appliance fine so I kn...
Recently Cisco/SourceFire released a bulletin about a cloud migration for our SourceFire AMP clients and that we would need to update some policies to ensure our clients can talk to Cisco's cloud servers. I deployed the updated policy to one of our t...
I have tested installing AnyConnect with Web Security using the installation script found in the AnyConnect deployment guide and successfully gotten it to work.When I installed the client, I enabled the flags to hide the uninstall under Add/Remove Pr...
I have this same issue except the "Would Have Dropped" events are only triggered on port scan detection rules 122. I worked with TAC for several months and case was eventually escalated to Cisco's BU. Cisco seems to think it's related to FirePower's ...
I converted my ACL from ASA to FTD. Just know that all rules imported from ASA will be put into the pre-filter policy. My best explanation is that pre-filter is more like traditional ASA policy where as Access Control Policy allows you to apply laye...
Don't upgrade to it yet. Go to 6.2.3.7 and stay at that version until Cisco gets the bugs fixed in 6.3. I've opened 3 cases since I upgraded to 6.3 and all issues were traced back to a bug or being investigated by the BU as a potential bug. I spoke t...
FTD version 6.2.2.2 was released Feb. 26th and contains many bug fixes, but I did not see this particular bug referenced in the release notes.
Although, this bug is worded sort of weird as the title references the 2100 series, "FP2100 FTD/ASA might...
I just posted a topic similar to this. SourceFire is in the process of updating their cloud servers to new IP's/Hostnames. Below is a list of the new IP's that AMP will be using.
23.23.197.169
23.23.198.191
23.23.224.83
50.16.244.193
52.0.55.209
52.2...
