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.
Was looking for a way to find and remove unused objects in the FMC (6.2.2) like you could with ASAs in ASDM. Is there really no way to do this?
Every other day I find some annoying little thing about the FMC and FTDs...
Regards,
Keith
I'm in the midst of working with a VAR to replace 5510s with 2110s and it's just been 1 caveat after another with these devices; mainly VPN. Then today, I received a Cisco software update notification for the 2110s with ASA code 9.8(2) listed. I deci...
Hello all, As I've previously posted, we are moving away from a pair of active/standby ASA 5510s both here in our corporate DC and at our colo. The way DR works for us is if we have a disaster here, everything would be recovered at the colo using bac...
Hello all, We purchased the new Firepower 2110s and I'm working on converting the configs on our ASA 5510s running on 9.0(4) to the FTD platform. Something I've noticed for one of our use-cases is that I can not specify multiple (2) peers for a speci...
Hello all,I would like to create custom reports using the Report Designer (Reports -> Report Designer -> Syslog) and filter certain syslogs from being seen when I run the report like permitted ACL entries, 802.1x successful authentications. It seems ...
The first vulnerability on the list could be mitigated by enforcing a user lockout if this is a local management user:
If it's through LDAP, then the lockout policy would need to be configured there.
Cisco released a HF for this on October 20th. I applied it this morning and everything seems to be fine now.
Cisco_FTD_SSP_FP2K_Hotfix_D-6.2.2.1-2.sh.REL.tar
Regards,
Keith
Seems to have happened to me as well. Primary was the active box and now it is the secondary with nothing else appearing to fail. Cosmetic bug is not cosmetic if it causes changes in your environment!
