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.
Hello!I'm trying to automate my FMC deployment to be able to add rules with some ease, been looking at https://github.com/CiscoDevNet/FMCAnsible and their examples but I'm stuck when trying to add a firewall rule with a port number.
I've got as far a...
Hi!We recently setup a new deployment with ISE 3.1 Patch 3. Our old setup is still up and running with ISE 2.7.We took the backup from the 2.7 deployment and deployed into the 3.1 setup. Everything seemed fine at first glance.The plan was to switchov...
Hey! We're currenty running ISE 2.2 Patch 11 in a distrubuted deployment and looking to go and upgrade to 2.6 however I'm a bit worried something will stop working even though we only do wired and wireless AAA. Is it possible to backup the distribute...
Hey! FXOS: 2.2 and 2.3FTD: 6.2.2 build 81FMC: 6.2.3 build 84. Looking to upgrade our 4100 setup. We're looking to go up to 6.4.0.7As far as I understand you should do the upgrade in the following steps FMC--> FXOS --> FTD?Is it possible to go from FT...
Hi!
I'm having problem registration the smartnet collector with a trial version.
I'm getting the following error message "Failed to download registration file from Cisco Backend. Please try again." after entering my CCO credentials.
I've checked ...
Opened a TAC case and it seems that 3.1 using a diffrent SSL library/version. In patch 4 which should arrive in October you're able to choose the diffrent ciphers ISE will use to negogiate with the client so you can disable the RSA PSS which causes t...
Hey Justin, Thanks for the info. Do you have any new information regarding this? It seems like you're only able to download the 2.7.x version from cisco now?
Hi
It's working however same issue when trying to register the collector with any service (trial) "Failed to download registration file from Cisco Backend. Please try again."
# wget https://72.163.7.113/HeadEndWebAppServlet/ --no-check-certificate ...