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.
**bleep**, what a mess. Tried to migrate a 600+ rules access policy (no NAT, ...) from Palo Alto to Firepower FMC 6.7.0.1. Already lost 2 days. I better start doing it manually. Last errormessage:Migration Unsuccessful!Error while pushing access rule...
Anyone who knows what's inside the latest Firepower 6.7.0.1 patch?I cannot find any release notes. Install went fine on my FMC lab environment. So that's looking good so far.
Dear all,
Currently deploying a smart licensing satellite server (version 4.2) in a greenfield environment. The satellite has some very poor performance. The WebUI is not responsive, the popups for initial configuration only appears after multiple ...
Hi all,
I'm reimaging a bunch of FP4110 appliances. They were shipped with a very old version of FXOS and upgrading them (with intermediate steps) just would take too much time.
So, I started with the section 'Recovering from a corrupted filessystem...
Missing for 2 days, but here they are... https://www.cisco.com/c/en/us/td/docs/security/firepower/670/67xx/relnotes/firepower-release-notes-67xx.html
Hello,
A bit late, but maybe it's useful for another engineer.
I had the same problem (FP4110 FXOS 2.2-66 running Smart Agent 1.6 and Satellite 4.2) and solved it as described below:
1) Make sure DNS and NTP are OK.
2) If you renamed your FXOS chassi...
Hello Marvin,
Using the tools you mentioned, I was able to see there is load on the 2 'unused' cores. However, the load is low (<1%) and therefore, not visible on the graphs in FMC.
Thanks!
Hello Marvin,
Thank you for your assistance! I'll verify the cores with the tools you provided. If it seems not to be a cosmetical issue, I'll log a TAC case.
Br,
Ruben
Hi all,
The problem is solved. Despite the fact I didn't setup ACL's for SSH and HTTPS during the initial wizard, all access through HTTPS/SSH was blocked. You can easily solve it by configuring ACL's afterwards....
See page 74 of the config guide:
F...