- Products
- Learn
- Local User Groups
- Partners
-
More
Celebrate the New Year
With CheckMates!
Value of Security
Vendor Self-Awareness
Join Us for CPX 360
23-24 February 2021
Important certificate update to CloudGuard Controller, CME,
and Azure HA Security Gateways
How to Remediate Endpoint & VPN
Issues (in versions E81.10 or earlier)
Mobile Security
Buyer's Guide Out Now
Important! R80 and R80.10
End Of Support around the corner (May 2021)
Hi!
We did a clean install (upgrade) to R80.30 take 215 on our 23900 appliances (vsx with vsls) three weeks ago.
After two weeks we noticed that we were hit by the sk168513. There is a hotfix for it in take 219,
but that doesnt seem to work for VSX as mentioned in sk169352...
There is a workaround mentioned in sk168513 though:
fw ctl set int fwmultik_enable_increment_first 1
fw ctl set int fwmultik_enable_round_robin 1
Does anyone know if this workaround also is working and supported on VSX/vsls?
If yes: should it be enabled on the affected virtual-server or on vs0? (fwkern.conf)
Thx
Mattias
If I'm reading those two SK's correctly, you need a special hotfix for this issue under VSX that is separate from the hotfix added into R80.30 Jumbo HFA Take 219 for non-VSX gateways.
Yes, I agree with you about the hotfix.
Therefore my question if the workaround is working (and is supported) on VSX?
The workaround and (non Jumbo) hotfix are in seperate SKs hence address different problems.
Applying the below in the affected VS resolves the issue? Anybody tried it and the CPU come down?
fw ctl set int fwmultik_enable_increment_first 1
fw ctl set int fwmultik_enable_round_robin 1
We are facing the same issue after we upgraded the VSX cluster from R77.30 to R80.30 with the Take 219 HF
For VSX JHF T227 or above is needed.
We are running VSX and the issue was solved for us after installing take 219
I never tried the workaround.
About CheckMates
Learn Check Point
Advanced Learning
WELCOME TO THE FUTURE OF CYBER SECURITY