ā05-29-2024 09:26 AM
Do we have any progess on this bug? This is affecting our 12K users and we dont have workaround. we also tried the revert but it seems taht the configuration file exported before the rollback is corrupted, so, we are stucked.
many thaks,
Jacir
ā05-29-2024 10:06 AM
- Best is to query TAC ,
M.
ā05-29-2024 11:49 AM
Sure there is no work around so far that issue.
You have 2 options depends on the device Physical or virtual - depends on how many WSA you have - TAC help you get the configuration role back.
1. If the virtual easy to build new VM with version 14.X and build new rule and move from 15 to 14 for stability.
2. you can kick command every week that reduce the CPU load for week.
3. you can automated kick every week using advancedconfig --> mis option
ā05-29-2024 11:55 AM
Hello,
we have about two week to be trying to do the rollback from 15 to 14 and it doesnāt work at all. And about the kick command we are doing so every hour, at the begin we started every 4 hours but it was not enough so, now we kick the proxy process every hour.
ā05-29-2024 12:07 PM - edited ā05-29-2024 12:08 PM
Not sure how many WSA you have - if you have open TAC case engage with them for the options i am sure they can suggest you.
Also check which rules are main hitters - try to offload until this resolved like MS URLS
ā05-29-2024 12:23 PM
Currently we have 15 WSA. We already have a case on the TAC but as I told before they are trying to make work the rollback but until now we have a lot of errors when inmporting the config file.
Jacir
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide