- Products
- Learn
- Local User Groups
- Partners
- More
Access Control and Threat Prevention Best Practices
5 November @ 5pm CET / 11am ET
Ask Check Point Threat Intelligence Anything!
October 28th, 9am ET / 3pm CET
Check Point Named Leader
2025 Gartner® Magic Quadrant™ for Hybrid Mesh Firewall
HTTPS Inspection
Help us to understand your needs better
CheckMates Go:
Spark Management Portal and More!
Hello,
I am trying to activate one of my Threat Prevention Blades "Anti-Virus" and I am getting this error on my VSX Env FPVSX12 on (Cluster) FPVSX01.
Well i found out that this issue by all my VSX, the one thing that we did was upgrading the management to R82 and VSX is on R81.20.
Any idea what could this be?
PS: All Interfaces under Typology are assigned and there are no problems there!
Checking connection with VSX
Generating VSX Configuration for FPVSX12 on FPVSX01.
Pushing VSX Configuration to FPVSX01.
FPVSX01: processed 33% of configuration...
Failed to configure FPVSX01 with the following errors:
FPVSX01...: VSX configuration was applied successfully.
Virtual System Processing Completed with Errors
Pushing network configuration to Virtual System operation has finished with errors.
Refer to the messages retrieved during the VSX push configuration stage
and make sure that the configuration you are trying to push is legal.
If the problem persists contact Check Point Technical Support.
Operation has failed.
So we had this issue on all our MDS upgrades to R82 HFA39
More or less its enough to.
- Push policy to the VSX cluster (VS0)
- Open up a VS and just press OK on it for it to do the communication to without any changes what so ever.
- Install policy on the VS.
And after that its back to normal, and i experience the same on 7 MDS with 15+ VSX clusters 😉
Regards,
magnus
I recall seeing this while back and turned out to be license problem.
Andy
If the license is okay, see if below sk helps.
Best,
Andy
https://support.checkpoint.com/results/sk/sk108138
Thnx, but i already checked both. I have the license and all interfaces are assigned and have names,ips !
So you are saying sk is not applicable in your situation?
Andy
Exactly, cuz i have the IPS active and there is no issue
Let me see if I can reproduce this in the lab and will update you. Did you check with TAC yet?
Best,
Andy
Well i found out that this issue by all my VSX, the one thing that we did was upgrading the management to R82 last week. This is the only relative thing that happened lately
To me, does not sound like that would have caused the issue, but I could be mistaken. If you are saying all works with IPS blade, then certainly would make sense its strictly anti virus related. If you uncheck av blade, then all is good?
Andy
Does issue go away if you uncheck the blade?
Hey,
Just tried this in brand new R82 lab, no errors for me. So, that logically tells me there must be something in your environment causing this...cant say 100% if its strictly AV blade related, but might be worth checking with TAC to confirm.
Andy
So we had this issue on all our MDS upgrades to R82 HFA39
More or less its enough to.
- Push policy to the VSX cluster (VS0)
- Open up a VS and just press OK on it for it to do the communication to without any changes what so ever.
- Install policy on the VS.
And after that its back to normal, and i experience the same on 7 MDS with 15+ VSX clusters 😉
Regards,
magnus
Hi Magnus,
Thank you! This fixed my issue.
Tim
np 🙂
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
User | Count |
---|---|
25 | |
13 | |
9 | |
9 | |
7 | |
7 | |
6 | |
6 | |
4 | |
4 |
Wed 22 Oct 2025 @ 11:00 AM (EDT)
Firewall Uptime, Reimagined: How AIOps Simplifies Operations and Prevents OutagesWed 22 Oct 2025 @ 11:00 AM (EDT)
Firewall Uptime, Reimagined: How AIOps Simplifies Operations and Prevents OutagesTue 28 Oct 2025 @ 11:00 AM (EDT)
Under the Hood: CloudGuard Network Security for Google Cloud Network Security Integration - OverviewAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY