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.
This bug still isn't fixed after over two years although it's a simple GUI validation issue only.Please put this on the roadmap for the next patch release!Thanks!
Not sure if Cisco is monitoring this board, but I'm tired of opening a TAC for each bug I find in the APIs. On FMC 6.6.0 the any-ipv6 object has an incorrect type of 'Host' instead of 'Network' and is therefore returned by the GET hosts instead of th...
I've written a FMC REST API client module in Perl 5 which we use to cleanup access policies generated by the Cisco Firepower Migration Tool.It can be found at https://metacpan.org/pod/Net::Cisco::FMC::v1. It can be used from Perl 6 Raku as well using...
Both icmp and icmp error inspection is disabled in FTD 6.2, was enabled in 6.1.
This breaks e.g. ping through the FTD and isn't mentioned in the 6.2 release notes.
Is this a new bug caused by the addition of FlexConfig or deliberately changed, becaus...
Hi,
I didn't find any documentation how to restore a failed FTD, for example after a hardware RMA or a failed upgrade, as in my case.
I've already reimaged the FTD and want to re-register it with the FMC. It's part of a failover pair too in our case.
Hi @Manoj Papisetty,Thanks for your answer!Yes, I saw the wrong type in the GUI else I would have searched much longer to find it via the API.Was a bug id already assigned I can subscribe to?
The ASAs support it and you only need to add the CA certificates of the root CA to the ASA if your syslog server sends the complete intermediate certificate chain, if not all the CAs forming the certificate chain.'show logging' will show you four con...
If you read the updated release notes of 6.3.0 you will see that build 84 fixes an upgrade bug when the FMC has been installed with a pre 6.0 version. If the upgrade was successful for you, you don't need this build.
