- Products
- Learn
- Local User Groups
- Partners
- More
MVP 2026: Submissions
Are Now Open!
What's New in R82.10?
Watch NowOverlap in Security Validation
Help us to understand your needs better
CheckMates Go:
Maestro Madness
Hi All,
VSX environment:
I wanted to upgrade our VSXHA cluster to recommended R81 version and an issue arose at the very first step 🙂
vsx_util tool on MGMT server failed to upgrade VS's configuration to wanted R81 version.
It failed at upgrading virtual router step. Final vsx_util upgrade result is - Policy compilation failed. Upgrade operaton (before this error) in first two steps, previously finished successfully (for another virtual devices (virtual firewall and for VS0/VSX context)).
In vsx_util upgrade log there were errors for one virtual device - virtual router:
The problematic output part is:
firewall_application Policy installation/compilation for External_vRouter: Invalid installation target received. Target gateway External_vRouter is not in the specific targets list for policy package Cluster_VSX_polisa( message from member VSX_FW2_External_vRouter ) firewall_application Policy installation/compilation for External_vRouter: Policy verification failed.( message from member VSX_FW2_External_vRouter ) firewall_application Policy installation/compilation for External_vRouter: Invalid installation target received. Target gateway External_vRouter is not in the specific targets list for policy package Cluster_VSX_polisa( message from member VSX_FW1_External_vRouter ) firewall_application Policy installation/compilation for External_vRouter: Policy verification failed.( message from member VSX_FW1_External_vRouter ) **** Policy compilation failed ---- Finished upgrade operation. ---- Regenerating VSs ---- Finished VSs regeneration. Database saved successfully. ===================== SUMMARY ===================== **** Upgrade operation finished with errors. **** Please resolve errors above. **** NOTE: If gateway/cluster member was upgraded using clean installation, run 'vsx_util upgrade' again in order to complete the operation. VS name: External_vRouter Errors: firewall_application Policy installation/compilation for External_vRouter: Invalid installation target received. Target gateway External_vRouter is not in the specific targets list for policy package Cluster_VSX_polisa( message from member VSX_FW2_External_vRouter ) firewall_application Policy installation/compilation for External_vRouter: Policy verification failed.( message from member VSX_FW2_External_vRouter ) firewall_application Policy installation/compilation for External_vRouter: Invalid installation target received. Target gateway External_vRouter is not in the specific targets list for policy package Cluster_VSX_polisa( message from member VSX_FW1_External_vRouter ) firewall_application Policy installation/compilation for External_vRouter: Policy verification failed.( message from member VSX_FW1_External_vRouter ) Logging details are available at /opt/CPsuite-R81.10/fw1/log/vsx_util_20210922_23_35.elg |
After failed vsx_util upgrade operation, status of GW/VS objects in Smart Dashboard was as in following picture:
It is strange that virtual route object was on new R81 version, even though virtual router was complying - policy compilation failed error log. This does not match with error log messages. Only VSX (VS0) context was on old R80.30 version.
I checked policy installation target colomn in Smart dash and it seems like Okay:
This part from logs - messages from VSX_FW1_External_vRouter and VSX_FW1_External_vRouter is not understandable. We do not have these object names defined in smart dash, for non of the GW's/objects under Gateways and Servers tab.
MGMT server is reverted from snapshot to state as was before vsx_util operation problems, and is working with defined objects as follows:
All policies are installed and all setup is AS-Before.
Any thoughts are welcome 🙂
Milos
Contact TAC to resolve this.
I already opened SR 6-0002989518
i had same problem upgrading VSX from R80.30 to R81.
vsx_util upgrade on mgmt finished correctly, but not all the virtual devices changed version...few remained R80.30 and i could not install policy on them.
Solution is changing version through guidbedit, doing a connection between mgmt and vsx changing something (ex. i enabled a blade and then disabled it), reinstalling policy, and it worked fine.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 12 | |
| 10 | |
| 9 | |
| 8 | |
| 6 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 1 |
Tue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Thu 18 Dec 2025 @ 10:00 AM (CET)
Cloud Architect Series - Building a Hybrid Mesh Security Strategy across cloudsTue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Thu 18 Dec 2025 @ 10:00 AM (CET)
Cloud Architect Series - Building a Hybrid Mesh Security Strategy across cloudsAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY