- CheckMates
- :
- Products
- :
- General Topics
- :
- R81.20 feedback
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
R81.20 feedback
Hey guys,
Figured would share my feedback so far on brand new distributed install of R81.20 in esxi lab. I really do like zero phishing feature, though for that to work, https inspection has to be on, so may try that out some time this week.
In all honesty, I dont see any drastic changes from R81.10 as far as policy layout, log filtering, IPS...
Also, not sure if this is just my lab, but I made few rule changes and for some reason, accelerated policy push never takes an effect, though its not disabled.
Just my 100% honest feedback, looks good so far, but the real test would be to see it in busy production environment.
Anyway, thats all I can think of for now. Will add more things as I do more testing : - )
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Not sure if this has come up anywhere else before but I just experienced sk105441 in a VSX GW upgrade from R81.10 to R81.20.
I ended up doing the debug and then the 'vsx_util reconfigure' ran without failing:
fw debug fwm on TDERROR_ALL_VSXM_DBG_SKIP_RECONF_VERIFY=INFO
The vsx_util reconfigure failed and the .elg had the line:
"
**** Error: Interface 'eth1' exists in the management database, but not on the gateway.
"
The interface existed and had not been changed.
eth1 exists
The SK is inaccurate in my view because it states:
"
This problem was fixed. The fix is included in:
"
Left feedback on the SK
End of report 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I can take a look if you have a lab with the issue. You can contact me via Teams\E-mail.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Erez,
It was exactly as per the SK (the error message) and simply running the fwm debug, as per the SK, allowed the 'vsx_util reconfigure' command to complete successfully.
It was a clean build R81.10 VSX GW that got an R81.20 upgrade (CPUSE). On a Hyper-V platform.
If I do it again in the lab and it happens again then I will let you know and give you access to the lab.
Thanks,
Don
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I actually had exact same issue as well, so definitely not just you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hyper-V 2022 or another version out of interest?
https://www.checkpoint.com/support-services/hcl/

- « Previous
- Next »