- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-20-2023 03:25 AM
Hi - I have a 5508 in my home lab with a firepower SFR - I recently upgraded it to version 7.0.4 - (had to do a re-image but thats another story
In the task manager I get Failed to validate configuration files as the reason.
I do see a bug with a similar issue point to the snort engine - but unable to resolve. I have tried a full reboot and all services appear to be up.
Any ideas are welcome..
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2023 05:08 AM
What versions of ASA and ASDM are you running? 9.16(x) with 7.16(X) would be recommended since ASA > 9.16 is not supported with Firepower service modules.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-20-2023 03:50 AM
How are you managing the SFR? If using FMC check the following:
Possibly an SRU mismatch? If you go to Updates > Rule Updates > Rule Update Log do you see any errors here?
Also, might be a good idea to check the Deployment History also.
Please remember to select a correct answer and rate helpful posts
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-20-2023 03:59 AM
Hi Marius,
I am using ASDM to manage the SFR
in the rule update the following:-
lsp-rel-20210503-2107 | Policies | Could not update LSP policies. |
I going to have a look as to why that failed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2023 05:08 AM
What versions of ASA and ASDM are you running? 9.16(x) with 7.16(X) would be recommended since ASA > 9.16 is not supported with Firepower service modules.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2023 06:51 AM
Hi Marvin, many thanks it was a version issue - I had change to version 6.6.7 to resolve the issue
